Comment 20 for bug 1838525
Revision history for this message
| Rafael David Tinoco (rafaeldtinoco) wrote | #20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
After Andreas and I compared side by side the 2 "set -x" outputs, we discovered what is happening.
https:/
And "/dev/vda1" is being caught instead of "/dev/vda", as it happens to "/dev/sda" (instead of getting "/dev/sda1"). This logic comes a bit above that execution output:
https:/
And this is why andreas talks about "grub-mkdevicemap" here, and he is triggered by the "head -n1" usage:
17:10 <rafaeldtinoco> instead of /dev/vda
17:10 <andreas> cyphermox: I wonder about this head -n1
17:10 <andreas> default_
17:10 <andreas> if it's making an assumption
17:10 <cyphermox> well, usually hd0 is really what you want
17:10 <cyphermox> and it works for sda
17:10 <cyphermox> I mean, what is so different about virtio?
17:10 <andreas> yeah, I don't have the raw output in the sda case
We then tested both, virtio and non-virtio installations and saw that, for the SCSI case:
bash-5.0# grub-mkdevicemap --no-floppy -m -
(hd0) /dev/disk/
(hd1) /dev/disk/
the disk is listed first (as hd0) in grub-mkdevicemap, while in the VIRTIO case, it is listed as SECOND (explaining why /dev/mapper was generated in subsequent wrong logic bellow).
https:/