[Bug 964990] [NEW] [Ubuntu 12.04] partitions with ext2 are NEVER cleanly unmounted on shutdown/reboot
Christian Niemeyer
chr.niemeyer at gmail.com
Mon Mar 26 05:28:38 UTC 2012
Public bug reported:
Using Ubuntu 12.04 (64bit) with all updates. I use only one partition
(/dev/sda4 mounted on /).
On *every* reboot or after shutdown and booting again, I get this error message:
/dev/sda4 not cleanly unmounted, check forced
My fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda4 during installation
UUID=7c347aca-031a-4f6b-9213-b136eed5429c / ext2 errors=remount-ro 0 1
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
uname -a: Linux kringels 3.2.0-20-generic #32-Ubuntu SMP Thu Mar 22
02:22:46 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I'm pretty sure, it is related that I use ext2 as filesystem. I haven't
found anything else, so I guess this problem doesn't occur on ext3/ext4.
I only found this one: https://answers.launchpad.net/ubuntu/+source
/util-linux/+question/189716
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/964990
Title:
[Ubuntu 12.04] partitions with ext2 are NEVER cleanly unmounted on
shutdown/reboot
Status in “util-linux” package in Ubuntu:
New
Bug description:
Using Ubuntu 12.04 (64bit) with all updates. I use only one partition
(/dev/sda4 mounted on /).
On *every* reboot or after shutdown and booting again, I get this error message:
/dev/sda4 not cleanly unmounted, check forced
My fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda4 during installation
UUID=7c347aca-031a-4f6b-9213-b136eed5429c / ext2 errors=remount-ro 0 1
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
uname -a: Linux kringels 3.2.0-20-generic #32-Ubuntu SMP Thu Mar 22
02:22:46 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I'm pretty sure, it is related that I use ext2 as filesystem. I
haven't found anything else, so I guess this problem doesn't occur on
ext3/ext4. I only found this one:
https://answers.launchpad.net/ubuntu/+source/util-
linux/+question/189716
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/964990/+subscriptions
More information about the foundations-bugs
mailing list