RE: 3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Erwin Cloostermans]

I have done something wrong i guess :-(

I did
/sbin/mkinitrd -v -f /boot/initrd-2.6.8-1.521smp.img 2.6.8-1.521smp

In my modprobe.conf is only
alias scsi_host_adapter 3w-9xxx

If I try to reboot the boot process stops with the following error messages

idel: I/O resource 0x170-0x177 not free.
idel: ports already in use, skipping probe
Red Hat nash version 3.5.22 starting
mkrootdev: label / not found
mount: error 2 on mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Kernel panic: No init found. Try passing init- option to kernel.

Any idea how I can solve this ?

Erwin

3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Markku Kolkka]

Erwin Cloostermans kirjoitti viestissään (lähetysaika perjantai, 
24. syyskuuta 2004 00:41):
> In my modprobe.conf is only
> alias scsi_host_adapter 3w-9xxx
>
> If I try to reboot the boot process stops with the following
> error messages
>
> idel: I/O resource 0x170-0x177 not free.
> idel: ports already in use, skipping probe
> Red Hat nash version 3.5.22 starting
> mkrootdev: label / not found
> mount: error 2 on mounting ext3
> pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> umount /initrd/proc failed: 2
> Kernel panic: No init found. Try passing init- option to
> kernel.

You removed the entry for your motherboard  SATA adapter 
(ata_piix) from modprobe.conf, so the root filesystem can't be 
accessed.

3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Erwin Cloostermans]

You removed the entry for your motherboard  SATA adapter 
(ata_piix) from modprobe.conf, so the root filesystem can't be 
accessed.

3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Erwin Cloostermans]

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: [e-mail] [mailto:[e-mail]]
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.

3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Aly Dharshi]

I guess that you can actually write a script to do this as the last task in the 
startup or at the appropriate start up point. So the script would contain 
exactly y what you have for command line steps.

This isn't the most elegant way, but it will surely work. I am sure that someone 
would probably have a better way to go.

Cheers,

Aly.

Erwin Cloostermans wrote:
> 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: [e-mail] [mailto:[e-mail]]
> 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.

3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Alexander Dalloz]

Am Do, den 30.09.2004 schrieb Erwin Cloostermans um 21:12:
> In a terminal window I typed
>    /sbin/mkinitrd -v -f /boot/initrd/2.6.8-1.521smp.img 2.6.6-1.521smp
> TIA, Erwin

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

3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Alexander Dalloz]

Am Do, den 30.09.2004 schrieb Alexander Dalloz um 22:00:
> > In a terminal window I typed
> >    /sbin/mkinitrd -v -f /boot/initrd/2.6.8-1.521smp.img 2.6.6-1.521smp
> 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.

Addition to my maybe misleading comment: so the /etc/grub.conf entry is

initrd /initrd-2.6.8-1.521smp.img

and not

initrd /initrd/initrd-2.6.8-1.521smp.img

which would be necessary following your mkinitrd command line.

Alexander

3ware 9000 Series SATA Raid and Fedora Core 2 ?

[Erwin Cloostermans]

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