system down - can't find luns (correction)

[Dana Holland]

Correction to my original post - this is an AS 2.1 box, not AS 30.

And a sudo mount -a returns:

  # sudo mount -a
mount: special device LABEL=/dev/sdb1 does not exist
mount: special device LABEL=/dev/sdc1 does not exist


Dana Holland wrote:
> One of my redhat boxes (AS 3.0) uses storage on an IBM FastT box.  The 
> HBA is a qla2300.  The FastT flaked out on us Friday - it has since been 
> rebooted and the other servers connected to it are working fine.
> 
> One server still doesn't see the filesystem located on the SAN.  When I 
> reboot, it tells me that /dev/sdb1 can't be found.  The only way I can 
> get the box up is to go into /etc/fstab and comment out the two file 
> systems that live on the SAN.
> 
> When I do a modprobe -r qla2300 and then a modprobe -v qla2300, doing a 
> cat of /proc/scsi/qla2300/1 and /proc/scsi/qla2300/2 looks fine - or at 
> least I think it does, I'm still very new to the SAN world.  Here are 
> the results of the cat command:
> 
> /proc/scsi/qla2300/1:
> 
> QLogic PCI to Fibre Channel Host Adapter for QLA2340 :
>         Firmware version:  3.03.06, Driver version 7.03.00-fo
> Entry address = f887d060
> HBA: QLA2312 , Serial# S25876
> Request Queue = 0x362a0000, Response Queue = 0x36290000
> Request Queue count= 512, Response Queue count= 512
> Total number of active commands = 0
> Total number of interrupts = 28
> Total number of IOCBs (used/max) = (0/600)
> Total number of queued commands = 0
>     Device queue depth = 0x20
> Number of free request entries = 483
> Number of mailbox timeouts = 0
> Number of ISP aborts = 0
> Number of loop resyncs = 0
> Number of retries for empty slots = 0
> Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
> Number of reqs in failover_q= 0
> Host adapter:loop state= <READY>, flags= 0x860833
> Dpc flags = 0x40
> MBX flags = 0x0
> SRB Free Count = 4096
> Link down Timeout = 030
> Port down retry = 030
> Login retry count = 030
> Commands retried with dropped frame(s) = 0
> Configured characteristic impedence: 50 ohms
> Configured data rate: 1-2 Gb/sec auto-negotiate
> 
> 
> SCSI Device Information:
> scsi-qla0-adapter-node=200000e08b1b54dc;
> scsi-qla0-adapter-port=210000e08b1b54dc;
> scsi-qla0-target-0=200500a0b8110d15;
> 
> FC Port Information:
> scsi-qla0-port-0=200400a0b8110d14:200500a0b8110d15;
> 
> SCSI LUN Information:
> (Id:Lun)  * - indicates lun is not registered with the OS.
> ( 0: 0): Total reqs 14, Pending reqs 0, flags 0x0, 0:0:81,
> ( 0: 1): Total reqs 14, Pending reqs 0, flags 0x0, 0:0:81,
> 
> /proc/scsi/qla2300/2:
> 
> QLogic PCI to Fibre Channel Host Adapter for QLA2340 :
>         Firmware version:  3.03.06, Driver version 7.03.00-fo
> Entry address = f887d060
> HBA: QLA2312 , Serial# S04875
> Request Queue = 0x36150000, Response Queue = 0x36140000
> Request Queue count= 512, Response Queue count= 512
> Total number of active commands = 0
> Total number of interrupts = 0
> Total number of IOCBs (used/max) = (0/600)
> Total number of queued commands = 0
>     Device queue depth = 0x20
> Number of free request entries = 511
> Number of mailbox timeouts = 0
> Number of ISP aborts = 0
> Number of loop resyncs = 0
> Number of retries for empty slots = 0
> Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
> Number of reqs in failover_q= 0
> Host adapter:loop state= <READY>, flags= 0x860833
> Dpc flags = 0x40
> MBX flags = 0x0
> SRB Free Count = 4096
> Link down Timeout = 030
> Port down retry = 030
> Login retry count = 030
> Commands retried with dropped frame(s) = 0
> Configured characteristic impedence: 50 ohms
> Configured data rate: 1-2 Gb/sec auto-negotiate
> 
> 
> SCSI Device Information:
> scsi-qla1-adapter-node=200000e08b1b4b8a;
> scsi-qla1-adapter-port=210000e08b1b4b8a;
> 
> FC Port Information:
> scsi-qla1-port-0=200400a0b8110d14:200400a0b8110d15;
> 
> SCSI LUN Information:
> (Id:Lun)  * - indicates lun is not registered with the OS.
> 
> This box had never been rebooted since it was initially set up on the 
> SAN (about 90 days) ago.  I'm wondering if there was some type of setup 
> that I needed to do in the init files to make it recognize the SAN each 
> time I reboot.  Like I said, we've had no prior experience with SANs, so 
> this is a very new world to us.
> 
>