Bug#605562: installation-report: Installation from usb stick lead, to unbootable system (und unbootable usb stick)
Hi!
* Joachim Schleicher <joachim@dormettingen.de> [110103 14:06]:
> ~ # chroot /target grub-mkdevicemap --no-floppy -m -
> (hd0) /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_20053349610A41A2F01B-0:0
> (hd1) /dev/disk/by-id/ata-FUJITSU_M1623TAU_08316741
>
> ~ # readlink -f $(chroot /target grub-mkdevicemap --no-floppy -m - | head -n1 | cut -f2)
> /dev/sda
> <ash>
I finally found the time to play a bit with my system here. The bad
news is, that I can still reproduce this bug with the rc1 images.
However, on a first glance it seems that Joachim is right.
Currently I have the following:
$ sudo grub-mkdevicemap --no-floppy -m -
(hd0) /dev/disk/by-id/ata-WDC_WD360GD-00FNA0_WD-WMAH91382658
(hd1) /dev/disk/by-id/usb-SanDisk_Cruzer_Micro_200445276207662139DB-0:0
(hd2) /dev/disk/by-id/scsi-3600508e000000000a28c3e222acc010b
(hd1) is the usb-stick I used to boot, (hd0) a normal sata disk (I
pluged that in for additional testing after my bug report) and
(hd2) my actual disc (a "dell virtual disc" from an mpt hardware raid
controller if that matters).
As said I played a bit, regardless of the way I boot from usb-stick
(new "isohybrid dd"-way or old fashioned "zcat mount copy iso"-way) and
installation target, grub always got installed into (hd0) (while it got
installed on the usb-stick during my first installation).
For reference the readlink command always said /dev/sda, independend of
the usb-stick being pluged in or not, while without the stick being
present, I got the following for the grub-mkdevicemap:
$ sudo grub-mkdevicemap --no-floppy -m -
(hd0) /dev/disk/by-id/ata-WDC_WD360GD-00FNA0_WD-WMAH91382658
(hd1) /dev/disk/by-id/scsi-3600508e000000000a28c3e222acc010b
Best Regards,
Alexander
Reply to: