Bug#514967: grub-mkdevicelist does not cope with /boot on a disk > #16

[Robert Millan]

On Thu, Feb 12, 2009 at 10:53:18PM +1100, Chris Samuel wrote:
> Package: grub
> Version: 0.97-47lenny2
> Severity: important
> 
> 
> This system has 25 disks and upgrading from Etch to Lenny
> hit problems when the new version of grub in Lenny did not
> create the correct device.map file, it stopped at disk #16
> /dev/sdp (hd15).
> 
> On this system the system disk with /boot is #25, /dev/sdy1.
> 
> grub-mkdevicelist should be able to cope with larger number
> of disks - for example we have another system with 35 disks,
> and due to the way that the aacraid driver discovers its host
> the /boot partition is on disk #33, /dev/sdag1.
> 
> We worked around the issue on this system by extending the
> device.map file by hand.

So what is the actual limit ?

And how are disks named after we reach /dev/sdz ?

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."