system down - can't find luns (correction)
Rigler, Stephen C.
srigler at marathonoil.com
Mon May 23 14:58:28 UTC 2005
I'm assuming the last 2 entries in /proc/scsi/scsi are your IBM array?
Does /var/log/dmesg give you any clues as to what /dev/sd* entries they
would be mapped to (you should see things like "Attached scsi disk sda
at scsi0, channel 0, id 0, lun 0")?
-Steve
On Mon, 2005-05-23 at 09:41 -0500, Dana Holland wrote:
> Rigler, Stephen C. wrote:
> > Do you see your luns when you cat /proc/scsi/scsi? Also, how are you
> > presenting the luns to the problem box and are you using SANSurfer?
>
> Here are the results of cat /proc/scsi/scsi:
>
> # cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: MegaRAID Model: LD 0 RAID5 139G Rev: 513O
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 04 Id: 06 Lun: 00
> Vendor: PE/PV Model: 1x6 SCSI BP Rev: 1.0
> Type: Processor ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
> Vendor: IBM Model: 3542 Rev: 0520
> Type: Direct-Access ANSI SCSI revision: 03
> Host: scsi1 Channel: 00 Id: 00 Lun: 01
> Vendor: IBM Model: 3542 Rev: 0520
> Type: Direct-Access ANSI SCSI revision: 03
>
> Not using SANSurfer - I can see the LUNs on IBM's FastT client. It
> isn't showing any errors on those partitions.
>
> Not sure what you mean by "how are you presenting the LUNs to the
> problem box"?
>
More information about the redhat-list
mailing list