Re: fsck to fix HD problem
On Wed, 25 Jul 2007 07:50:38 +0200 Zbigniew Szalbot <[EMAIL PROTECTED]> wrote: > > Hello, > > >> so I decided to use fsck to check my HD. I ran it > >> in the foreground mode with the -y flag. It gives me the below > >> information. My question is - should I worry (it is more a home > >> machine than a real server) and if yes, how can I fix the problem? > > . . . > > > > To do anything more than merely report problems > > you should drop into single-user mode, unmount > > everything except root (hopefully. If it gets angry, > > reboot into single-user mode.) and run fsck (as is > > or with the -y flag if you feel daring.) on the filesystems > > in question. > > Is the single-user mode necessary. As it is a family machine I know > when I am the only one using it. > The fsck output was the normal stuff you see if you pull-out the plug (if you're lucky). Did you check if the background fsck was still running? In practice you rarely need to do do a manual check - most reboots can be handled by a background check, and most cases where it can't are spotted during the initial foreground check and done in the foreground. Just watch the console for unexpected softupdate inconsistencies. If you run fsck with -y, you might as well set "fsck_y_enable=yes" in rc.conf and have it done automatically if the initial preen fails. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fsck to fix HD problem
On Wed, 25 Jul 2007 07:27:27 +0200 Zbigniew Szalbot <[EMAIL PROTECTED]> wrote: > I got a Charlie report: > +WARNING: / was not properly dismounted > +WARNING: /var was not properly dismounted > +/var: mount pending error: blocks 8200 files 43 > +/usr: mount pending error: blocks 4552 files 6 'mount pending error' is what you get as background fsck gets busy with cleaning up filesystems improperly dismounted, ie dirty. If you check /var/log/messages for after that boot you'll likely see 'DEFER' messages then background fsck listing any corrections and finishing, probably ok. > so I decided to use fsck to check my HD. I ran it > in the foreground mode with the -y flag. It gives me the below > information. My question is - should I worry (it is more a home machine > than a real server) and if yes, how can I fix the problem? If you'd shown the lines just before what you pasted, they probably would have looked like, apart from your slice numbering: ** /dev/ad0s2d (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity Notice (NO WRITE). As others pointed out, fsck won't write to a mounted filesystem; running 'fsck -y /var' is then the same as 'fsck -n /var' You can run 'fsck -n' anytime you like, even as a non-root user, and see what would show up if you (again) lost power right now without a clean shutdown. Here's the rest of mine, run just now .. pretty similar to yours below, noting that the file mtimes are as of my last boot .. ** Phase 4 - Check Reference Counts UNREF FILE I=18 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 3 23:28 2007 CLEAR? no UNREF FILE I=24 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 3 23:28 2007 CLEAR? no UNREF FILE I=39 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 3 23:28 2007 CLEAR? no UNREF FILE I=25246 OWNER=root MODE=140666 SIZE=0 MTIME=Jul 3 23:28 2007 CLEAR? no ** Phase 5 - Check Cyl groups SUMMARY BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no 2347 files, 56617 used, 70481 free (609 frags, 8734 blocks, 0.5% fragmentation) > ** Phase 4 - Check Reference Counts > UNREF FILE I=133267 OWNER=root MODE=140666 > SIZE=0 MTIME=Jul 24 07:54 2007 > CLEAR? no > > UNREF FILE I=235892 OWNER=mysql MODE=100600 > SIZE=0 MTIME=Jul 24 16:43 2007 > CLEAR? no > > UNREF FILE I=235894 OWNER=mysql MODE=100600 > SIZE=0 MTIME=Jul 24 16:43 2007 > CLEAR? no > > UNREF FILE I=235929 OWNER=mysql MODE=100600 > SIZE=0 MTIME=Jul 24 16:43 2007 > CLEAR? no > > UNREF FILE I=235932 OWNER=mysql MODE=100600 > SIZE=0 MTIME=Jul 24 16:43 2007 > CLEAR? no > > UNREF FILE I=235933 OWNER=mysql MODE=100600 > SIZE=0 MTIME=Jul 24 16:43 2007 > CLEAR? no > > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLK > SALVAGE? no > > SUMMARY INFORMATION BAD > SALVAGE? no > > BLK(S) MISSING IN BIT MAPS > SALVAGE? no > > 53119 files, 473457 used, 617845 free (10557 frags, 75911 blocks, 1.0% > fragmentation) If in doubt, drop to single user, umount /var and fsck it .. but you're probably in good shape; the sort of inconsistencies shown above are to be entirely expected whenever running fsck (-n) on a mounted fs. Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fsck to fix HD problem
On 25/07/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote: One little question - when I drop into single-user mode, do I need to mount /usr and /var? Is mount -a OK? Generally, no. Or mount read-only, if you must. When doing ugly repairs, fsck would prefer to not have the filesystem changing under it. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fsck to fix HD problem
On 25/07/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote: Hello, >> so I decided to use fsck to check my HD. I ran it >> in the foreground mode with the -y flag. It gives me the below >> information. My question is - should I worry (it is more a home machine >> than a real server) and if yes, how can I fix the problem? > . . . > > To do anything more than merely report problems > you should drop into single-user mode, unmount > everything except root (hopefully. If it gets angry, > reboot into single-user mode.) and run fsck (as is > or with the -y flag if you feel daring.) on the filesystems > in question. Is the single-user mode necessary. As it is a family machine I know when I am the only one using it. Well, fsck-ing /var on a fully multiuser system is hairy, at best, since /var is almost always being written to by something or other. Single user mode is the simplest way of dealing with this, since none of the logging, mail, or one of any of a 10^4 daemons will be trying to write to it, while you're trying to fix it. With mysql, I would assume* many of the same problems with /usr (or /usr/local, if that is its own filesystem). *given that I know meow-all about mysql: where it may wish to write, or what horrible perversions it commits while running. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fsck to fix HD problem
Hello, >> so I decided to use fsck to check my HD. I ran it >> in the foreground mode with the -y flag. It gives me the below >> information. My question is - should I worry (it is more a home machine >> than a real server) and if yes, how can I fix the problem? > . . . > > To do anything more than merely report problems > you should drop into single-user mode, unmount > everything except root (hopefully. If it gets angry, > reboot into single-user mode.) and run fsck (as is > or with the -y flag if you feel daring.) on the filesystems > in question. Is the single-user mode necessary. As it is a family machine I know when I am the only one using it. > > As an aside, you might want to figure out why your > machine fell over, so as to possibly avoid this in > the future (such as it is). Lack of UPS and sudden power outage. Thank you! -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fsck to fix HD problem
On 25/07/07, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote: Hello, I got a Charlie report: +WARNING: / was not properly dismounted +WARNING: /var was not properly dismounted +/var: mount pending error: blocks 8200 files 43 +/usr: mount pending error: blocks 4552 files 6 so I decided to use fsck to check my HD. I ran it in the foreground mode with the -y flag. It gives me the below information. My question is - should I worry (it is more a home machine than a real server) and if yes, how can I fix the problem? . . . To do anything more than merely report problems you should drop into single-user mode, unmount everything except root (hopefully. If it gets angry, reboot into single-user mode.) and run fsck (as is or with the -y flag if you feel daring.) on the filesystems in question. As an aside, you might want to figure out why your machine fell over, so as to possibly avoid this in the future (such as it is). -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fsck to fix HD problem
Hello, I got a Charlie report: +WARNING: / was not properly dismounted +WARNING: /var was not properly dismounted +/var: mount pending error: blocks 8200 files 43 +/usr: mount pending error: blocks 4552 files 6 so I decided to use fsck to check my HD. I ran it in the foreground mode with the -y flag. It gives me the below information. My question is - should I worry (it is more a home machine than a real server) and if yes, how can I fix the problem? ** Phase 4 - Check Reference Counts UNREF FILE I=133267 OWNER=root MODE=140666 SIZE=0 MTIME=Jul 24 07:54 2007 CLEAR? no UNREF FILE I=235892 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 24 16:43 2007 CLEAR? no UNREF FILE I=235894 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 24 16:43 2007 CLEAR? no UNREF FILE I=235929 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 24 16:43 2007 CLEAR? no UNREF FILE I=235932 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 24 16:43 2007 CLEAR? no UNREF FILE I=235933 OWNER=mysql MODE=100600 SIZE=0 MTIME=Jul 24 16:43 2007 CLEAR? no ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no 53119 files, 473457 used, 617845 free (10557 frags, 75911 blocks, 1.0% fragmentation) Thank you in advance! -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
