mountall on karmic server install fails
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mountall (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: mountall
Newly installed and then freshly updated Karmic server install as of 24-Oct-2009 21:39 -0400.
Problem is that mountall persists in running (for 1 to 2 hours) and eventually fails and displays a message on the console saying that the system is starting an emergency shell, even if the system is already running and I'm logged into a shell. Then the new shell and my shell complete for the tty input and it's not pretty.
All I know, and all I can find out, at this point, is that mountall is broken in the default server install and I don't know how to fix it. I discovered this problem after updating the server and my lxc-containers then failed to start. Now, I can't get past the point of an initial setup. This bug is in the release candidate and at least in my case is inhibiting me from getting my server setup without having to do something entirely off the wall like installing Jaunty and heavily modifying it to suit my needs.
| Michael B. Trausch (mtrausch) wrote | #1 |
| tags: | added: critical mountall server |
| Michael B. Trausch (mtrausch) wrote | #2 |
| Michael B. Trausch (mtrausch) wrote | #3 |
| Alexandr Novel (normalex) wrote | #4 |
A-ha. I have found a way to reliably trigger the failure of mountall.
Install a bare server using Karmic, update it fully.
Then, on that server, try to view a man page on the console. Arrow keys will appear to not work correctly.
Install emacs-snapshot-nox on that server.
Attempt to arrow around.
The following text will then display:
mountall: Cancelled
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell re-try.
root@saffron:~# _
Now, note that in Emacs, this will not appear with the newlines correctly displayed; it will clobber the terminal and the text shown is stair stepped. Something very wrong is going on here, this bug should be critical for release.