system fails to initramfs after reboot during build

Anderson, Steven steven.anderson at
Mon Jan 8 06:54:36 CST 2007

This failure is due to the virtual loader does not have the correct
drivers and does not select the correct disk during the boot process.

The newest version of the installer has fixed the problem 

Setup Server
1.    Install from the Debian CD (Downloaded the Debian installer from (32
bit version of network loader))

2.    If you are using the 1st NIC select the 2nd NIC (there is a bug in
the install that uses the opposite NIC

3.    Add the ssh daemon by typing "apt-get update && apt-get install

4.    Reload keyboard, mouse, and video drivers by typing the following
(enables xwindows)

4.1.  aptitude install xserver-xorg-input-kbd

4.2.  aptitude install xserver-xorg-input-mouse

4.3.  aptitude install xserver-xorg-input-evdev

4.4.  aptitude install xserver-xorg-video-all

4.5.  dpkg-reconfigure xserver-xorg


Steven Anderson
City of Dallas
Streets Department
Flood Control
2255 Irving Blvd.
Dallas, TX, 75207-6201
fax - (214)670-6526
e-mail steven.anderson at
Web Sites
World Wide Web -
Wireless Web -
City Intranet - http://fc.sts.cod

-----Original Message-----
From: linux-poweredge-bounces at
[mailto:linux-poweredge-bounces at] On Behalf Of sean finney
Sent: Sunday, January 07, 2007 9:33 PM
To: J. Epperson
Cc: linux-poweredge at
Subject: Re: system fails to initramfs after reboot during build

and to add a reply to my own mail.... :)

> chances are the installer detected your hardware as part of the 
> standard hardware-probing, but wasn't smart enough to realize that you

> need the driver loaded from the initrd to be able to get to /.  so, 
> you need to basically do something like the following before rebooting

> (or after booting from a rescue disk and mounting/chrooting stuff if 
> it's too late):
> echo drivername >> /etc/initramfs-tools/modules update-initramfs -u -k

> all
> my memory is hazy on this, so use this as a reference when figuring it

> out on your own... but that should be it.  in my case (perc 5 di) the 
> drivername is megaraid_sas.

also, keep in mind that device naming might be problematic in the case
of an updated kernel/driver, and in the case of insertion/removal of
additional disks.   for example, on the last system i installed (dapper
on a pe 2950), the physical disks of a 4 disk raid set showed up as
sda-d, and the logical raid disk was sde.  guess what  happens if you
add a disk to that raid set when you try to mount sde... the solution in
my case was to rename the raid disk using udev.  if you look back about
2 months in the archives, you should see the specific udev config option
i used.


More information about the Linux-PowerEdge mailing list