November 29, 20241 yr Hi Guys. I've got an issue were i've purchased a HGST sas drive (preowned) and its showing up as all 0's on the unassigned devices. I've checked my HBA (LSISAS9300) and its flashed to firmware 16 I'm not sure what to do. I've seen some people say to sg_format as it might be byte size.. but that comes up with "format unit command: device not ready, type sense key" any help would be greatful *Edit - This is my first and only SAS drive in the system. everything else is sata via mobo or sata card Edited November 29, 20241 yr by Joeh Additional information.
November 30, 20241 yr Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Sense Key : 0x2 [current] [descriptor] Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] ASC=0x4 ASCQ=0x2 Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Sense Key : 0x2 [current] [descriptor] Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] ASC=0x4 ASCQ=0x2 Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] 0 512-byte logical blocks: (0 B/0 B) Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] 0-byte physical blocks Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Write Protect is off Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Mode Sense: f7 00 10 08 Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Nov 29 20:59:09 Soja kernel: sd 44:0:0:0: [sdf] Attached SCSI disk It's failing to initialize but don't see why, used SAS disks can have these issues, sometimes they some kind of protection or encryption enabled, or the disk is just bad.
November 30, 20241 yr It could be, but like mentioned, sometimes there are strange issues with used SAS devices, e.g.: https://forums.unraid.net/topic/180069-hgst-drives-showing-0000-gib-free-firmware-locked/#findComment-1489164
November 30, 20241 yr Author 27 minutes ago, JorgeB said: It could be, but like mentioned, sometimes there are strange issues with used SAS devices, e.g.: https://forums.unraid.net/topic/180069-hgst-drives-showing-0000-gib-free-firmware-locked/#findComment-1489164 Thanks for this. A wealth of information here. However i'm now left with a bigger question. Thanks to to Wody's reply i looked at the ASC and ASCQ lines.. However the ASCQ indicates that the drive is ready and needs to be spun up. However when i spin up the drive it fails to read capacity. "Nov 30 11:56:31 Soja kernel: sd 44:0:0:0: [sdf] Spinning up disk... Nov 30 11:58:12 Soja kernel: ..................................................................................................not responding... Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Sense Key : 0x2 [current] [descriptor] Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] ASC=0x4 ASCQ=0x2 Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Sense Key : 0x2 [current] [descriptor] Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] ASC=0x4 ASCQ=0x2" ANy idea?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.