yes, it does still happen IFF there is a faulty entry in /etc/fstab. I
agree that this is an error situation, but the error handling in this
case (for a volume mounted in /media) should be as bad as this.
** Changed in: sysvinit (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- /etc/init.d/checkfs.sh fails badly
+ /etc/init.d/checkfs.sh fails badly if one of the filesystems in /etc/fstab
has an different UUID than in reality
** Description changed:
Binary package hint: initscripts
+
+ During installation, I told the installer to create an ext3 partition in
+ /dev/sda6, which got mounted in /media/sda6. The installation ended of
+ with /etc/fstab having a different UUID than ended up in the installed
+ system.
on every system startup, I'm presented an error message that an drive
could not be checked, and I'm thrown to an root shell. If I exit that
shell using CTRL-D as suggested, the system boots up just fine.
The system is a very freshly installed Hardy alpha6 system, and just
upgraded using update-manager.
--
/etc/init.d/checkfs.sh fails badly if one of the filesystems in /etc/fstab has
an different UUID than in reality
https://bugs.launchpad.net/bugs/203166
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
