GRUB2 boots from raid1 device only after "grub rescue> insmod linux" + "rescue:grub> normal"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: grub2
GRUB2 doesn't boot karmic from raid1 device (md0). Instead it shows...
GRUB loading.
error: cannot get C/H/S values
grub rescue>
After invoking...
grub rescue> insmod linux
it shows...
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device/file completions. ]
rescue:grub>
where
rescue:grub> normal
boots the system (splash screen is shown after six to eight seconds and system boots).
ProblemType: Bug
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfead8000 irq 23'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,
Controls : 28
Simple ctrls : 16
DKDisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
Date: Sun Dec 6 20:00:54 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
HotplugNewDevices:
HotplugNewMounts:
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Lsusb:
Bus 001 Device 003: ID 0ea0:2126 Ours Technology, Inc. 7-in-1 Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 046d:c045 Logitech, Inc. Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. AM2NF4G-SATA2
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.25
RfKill:
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
Uname: Linux 2.6.31-16-generic x86_64
dmi.bios.date: 03/08/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: AM2NF4G-SATA2
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: AM2NF4G-SATA2
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
Once system bootet without any interaction. Maybe it's a timing problem. But how could it be fixed?