| View previous topic :: View next topic |
| Author |
Message |
Gb
Joined: 04 Aug 2007
Posts: 8
|
 Posted: Sat Aug 04, 2007 11:52 am Post subject: fsck doesn't automatically check filesystems at boot |
 |
|
Hi everyone! 
I have just signed onto the Lunar linux Forum.
I am running lunar with kernel 2.6.22.1 and I have this problem:
when lunar boots up and my filesystems reach maximal mount count,
I get warning messages at bootup (warning, maximal mount count reached),
but fsck doesn't kick in and check them automatically.
What I have always done is rebooting with the lunar CD and checking the filesystems manually while they are unmounted.
I checked my fstab file, and it seems to be ok (the last field is fine according to man fstab):
| Quote: | # /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
# proc is required pretty much on any linux system except embedded systems:
proc /proc proc defaults 0 0
# shmfs is surpassed and obsolete
#shm /dev/shm shm defaults 0 0
# devfs and devpts are not friends, yet 2.6 needs devpts:
devpts /dev/pts devpts defaults 0 0
# usb devfs can be helpfull on interactive (desktop) machines
usbfs /proc/bus/usb usbfs defaults 0 0
# /tmp should be wiped on boot so by default it helps to have it on tmpfs
#tmpfs /tmp tmpfs defaults,size=256m,nr_inodes=64m 0 0
# /var/lock and /var/run need to be clean on reboot:
tmpfs /var/lock tmpfs size=4m 0 0
tmpfs /var/run tmpfs size=4m 0 0
# /var/tmp should NOT be on tmpfs, LSB states that the contents of it must
# stay intact on reboot
#tmpfs /var/tmp tmpfs size=32m 0 0
/dev/md1 / ext3 defaults 0 1
/dev/md0 /boot ext3 defaults 0 2
/dev/md7 /home ext3 defaults 0 2
/dev/md2 none swap sw 0 0
/dev/md4 /tmp ext3 defaults 0 2
/dev/md6 /usr ext3 defaults 0 2
/dev/md5 /var ext3 defaults 0 2 |
Should I change some other config file?
Help welcome.
Thank you,
Gb |
|
| Back to top |
|
 |
sofar
Joined: 11 Aug 2005
Posts: 172
|
| Posted: Fri Sep 14, 2007 7:23 am Post subject: |
|
|
try `lin lunar-init` and follow the instructions, then reboot.
CAREFULLY READ AND FIX ANY MESSAGES!!! REPEAT THIS COMMAND UNTIL IT STOPS WARNING!!! |
|
| Back to top |
|
|
Gb
Joined: 04 Aug 2007
Posts: 8
|
| Posted: Sun Sep 16, 2007 9:07 am Post subject: |
|
|
Done "lin lunar-init" successfully, no errors reported.
Had no effect.
Recently (starting from two weeks ago)
it seems that unclean filesystems are no more reported during boot.
fsck'ing from CD shows that they did actually need a check, however.
I will monitor this issue and see if "lin lunar-init" has changed things.
I will report back here later (I fsck'ed all filesystems today, so I need to wait a while to get some of them unclean again).
Thanks,
Gb |
|
| Back to top |
|
|
engelsman
Joined: 21 Aug 2005
Posts: 131
Location: Netherlands
|
| Posted: Sun Sep 16, 2007 12:18 pm Post subject: |
|
|
A long time ago, I also had problems with fsck not being called when I expected, and
someone suggested that I create /forcefsck to get it to run. man fsck doesn't mention
this trick but I see that the K99mount and S10mount scripts in /etc/rc.d/* do.
Don't know whether this helps you with your problem though... |
|
| Back to top |
|
|
Gb
Joined: 04 Aug 2007
Posts: 8
|
| Posted: Sun Sep 23, 2007 6:40 pm Post subject: |
|
|
Today I found out that one error is reported during boot.
It was there from the beginning,
so it passed totally under my radar.
During boot, it reports:
| Quote: | | /etc/rcS.d/S10mount: line 221: uniq: command not found |
Now, this is /etc/init.d/mount around line 221:
| Quote: | # or do we want to explicitly _not_ fsck at all
if ! grep -qw nofsck /proc/cmdline ; then
# force fsck run?
if [ -f /forcefsck ] || grep -qw forcefsck /proc/cmdline ; then
FORCE="-f"
fi
# check filesystems
(LINE 221) FSCKLEVELS=$(sed 's/#.*$//g' /etc/fstab | awk '($6>0){print$6}' | sort -n | uniq)
if [ -n "$FSCKLEVELS" ]; then
echo "Checking file systems:"
for FSCKLEVEL in $FSCKLEVELS; do
for FS in $(sed 's/#.*$//g' /etc/fstab | awk "(\$6==$FSCKLEVEL){print\$1}"); do
run_with_msg_and_exit_codes " * Checking $FS" "fsck -T -C -y -V $FORCE $FS" "0" "1" ""
|
uniq, however, is perfectly working (at least after boot).
Help welcome.
Gb |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Profile
Log in to check your private messages
Log in
