Public bug reported:
This has happened 3 times to me so far.
2 times on the Samsung NC20 of my girlfriend, using Ubuntu 10.10 / Windows XP
parallel installation.
1 time on my Dell inspiron mini 10 using standalone Ubuntu 10.10.
Both notebooks use ext4 as filesystem.
I can't reproduce it but it seems to happen after Ubuntu installs an update.
After doing whatever causes it and restarting the system ubuntu doesn't boot
anymore and no matter which kernel I choose in grub I end up in BusyBox.
This is what the monitor shows after trying to boot:
[... some error trace ...]
Killed
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
Starting the computer with an USB Stick and trying to mount the affected drive
results in endless waiting, but nothing happens even if I wait for hours.
Reboot really often and using a random combination of trying to mount /
unmounting / alt + s-abf + s / alt + s-abf + b / seems to fix the issue,
however in the first two cases some random system files were gone (like
the network manager applet image), which makes it necessary to reinstall
ubuntu completely.
I am leaving the inspiron mini in the described state, if someone tells
me how to do it I will gladly provide any error traces or system logs
you need, assuming there is a way to write them into a text file on an
usb stick.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: damaged filesystem reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692623
Title:
filesystem damaged after reboot
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
