Dell/NetApp SAS Hard Drive Not Assignable


koshia

Recommended Posts

Hello all.  I'm very green to UnRaid - finally got it up and running two days ago, after a few weeks of troubleshooting. Most of my drives are detected now and came up just fine.  There's a few that i'm having issues with and would like anyone's feedback if they now why or suggest things I can do to get it working.

 

Issue with Dell Drive: ST32000444SS // 2tb // sas

This drive came on and was assignable during my troubleshooting of the server.  At one point, I had accidentally hit the spin down button and since then, it's won't come back up.  Even after initiating a new parity and placing the drive in different bays.  I had even restored the USB drive and redid unRAID from scratch.  Nothing seems to get it back up.

 

Issue with NetApp Drive: X411_HVIPC420A15 // 450GB 15k // sas

While I understand that NetApp and EMC has proprietary firmware on their controllers that read these specially formatted drives at 520/528 blocks - I found an article that if you use sg_format, you could potentially get the drive reformatted to 512 and be able to use it.

 

My UnRaid setup detects these drives and I was able to get sg_format installed on unRAID and had formatted the drives to 512, but I cannot seem to assign them to anything. 

 

The symptoms are the same for both types of drives in the assignable storage locations and cache location.  If I select it in the storage location, the page refreshes and the sd? does not get assigned.

 

If I assign it to the cached area, the page refreshes and a message "no device" appears in the slots.

 

----diagnostics log--

I'm on Stable 6.2 - I tried to get a diagnostics log generated/exported but it doesn't look like it is working. The loading icon comes up in the browser, the page refreshes and the message about log generation disappears.

 

Alternatively, this is from the WebGUI Log

Sep 15 20:29:04 Tower kernel: mdcmd (21): import 20
Sep 15 20:29:04 Tower kernel: mdcmd (22): import 21
Sep 15 20:29:04 Tower kernel: mdcmd (23): import 22
Sep 15 20:29:04 Tower kernel: mdcmd (24): import 23
Sep 15 20:29:04 Tower kernel: mdcmd (25): import 24
Sep 15 20:29:04 Tower kernel: mdcmd (26): import 25
Sep 15 20:29:04 Tower kernel: mdcmd (27): import 26
Sep 15 20:29:04 Tower kernel: mdcmd (28): import 27
Sep 15 20:29:04 Tower kernel: mdcmd (29): import 28
Sep 15 20:29:04 Tower emhttp: import 30 cache device: no device
Sep 15 20:29:04 Tower emhttp: import 31 cache device: no device
Sep 15 20:29:04 Tower emhttp: check_pool: no cache pool devices
Sep 15 20:29:04 Tower emhttp: cacheUUID: 
Sep 15 20:29:04 Tower emhttp: cacheNumDevices: 0
Sep 15 20:29:04 Tower emhttp: cacheTotDevices: 0
Sep 15 20:29:04 Tower emhttp: cacheNumMissing: 0
Sep 15 20:29:04 Tower emhttp: cacheNumMisplaced: 0
Sep 15 20:29:04 Tower emhttp: cacheNumExtra: 0
Sep 15 20:29:04 Tower kernel: mdcmd (30): import 29
Sep 15 20:29:04 Tower emhttp: import flash device: sda
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: removing unresponding devices: start
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: removing unresponding devices: end-devices
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: removing unresponding devices: volumes
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: removing unresponding devices: expanders
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: removing unresponding devices: complete
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: start
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: expanders start
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: break from expander scan: ioc_status(0x0022), loginfo(0x310f0400)
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: expanders complete
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: phys disk start
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: break from phys disk scan: ioc_status(0x0001), loginfo(0x00000000)
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: phys disk complete
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: volumes start
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: break from volume scan: ioc_status(0x0001), loginfo(0x00000000)
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: volumes complete
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: end devices start
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: break from end device scan: ioc_status(0x0022), loginfo(0x310f0400)
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: end devices complete
Sep 15 20:29:05 Tower kernel: mpt2sas_cm1: scan devices: complete

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.