Re: Adaptec RAID SCSI 2100S
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: DPT Model: 2100SRev: 320P, scsi 0: DPT I2O Driver Version: 1.14/1.14: cmd_per_lun = 210, max_id = 15, max_lun = 7, max_channel = 0 sg_tablesize = 39, irq = 11, OutstandingMsgs = 0 maxfromiopmsgs = 64, maxtoiopmsgs = 210 Devices: Channel = 0, Target = 1, Lun = 0 [root@lala log]# [root@lala log]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: ADAPTEC Model: RAID-1 Rev: 320P Type: Direct-AccessANSI SCSI revision: 02 [root@lala log]# If I want to see each device separately I have to go to the controller's software by pressing ctrl-a at boot time. Juan Pablo Abuyeres On Mon, 14 May 2001, Josh Logan wrote: > > 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 /dev/i2o/hd/dics0/part1 but not > /dev/sda1 (no filesystem). > > I was hoping i2o_scsi would make it appear as a "normal" scsi device, but > I don't think that is happening with the current driver. > > If you are having a different scsi setup I would be interested in trying > to set my system up the same way. Thanks! > > Later, JOSH > > > On Mon, 14 May 2001, Juan Pablo Abuyeres wrote: > > > > > 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. > > > > > > Ok I need to put mroe disks and newer firmware on my card when I have some > > > time > > > > my /dev/dsa is a RAID1 made of two quantum atlas 10K II 18.xGb. > > Unfortunately I have to get this RAID running this week (maybe on > > wednesday) and after that I won't be able to do tests... so.. maybe > > I would have to use 2.2.19 instead of 2.4.4 :-(... > > > > Juan Pablo Abuyeres > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to [EMAIL PROTECTED] > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 /dev/i2o/hd/dics0/part1 but not /dev/sda1 (no filesystem). I was hoping i2o_scsi would make it appear as a "normal" scsi device, but I don't think that is happening with the current driver. If you are having a different scsi setup I would be interested in trying to set my system up the same way. Thanks! Later, JOSH On Mon, 14 May 2001, Juan Pablo Abuyeres wrote: > > > 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. > > > > Ok I need to put mroe disks and newer firmware on my card when I have some > > time > > my /dev/dsa is a RAID1 made of two quantum atlas 10K II 18.xGb. > Unfortunately I have to get this RAID running this week (maybe on > wednesday) and after that I won't be able to do tests... so.. maybe > I would have to use 2.2.19 instead of 2.4.4 :-(... > > Juan Pablo Abuyeres > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
> > 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. > > Ok I need to put mroe disks and newer firmware on my card when I have some > time my /dev/dsa is a RAID1 made of two quantum atlas 10K II 18.xGb. Unfortunately I have to get this RAID running this week (maybe on wednesday) and after that I won't be able to do tests... so.. maybe I would have to use 2.2.19 instead of 2.4.4 :-(... Juan Pablo Abuyeres - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
> 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 OK. I am asking the card for tables and it is telling me it doesnt have them > May 14 16:29:12 lala kernel: scsi0 : i2o/iop0 Ok it found a scsi mode IOP > May 14 16:29:12 lala kernel: sda : sense not available. That might be my bug > May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. > May 14 16:29:12 lala kernel: sdb : READ CAPACITY failed. And it struggles for some reason to get going. > May 14 16:29:12 lala kernel: Claim Claimed Mount Lock Ready. > May 14 16:29:12 lala kernel: Flushing...Unlocking...Unlocked. > May 14 16:29:12 lala kernel: Unclaim Debugging.. > 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 ? > And issuing a fdisk: Ok the geometry is different > 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. Ok I need to put mroe disks and newer firmware on my card when I have some time - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 don't have a spare disk to do the trick > > :/) > > > > Ideas? > > "Mine works" 8) > > Send me the messages. I'd really like to see whats up you asked for it :-) This is a RedHat 7.1 with kernel-2.4.4-ac9 May 14 16:29:12 lala kernel: SCSI subsystem driver Revision: 1.00 May 14 16:29:12 lala kernel: request_module[scsi_hostadapter]: Root fs not mounted May 14 16:29:12 lala kernel: i2o_scsi.c: Version 0.0.1 May 14 16:29:12 lala kernel: chain_pool: 2048 bytes @ c14b7800 May 14 16:29:12 lala kernel: (512 byte buffers X 4 can_queue X 1 i2o controllers) 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 May 14 16:29:12 lala kernel: scsi0 : i2o/iop0 May 14 16:29:12 lala kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6 May 14 16:29:12 lala kernel: Type: Direct-Access ANSI SCSI revision: 03 May 14 16:29:12 lala kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6 May 14 16:29:12 lala kernel: Type: Direct-Access ANSI SCSI revision: 03 May 14 16:29:12 lala kernel: Attached scsi disk sda at scsi0, channel 0, id 1, lun 0 May 14 16:29:12 lala kernel: Attached scsi disk sdb at scsi0, channel 0, id 2, lun 0 May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: sda : READ CAPACITY failed. May 14 16:29:12 lala keytable: May 14 16:29:12 lala kernel: sda : status = 0, message = 00, host = 7, driver = 27 May 14 16:29:12 lala keytable: Loading system font: May 14 16:29:12 lala kernel: sda : sense not available. May 14 16:29:12 lala kernel: sda : block size assumed to be 512 bytes, disk size 1GB. May 14 16:29:12 lala kernel: sda: sda1 sda2 < sda5 sda6 > May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: sdb : READ CAPACITY failed. May 14 16:29:12 lala kernel: sdb : status = 0, message = 00, host = 7, driver = 27 May 14 16:29:12 lala kernel: sdb : sense not available. May 14 16:29:12 lala kernel: sdb : block size assumed to be 512 bytes, disk size 1GB. May 14 16:29:12 lala kernel: sdb: sdb1 sdb2 < sdb5 sdb6 > May 14 16:29:12 lala kernel: NET4: Linux TCP/IP 1.0 for NET4.0 May 14 16:29:12 lala kernel: IP Protocols: ICMP, UDP, TCP, IGMP May 14 16:29:12 lala kernel: IP: routing cache hash table of 2048 buckets, 16Kbytes May 14 16:29:12 lala kernel: TCP: Hash tables configured (established 16384 bind 16384) May 14 16:29:12 lala kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. May 14 16:29:12 lala kernel: VFS: Mounted root (ext2 filesystem) readonly. May 14 16:29:12 lala kernel: Freeing unused kernel memory: 208k freed May 14 16:29:12 lala kernel: Adding Swap: 265032k swap-space (priority -1) May 14 16:29:12 lala kernel: Claim Claimed Mount Lock Ready. May 14 16:29:12 lala kernel: Flushing...Unlocking...Unlocked. May 14 16:29:12 lala kernel: Unclaim May 14 16:29:12 lala kernel: Claim Claimed Mount Lock Ready. May 14 16:29:12 lala
Adaptec RAID SCSI 2100S
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 http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
> 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 > :/) > > Ideas? "Mine works" 8) Send me the messages. I'd really like to see whats up - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 to 2.4.4ac8 or higher for dpt i2o_scsi and 2.4.4ac5 or so or higher > for dpt i2o_block 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 :/) Ideas? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 to 2.4.4ac8 or higher for dpt i2o_scsi and 2.4.4ac5 or so or higher for dpt i2o_block 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 :/) Ideas? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 :/) Ideas? Mine works 8) Send me the messages. I'd really like to see whats up - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Adaptec RAID SCSI 2100S
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 http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 don't have a spare disk to do the trick :/) Ideas? Mine works 8) Send me the messages. I'd really like to see whats up you asked for it :-) This is a RedHat 7.1 with kernel-2.4.4-ac9 May 14 16:29:12 lala kernel: SCSI subsystem driver Revision: 1.00 May 14 16:29:12 lala kernel: request_module[scsi_hostadapter]: Root fs not mounted May 14 16:29:12 lala kernel: i2o_scsi.c: Version 0.0.1 May 14 16:29:12 lala kernel: chain_pool: 2048 bytes @ c14b7800 May 14 16:29:12 lala kernel: (512 byte buffers X 4 can_queue X 1 i2o controllers) 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 May 14 16:29:12 lala kernel: scsi0 : i2o/iop0 May 14 16:29:12 lala kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6 May 14 16:29:12 lala kernel: Type: Direct-Access ANSI SCSI revision: 03 May 14 16:29:12 lala kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6 May 14 16:29:12 lala kernel: Type: Direct-Access ANSI SCSI revision: 03 May 14 16:29:12 lala kernel: Attached scsi disk sda at scsi0, channel 0, id 1, lun 0 May 14 16:29:12 lala kernel: Attached scsi disk sdb at scsi0, channel 0, id 2, lun 0 May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: sda : READ CAPACITY failed. May 14 16:29:12 lala keytable: May 14 16:29:12 lala kernel: sda : status = 0, message = 00, host = 7, driver = 27 May 14 16:29:12 lala keytable: Loading system font: May 14 16:29:12 lala kernel: sda : sense not available. May 14 16:29:12 lala kernel: sda : block size assumed to be 512 bytes, disk size 1GB. May 14 16:29:12 lala kernel: sda: sda1 sda2 sda5 sda6 May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: scsi0 channel 0 : resetting for second half of retries. May 14 16:29:12 lala kernel: SCSI bus is being reset for host 0 channel 0. May 14 16:29:12 lala kernel: i2o_scsi: Attempting to reset the bus. May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: sdb : READ CAPACITY failed. May 14 16:29:12 lala kernel: sdb : status = 0, message = 00, host = 7, driver = 27 May 14 16:29:12 lala kernel: sdb : sense not available. May 14 16:29:12 lala kernel: sdb : block size assumed to be 512 bytes, disk size 1GB. May 14 16:29:12 lala kernel: sdb: sdb1 sdb2 sdb5 sdb6 May 14 16:29:12 lala kernel: NET4: Linux TCP/IP 1.0 for NET4.0 May 14 16:29:12 lala kernel: IP Protocols: ICMP, UDP, TCP, IGMP May 14 16:29:12 lala kernel: IP: routing cache hash table of 2048 buckets, 16Kbytes May 14 16:29:12 lala kernel: TCP: Hash tables configured (established 16384 bind 16384) May 14 16:29:12 lala kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. May 14 16:29:12 lala kernel: VFS: Mounted root (ext2 filesystem) readonly. May 14 16:29:12 lala kernel: Freeing unused kernel memory: 208k freed May 14 16:29:12 lala kernel: Adding Swap: 265032k swap-space (priority -1) May 14 16:29:12 lala kernel: Claim Claimed Mount Lock Ready. May 14 16:29:12 lala kernel: Flushing...Unlocking...Unlocked. May 14 16:29:12 lala kernel: Unclaim May 14 16:29:12 lala kernel: Claim Claimed Mount Lock Ready. May 14 16:29:12 lala kernel:
Re: Adaptec RAID SCSI 2100S
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 OK. I am asking the card for tables and it is telling me it doesnt have them May 14 16:29:12 lala kernel: scsi0 : i2o/iop0 Ok it found a scsi mode IOP May 14 16:29:12 lala kernel: sda : sense not available. That might be my bug May 14 16:29:12 lala kernel: i2o_scsi: bus reset reply. May 14 16:29:12 lala kernel: sdb : READ CAPACITY failed. And it struggles for some reason to get going. May 14 16:29:12 lala kernel: Claim Claimed Mount Lock Ready. May 14 16:29:12 lala kernel: Flushing...Unlocking...Unlocked. May 14 16:29:12 lala kernel: Unclaim Debugging.. 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 ? And issuing a fdisk: Ok the geometry is different 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. Ok I need to put mroe disks and newer firmware on my card when I have some time - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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. Ok I need to put mroe disks and newer firmware on my card when I have some time my /dev/dsa is a RAID1 made of two quantum atlas 10K II 18.xGb. Unfortunately I have to get this RAID running this week (maybe on wednesday) and after that I won't be able to do tests... so.. maybe I would have to use 2.2.19 instead of 2.4.4 :-(... Juan Pablo Abuyeres - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 /dev/i2o/hd/dics0/part1 but not /dev/sda1 (no filesystem). I was hoping i2o_scsi would make it appear as a normal scsi device, but I don't think that is happening with the current driver. If you are having a different scsi setup I would be interested in trying to set my system up the same way. Thanks! Later, JOSH On Mon, 14 May 2001, Juan Pablo Abuyeres wrote: 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. Ok I need to put mroe disks and newer firmware on my card when I have some time my /dev/dsa is a RAID1 made of two quantum atlas 10K II 18.xGb. Unfortunately I have to get this RAID running this week (maybe on wednesday) and after that I won't be able to do tests... so.. maybe I would have to use 2.2.19 instead of 2.4.4 :-(... Juan Pablo Abuyeres - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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: DPT Model: 2100SRev: 320P, scsi 0: DPT I2O Driver Version: 1.14/1.14: cmd_per_lun = 210, max_id = 15, max_lun = 7, max_channel = 0 sg_tablesize = 39, irq = 11, OutstandingMsgs = 0 maxfromiopmsgs = 64, maxtoiopmsgs = 210 Devices: Channel = 0, Target = 1, Lun = 0 [root@lala log]# [root@lala log]# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: ADAPTEC Model: RAID-1 Rev: 320P Type: Direct-AccessANSI SCSI revision: 02 [root@lala log]# If I want to see each device separately I have to go to the controller's software by pressing ctrl-a at boot time. Juan Pablo Abuyeres On Mon, 14 May 2001, Josh Logan wrote: 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 /dev/i2o/hd/dics0/part1 but not /dev/sda1 (no filesystem). I was hoping i2o_scsi would make it appear as a normal scsi device, but I don't think that is happening with the current driver. If you are having a different scsi setup I would be interested in trying to set my system up the same way. Thanks! Later, JOSH On Mon, 14 May 2001, Juan Pablo Abuyeres wrote: 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. Ok I need to put mroe disks and newer firmware on my card when I have some time my /dev/dsa is a RAID1 made of two quantum atlas 10K II 18.xGb. Unfortunately I have to get this RAID running this week (maybe on wednesday) and after that I won't be able to do tests... so.. maybe I would have to use 2.2.19 instead of 2.4.4 :-(... Juan Pablo Abuyeres - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
> 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 2.4.4ac5 or so or higher for dpt i2o_block - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Adaptec RAID SCSI 2100S
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 module (dpt_i2o) which works fine (only?) with 2.2.14. Adaptec web site says next to nothing about current linux drivers for this card. I don't understand why they don't just provide a patch against current 2.2.x and 2.4.x ... The best I've found is http://people.redhat.com/tcallawa/dpt/, where they provide a rpm packaged 2.2.19 kernel already with support for adaptec 2100S, and works :-) ... (where did they get the driver??? mistery...) So, is it possible to make it work under 2.4.4? :-) ps: has anyone the patch againt 2.2.x? (it would be nice to have the patch, although I already have 2.2.19 with support) Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Adaptec RAID SCSI 2100S
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 module (dpt_i2o) which works fine (only?) with 2.2.14. Adaptec web site says next to nothing about current linux drivers for this card. I don't understand why they don't just provide a patch against current 2.2.x and 2.4.x ... The best I've found is http://people.redhat.com/tcallawa/dpt/, where they provide a rpm packaged 2.2.19 kernel already with support for adaptec 2100S, and works :-) ... (where did they get the driver??? mistery...) So, is it possible to make it work under 2.4.4? :-) ps: has anyone the patch againt 2.2.x? (it would be nice to have the patch, although I already have 2.2.19 with support) Thanks. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec RAID SCSI 2100S
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 2.4.4ac5 or so or higher for dpt i2o_block - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
