Before merging both hard disks I saw each of them as a separate SCSI
device, at boot time and when the system booted up. After building the
RAID1, when the system boots I only see one RAID device recognized, and so
do I when linux recognizes it.
[root@lala log]# cat /proc/scsi/dpt_i2o/0
Vendor:
What makes you think /dev/sda is the raid? For me cat /proc/scsi/scsi
lists all 4 drives which, to me, implies that it is raw.
fdisk could not partition the raid by default. I needed to use sfdisk the
first time. After that fdisk worked fine.
If I have both modules loaded I can mount
> > Then When I tried to fdisk /dev/sda (/dev/sda is a RAID1 of two
> > Quantum disks) syslog shows this:
>
> is /dev/sda the raid or the disks raw ?
/dev/sda is the RAID1
> > So, I don't know if I'm doing something wrong or what, but I haven't been
> > able to get it working on 2.4.4 yet...
> May 14 16:29:12 lala kernel: PARAMS_GET - Error:
> May 14 16:29:12 lala kernel: ErrorInfoSize = 0x01, BlockStatus = 0x08,
> BlockSize = 0x0002
> May 14 16:29:12 lala kernel: PARAMS_GET - Error:
> May 14 16:29:12 lala kernel: ErrorInfoSize = 0x01, BlockStatus = 0x08,
> BlockSize = 0x0002
On Mon, 14 May 2001, Alan Cox wrote:
> > well, I applied 2.4.4ac8 (I couldn't find ac9) and I still have only
> > errors when recognizing the hardware. The long waiting is gone. I will try
> > to send the messages somehow. They were not saved on log files because it
> > couldn't mount the
linux.adaptec.com is where they put linux stuff.
Ask [EMAIL PROTECTED] for the latest 2.4.x kernel patch/driver for dpt
i2o controllers.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
> well, I applied 2.4.4ac8 (I couldn't find ac9) and I still have only
> errors when recognizing the hardware. The long waiting is gone. I will try
> to send the messages somehow. They were not saved on log files because it
> couldn't mount the devices (and I don't have a spare disk to do the
On Mon, 14 May 2001, Alan Cox wrote:
> > I'm trying to make this card work under 2.4.4, but I couldn't find a patch
> > anywhere to get it working under 2.4.x nor on 2.2.x. I tried with the I2O
> > kernel support, but it didn't work, it only reported errors after a pretty
> > long waiting :)
>
>
On Mon, 14 May 2001, Alan Cox wrote:
I'm trying to make this card work under 2.4.4, but I couldn't find a patch
anywhere to get it working under 2.4.x nor on 2.2.x. I tried with the I2O
kernel support, but it didn't work, it only reported errors after a pretty
long waiting :)
You need
well, I applied 2.4.4ac8 (I couldn't find ac9) and I still have only
errors when recognizing the hardware. The long waiting is gone. I will try
to send the messages somehow. They were not saved on log files because it
couldn't mount the devices (and I don't have a spare disk to do the trick
linux.adaptec.com is where they put linux stuff.
Ask [EMAIL PROTECTED] for the latest 2.4.x kernel patch/driver for dpt
i2o controllers.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, 14 May 2001, Alan Cox wrote:
well, I applied 2.4.4ac8 (I couldn't find ac9) and I still have only
errors when recognizing the hardware. The long waiting is gone. I will try
to send the messages somehow. They were not saved on log files because it
couldn't mount the devices (and I
May 14 16:29:12 lala kernel: PARAMS_GET - Error:
May 14 16:29:12 lala kernel: ErrorInfoSize = 0x01, BlockStatus = 0x08,
BlockSize = 0x0002
May 14 16:29:12 lala kernel: PARAMS_GET - Error:
May 14 16:29:12 lala kernel: ErrorInfoSize = 0x01, BlockStatus = 0x08,
BlockSize = 0x0002
This is
Then When I tried to fdisk /dev/sda (/dev/sda is a RAID1 of two
Quantum disks) syslog shows this:
is /dev/sda the raid or the disks raw ?
/dev/sda is the RAID1
So, I don't know if I'm doing something wrong or what, but I haven't been
able to get it working on 2.4.4 yet... please help.
What makes you think /dev/sda is the raid? For me cat /proc/scsi/scsi
lists all 4 drives which, to me, implies that it is raw.
fdisk could not partition the raid by default. I needed to use sfdisk the
first time. After that fdisk worked fine.
If I have both modules loaded I can mount
Before merging both hard disks I saw each of them as a separate SCSI
device, at boot time and when the system booted up. After building the
RAID1, when the system boots I only see one RAID device recognized, and so
do I when linux recognizes it.
[root@lala log]# cat /proc/scsi/dpt_i2o/0
Vendor:
> I'm trying to make this card work under 2.4.4, but I couldn't find a patch
> anywhere to get it working under 2.4.x nor on 2.2.x. I tried with the I2O
> kernel support, but it didn't work, it only reported errors after a pretty
> long waiting :)
You need to 2.4.4ac8 or higher for dpt i2o_scsi
hi,
I'm trying to make this card work under 2.4.4, but I couldn't find a patch
anywhere to get it working under 2.4.x nor on 2.2.x. I tried with the I2O
kernel support, but it didn't work, it only reported errors after a pretty
long waiting :)
The CDROM the card comes with brings a precompiled
hi,
I'm trying to make this card work under 2.4.4, but I couldn't find a patch
anywhere to get it working under 2.4.x nor on 2.2.x. I tried with the I2O
kernel support, but it didn't work, it only reported errors after a pretty
long waiting :)
The CDROM the card comes with brings a precompiled
I'm trying to make this card work under 2.4.4, but I couldn't find a patch
anywhere to get it working under 2.4.x nor on 2.2.x. I tried with the I2O
kernel support, but it didn't work, it only reported errors after a pretty
long waiting :)
You need to 2.4.4ac8 or higher for dpt i2o_scsi and
20 matches
Mail list logo
