-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi!
I just installed grml 1.0 to 5 PCs with grml2hd.
I let it run, added root pwd, username,userpwd, deleted the apache server, added hal, choosed grub in mbr and waited til it was done and rebooted.
After reboot, it couldn´t mount /root, because "device not found or busy". I tried it with UUID and with /dev/sda3 in grub....
MfG, Lars Schimmer - -- - ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723
Quoting Lars Schimmer l.schimmer@cgv.tugraz.at:
I let it run, added root pwd, username,userpwd, deleted the apache server, added hal, choosed grub in mbr and waited til it was done and rebooted. After reboot, it couldn´t mount /root, because "device not found or busy". I tried it with UUID and with /dev/sda3 in grub....
We've debugged the problem together and found the evil root cause!
It was dmraid! Dmraid starts an intel fakeraid because there was a valied intel software raid metadata chunk on the disk. We suppose this comes from some stresstesting with Windows from the vendor.
Once found this could easily be corrected.
dmraid -r /dev/sda -E dmraid -r /dev/sdb -E
The command aborts and prints out a backtrace but netherless it removed the metadata chunk from the disk successfully.
But after this metadata removeal grub won't boot the system anymore, just reinstall it.
mount /dev/sda3 /mnt/sda3 grub-install --root-directory /mnt/sda3 /dev/sda
And everything worked as expected.
cu, Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael Gebetsroither wrote:
Quoting Lars Schimmer l.schimmer@cgv.tugraz.at:
I let it run, added root pwd, username,userpwd, deleted the apache server, added hal, choosed grub in mbr and waited til it was done and rebooted. After reboot, it couldn´t mount /root, because "device not found or busy". I tried it with UUID and with /dev/sda3 in grub....
We've debugged the problem together and found the evil root cause!
It was dmraid! Dmraid starts an intel fakeraid because there was a valied intel software raid metadata chunk on the disk. We suppose this comes from some stresstesting with Windows from the vendor.
Once found this could easily be corrected.
dmraid -r /dev/sda -E dmraid -r /dev/sdb -E
The command aborts and prints out a backtrace but netherless it removed the metadata chunk from the disk successfully.
But after this metadata removeal grub won't boot the system anymore, just reinstall it.
mount /dev/sda3 /mnt/sda3 grub-install --root-directory /mnt/sda3 /dev/sda
And everything worked as expected.
A BIG thanks to the helping people :-)
cu, Michael
MfG, Lars Schimmer - -- - ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723
Teilnehmer (2)
-
Lars Schimmer -
Michael Gebetsroither