On Wed, Oct 08, 2008 at 10:46:26AM +0100, Dan Poltawski wrote: > On Wed, Oct 08, 2008 at 01:35:53AM -0400, Samat K Jain wrote: > > On Tuesday 07 October 2008 04:53:57 am Dan Poltawski wrote: > > > Just in response to this - my problem has not been caused by an upgrade - > > > it was a clean lenny install > > > onto a new machine a few days ago. > > > > Well, something regenerated device.map since installation. I don't think > > your system would boot with the device.map you've provided---grub would > > have ever installed properly. I believe, from what you've provided, your > > device.map should contain: > > > > (hd0) /dev/sda > > (hd1) /dev/sdb > > > > Did you try the workaround? Namely running `grub-mkdevicemap --no-floppy` > > again? > > Yes I did, this does resolve the problem and also contains the same map as > you guessed at. > > I'm looking through the apt log to see if I can find anything which would > regenerate the device.map since install.
It might be possible that the names sda to sdd were used for something that wasn't an hard disk during the install (a card reader with 4 different slots might be a good candidate). Then your system would still boot properly with your old device.map because grub detected that sde was the first hard disk, but then you wouldn't be able to run update-grub because your first hard disk is sda now. Could you check this in the installation log or by running the debian installer again to the point where it detects all the disks? Regards, Jeroen Dekkers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
