On 13/11/10 05:33 AM, Peter Taps wrote:
James,
Thank you for your help.
The system I am working on has a SAS backplane. It has SCSI as well as
SATA drives mixed. There are a total of about 10 disks.
Although I don't have /dev/es folder, I do see /dev/scsi folder. There
are two subfolders in it - direct and rodirect. Both of them have one file
each.
I ran:
# sestopo /dev/scsi/direct/c0t1d0
The error I get is target does not support configuration diagnostic
page.
I ran:
#sestopo /dev/scsi/rodirect/c2t0d0
The error I get is diagnostic results failed: SCSI status 2 sense key
5 (illegal request) additional sense code 0x20/0x0 (invalid command
operation code).
What is it that I am missing?
Hi Peter,
if you've got /dev/scsi/{ro}direct directories, these will
be aliases for cd/dvd media, or perhaps a changer device.
If you don't have either the ses or sgen drivers loaded
then you won't see any /dev/scsi/ses or /dev/es directories
either, sorry.
Please examine the output from prtconf -v and check for
any devices showing a scsiclass,0d entry in their 'compatible'
properties list. Here's an example:
ses, instance #1
Hardware properties:
name='inquiry-revision-id' type=string items=1
value='3A24'
name='inquiry-product-id' type=string items=1
value='Storage J4200'
name='inquiry-vendor-id' type=string items=1
value='SUN'
name='inquiry-device-type' type=int items=1
value=000d
name='class' type=string items=1
value='scsi'
name='sas-mpt' type=boolean
name='port-wwn' type=byte items=8
value=50.01.63.60.00.0a.a5.fd
name='target-port' type=string items=1
value='5001636aa5fd'
name='compatible' type=string items=5
value='scsiclass,0d.vSUN.pStorage_J4200.r3A24' +
'scsiclass,0d.vSUN.pStorage_J4200' + 'scsa,0d.bmpt' + 'scsiclass,0d' +
'scsiclass'
name='lun' type=int items=1
value=
name='target' type=int items=1
value=0025
Device Minor Nodes:
dev=(145,1)
dev_path=/p...@0,0/pci8086,3...@2/pci8086,3...@0/pci8086,3...@1/pci1000,3...@0/s...@25,0:ses
spectype=chr type=minor
dev_link=/dev/scsi/ses/c11t5001636AA5FDd0
So when you run /usr/lib/scsi/sestopo over your devlink
in /dev/scsi/{ro}direct, you're trying to send SES commands
to a device which doesn't understand them. Which just won't
give you any joy at all.
I'm not certain this will work properly for your system, but
it's worth a shot anyway: Run this command as root, and if your
chassis does the right thing then you should see a bunch of
bay and disk nodes listed:
# /usr/lib/fm/fmd/fmtopo -dV
This is the sort of output you could see:
hc://:product-id=SUN-Storage-J4200:server-id=:chassis-id=0848QAJ001:serial=0820T4LXSA3LM4LXSA:part=SEAGATE-ST330055SSUN300G:revision=0B92/ses-enclosure=1/bay=0/disk=0
group: protocol version: 1 stability:
Private/Private
resource fmri
hc://:product-id=SUN-Storage-J4200:server-id=:chassis-id=0848QAJ001:serial=0820T4LXSA3LM4LXSA:part=SEAGATE-ST330055SSUN300G:revision=0B92/ses-enclosure=1/bay=0/disk=0
label stringSCSI Device 0
FRU fmri
hc://:product-id=SUN-Storage-J4200:server-id=:chassis-id=0848QAJ001:serial=0820T4LXSA3LM4LXSA:part=SEAGATE-ST330055SSUN300G:revision=0B92/ses-enclosure=1/bay=0/disk=0
ASRU fmri
dev:///:devid=id1,s...@n5000c5000b20566b//scsi_vhci/d...@g5000c5000b20566b
group: authority version: 1 stability:
Private/Private
product-idstringSUN-Storage-J4200
chassis-idstring0848QAJ001
server-id string
group: storageversion: 1 stability:
Private/Private
logical-disk stringc0t5000C5000B20566Bd0
manufacturer stringSEAGATE
model stringST330055SSUN300G
serial-number string0820T4LXSA3LM4LXSA
firmware-revision string0B92
capacity-in-bytes string3000
target-port-l0ids string[] [ w5000c5000b205669 ]
group: io version: 1 stability:
Private/Private
devfs-pathstring/scsi_vhci/d...@g5000c5000b20566b
devid stringid1,s...@n5000c5000b20566b
phys-path string[] [
/p...@0,0/pci8086,3...@2/pci8086,3...@0/pci8086,3...@1/pci1000,3...@0/d...@19,0
]
Finally, what problem are you trying to solve?
cheers,
James
--
Oracle
http://www.jmcp.homeunix.com/blog
___
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
