Weblog entry #60 for ajt
See all weblog entries made by ajt.
We tried to put Etch (from the D-I rc1) on an old Compaq DL360 G1 at work today. It boots up okay but refuses to correctly access the disks. An old Ubuntu live disk is happy to find the disks, and even partition and put ext3 onto them. Annoying!
I'll have to see if I have an older disk lurking around and see if that is happier...
update: Sarge was happy!
Comments on this Entry
[ Parent | Reply to this comment ]
Bullseye!/dev/hda or /dev/sda, the first logical disk is found at /dev/ida/c0d0, and the first partition on this disk is /dev/ida/c0d0p0 instead of /dev/hda1 or /dev/sda1.cpqarray: Finding drives on ida0", "cpqarray: ida0: idaSendPciCmd Timeout out, No command List address returned.", "cpqarray: error sending ID Controller", etc. It turns out that the RAID device would be taken by another driver (sym53c8xx) before the cpqarray driver could claim it. The change in 2.6.18 that fixes this problem can be found in this git commitdiff. Most recent distro installation CDs use an afflicted version of the 2.6 kernel. I made sure to boot into the 2.4 kernel when booting from the installation CD because if I booted into a 2.6 kernel, I couldn't use the disks. One good fix to this problem is to remove the sym53c8xx driver from the kernel (maybe you can just unload the sym53c8xx module and reload the cpqarray module?). My old fix was to recompile the kernel with the cpqarray driver built-in instead of a module. Of course, the very best solution is to get a 2.6.18 kernel. By the way, thanks to Andrew Beverley for explaining what the real cause of the problem is.
--
"It's Not Magic, It's Work"
Adam
[ Parent | Reply to this comment ]