> After a very long time, it finally boots up and sees the disks, but > here's the output from dmesg | grep aacraid: > > [ 1.357760] Adaptec aacraid driver 1.2.1[50877]-custom > [ 1.388119] aacraid: Comm Interface type2 enabled > [ 3.405113] scsi host0: aacraid > [ 50.156024] aacraid: Host adapter abort request. > aacraid: Outstanding commands on (0,0,0,0): > [ 50.156126] aacraid: Host adapter abort request. > aacraid: Outstanding commands on (0,0,0,0): > [ 50.172032] aacraid: Host adapter reset request. SCSI hang ? > [ 65.536106] aacraid: Host adapter reset request. SCSI hang ? > [ 65.536204] aacraid 0000:01:00.0: outstanding cmd: midlevel-0 > [ 65.536206] aacraid 0000:01:00.0: outstanding cmd: lowlevel-0 > [ 65.536207] aacraid 0000:01:00.0: outstanding cmd: error handler-0 > [ 65.536208] aacraid 0000:01:00.0: outstanding cmd: firmware-2 > [ 65.536210] aacraid 0000:01:00.0: outstanding cmd: kernel-0 > [ 65.536228] aacraid 0000:01:00.0: Controller reset type is 3 > [ 65.536314] aacraid 0000:01:00.0: Issuing IOP reset > [ 98.675617] aacraid 0000:01:00.0: IOP reset succeded > [ 98.684161] aacraid: Comm Interface type2 enabled > [ 110.015352] aacraid 0000:01:00.0: Scheduling bus rescan > [ 166.896116] aacraid: Host adapter reset request. SCSI hang ? > [ 166.896214] aacraid 0000:01:00.0: outstanding cmd: midlevel-0 > [ 166.896216] aacraid 0000:01:00.0: outstanding cmd: lowlevel-0 > [ 166.896217] aacraid 0000:01:00.0: outstanding cmd: error handler-0 > [ 166.896218] aacraid 0000:01:00.0: outstanding cmd: firmware-2 > [ 166.896220] aacraid 0000:01:00.0: outstanding cmd: kernel-0 > [ 166.896236] aacraid 0000:01:00.0: Controller reset type is 3 > [ 166.896322] aacraid 0000:01:00.0: Issuing IOP reset > [ 198.858466] aacraid 0000:01:00.0: IOP reset succeded > [ 198.870660] aacraid: Comm Interface type2 enabled > [ 211.129896] aacraid 0000:01:00.0: Scheduling bus rescan > [ 228.844034] aacraid: Host adapter abort request. > aacraid: Outstanding commands on (0,0,0,0): > [ 266.835610] aacraid: Host adapter reset request. SCSI hang ? > [ 266.837891] aacraid 0000:01:00.0: outstanding cmd: midlevel-0 > [ 266.837894] aacraid 0000:01:00.0: outstanding cmd: lowlevel-0 > [ 266.837897] aacraid 0000:01:00.0: outstanding cmd: error handler-0 > [ 266.837899] aacraid 0000:01:00.0: outstanding cmd: firmware-2 > [ 266.837902] aacraid 0000:01:00.0: outstanding cmd: kernel-0 > [ 266.837939] aacraid 0000:01:00.0: Controller reset type is 3 > [ 266.840415] aacraid 0000:01:00.0: Issuing IOP reset > [ 299.846642] aacraid 0000:01:00.0: IOP reset succeded > [ 299.858811] aacraid: Comm Interface type2 enabled > [ 312.098221] aacraid 0000:01:00.0: Scheduling bus rescan > [ 367.869277] aacraid: Host adapter reset request. SCSI hang ? > [ 367.871382] aacraid 0000:01:00.0: outstanding cmd: midlevel-0 > [ 367.871385] aacraid 0000:01:00.0: outstanding cmd: lowlevel-0 > [ 367.871387] aacraid 0000:01:00.0: outstanding cmd: error handler-0 > [ 367.871389] aacraid 0000:01:00.0: outstanding cmd: firmware-2 > [ 367.871391] aacraid 0000:01:00.0: outstanding cmd: kernel-0 > [ 367.871480] aacraid 0000:01:00.0: Controller reset type is 3 > [ 367.873982] aacraid 0000:01:00.0: Issuing IOP reset > [ 400.765513] aacraid 0000:01:00.0: IOP reset succeded > [ 400.776673] aacraid: Comm Interface type2 enabled > [ 413.036505] aacraid 0000:01:00.0: Scheduling bus rescan > [ 468.995678] aacraid: Host adapter reset request. SCSI hang ? > [ 468.995700] aacraid 0000:01:00.0: outstanding cmd: midlevel-0 > [ 468.995704] aacraid 0000:01:00.0: outstanding cmd: lowlevel-0 > [ 468.995706] aacraid 0000:01:00.0: outstanding cmd: error handler-0 > [ 468.995709] aacraid 0000:01:00.0: outstanding cmd: firmware-2 > [ 468.995711] aacraid 0000:01:00.0: outstanding cmd: kernel-0 > [ 468.995740] aacraid 0000:01:00.0: Controller reset type is 3 > [ 468.995745] aacraid 0000:01:00.0: Issuing IOP reset > [ 501.875537] aacraid 0000:01:00.0: IOP reset succeded > [ 501.887288] aacraid: Comm Interface type2 enabled > [ 514.148609] aacraid 0000:01:00.0: Scheduling bus rescan > > The RAID controller is unusable, obviously. Rebooting with 4.13, now... Hi Emmanuel, It is curious that the FW is having outstanding commands ... I've created a ticket to iderntify the differences. I suspect that the large drive size may be related, but all options are open. Thanks, -Dave
