You are not logged in.
Pages: 1
I'm beginning to work on some RAID stuff in Arch and bought a really cheap second hand HDD from eBay with exactly the same model/spec as another old HDD I had (so I could have two to mirror RAID). I'm pretty sure it's DOA; it sounds like it's spinning in sand and causes some bad error messages on start up, causing a super slow boot. The drive is a Seagate Cheetah 15K.7 300GB SAS drive (ST3300657SS) and I ran:
dmesg | grep sdto check out what was going on:
[ 18.169324] sd 6:0:0:0: [sdf] Spinning up disk...
[ 118.580753] sd 6:0:0:0: [sdf] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 118.580760] sd 6:0:0:0: [sdf] Sense Key : Not Ready [current]
[ 118.580763] sd 6:0:0:0: [sdf] Add. Sense: Logical unit not ready, cause not reportable
[ 118.581333] sd 6:0:0:0: [sdf] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 118.581336] sd 6:0:0:0: [sdf] Sense Key : Not Ready [current]
[ 118.581339] sd 6:0:0:0: [sdf] Add. Sense: Logical unit not ready, cause not reportable
[ 118.582375] sd 6:0:0:0: [sdf] Test WP failed, assume Write Enabled
[ 118.582564] sd 6:0:0:0: [sdf] Asking for cache data failed
[ 118.582581] sd 6:0:0:0: [sdf] Assuming drive cache: write through
[ 118.584022] sd 6:0:0:0: [sdf] Spinning up disk...
[ 218.995848] sd 6:0:0:0: [sdf] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 218.995855] sd 6:0:0:0: [sdf] Sense Key : Not Ready [current]
[ 218.995859] sd 6:0:0:0: [sdf] Add. Sense: Logical unit not ready, cause not reportable
[ 218.996426] sd 6:0:0:0: [sdf] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 218.996429] sd 6:0:0:0: [sdf] Sense Key : Not Ready [current]
[ 218.996432] sd 6:0:0:0: [sdf] Add. Sense: Logical unit not ready, cause not reportable
[ 218.997897] sd 6:0:0:0: [sdf] Attached SCSI diskTried Googling around for a while now, but haven't been able to find out much. Would someone be able to point me towards what the messages mean? I figure the key lines are 'read capacity failed' and 'sense key not ready'.
Any suggestions on other troubleshooting methods? Is the drive completely screwed? I've already got another replacement, so not really fussed if it can't be salvaged, but would be cool if it could be.
Offline
Offline
smartctl --info -T permissive /dev/sdf...
device is NOT READY (e.g. spun down, busy)
SMART support is: Unavailable - device lacks SMART capability.Offline
I'd say get rid of it. If it really sounds like it is rotating in sand, it doesn't have much life left anyway. You might even be able to get a refund if it was truly DOA.
Offline
I have zero experience with SAS drives but it does look like you bought a broken drive. Make sure you check if it works when you swap a known good drive that you can access by that one, just in case what you are seeing is caused by a driver or cabling problem.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Pages: 1