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.

Adding SAS HD - think I got a bad one

Featured Replies

Hello - 

 

I couldn't find anything about this error -

Oct 22 14:43:02 Skynet kernel: ahci 0000:03:00.1: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part sxs deso sadm sds apst
Nov 23 08:59:45 Skynet kernel: sd 3:0:19:0: [sds] Spinning up disk...
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Read Capacity(16) failed: Result: hostbyte=0x01 driverbyte=0x00
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Sense not available.
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Sense not available.
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] 0 512-byte logical blocks: (0 B/0 B)
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] 0-byte physical blocks
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Write Protect is off
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Mode Sense: 00 00 00 00
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Asking for cache data failed
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Assuming drive cache: write through
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Read Capacity(16) failed: Result: hostbyte=0x01 driverbyte=0x00
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Sense not available.
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Sense not available.
Nov 23 09:00:56 Skynet kernel: sd 3:0:19:0: [sds] Attached SCSI disk
Nov 23 09:01:05 Skynet kernel: sd 3:0:20:0: [sds] Spinning up disk...
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] 0 512-byte logical blocks: (0 B/0 B)
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] 0-byte physical blocks
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Write Protect is off
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Mode Sense: e7 00 10 08
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Write cache: disabled, read cache: enabled, supports DPO and FUA
Nov 23 09:03:03 Skynet kernel: sd 3:0:20:0: [sds] Spinning up disk...
Nov 23 09:04:43 Skynet kernel: sd 3:0:20:0: [sds] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 09:04:43 Skynet kernel: sd 3:0:20:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 09:04:43 Skynet kernel: sd 3:0:20:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 09:04:43 Skynet kernel: sd 3:0:20:0: [sds] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 09:04:43 Skynet kernel: sd 3:0:20:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 09:04:43 Skynet kernel: sd 3:0:20:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 09:04:43 Skynet kernel: sd 3:0:20:0: [sds] Attached SCSI disk
Nov 23 13:07:22 Skynet kernel: sd 3:0:21:0: [sds] Spinning up disk...
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] 0 512-byte logical blocks: (0 B/0 B)
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] 0-byte physical blocks
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Write Protect is off
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Mode Sense: e7 00 10 08
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Write cache: disabled, read cache: enabled, supports DPO and FUA
Nov 23 13:09:13 Skynet kernel: sd 3:0:21:0: [sds] Spinning up disk...
Nov 23 13:10:54 Skynet kernel: sd 3:0:21:0: [sds] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 13:10:54 Skynet kernel: sd 3:0:21:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 13:10:54 Skynet kernel: sd 3:0:21:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 13:10:54 Skynet kernel: sd 3:0:21:0: [sds] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Nov 23 13:10:54 Skynet kernel: sd 3:0:21:0: [sds] Sense Key : 0x2 [current] [descriptor]
Nov 23 13:10:54 Skynet kernel: sd 3:0:21:0: [sds] ASC=0x4 ASCQ=0x2
Nov 23 13:10:54 Skynet kernel: sd 3:0:21:0: [sds] Attached SCSI disk

 

The logical blocks is ok according to what I read but because the read capacity failed - does that mean I can do a manual format via terminal in order to get preclear to show up on the UI or does that mean I got a bad one.   Thoughts?

  • Community Expert

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

  • Community Expert
On 11/23/2020 at 8:35 PM, cbr600ds2 said:

Thoughts?

Looks more like a disk problem, there's no SMART report for that disk in the diags, see if you can get one manually.

  • Author
10 hours ago, JorgeB said:

Looks more like a disk problem, there's no SMART report for that disk in the diags, see if you can get one manually.

Had to run the manual long test via CLI because it failed through GUI.   Hopefully it'll have something by tonight.  

 

@slobert - yeah same it was a cheapo from Ebay because I wanted to test how the system works w/a SAS drive.   

  • Author
13 hours ago, JorgeB said:

Looks more like a disk problem, there's no SMART report for that disk in the diags, see if you can get one manually.

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HITACHI
Product:              H7230AS60SUN3.0T
Revision:             A310
Compliance:           SPC-4
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca01a8c89a0
Serial number:        001216RH90DD        YHJH90DD
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Wed Nov 25 16:34:38 2020 EST
device is NOT READY (e.g. spun down, busy)
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

root@Skynet:~# smartctl --test=short /dev/sds
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

Short offline self test failed [device not ready]

 

 

Edited by cbr600ds2
Figured out smart controls

  • Community Expert
10 hours ago, cbr600ds2 said:

Short offline self test failed [device not ready]

This points to a device problem.

  • Author

so its attached to a Supermicro 847 chassis with an BPN-SAS2-846EL1 attached to an LSI 9207-8i and showing up on unassigned devices.  All of the other SATA hard drives are working while on it.  Everything I've read says I can run a SAS HD.  You don't think so?  That's....a bummer.   

  • Community Expert
1 minute ago, cbr600ds2 said:

Everything I've read says I can run a SAS HD

You can, the current problem points to an issue with that disk.

 

  • Author

Thanks@JorgeB. Happy Thanksgiving!

Sent from my LM-V405 using Tapatalk

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.