> On Jan 3, 2017, at 2:59 PM, lakhera2017 <plakhera@xxxxxxxxxxxxxx> wrote: > > |- 1:0:0:15 sdq 65:0 failed ready running > - 3:0:0:15 sdai 66:32 failed ready running Does the same SAN target fail each time? What brand/model/firmware SAN switch is between initiator and target? Does the HBA show any SCSI aborts? _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos
Re: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
- From: Steven Tardy <sjt5atra@xxxxxxxxx>
- Date: Wed, 4 Jan 2017 20:48:02 -0500
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <1483473557235-5746449.post@n5.nabble.com>
- References: <1483473557235-5746449.post@n5.nabble.com>
- Follow-Ups:
- Re: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
- From: lakhera2017
- Re: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
- References:
- Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
- From: lakhera2017
- Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
- Prev by Date: Re: [OT] Network Attached Storage
- Next by Date: Re: ghostscript update breaks evince
- Previous by thread: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
- Next by thread: Re: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
- Index(es):
 |