Cannot boot even in singe or recovery mode if the network settings are wrong or filesystem error Lucid Beta 2
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| base-files (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: base-files
Cannot boot if some settings in the interface file is wrong, not able to get recovery console.
I had only this little problem there ( Having 2 interfaces)
auto eth1 eth1 bond0
^
And this has blocked the boot.
Problems with this behavior:
- A configuration issue should not stop booting process! And even not the Single user/ Recovery mode...
- Single mode should not start networking
If a filesystem error occurs again not able to boot into recovery console only with the workaround described below and mountall: Unrecoverable fsck error: loops endless...
Yes the new booting concept is very fast but fails on every little problem even by booting to single mode...
current workaround:
start the system with init=/bin/bash and remount the file system rw, and correct the config or repair the filesystem..
Best Regards
Udo Attila Fischer
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: base-files 5.0.0ubuntu15
ProcVersionSign
Uname: Linux 2.6.32-19-server x86_64
Architecture: amd64
Date: Mon Apr 12 14:06:06 2010
InstallationMedia: Ubuntu-Server 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcEnviron:
LANG=hu_HU.UTF-8
SHELL=/bin/bash
SourcePackage: base-files
| summary: |
Cannot boot even in singe or recovery mode if the network settings are - wrong Lucid Beta 2 + wrong or filesystem error Lucid Beta 2 |
| description: | updated |
| description: | updated |
| description: | updated |
| Mads Bondo Dydensborg (mads-dydensborg) wrote | #2 |
I would like to confirm this issue in a slightly different matter. I upgraded yesterday from karmic to lucid, with my laptop docked at work. Attached to the dock was an usb harddisk, which have long had an entry in my fstab.
I had some issues with the upgrade, which meant I had to reboot at some point, and had to resolve the upgrade manually in a cli.
Eventually it worked.
However, returning home, I could not boot: no single user, no recovery, nothing.
After spending 5 hours on this, I believe I have finally found out, that mountall never emitted the filesystem* event. Most likely because the usb harddisk was not found. Removing the entry from /etc/fstab resolved all my issues.
But I will never get the 5 hours back :-(
Anyway: I think this is a bug: If the bloody disk is missing, please detect this, and provide some kind of feedback, instead of doing absolutely nothing at all. Had I not had my unix-fu to fall back on, the system would have been a brick. :-)
Regards, and keep up the good work.