Public bug reported:
My layout of hard disks is:
hda6 => BOOT partition of my (K)Ubuntu
sda1 = partition of the RAID0 device /dev/md0 which uses REISERFS (v 3.6)
sdb1 = partition of the RAID0 device /dev/md0 which uses REISERFS (v 3.6)
I've done Edgy->Feisty upgrade (using update-manager) but at the restart, after
GRUB, I'm being dropped in a BusyBox. Very nice thing is the fact that it does
not "see" the keyboad and thus I cannot type anything (I press keys but nothing
happens on the screen).
I think this is somehow related to the fact my keyboard (and mouse) are USB...
maybe the busybox is launched _before_ loading the USB driver? I suspect that's
the source of the problem because e.g. the numpad LED does not turn on when I
press Block-num, which typically happens when keyboard is not turned on by the
kernel.
Things get much better if I put a "break=mount" in the GRUB options for
"kernel" command as the busybox which comes up then is interactive (i.e. when a
press a keyboard key it's responsive and show it on the screen).
I've found that from the busybox I'm dropped after GRUB, my MD device is
already assembled and working.
In fact, I've discovered that I don't need to do _anything_ from that busybox.
I.e. if I just press Ctrl+D, busybox exits and the boot proceed correctly.
However if I remove the "break=mount" option from the GRUB "kernel" command, I
still get an unresponsive busybox (and I'm forced to turn off the computer
unplugging the cable: the turn-off button nor the reset button do anything!).
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
feisty opens a busybox on boot with RAID0+reiserfs
https://bugs.launchpad.net/bugs/104790
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
