lucid: update-grub does not work with 4 character disk names in /dev

Bug #922041 reported by Jochen Barth
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

We're using Lucid 10.04.3 (Server, 64 Bit) and have a lot of attached disks.
During installation, there has been only one drive named /dev/sda, everything worked fine.
Now we've attached all storage, update-grub (which calls grub-probe) does not work anymore:

root@xxx:/root# grub-probe -v -t fs_uuid -d /dev/sdby
grub-probe: info: »/boot/grub/device.map« kann nicht geöffnet werden.
grub-probe: info: /dev/sdby starts from 0.
grub-probe: info: opening /dev/sdb.
grub-probe: info: the size of /dev/sdb is 4194304000.
grub-probe: error: unknown filesystem.

Have a look at the /dev - names: in the third output line grub-probe is talking about "sdb" instead of "sdby".

We made an inconvenient (not easily transferable) workaround using udev:
root@...:# cat /ect/udev/rules.d/61-persistent-local-drive.rules
KERNEL=="sd*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="3600508e000000000f92b957d13e3870a", NAME="sda"
KERNEL=="sd*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL}=="3600508e000000000f92b957d13e3870a", NAME="sda%n"

Version of grub-pc is 1.98-1ubuntu5

Revision history for this message
lmhd (maylein) wrote :

I think, this is the same bug as

https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/776633

Isn't there any solution?

The described workaround seems not to work in every case.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.