I have yet to successfully install SuSE8.1 using Autoyast. I have tested 3 different machines. One with aic7xxx, another with IBM ServeRAID, and a 3rd with aic7xxx as the OS drive and qla2200 for other filesystems. All 3 systems install, but after the initial reboot, none boot. They all fail with different errors, but they look related to SCSI resets failing on the ips.o, aic7xxx.o, and qla2200.o modules. BTW, all three systems work great with SLES8. Anyone else experience this?
* Egan Ford <egan@sense.net> [Jan 12. 2003 21:05]:
I have yet to successfully install SuSE8.1 using Autoyast. I have tested 3 different machines. One with aic7xxx, another with IBM ServeRAID, and a 3rd with aic7xxx as the OS drive and qla2200 for other filesystems.
All 3 systems install, but after the initial reboot, none boot. They all fail with different errors, but they look related to SCSI resets failing on the ips.o, aic7xxx.o, and qla2200.o modules.
BTW, all three systems work great with SLES8.
Anyone else experience this?
The only way this can happen is when the initrd is created without the kernel modules for the above drivers. Please try with the kernel you used to boot SLES with and see if it works. I suspect there is an issue with kernel used to install 8.1 wrt aic7xxx. Would it be possible to send me the y2log files? Anas
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Egan Ford wrote:
I have yet to successfully install SuSE8.1 using Autoyast. I have tested 3 different machines. One with aic7xxx, another with IBM ServeRAID, and a 3rd with aic7xxx as the OS drive and qla2200 for other filesystems.
All 3 systems install, but after the initial reboot, none boot. They all fail with different errors, but they look related to SCSI resets failing on the ips.o, aic7xxx.o, and qla2200.o modules.
BTW, all three systems work great with SLES8.
Anyone else experience this?
I had similar experience on a system using an Adaptec RAID controller. In 8.1, it would hang during boot half-way through initialization of the i2o module. 8.0 was fine. I had a perfect Autoyast2 autoinstallation setup for 8.0, but wanted to install 8.1. 8.1 would not even install manually due to the hang. I could boot somewhat on various rescue-type floppies, but I don't remember the exact details. My eventual workaround was to install 8.0, then do a manual upgrade to 8.1. I have done several kernel rebuilds since, with different kernel versions, and no problems. I am not sure that I trust the modules.conf that comes with 8.1, for my system, at least. My system would be using the aic7xxx driver if it weren't for the RAID controller, and perhaps there is some commonality, there. Good luck, John Young
* John Young <john_young@sonic.net> [Jan 13. 2003 10:44]:
Egan Ford wrote:
I have yet to successfully install SuSE8.1 using Autoyast. I have tested 3 different machines. One with aic7xxx, another with IBM ServeRAID, and a 3rd with aic7xxx as the OS drive and qla2200 for other filesystems.
All 3 systems install, but after the initial reboot, none boot. They all fail with different errors, but they look related to SCSI resets failing on the ips.o, aic7xxx.o, and qla2200.o modules.
BTW, all three systems work great with SLES8.
Anyone else experience this?
I had similar experience on a system using an Adaptec RAID controller. In 8.1, it would hang during boot half-way through initialization of the i2o module. 8.0 was fine. I had a perfect Autoyast2 autoinstallation setup for 8.0, but wanted to install 8.1. 8.1 would not even install manually due to the hang. I could boot somewhat on various rescue-type floppies, but I don't remember the exact details.
My eventual workaround was to install 8.0, then do a manual upgrade to 8.1. I have done several kernel rebuilds since, with different kernel versions, and no problems. I am not sure that I trust the modules.conf that comes with 8.1, for my system, at least. My system would be using the aic7xxx driver if it weren't for the RAID controller, and perhaps there is some commonality, there.
Hmm, sound like a non-autoinstall related problem to me after i have check the logs from Egan. Could you please try booting with acpi=off? Or use the dafe settings if available in the bootloader. Anas
Good luck, John Young
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Anas Nashif wrote:
Hmm, sound like a non-autoinstall related problem to me after i have check the logs from Egan. Could you please try booting with acpi=off? Or use the dafe settings if available in the bootloader.
Yes, I believe you are correct. The host of which I spoke does now boot with acpi=off, but I'm afraid I no longer have the opportunity to experiment with installations on it (it's been moved into production). Since in my case I, too, believed it was a non-autoinstall related problem, I had checked with regular SuSE support about it. Help was not available since RAID was involved (which is understandable), so I had to find other ways around it. I know that there was some problem that went away after I did away with the SuSE modules.conf and replaced it with a much more tailored (and simpler) version, but unfortunately I can't remember for sure if it was the SCSI RAID boot hanging problem or not. Thanks for your reply! John Young
participants (3)
-
Anas Nashif -
Egan Ford -
John Young