Hello,

 

I was randomly checking my server this morning and found the following entries:

 

Mar 13 04:02:42 orbit logger: mover finished

Mar 13 04:22:41 orbit kernel: mdcmd (729): spindown 5

Mar 13 05:04:58 orbit kernel: mdcmd (730): spindown 1

Mar 13 05:04:59 orbit kernel: mdcmd (731): spindown 2

Mar 13 05:04:59 orbit kernel: mdcmd (732): spindown 3

Mar 13 05:05:00 orbit kernel: mdcmd (733): spindown 4

Mar 13 05:05:00 orbit kernel: mdcmd (734): spindown 6

Mar 13 05:05:00 orbit kernel: mdcmd (735): spindown 7

Mar 13 05:05:01 orbit kernel: mdcmd (736): spindown 8

Mar 13 05:05:01 orbit kernel: mdcmd (737): spindown 9

Mar 13 05:05:02 orbit kernel: mdcmd (738): spindown 11

Mar 13 05:05:24 orbit kernel: mdcmd (739): spindown 0

Mar 13 05:05:24 orbit kernel: mdcmd (740): spindown 10

Mar 13 06:00:37 orbit kernel: sas: command 0xefb14e40, task 0xf0332c80, timed out: BLK_EH_NOT_HANDLED

Mar 13 06:00:37 orbit kernel: sas: Enter sas_scsi_recover_host

Mar 13 06:00:37 orbit kernel: sas: trying to find task 0xf0332c80

Mar 13 06:00:37 orbit kernel: sas: sas_scsi_find_task: aborting task 0xf0332c80

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 1703:<7>mv_abort_task() mvi=f7260000 task=f0332c80 slot=f727163c slot_idx=x2

Mar 13 06:00:37 orbit kernel: sas: sas_scsi_find_task: querying task 0xf0332c80

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 1632:mvs_query_task:rc= 5

Mar 13 06:00:37 orbit kernel: sas: sas_scsi_find_task: task 0xf0332c80 failed to abort

Mar 13 06:00:37 orbit kernel: sas: task 0xf0332c80 is not at LU: I_T recover

Mar 13 06:00:37 orbit kernel: sas: I_T nexus reset for dev 0000000000000000

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 0 ctrl sts=0x89800.

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 0 irq sts = 0x1001

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy0 Unplug Notice

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 0 ctrl sts=0x199800.

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 0 irq sts = 0x11081

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2138:notify plug in on phy[0]

Mar 13 06:00:37 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2163:plugin interrupt but phy0 is gone

Mar 13 06:00:39 orbit kernel: mvsas 0000:02:00.0: Phy0 : No sig fis

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy0 Attached Device

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 0 ctrl sts=0x89800.

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 0 irq sts = 0x1001

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy0 Unplug Notice

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 0 ctrl sts=0x199800.

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 0 irq sts = 0x81

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 0 ctrl sts=0x199800.

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 0 irq sts = 0x10000

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 2138:notify plug in on phy[0]

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 1224:port 0 attach dev info is 40000

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 1226:port 0 attach sas addr is 0

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 378:phy 0 byte dmaded.

Mar 13 06:00:39 orbit kernel: sas: sas_form_port: phy0 belongs to port0 already(1)!

Mar 13 06:00:39 orbit kernel: drivers/scsi/mvsas/mv_sas.c 1586:mvs_I_T_nexus_reset for device[0]:rc= 0

Mar 13 06:00:39 orbit kernel: sas: I_T 0000000000000000 recovered

Mar 13 06:00:39 orbit kernel: sas: sas_ata_task_done: SAS error 8d

Mar 13 06:00:39 orbit kernel: ata15: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00

Mar 13 06:00:39 orbit kernel: ata15: status=0x01 { Error }

Mar 13 06:00:39 orbit kernel: ata15: error=0x04 { DriveStatusError }

Mar 13 06:00:39 orbit kernel: sas: --- Exit sas_scsi_recover_host

 

Is this just a drive not responding briefly? Anything to be concerned about?

 

I'm running 5.0 B11 currently and haven't seen any errors since March 1st prior to this.

 

Thanks

I believe that is just an interface reset, likely because the drive didn't respond as expected. I see a somewhat similar thing on my motherboard ports every so often and have for years now. My Seagate drives cause it.