Hi! Under 10.0, we had: da0 at aacraidp1 bus 0 scbus1 target 0 lun 0 da0: <HGST HUS724020ALE640 MJ6O> Fixed Direct Access SCSI-5 device (offline) da0: Serial Number PK1B31P8H5DD2V da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da1 at aacraidp1 bus 0 scbus1 target 1 lun 0 da1: <HGST HUS724020ALE640 MJ6O> Fixed Direct Access SCSI-5 device (offline) da1: Serial Number PK1B31P8H5L97P da1: 300.000MB/s transfers da1: Command Queueing enabled da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) Under 10.1, we have: pass0 at aacraidp1 bus 0 scbus1 target 0 lun 0 pass0: <HGST HUS724020ALE640 MJ6O> Fixed unknown SCSI-5 device (offline) pass0: Serial Number PK1B31P8H5DD2V pass0: 300.000MB/s transfers pass0: Command Queueing enabled pass1 at aacraidp1 bus 0 scbus1 target 1 lun 0 pass1: <HGST HUS724020ALE640 MJ6O> Fixed unknown SCSI-5 device (offline) pass1: Serial Number PK1B31P8H5L97P pass1: 300.000MB/s transfers pass1: Command Queueing enabled The raid controller: Adaptec 6405E aacraid0: <Adaptec RAID Controller> mem 0xf7400000-0xf77fffff,0xf7841000-0xf78417ff,0xf7840000-0xf78400ff irq 17 at device 0.0 on pci2 aacraid0: Enable Raw I/O aacraid0: Enable 64-bit array aacraid0: New comm. interface type1 enabled aacraid0: Adaptec 6405E, aacraid driver 3.2.5-1 aacraidp0 on aacraid0 aacraidp1 on aacraid0 aacraidp2 on aacraid0 aacraidp3 on aacraid0 How do I tell the controller to start those drives and make them visible again ? -- pi at opsec.eu +49 171 3101372 6 years to go !
Hi!> The raid controller: Adaptec 6405EReplacing it with an Adaptec ASR8405 and the drives are back alive. Any ideas why this happens ? That behaviour is very unexpected. aacraid0: <Adaptec RAID Controller> port 0xb000-0xb0ff mem 0xf7400000-0xf74fffff,0xf7580000-0xf75803ff irq 16 at device 0.0 on pci6 aacraid0: Enable Raw I/O aacraid0: Enable 64-bit array aacraid0: using MSI-X interrupts (32 vectors) aacraid0: New comm. interface type2 enabled aacraid0: ASR8405, aacraid driver 3.2.5-1 aacraidp0 on aacraid0 aacraidp1 on aacraid0 aacraidp2 on aacraid0 aacraidp3 on aacraid0 da0 at aacraidp1 bus 0 scbus1 target 0 lun 0 da0: <ATA HGST HUS724020AL MJ6O> Fixed Direct Access SCSI-6 device da0: Serial Number PK1B31P8H5DD2V da0: 300.000MB/s transfers da0: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da1 at aacraidp1 bus 0 scbus1 target 1 lun 0 da1: <ATA HGST HUS724020AL MJ6O> Fixed Direct Access SCSI-6 device da1: Serial Number PK1B31P8H5L97P da1: 300.000MB/s transfers da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) -- pi at opsec.eu +49 171 3101372 6 years to go !
If your running a custom kernel do you have both the options for aac enable: device aac # Adaptec FSA RAID device aacp # SCSI passthrough for aac (requires CAM) device aacraid # Adaptec by PMC RAID If you're missing aacp then you might get the behaviour your seeing. On 16 November 2014 21:39, Kurt Jaeger <lists at opsec.eu> wrote:> Hi! > > Under 10.0, we had: > > da0 at aacraidp1 bus 0 scbus1 target 0 lun 0 > da0: <HGST HUS724020ALE640 MJ6O> Fixed Direct Access SCSI-5 device > (offline) > da0: Serial Number PK1B31P8H5DD2V > da0: 300.000MB/s transfers > da0: Command Queueing enabled > da0: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) > da1 at aacraidp1 bus 0 scbus1 target 1 lun 0 > da1: <HGST HUS724020ALE640 MJ6O> Fixed Direct Access SCSI-5 device > (offline) > da1: Serial Number PK1B31P8H5L97P > da1: 300.000MB/s transfers > da1: Command Queueing enabled > da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) > > Under 10.1, we have: > > pass0 at aacraidp1 bus 0 scbus1 target 0 lun 0 > pass0: <HGST HUS724020ALE640 MJ6O> Fixed unknown SCSI-5 device (offline) > pass0: Serial Number PK1B31P8H5DD2V > pass0: 300.000MB/s transfers > pass0: Command Queueing enabled > pass1 at aacraidp1 bus 0 scbus1 target 1 lun 0 > pass1: <HGST HUS724020ALE640 MJ6O> Fixed unknown SCSI-5 device (offline) > pass1: Serial Number PK1B31P8H5L97P > pass1: 300.000MB/s transfers > pass1: Command Queueing enabled > > The raid controller: Adaptec 6405E > > aacraid0: <Adaptec RAID Controller> mem > 0xf7400000-0xf77fffff,0xf7841000-0xf78417ff,0xf7840000-0xf78400ff irq 17 at > device 0.0 on pci2 > aacraid0: Enable Raw I/O > aacraid0: Enable 64-bit array > aacraid0: New comm. interface type1 enabled > aacraid0: Adaptec 6405E, aacraid driver 3.2.5-1 > aacraidp0 on aacraid0 > aacraidp1 on aacraid0 > aacraidp2 on aacraid0 > aacraidp3 on aacraid0 > > How do I tell the controller to start those drives and make > them visible again ? > > -- > pi at opsec.eu +49 171 3101372 6 years to > go ! > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >