Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

AOC-SASLP-MV8 Error: timed out: BLK_EH_NOT_HANDLED

Featured Replies

Having some issues with my unraid server and aoc-saslp-mv8. Reasonably experience with Linux and unraid.

 

There doesn't seem to be any data issues, and the problem is solved by stopping / rebooting. Happens every 24-48 hours.

 

The problem is detailed below in the syslog exert, the section between "sas: --- Exit sas_scsi_recover_host" repeats until I reboot the server (196 MB syslog file).

 

2 WD WDC_WD15EARS Connected to the controller and 1 cache drive ST3500320AS.

 

I didn't jump the 7-8 pins (I plan to resolve that shortly), but I'm not sure if that is the cause.

 

First time posting let me know if any additional information will help.

 

Thanks

 

Syslog Cut:

 

Jun 29 07:42:40 Olympus logger: mover finished

Jun 29 08:42:45 Olympus kernel: mdcmd (11993): spindown 0

Jun 29 08:42:46 Olympus kernel: mdcmd (11994): spindown 1

Jun 29 08:42:47 Olympus kernel: mdcmd (11995): spindown 3

Jun 29 08:42:48 Olympus kernel: mdcmd (11996): spindown 4

Jun 29 08:42:48 Olympus emhttp: shcmd (47): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Jun 29 08:42:48 Olympus ata_id[9517]: HDIO_GET_IDENTITY failed for '/dev/block/8:48'

Jun 29 08:42:48 Olympus kernel: mdcmd (11997): spindown 5

Jun 29 08:51:59 Olympus kernel: mdcmd (12053): spindown 2

Jun 29 08:52:00 Olympus kernel: mdcmd (12054): spindown 6

Jun 29 08:52:01 Olympus kernel: mdcmd (12055): spindown 7

Jun 29 18:22:19 Olympus kernel: mdcmd (15474): spindown 0

Jun 29 18:22:29 Olympus kernel: mdcmd (15476): spindown 2

Jun 29 18:22:30 Olympus kernel: mdcmd (15477): spindown 6

Jun 29 18:22:31 Olympus kernel: mdcmd (15478): spindown 7

Jun 29 19:33:57 Olympus emhttp: shcmd (48): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Jun 29 19:33:57 Olympus ata_id[9561]: HDIO_GET_IDENTITY failed for '/dev/block/8:48'

Jun 29 21:53:03 Olympus kernel: mdcmd (16740): spindown 1

Jun 29 21:55:34 Olympus kernel: mdcmd (16756): spindown 3

Jun 29 21:55:35 Olympus kernel: mdcmd (16757): spindown 4

Jun 29 21:55:35 Olympus kernel: mdcmd (16758): spindown 5

Jun 29 23:17:12 Olympus kernel: mdcmd (17247): spindown 0

Jun 30 00:07:08 Olympus kernel: mdcmd (17547): spindown 1

Jun 30 00:07:08 Olympus kernel: mdcmd (17548): spindown 3

Jun 30 00:07:09 Olympus kernel: mdcmd (17549): spindown 4

Jun 30 00:07:09 Olympus kernel: mdcmd (17550): spindown 5

Jun 30 00:41:32 Olympus kernel: mdcmd (17757): spindown 2

Jun 30 00:41:33 Olympus kernel: mdcmd (17758): spindown 6

Jun 30 00:41:34 Olympus kernel: mdcmd (17759): spindown 7

Jun 30 01:29:29 Olympus kernel: sas: command 0xf6cc1d80, task 0xc410c640, timed out: BLK_EH_NOT_HANDLED

Jun 30 01:29:29 Olympus kernel: sas: Enter sas_scsi_recover_host

Jun 30 01:29:29 Olympus kernel: sas: trying to find task 0xc410c640

Jun 30 01:29:29 Olympus kernel: sas: sas_scsi_find_task: aborting task 0xc410c640

Jun 30 01:29:29 Olympus kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5

Jun 30 01:29:29 Olympus kernel: sas: sas_scsi_find_task: querying task 0xc410c640

Jun 30 01:29:29 Olympus kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5

Jun 30 01:29:29 Olympus kernel: sas: sas_scsi_find_task: task 0xc410c640 failed to abort

Jun 30 01:29:29 Olympus kernel: sas: task 0xc410c640 is not at LU: I_T recover

Jun 30 01:29:29 Olympus kernel: sas: I_T nexus reset for dev 0300000000000000

Jun 30 01:29:29 Olympus kernel: sas: I_T 0300000000000000 recovered

Jun 30 01:29:29 Olympus kernel: sas: --- Exit sas_scsi_recover_host

Jun 30 01:30:00 Olympus kernel: sas: command 0xf6cc1d80, task 0xc410c640, timed out: BLK_EH_NOT_HANDLED

Jun 30 01:30:00 Olympus kernel: sas: Enter sas_scsi_recover_host

Jun 30 01:30:00 Olympus kernel: sas: trying to find task 0xc410c640

Jun 30 01:30:00 Olympus kernel: sas: sas_scsi_find_task: aborting task 0xc410c640

Jun 30 01:30:00 Olympus kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5

Jun 30 01:30:00 Olympus kernel: sas: sas_scsi_find_task: querying task 0xc410c640

Jun 30 01:30:00 Olympus kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5

Jun 30 01:30:00 Olympus kernel: sas: sas_scsi_find_task: task 0xc410c640 failed to abort

Jun 30 01:30:00 Olympus kernel: sas: task 0xc410c640 is not at LU: I_T recover

Jun 30 01:30:00 Olympus kernel: sas: I_T nexus reset for dev 0300000000000000

Jun 30 01:30:00 Olympus kernel: sas: I_T 0300000000000000 recovered

Jun 30 01:30:00 Olympus kernel: sas: --- Exit sas_scsi_recover_host

Jun 30 01:37:33 Olympus kernel: sas: command 0xf678a840, task 0xc410c640, timed out: BLK_EH_NOT_HANDLED

Jun 30 01:37:33 Olympus kernel: sas: Enter sas_scsi_recover_host

Jun 30 01:37:33 Olympus kernel: sas: trying to find task 0xc410c640

Jun 30 01:37:33 Olympus kernel: sas: sas_scsi_find_task: aborting task 0xc410c640

Jun 30 01:37:33 Olympus kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5

Jun 30 01:37:33 Olympus kernel: sas: sas_scsi_find_task: querying task 0xc410c640

Jun 30 01:37:33 Olympus kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5

Jun 30 01:37:33 Olympus kernel: sas: sas_scsi_find_task: task 0xc410c640 failed to abort

Jun 30 01:37:33 Olympus kernel: sas: task 0xc410c640 is not at LU: I_T recover

Jun 30 01:37:33 Olympus kernel: sas: I_T nexus reset for dev 0300000000000000

Jun 30 01:37:33 Olympus kernel: sas: I_T 0300000000000000 recovered

Jun 30 01:37:33 Olympus kernel: sas: --- Exit sas_scsi_recover_host

I don't think the jumper pins are the issue.

Could it be with the spindown and then having something wake it up, but the wakeup/spinup times out?

 

I suppose you could turn off the spindown for the drives on that controller temporarily and see.

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.