Erwin Cloostermans kirjoitti viestissään (lähetysaika perjantai, 24. syyskuuta 2004 00:41): You removed the entry for your motherboard SATA adapter (ata_piix) from modprobe.conf, so the root filesystem can't be accessed. -- Markku Kolkka markku.kolkka(a)iki.fi

Here I'm again. I still have some problems. I did a fresh install from the cd images available as iso files (kernel 2.6.5-1.358) I edited /etc/yum.conf (to download from a local mirror server instead of the primary fedora server) Updated my system with yum update to kernel 2.6.8-1.521 In /etc/modprobe.conf I replaced alias scsi_hostadapter1 3w-xxxx With alias scsi_hostadapter1 3w-9xxx In a terminal window I typed /sbin/modprobe -r 3w-xxxx /sbin/modprobe 3w-9xxx To remove the old driver and load the new one At that moment I'm able to see my raid disk as /dev/sdb (The sata drive connected to the main board is /dev/sda) In a terminal window I typed /sbin/mkinitrd -v -f /boot/initrd/2.6.8-1.521smp.img 2.6.6-1.521smp But after a reboot the old driver 3w-xxxx is loaded again and /dev/sdb is gone In kernel startup log I see a message 3ware Storage Controller device driver for Linux v.1.26.00.039 3w-xxxx No cards found I did this for both kernels: 2.6.8-1.521smp and 2.6.8-1.521 How can I make my Linux load the 3w-9xxx driver at startup instead of the old 3w-xxxx ???? TIA, Erwin -----Original Message----- From: fedora-list-bounces(a)redhat.com [mailto:fedora-list-bounces@redhat.com] On Behalf Of Erwin Cloostermans Sent: vrijdag 24 september 2004 0:09 To: 'For users of Fedora Core releases' Subject: RE: 3ware 9000 Series SATA Raid and Fedora Core 2 ? You removed the entry for your motherboard SATA adapter (ata_piix) from modprobe.conf, so the root filesystem can't be accessed. -- Markku Kolkka markku.kolkka(a)iki.fi How stupid can one be :-(( At least now I know what the first scsi_host_adapter was for :-) Erwin -- fedora-list mailing list fedora-list(a)redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

Am Do, den 30.09.2004 schrieb Erwin Cloostermans um 21:12: And this initial ramdisk is really used and not the older one with the other 3ware module? I ask because /boo/initrd/ is not a default path that Fedora uses. It works but you have to be sure the path to the initrd.img file in the grub.conf matches this path. The default path - used in /etc/grub.conf - is /boot/initrd-2.6.8-1.521smp.img. Alexander -- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp Serendipity 21:56:55 up 1 day, 23 users, load average: 0.67, 0.32, 0.28

And this initial ramdisk is really used and not the older one with the other 3ware module? I ask because /boo/initrd/ is not a default path that Fedora uses. It works but you have to be sure the path to the initrd.img file in the grub.conf matches this path. The default path - used in /etc/grub.conf - is /boot/initrd-2.6.8-1.521smp.img. Alexander /etc/grub.conf contains Initrd /initrd-2.6.8-1.521smp.img I made the ramdisk again with /sbin/mkinitrd -v - f /boot/initrd-2.6.8-1.521smp.img 2.6.8-1.521smp All went well and there were some messages saying the 3w-9xxx module is used After a reboot /dev/sdb is stil there ! After shutdown/power off/power on, everything still ok ! In /etc/sysconfig/hwconf there is driver: 3w-xxxx That's also what I see when using the hardware browser GUI, but it seems to work anyway. Thanks a lot to everybody who helped me out on this. It's a nice experience to meet people who are willing to help without having to pay them. I've learned a lot from your answers. Now I'm going to find out how to mount the array to my file system and share it with a windows client. I guess this will not be my last message :-). Erwin