|
List Info
Thread: Maxtronic SCSI-to-SATA Array on Dell 2950
|
|
| Maxtronic SCSI-to-SATA Array on Dell
2950 |
  United States |
2008-05-29 08:34:48 |
I'm attempting to move a previously working Maxtronic
SA-3340S
SCSI-to-SATA disk array from a Sun Sparc system to a RedHat
5.2 system
running on Dell 2950 hardware.
While I don't expect, of course, to get at the data on the
array, I would
like to deploy it.
The Dell sees the array, and /var/log/messages reports:
May 29 08:40:35 s31e066 kernel: SCSI device sdb: 2925232128
512-byte hdwr
sectors (1497719 MB
May 29 08:40:35 s31e066 kernel: sdb: Write Protect is off
May 29 08:40:35 s31e066 kernel: SCSI device sdb: drive
cache: write back
May 29 08:40:35 s31e066 kernel: SCSI device sdb: 2925232128
512-byte hdwr
sectors (1497719 MB)
May 29 08:40:35 s31e066 kernel: sdb: Write Protect is off
May 29 08:40:35 s31e066 kernel: SCSI device sdb: drive
cache: write back
May 29 08:40:35 s31e066 kernel: sdb: sdb1 sdb9
May 29 08:40:35 s31e066 kernel: sd 2:0:0:0: Attached scsi
disk sdb
Despite the indication scsi disk sdb was
"attached," and the presence of
sdb device files in /dev, the system reports:
# fdisk /dev/sdb
Unable to open /dev/sdb
There are extensive, repeated dmesg entries, however:
scsi2 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
<Adaptec 39320A Ultra320 SCSI adapter>
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X
101-133Mhz, 512
SCBs
Vendor: Model: Rev: R0.0
Type: Direct-Access ANSI SCSI
revision: 04
target2:0:0: asynchronous
scsi2:A:0:0: Tagged Queuing enabled. Depth 4
target2:0:0: Beginning Domain Validation
target2:0:0: wide asynchronous
target2:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RTI
WRFLOW PCOMP
(6.25 ns,
offset 127)
scsi 2:0:0:0: Attempting to queue an ABORT message:CDB: 0x12
0x0 0x0 0x0
0x40 0x0
scsi2: At time of recovery, card was not paused
>>>>>>>>>>>>>>>
>>> Dump Card State Begins
<<<<<<<<<<<<<<<
<<
scsi2: Dumping Card State at program address 0x24 Mode 0x22
Card was paused
[ lengthy hex messages elided ]
<<<<<<<<<<<<<<<
<< Dump Card State Ends
>>>>>>>>>>>>>>>
>>>
scsi2:0:0:0: Cmd aborted from QINFIFO
scsi 2:0:0:0: Attempting to queue an ABORT message:CDB: 0x0
0x0 0x0 0x0
0x0 0x0
--
Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court
UNIX System Admin Consulting | Owings Mills, MD 21117
http://www.tkevans.com/
| 443-394-3864
http://www.come-here.c
om/News/ | tkevans tkevans.com
_______________________________________________
rhelv5-list mailing list
rhelv5-list redhat.com
h
ttps://www.redhat.com/mailman/listinfo/rhelv5-list
|
|
| Re: Maxtronic SCSI-to-SATA Array on
Dell 2950 |

|
2008-05-29 08:48:38 |
|
On 5/29/08, Tim Evans < tkevans tkevans.com">tkevans tkevans.com> wrote:
I'm attempting to move a previously working Maxtronic SA-3340S SCSI-to-SATA disk array from a Sun Sparc system to a RedHat 5.2 system
running on Dell 2950 hardware.
While I don't expect, of course, to get at the data on the array, I would like to deploy it.
The Dell sees the array, and /var/log/messages reports:
May 29 08:40:35 s31e066 kernel: SCSI device sdb: 2925232128 512-byte hdwr
sectors (1497719 MB
May 29 08:40:35 s31e066 kernel: sdb: Write Protect is off
May 29 08:40:35 s31e066 kernel: SCSI device sdb: drive cache: write back
May 29 08:40:35 s31e066 kernel: SCSI device sdb: 2925232128 512-byte hdwr
sectors (1497719 MB)
May 29 08:40:35 s31e066 kernel: sdb: Write Protect is off
May 29 08:40:35 s31e066 kernel: SCSI device sdb: drive cache: write back
May 29 08:40:35 s31e066 kernel: sdb: sdb1 sdb9
May 29 08:40:35 s31e066 kernel: sd 2:0:0:0: Attached scsi disk sdb
Despite the indication scsi disk sdb was "attached," and the presence of sdb device files in /dev, the system reports:
# fdisk /dev/sdb
Unable to open /dev/sdb
There are extensive, repeated dmesg entries, however:
scsi2 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0 <Adaptec 39320A Ultra320 SCSI adapter> aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512
SCBs
Vendor: Model: Rev: R0.0 Type: Direct-Access ANSI SCSI revision: 04 target2:0:0: asynchronous scsi2:A:0:0: Tagged Queuing enabled. Depth 4 target2:0:0: Beginning Domain Validation
target2:0:0: wide asynchronous target2:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RTI WRFLOW PCOMP (6.25 ns, offset 127) scsi 2:0:0:0: Attempting to queue an ABORT message:CDB: 0x12 0x0 0x0 0x0 0x40 0x0
scsi2: At time of recovery, card was not paused >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< scsi2: Dumping Card State at program address 0x24 Mode 0x22
Card was paused [ lengthy hex messages elided ] <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> scsi2:0:0:0: Cmd aborted from QINFIFO
scsi 2:0:0:0: Attempting to queue an ABORT message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0 --
Would you be able to re-initialize the array?
&nb sp;
|
| Re: Maxtronic SCSI-to-SATA Array on
Dell 2950 |
  United States |
2008-05-29 08:52:28 |
solarflow99 wrote:
> Would you be able to re-initialize the array?
You mean as if it just came out of the box new, right? If
so, yes I can;
the old Solaris filesystem there is of no use.
--
Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court
UNIX System Admin Consulting | Owings Mills, MD 21117
http://www.tkevans.com/
| 443-394-3864
http://www.come-here.c
om/News/ | tkevans tkevans.com
_______________________________________________
rhelv5-list mailing list
rhelv5-list redhat.com
h
ttps://www.redhat.com/mailman/listinfo/rhelv5-list
|
|
| Re: Maxtronic SCSI-to-SATA Array on
Dell 2950 |

|
2008-05-29 09:01:21 |
|
On 5/29/08, Tim Evans < tkevans tkevans.com">tkevans tkevans.com> wrote:
solarflow99 wrote:
> Would you be able to re-initialize the array?
You mean as if it just came out of the box new, right? If so, yes I can;
the old Solaris filesystem there is of no use.
--
thats good then, maybe it just needs to be initialized in the 2950, its worth trying at least. Perhaps there might be a firmware update for it too. I guess you're trying to use this controller to save costs right?
|
| Re: Maxtronic SCSI-to-SATA Array on
Dell 2950 |
  United States |
2008-05-29 09:14:44 |
solarflow99 wrote:
> thats good then, maybe it just needs to be initialized
in the 2950, its
> worth trying at least.
OK, I will. Stay tuned.
> too. I guess you're trying to use this controller to
save costs right?
Seems a shame not to use it, since it's right here using
electricity.
Thanks.
--
Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court
UNIX System Admin Consulting | Owings Mills, MD 21117
http://www.tkevans.com/
| 443-394-3864
http://www.come-here.c
om/News/ | tkevans tkevans.com
_______________________________________________
rhelv5-list mailing list
rhelv5-list redhat.com
h
ttps://www.redhat.com/mailman/listinfo/rhelv5-list
|
|
| Re: Maxtronic SCSI-to-SATA Array on
Dell 2950 |
  United States |
2008-05-29 14:57:33 |
>> solarflow99 wrote:
>>
>> > Would you be able to re-initialize the array?
>>
Done, but results are the same. If you, or anyone else on
the list, have
other suggestions, I'm all ears. Thanks.
--
Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court
UNIX System Admin Consulting | Owings Mills, MD 21117
http://www.tkevans.com/
| 443-394-3864
http://www.come-here.c
om/News/ | tkevans tkevans.com
_______________________________________________
rhelv5-list mailing list
rhelv5-list redhat.com
h
ttps://www.redhat.com/mailman/listinfo/rhelv5-list
|
|
| Re: Maxtronic SCSI-to-SATA Array on
Dell 2950 |

|
2008-05-29 17:43:47 |
|
On Thu, May 29, 2008 at 8:57 PM, Tim Evans < tkevans  tkevans.co m">tkevans tkevans.com> wrote:
>> solarflow99 wrote:
>>
>> > Would you be able to re-initialize the array?
>>
Done, but results are the same. If you, or anyone else on the list, have
other suggestions, I'm all ears. Thanks.
-- after you initialised it, were you able to format and install onto it ok?
|
| Re: Maxtronic SCSI-to-SATA Array on
Dell 2950 |

|
2008-05-30 03:58:26 |
|
On 5/30/08, Tim Evans < tkevans tkevans.com">tkevans tkevans.com> wrote:
solarflow99 wrote:
Done, but results are the same. If you, or anyone else on the list, have other suggestions, I'm all ears. Thanks.
--
after you initialised it, were you able to format and install onto it ok?
No, all the same error messages appeared, and the device isn't accessible to fdisk, parted, or anything else.
did the installer format it then? Did the installation go sucessfully?
|
[1-8]
|
|