Weblog entry #2 for kodzoman

Installing Debian Etch on Dell 1950/2950 with PERC
Posted by kodzoman on Wed 21 Nov 2007 at 14:08
Tags: none.

Debian installation on Dell 1950 machines worked great for me, until I got my shining new PERC 5/i and SAS disks.

After some searching on the internet and figuring out a few things I found this to work.

This solution works for me on all new Dell machines we got.

  • Insert Debian Netinst CD in your Dell machine, and power it up.
  • Select country/language.
  • When configuring network, please note that Gb1 is eth1 and Gb2 is eth0 (reversed order).
  • Partition hard disks as you like and install your system as usual (I always choose Standard System only).
  • When you get the "Installation complete" screen, do not choose continue, but rather switch to another console ().
  • In console, do the following steps (it's good if you understand what you are doing, but my guess is you are not installing any servers without understanding this, so I will not elaborate them).

  • mkdir /tmp_target
  • mount /dev/sdb1 /tmp_target
  • chroot /tmp_target
  • echo "megaraid_sas" >> /etc/initramfs_tools/modules
  • update-initramfs -u
  • in /etc/fstab replace all /dev/sdbX with /dev/sdaX (/dev/sdb1 with /dev/sda1,...)
  • in /boot/grub/menu.lst replace all /dev/sdbX with /dev/sdaX
  • grub-install /dev/sdb (because it's still dev/sdb in the install, it will change later :)
  • exit
  • umount /tmp_target
  • switch back to installation ()
  • press continue

You might have noticed that the actual key to the entire process is megaraid_sas driver, which is not loaded by default. With some luck you should have a running Debian Etch on your Dell machine now!

 

Comments on this Entry

Posted by mwr (149.149.xx.xx) on Wed 21 Nov 2007 at 21:58
[ Send Message | View Weblogs ]

I don't remember having that kind of trouble with our 2950 a few months ago. I LVM'ed as much of the internal array as possible, but /boot couldn't be in LVM, so that's still on /dev/sda1.

Details on the setup are here. Ours has a PERC 5/i and a 5/E, with 2.5" SAS drives on the 5/i. Not sure what's different between my situation and yours that caused you all your trouble.

[ Parent | Reply to this comment ]

Posted by Anonymous (84.255.xx.xx) on Wed 21 Nov 2007 at 22:13
We did it before that, so it might be that this is outdated now. It worked for us on more machines, so I was rather sure it wasn't a one time thing. I just forgot to post it before, and I guess something changed for the better now :)

[ Parent | Reply to this comment ]

Posted by texnick (70.116.xx.xx) on Fri 23 Nov 2007 at 17:36
[ Send Message ]
I've had similar issues with about half of my PoweEdge / PERC installs in the last year.
Typically it would seem that sdb would get changed to sda for some reason. I'd change it back and everything worked fine. Here's what I saw this last time.

1. Install went smooth.
2. Reboot, initramfs mode.
3. Boot from install media, get to partitioning section. This is what I've always done. I see what the disk is detected as here and make a note of it. Then I'd find that /etc/fstab and /boot/grub/menu.lst were wrong. However, in this case I found all to agree on SDB. So based on this article I thought I'd try just changing it to SDA and see what happens.
4. Execute a shell from the debian installer. (go back, "execute a shell")
5. mkdir /tempdisk
6. modify /etc/fstab and add /dev/sdb3 /tempdisk defaults
7. mount /dev/sdb3 /tempdisk Now I can access the file system where debian is installed.
8. edit /etc/fstab and /boot/grub/menu.list and change sdb to sda in path statement.
9. Reboot. Success.

Note: fsck ran upon reboot and seemed to take a while. I'm not sure if that's related, but everything works now.

So in my case the driver thing wasn't necessary. If I notice anything else I'll post it.

[ Parent | Reply to this comment ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search