Re: upgrade-from-grub-legacy failure

[Wolfgang Schulze-Zachau]

Hi all,

some more information for this:

The file /boot/grub/device.map contains:

build5:/boot/grub# cat device.map.old
(hd0)   /dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0GST8
(hd1)   /dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0H7L9

However, the disks are identified as:

build5:/boot/grub# ls -alh /dev/disk/by-id/
total 0
drwxr-xr-x 2 root root 180 May 10 13:00 .
drwxr-xr-x 5 root root 100 May 10 13:00 ..
lrwxrwxrwx 1 root root   9 May 10 13:00
md-uuid-132c9ca3:9ffea779:3a5e3e9c:8479741d -> ../../md0
lrwxrwxrwx 1 root root   9 May 10 13:00 scsi-1ATA_ST3300831AS_3NF0GST8
-> ../../sda
lrwxrwxrwx 1 root root  10 May 10 13:00
scsi-1ATA_ST3300831AS_3NF0GST8-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 May 10 13:00
scsi-1ATA_ST3300831AS_3NF0GST8-part2 -> ../../sda2
lrwxrwxrwx 1 root root   9 May 10 13:00 scsi-1ATA_ST3300831AS_3NF0H7L9
-> ../../sdb
lrwxrwxrwx 1 root root  10 May 10 13:00
scsi-1ATA_ST3300831AS_3NF0H7L9-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  10 May 10 13:00
scsi-1ATA_ST3300831AS_3NF0H7L9-part2 -> ../../sdb2

If I update the file /boot/grub/device.map to contain the device IDs as
found during boot, then the command (as below) does not report any
errors. Can I safely do this and the run upgrade-from-grub-legacy?


On 10/05/12 14:22, Wolfgang Schulze-Zachau wrote:
> Hi all,
>
> I was asked to report the failure of grup to be upgraded here. What
> follows is the output of "/usr/sbin/grub-probe
> --device-map=/boot/grub/device.map --target=fs -v /boot/grub":
>
> build5:~# /usr/sbin/grub-probe --device-map=/boot/grub/device.map
> --target=fs -v /boot/grub >/tmp/grub-failure.txt
> /usr/sbin/grub-probe: info: Cannot stat
> `/dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0GST8', skipping.
> /usr/sbin/grub-probe: info: Cannot stat
> `/dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0H7L9', skipping.
> /usr/sbin/grub-probe: info: changing current directory to /dev.
> /usr/sbin/grub-probe: info: changing current directory to dri.
> /usr/sbin/grub-probe: info: changing current directory to snd.
> /usr/sbin/grub-probe: info: changing current directory to net.
> /usr/sbin/grub-probe: info: changing current directory to shm.
> /usr/sbin/grub-probe: info: opening md0.
> /usr/sbin/grub-probe: error: no such disk.
>
> I should probably mention that there was a problem during the upgrade.
> This machine runs entirely on a software RAID1 (no boot partition, and
> root is mounted on /dev/md0). During the upgrade to squeeze, mdadm found
> that the device ID for md0 had changed. I updated the
> /etc/mdadm/mdadm.conf file, but forgot to run update-initramfs, and then
> subsequent boots failed until I booted into rescue mode and ran the
> command from the rescue shell.
> The system now boots, using the chainloader. However, during the boot
> process I also get error messages that some information could not be
> read from the drives.
>
> Detailed log files are available if needed.
>

-- 
best regards

Wolfgang

Amino | Mob: +44 7554 457 455 | Desk: +44 1954 234 190 | skype: wszachauamino