[SOLVED] Unclean shutdown? Check forced on start-up.

DJRcomputing · 05-23-2011, 10:29 PM

This seems like only a slight inconvenience, but I don't like the idea of unclean shutdowns/reboots.

Whenever I boot/restart, I notice the message "/dev/hdb1 (and hdb2) was not cleanly unmounted, check forced." Then fsck(?) scans them without errors, and everything continues normally. FWIW, hdb1 @ hdb2 are ext2, /boot & /tmp respectively, whereas all other partitions are ext3. Could that (ext2) be why? I checked halt, reboot, umountfs, umountnfs.sh, and umountroot in /etc/init.d, and nothing jumped out at me, though I'm not exactly sure what I'm looking at/for.

nileshgr · 05-24-2011, 12:31 AM

It seems your filesystems are not unmounted at shutdown, that's why this is happening.
Do you mount those manually? Actually even manually mounted fses get remounted at least read only if not completely umounted. Must be some kind of bug.

kbp · 05-24-2011, 12:41 AM

Could you post the content of your /etc/fstab file ?

DJRcomputing · 05-24-2011, 12:57 AM

Quote:

Originally Posted by kbp

Could you post the content of your /etc/fstab file ?

LOL! I knew someone would ask for that, though nothing SEEMS out of the ordinary. *shrug* I just attached it for better width formatting than <CODE></CODE>

DJRcomputing · 05-24-2011, 01:31 AM

PS - FWIW, I've also attached the umountfs, umountnfs.sh, and umountroot scripts from /etc/init.d if that helps and/or someone wants to mod them to fix this problem. Just attach any changed files, please. Thanks.

DJRcomputing · 05-24-2011, 01:33 AM

Also halt and reboot. (Sorry. LQ maxes @ 3 attachments/post :P )

Stéphane Ascoët · 05-24-2011, 02:24 AM

I would put "/boot" in "ro" in the fstab

kbp · 05-25-2011, 12:00 AM

The only thing I noticed was that reboot was called with the argument '-f' which is force on my pc, can you tell us what '-f', '-i' and '-d' mean ? .. only '-f' is listed in my man pages.

DJRcomputing · 05-25-2011, 05:56 AM

Quote:

Originally Posted by kbp

The only thing I noticed was that reboot was called with the argument '-f' which is force on my pc, can you tell us what '-f', '-i' and '-d' mean ? .. only '-f' is listed in my man pages.

Wait...you're asking ME?? LOL! Thanks for inspiring me to consider flags as a possible cause, though dropping -d & -f (neither of which I like) from reboot & halt (latter script already calls for -h, -i & -p) didn't solve the problem...

-d Don’t write the wtmp record.
-f Force halt or reboot, don’t call shutdown.
-h Put all harddrives on the system in standby mode just before halt or poweroff.
-i Shut down all network interfaces just before halt or reboot.
-p When halting the system, switch off the power.

-b Blow your brains out from troubleshooting. (not really. LOL!)

Quote:

Originally Posted by Stéphane Ascoët

I would put "/boot" in "ro" in the fstab

Yeah, I've been meaning to lock down my mount options prior to bringing my LAMP server online, but I'm still in the config stages. /home & /var get usrquota, for www & to prevent massive spam to any one email address from hogging all of /var (I think/hope). Likewise /usr is going ro once complete for safety/security.

Quote:

Originally Posted by DJRcomputing

Could that (ext2) be why?

That seems to be the cause, though it shouldn't be (bug?). Mounting ro doesn't TECHNICALLY need to be unmounted, which solves /boot. I ultimately converted /tmp to ext3 via LiveCD, since /tmp wouldn't unmount no matter what I tried. *shrug*