SliTaz Forum

/dev/sda3 was not cleanly unmounted, check forced

(10 posts) (3 voices)

• Started 9 years ago by Ceel
• Latest reply from Ceel
• This topic is resolved

Tags:

No tags yet.

1. 

   Ceel
   

   offline

   Administrator

   Hello all,

   I noticed with ext2 partitions the following message at boot
   Checking filesystem: UUID=3c73de74-ea36-40e7-854f-f5cb87fdec10
/dev/sda3 was not cleanly unmounted, check forced.
/dev/sda3: 9341/869696 files (4.1% non-contiguous), 103783/3474432 blocks
Remounting rootfs read/write...

   This happens from the first boots; sometimes the message can be slightly different:
   Checking filesystem: UUID=ae0aea20-663a-4df7-8e2c-f88d8596024d
/dev/sda3 was not cleanly unmounted, check forced.
/dev/sda3: Deleted inode 300810 has zero dtime. FIXED.
/dev/sda3: ***** REBOOT LINUX *****
/dev/sda3: 9278/869696 files (5.3% non-contiguous), 444932/3474432 blocks
Remounting rootfs read/write...
   or
   Checking filesystem: UUID=ae0aea20-663a-4df7-8e2c-f88d8596024d
/dev/sda3 contains a file system with errors, check forced.
/dev/sda3: 9298/869696 files (5.4% non-contiguous), 445727/3474432 blocks
Remounting rootfs read/write...

   I thought that my old hard disk was dying but this never appears when partitions are formated ext3.
   I tested ext2 > ext3 > ext2 > ... for months, with rolling and 4.0, and I invariably come to the same conclusion: ext3 always OK, ext2 always KO...

   Any ideas? Do other users of ext2 partitions see similar messages in their /var/log/boot.log files?

   Posted 9 years ago #
2. 

   mojo
   

   offline

   Key Master

   I see similar error messages with ext3 and ext4 filesystems.
   You may find adding some extras to /etc/init.d/rc.shutdown decreases dirty umount shutdown error messages + e2fsck on boot

   # Umount filesystems
   sync && echo 3 > /proc/sys/vm/drop_caches && busybox umount -a -f 2>/dev/null

   Posted 9 years ago #
3. 

   Ceel
   

   offline

   Administrator

   Thanks mojo,

   I'm going to try and let you know.

   Posted 9 years ago #
4. 

   Ceel
   

   offline

   Administrator

   Messages continue to appear at boot. Never mind, I'll go back to ext3.

   Thanks

   Posted 9 years ago #
5. 

   gibor
   

   offline

   Moderator

   Hi Ceel, have tried this modding, and for me work correctly
   http://forum.slitaz.org/topic/new-busybox-ash-history-working-bad#post-35614

   Posted 9 years ago #
6. 

   Ceel
   

   offline

   Administrator

   Hi gibor,

   Thank you for your help but unfortunately, message reappeared tonight.

   Posted 9 years ago #
7. 

   gibor
   

   offline

   Moderator

   but unfortunately, message reappeared tonight

   But the error seem random or at specific situation
   You have dual boot with seven?
   From my experience, this error was generated at shuthdown can't umount because partition state on busy.
   If have unhide from script (view the trick over), at shutdown view this messages of error.
   One or more application have access to disk (firefox is one to have a long time first exit out).
   On this case try to insert sleep <time> command first line content umount -a. probability of success are good.
   On case of dual boot, for me seven not view ext3, but if launch windows at reboot slitaz appear your message, and this case not have any solution :/

   Posted 9 years ago #
8. 

   Ceel
   

   offline

   Administrator

   @gibor,

   You're right; I've forgotten to mention it. After installation, I can reboot and reboot as many times as I want, no problem; the message will appear after a shutdown.

   No dual boot on this computer, at least with Windows:
   sda1 = SliTaz 4.0 (ext3)
   sda2 = swap
   sda3 = rolling (back to ext3 because it's the biggest partition and checking it at boot lengthens the boot time)
   sda4 = extended
   -sda5 = data (ext2)
   -sda6 = free (fat32)
   -sda7 = rolling (ext2)

   I'd already thought an application could still have access to the disk when shutdown (but I don't see which one) and done the following test:

   • format sda7 in ext2 and install rolling (from SliTaz installer)
   • shutdown
   • boot sda7 -> OK
   • shutdown without doing anything
   • boot again and... /dev/sda7 was not cleanly unmounted, check forced.

   And not better with the sleep instruction...

   Posted 9 years ago #
9. 

   Ceel
   

   offline

   Administrator

   I wasn't awake!

   And not better with the sleep instruction...

   I was so focused on the boot that I didn't see the sleep command didn't work at shutdown.
   I suppressed line #25 killall busybox you suggested to add and now the sleep works and... it's seems OK at each boot!

   Thanks gibor.

   I'm going to test it a few days and will confirm.

   Posted 9 years ago #
10. 

    Ceel
    

    offline

    Administrator

    Adding a sleep 1 has significantly improved things.

    Just have to think to add it each time slitaz-boot-scripts is updated...

    EDIT: setting sleep to 2 gives 95% satisfaction; for the remaining 5%, just be sure that the CPU monitor in the upper right corner doesn't show any activity.

    EDIT2: nothing to do! It can work for days or weeks without any problem and then the message appears again for several days.
    I definitely forget ext2 for full installations...

    Posted 9 years ago #

RSS feed for this topic

Reply

You must log in to post.