Hiya! I'm trying to get SuSE 9.2 up and running from a system with an Adaptec 2100S SCSI RAID controller, and I want to run the system entirely on the SCSI arrays. No luck. Kernel panic after the first reboot after installation. It comes to mounting volumes, then setting up hardware dependencies and wham, there it dies. After some Googling I ran into Mark's guide for 9.1, does this apply to 9.2 and/or SLES9 as well? http://lists.suse.com/archive/suse-linux-e/2004-Aug/2476.html Later, Anders.
On Mon, 2005-03-07 at 12:37, Anders Norrbring wrote:
Hiya! I'm trying to get SuSE 9.2 up and running from a system with an Adaptec 2100S SCSI RAID controller, and I want to run the system entirely on the SCSI arrays.
No luck. Kernel panic after the first reboot after installation. It comes to mounting volumes, then setting up hardware dependencies and wham, there it dies.
After some Googling I ran into Mark's guide for 9.1, does this apply to 9.2 and/or SLES9 as well? http://lists.suse.com/archive/suse-linux-e/2004-Aug/2476.html
Later, Anders.
I looked this over briefly and wonder if he could have booted to the rescue DVD and run the commands: # mkdir /mnt/temp # mount /dev/i2o/hda3 /mnt/temp # mount /dev/i2o/hda1 /mnt/temp/boot add the i2o modules to the INITRD_MODULES line in /mnt/temp/etc/sysconfig/kernel in line INITRD_MODULES="i2o_core i2o_block" (plus other modules you need) # chroot /mnt/temp # mkinitrd Would seem to be much easier than adding an IDE drive and installing the OS to do the same thing. Isn't that the purpose of chroot, to temporarily change you root filesystem tree to something else? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Mon, 2005-03-07 at 18:22 -0500, Ken Schneider wrote:
On Mon, 2005-03-07 at 12:37, Anders Norrbring wrote:
Hiya! I'm trying to get SuSE 9.2 up and running from a system with an Adaptec 2100S SCSI RAID controller, and I want to run the system entirely on the SCSI arrays.
No luck. Kernel panic after the first reboot after installation. It comes to mounting volumes, then setting up hardware dependencies and wham, there it dies.
After some Googling I ran into Mark's guide for 9.1, does this apply to 9.2 and/or SLES9 as well? http://lists.suse.com/archive/suse-linux-e/2004-Aug/2476.html
Later, Anders.
I looked this over briefly and wonder if he could have booted to the rescue DVD and run the commands:
# mkdir /mnt/temp # mount /dev/i2o/hda3 /mnt/temp # mount /dev/i2o/hda1 /mnt/temp/boot
add the i2o modules to the INITRD_MODULES line in /mnt/temp/etc/sysconfig/kernel in line
INITRD_MODULES="i2o_core i2o_block" (plus other modules you need) # chroot /mnt/temp # mkinitrd
Would seem to be much easier than adding an IDE drive and installing the OS to do the same thing.
Isn't that the purpose of chroot, to temporarily change you root filesystem tree to something else?
Ken, You are right of course, and I did post an update to my howto after I learned about chrooting. Anders, The 21xx-series of controllers have a readme that says they do not support booting under SuSE. But, I have seen posts elsewhere that indicate updating to the latest firmware and using the Adaptec drivers corrects this. Adaptec seem to be increasing their Linux support somewhat. New drivers were released in December last year and February this year for some 21xx-series cards. HTH, Mark
On Mon, 2005-03-07 at 12:37, Anders Norrbring wrote:
Hiya! I'm trying to get SuSE 9.2 up and running from a system with an Adaptec 2100S SCSI RAID controller, and I want to run the system entirely on the SCSI arrays.
No luck. Kernel panic after the first reboot after installation. It comes to mounting volumes, then setting up hardware dependencies and wham, there it dies.
After some Googling I ran into Mark's guide for 9.1, does this apply to 9.2 and/or SLES9 as well? http://lists.suse.com/archive/suse-linux-e/2004-Aug/2476.html
Later, Anders.
I looked this over briefly and wonder if he could have booted to the rescue DVD and run the commands:
# mkdir /mnt/temp # mount /dev/i2o/hda3 /mnt/temp # mount /dev/i2o/hda1 /mnt/temp/boot
add the i2o modules to the INITRD_MODULES line in /mnt/temp/etc/sysconfig/kernel in line
INITRD_MODULES="i2o_core i2o_block" (plus other modules you need) # chroot /mnt/temp # mkinitrd
Would seem to be much easier than adding an IDE drive and installing the OS to do the same thing.
Isn't that the purpose of chroot, to temporarily change you root filesystem tree to something else?
Ken,
You are right of course, and I did post an update to my howto after I learned about chrooting.
Anders,
The 21xx-series of controllers have a readme that says they do not support booting under SuSE. But, I have seen posts elsewhere that indicate updating to the latest firmware and using the Adaptec drivers corrects this.
Adaptec seem to be increasing their Linux support somewhat. New drivers were released in December last year and February this year for some 21xx-series cards.
HTH, Mark
Mark, I did a fresh install of 9.2 on to the 2100S, it went fine up the where rc initiated the "Hardware scan", just after initiating the network adapters, there it went belly-up with the Kernel error. So, booting works, even mounting the file systems, but somewhere along the line it borkes. I reinstalled using the i2o_core and i2o_block drivers, the system now runs fine, but I can't use any of the Adaptec utilities to manage the arrays and have it send me warning e-mails. For that I'll need the Adaptec drivers. Do you happen to know where I can find them? I've surfed around on Adaptec's site but I haven't found anything useful, it seems like the only release pre-built binaries for systems up to kernel 2.4, and the sources doesn't seem to be available either. Anders.
On Tuesday 08 March 2005 08:54, Anders Norrbring wrote:
On Mon, 2005-03-07 at 12:37, Anders Norrbring wrote:
Hiya! I'm trying to get SuSE 9.2 up and running from a system with an
Adaptec
2100S SCSI RAID controller, and I want to run the system entirely on <etc.
I reinstalled using the i2o_core and i2o_block drivers, the system now runs fine, but I can't use any of the Adaptec utilities to manage the arrays and have it send me warning e-mails. For that I'll need the Adaptec drivers.
Do you happen to know where I can find them? I've surfed around on Adaptec's site but I haven't found anything useful, it seems like the only release pre-built binaries for systems up to kernel 2.4, and the sources doesn't seem to be available either.
Anders.
Not more than a couple of weeks back, Phillipp Thomas said this as part of the thread [SLE] Installing SuSE 9.2 onto Adaptec HostRaid:
It's unfortunate that I cannot get hardware raid to work,
Complain to Adaptec who don't want to offer an open source driver or at least the specs to enable the community to come up with a driver. Philipp So it seems maybe Adaptec support is limited by their own policies. Seems a pity. HTH Fergus -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Hiya! I'm trying to get SuSE 9.2 up and running from a system with an
Adaptec
2100S SCSI RAID controller, and I want to run the system entirely on <etc.
I reinstalled using the i2o_core and i2o_block drivers, the system now runs fine, but I can't use any of the Adaptec utilities to manage the arrays and have it send me warning e-mails. For that I'll need the Adaptec drivers.
Do you happen to know where I can find them? I've surfed around on Adaptec's site but I haven't found anything useful, it seems like the only release pre-built binaries for systems up to kernel 2.4, and the sources doesn't seem to be available either.
Anders.
Not more than a couple of weeks back, Phillipp Thomas said this as part of the thread [SLE] Installing SuSE 9.2 onto Adaptec HostRaid:
It's unfortunate that I cannot get hardware raid to work,
Complain to Adaptec who don't want to offer an open source driver or at least the specs to enable the community to come up with a driver.
Philipp
So it seems maybe Adaptec support is limited by their own policies. Seems a pity.
Yep.. They offer me to get the 2130SLP or 2230SLP instead. Which of course would make me swap motherboard as well since those two doesn't work in 32-bit PCI slots. I could fix that, but those controllers cost more than twice the cost of the motherboard. Geee.. They don't want to release newer drivers for any *nix, but they still update the Windows 2000, XP and 2003 drivers. Like any serious server owner would run a Windows server? Anyway, there must be a solution to this somewhere, it's just the question of finding it. I can run i2o_core and i2o_block, but then I can't use the alert system. This really is annoying. Anders.
On Tue, 2005-03-08 at 05:23, Anders Norrbring wrote:
Not more than a couple of weeks back, Phillipp Thomas said this as part of the thread [SLE] Installing SuSE 9.2 onto Adaptec HostRaid:
It's unfortunate that I cannot get hardware raid to work,
Complain to Adaptec who don't want to offer an open source driver or at least the specs to enable the community to come up with a driver.
Philipp
So it seems maybe Adaptec support is limited by their own policies. Seems a pity.
Yep.. They offer me to get the 2130SLP or 2230SLP instead. Which of course would make me swap motherboard as well since those two doesn't work in 32-bit PCI slots. I could fix that, but those controllers cost more than twice the cost of the motherboard. Geee..
They don't want to release newer drivers for any *nix, but they still update the Windows 2000, XP and 2003 drivers. Like any serious server owner would run a Windows server?
Anyway, there must be a solution to this somewhere, it's just the question of finding it.
It's called buying from another vendor. Seems to me that MS has bought off another supplier and forced them to no longer support linux. <opinion> It is a sorry state when one company has the power to tell another company how to run their business without owning any part of that business. How? By threatening to withhold specs, api's... </opinion> -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
check out this website, http://i2o.shadowconnect.com/, these are the guys supporting the i2o driver on linux....joe On Tue, 2005-03-08 at 11:23 +0100, Anders Norrbring wrote:
Hiya! I'm trying to get SuSE 9.2 up and running from a system with an
Adaptec
2100S SCSI RAID controller, and I want to run the system entirely on <etc.
I reinstalled using the i2o_core and i2o_block drivers, the system now runs fine, but I can't use any of the Adaptec utilities to manage the arrays and have it send me warning e-mails. For that I'll need the Adaptec drivers.
Do you happen to know where I can find them? I've surfed around on Adaptec's site but I haven't found anything useful, it seems like the only release pre-built binaries for systems up to kernel 2.4, and the sources doesn't seem to be available either.
Anders.
Not more than a couple of weeks back, Phillipp Thomas said this as part of the thread [SLE] Installing SuSE 9.2 onto Adaptec HostRaid:
It's unfortunate that I cannot get hardware raid to work,
Complain to Adaptec who don't want to offer an open source driver or at least the specs to enable the community to come up with a driver.
Philipp
So it seems maybe Adaptec support is limited by their own policies. Seems a pity.
Yep.. They offer me to get the 2130SLP or 2230SLP instead. Which of course would make me swap motherboard as well since those two doesn't work in 32-bit PCI slots. I could fix that, but those controllers cost more than twice the cost of the motherboard. Geee..
They don't want to release newer drivers for any *nix, but they still update the Windows 2000, XP and 2003 drivers. Like any serious server owner would run a Windows server?
Anyway, there must be a solution to this somewhere, it's just the question of finding it. I can run i2o_core and i2o_block, but then I can't use the alert system. This really is annoying.
Anders.
Subject: [SLE] Re: [clean] RE: [SLE] SuSE 9.2 and Adaptec 2100S SCSI RAID
check out this website, http://i2o.shadowconnect.com/, these are the guys supporting the i2o driver on linux....joe
Yeah.. I know. I was hoping to NOT use those drivers since they don't support the Adaptec alarm and config utilities.
On Tue, 2005-03-08 at 11:23 +0100, Anders Norrbring wrote:
> Hiya! > I'm trying to get SuSE 9.2 up and running from a system with an
Adaptec
> 2100S SCSI RAID controller, and I want to run the system entirely on <etc.
I reinstalled using the i2o_core and i2o_block drivers, the system now runs fine, but I can't use any of the Adaptec utilities to manage the arrays and have it send me warning e-mails. For that I'll need the Adaptec drivers.
Do you happen to know where I can find them? I've surfed around on Adaptec's site but I haven't found anything useful, it seems like the only release pre-built binaries for systems up to kernel 2.4, and the sources doesn't seem to be available either.
Anders.
Not more than a couple of weeks back, Phillipp Thomas said this as part of the thread [SLE] Installing SuSE 9.2 onto Adaptec HostRaid:
It's unfortunate that I cannot get hardware raid to work,
Complain to Adaptec who don't want to offer an open source driver or at least the specs to enable the community to come up with a driver.
Philipp
So it seems maybe Adaptec support is limited by their own policies. Seems a pity.
Yep.. They offer me to get the 2130SLP or 2230SLP instead. Which of course would make me swap motherboard as well since those two doesn't work in 32-bit PCI slots. I could fix that, but those controllers cost more than twice the cost of the motherboard. Geee..
They don't want to release newer drivers for any *nix, but they still update the Windows 2000, XP and 2003 drivers. Like any serious server owner would run a Windows server?
Anyway, there must be a solution to this somewhere, it's just the question of finding it. I can run i2o_core and i2o_block, but then I can't use the alert system. This really is annoying.
Anders.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I posted in the past about problems with the 2200S. I think I've managed to solve my problems. Here's my fix: Flashed the firmware back to 7244 firmware. Booted from a disk that used 2.4 kernel. Installed the driver (followed Adaptec directions) for the 7348/7349 firmware that was released Dec 17th even though Adaptec states it's for the 7348/7349 firmware. My system now boots without problem using hardware raid volumes. I've eliminated the system hangs and very long timeouts that I was experiencing. Adaptec may not support this, but so what, they weren't providing me with even marginally good support as it was. Now the only message I get from the system is that aacraid taints the kernel and that is due to the non-GPL Adaptec driver. I can live with that. At least the system stays up now, and its very responsive. John
On Mon, 2005-03-07 at 12:37, Anders Norrbring wrote:
Hiya! I'm trying to get SuSE 9.2 up and running from a system with an Adaptec 2100S SCSI RAID controller, and I want to run the system entirely on the SCSI arrays.
No luck. Kernel panic after the first reboot after installation. It comes to mounting volumes, then setting up hardware dependencies and wham, there it dies.
After some Googling I ran into Mark's guide for 9.1, does this apply to 9.2 and/or SLES9 as well? http://lists.suse.com/archive/suse-linux-e/2004-Aug/2476.html
Later, Anders.
I looked this over briefly and wonder if he could have booted to the rescue DVD and run the commands:
# mkdir /mnt/temp # mount /dev/i2o/hda3 /mnt/temp # mount /dev/i2o/hda1 /mnt/temp/boot
add the i2o modules to the INITRD_MODULES line in /mnt/temp/etc/sysconfig/kernel in line
INITRD_MODULES="i2o_core i2o_block" (plus other modules you need) # chroot /mnt/temp # mkinitrd
Would seem to be much easier than adding an IDE drive and installing the OS to do the same thing.
Isn't that the purpose of chroot, to temporarily change you root filesystem tree to something else?
I think that would be possible, but that's not really my question. My problem is that it seems like dpt_i2o STILL doesn't work properly with the controller. During boot, when rc comes to "Checking hardware dependencies" everything comes to a halt with a Kernel exception. According to Matt, aacraid should be a replacement for dpt_i2o, but I don't think so, they're used for two different controller types. I merely wonder what's happening with the dpt_i2o driver, is there another version than the one in the Kernel source that works? Anders.
participants (6)
-
Anders Norrbring -
Fergus Wilde -
Joe Brockert -
John Scott -
Ken Schneider -
L. Mark Stone