[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573356
Title:
Boot hang
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Hello
Is this problem present with the latest updated Lucid's or Maverick's packages?
Thanks in advance
Fabio
** Changed in: ubuntu
Status: New => Incomplete
--
Boot hangs after fsck following upgrade from Ubuntu 9.10 to 10.04
https://bugs.launchpad.net/bugs/573356
You received this bug n
See also http://ubuntu-ky.ubuntuforums.org/showthread.php?t=1560151
--
Boot hangs after fsck following upgrade from Ubuntu 9.10 to 10.04
https://bugs.launchpad.net/bugs/573356
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
It appears this was addressed in the Ubuntu 10.04 Release Notes at
http://www.ubuntu.com/getubuntu/releasenotes/1004 under the heading
"Changes in boot-time output on Ubuntu Server". If I read that
correctly, a splash boot will show instructions for how to get past this
by prompting the user to pr
I confirm the behavior described in the first post for a system with no
oddities (vaio tz laptop). The problem occurs after an upgrade from
9.10. I did not have any drive that was set to automount, and the
behavior was the same when I addressed the disk with its UUID and with
as /dev/sda2. The syst
** Description changed:
I upgraded my system from Ubuntu 9.10 to 10.04 and am having trouble
booting my box. Both in normal mode and in recovery mode, my system
hangs after the following message is printed:
- fsck from util-linux-ng 2.17.2
- /dev/sdb1: clean 380060/4259840 files,
Okay, I misspoke about my second hard drive not being set to automount
-- I had swapped drives a while back and still had an entry in
/etc/fstab pointing to a disk UUID that no longer existed. Editing
/etc/fstab to comment out the erroneous entry allowed my system to boot.
I believe the relevant
