cannot install lenny amd64 on 2950
alexander.mestiashvili at biotec.tu-dresden.de
Thu Feb 19 04:35:06 CST 2009
christian.peper at kpn.com wrote:
> Ah yes, I've had that on the PE2950, where the Dell virtual media
> devices add additional boot devices and mess up device enumeration.
> We've fixed that by installing using the option 'nousbstorage' on Red
> Hat, but I'm not sure if Debian will know about that option.
> Otherwise, simply poke around in the grub loader
> Grub>root hd(0,0)
> Grub>root hd(1,0)
> If it finds root environment, your set. Edit fstab using the device
> you've just found and reboot. This should be fairly straight forward
> from a stnd Linux rescue mode.
>> -----Original Message-----
>> From: linux-poweredge-bounces at dell.com
>> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Teodor MICU
>> Sent: Wednesday, February 18, 2009 5:45 PM
>> To: ronreg at mtholyoke.edu
>> Cc: linux-poweredge at dell.com
>> Subject: Re: cannot install lenny amd64 on 2950
>> On Wed, 18 Feb 2009 11:13:28 -0500
>> ronreg at mtholyoke.edu wrote:
>>> Lenny i386 isn't working either. Install appears to
>> complete OK, but
>>> the bootloader never starts on reboot. Again, running grub
>>> from Knoppix is no help - grub can't find the disk.
>> You should check the release notes:
>> Disk devices may change on reboot
>> On systems with multiple disk controllers, the
>> kernel/udev may assign a different device node on reboot of
>> the system than was used during installation due to
>> difference in load order of drivers. This can lead to failure
>> to boot the system. In most cases this can be corrected by
>> changing the bootloader configuration and /etc/fstab,
>> possibly using the rescue mode of the installer. Note however
>> that this problem may occur again on subsequent boots.
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge at dell.com
>> Please read the FAQ at http://lists.us.dell.com/faq
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> Please read the FAQ at http://lists.us.dell.com/faq
I had such problems with PE1950 , finally I changed device names to
their UUIDs and that worked just fine .
title Debian GNU/Linux, kernel 184.108.40.206-grsec
UUID=a90aaf9b-9b29-49f8-94ae-aebd7ca33378 / ext3
rw,errors=remount-ro 0 1
More information about the Linux-PowerEdge