I have been hunting over the forums and looking around but haven't found a good way to determine if this new drive is dead or I am just doing something wrong.

 

This drive is to replace a 6TB SAS Parity Drive. It's a Seagate EXOS x16 and has both 512 and 4k for formatting. Read that all I should have to do is replace the parity drive, fire it up, put things back replacing the old parity with the new one. Straight forward, should be easy.

 

Shut everything down just cause, I could have hot swapped wasn't super comfortable doing that with this new drive. 

 

Restart the Supermicro server we get to the LSI controller, it starts looking at drives. The new Seagate drive makes some really odd noise and when the LSI Controller thinks it is done it complains that the drive is still spinning up.

 

Unraid boots and I see the drive with a drive letter and serial number in the list of drives. Instead of it saying 'Disk 1' just says 'sdj' and I can't format it or anything. sg_format refuses to format it. I am about to spin it down and put the new drive back in and get all the exact errors for the drive.

 

I am sure there is info that would be helpful, I am new so ask me for anything and I will do my best to provide.

 

Drive: ST14000NM004G Exos X16 14TB SAS

Controller: LSI 9207-8i IT Mode

Unraid 6.9.latest

MB: Supermicro X9DRi-LN4+/X9DR3-LN4+

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

33 minutes ago, MarriedGeekGuy said:

replace the parity drive

 

33 minutes ago, MarriedGeekGuy said:

Instead of it saying 'Disk 1' just says 'sdj' and I can't format it or anything.

Unclear what you are trying to do. 

 

Parity is not Disk1 and you don't format Parity since it has no filesystem 

If you are replacing parity just assign the replacement to the parity slot and start the array to begin parity build 

Ok that was odd, took a minute to be able to post. 

 

Sorry, that description about drives is confusing. When I boot Unraid with the new drive it oddly shows as 'sdj' under Unassigned Devices. The others look like the image bellow. When I try and select the drive for parity it doesn't show in the dropdown.

 

I thought I would attempt to format it instead and see if it mounted as just a drive. I was thinking it would be a good way to make sure the drive was good and would let me know if it was bad.

 

I am just swapping the drive out right now and will get the Diagnostic.

 

Really appreciate this, it feels like an obvious PEBCAK issue to me.

 

Sorry, took me a minute. Wife highjacked me on the way to the garage.

 

This is what I end up with after the system boots and the Diagnostic.

deathstar-diagnostics-20210405-1826.zip

Could you give some more details about your hardware setup? I think there is probably something not working as needed.

Sure.

 

MotherBoard: Supermicro X9DRi-LN4+/X9DR3-LN4+, Version REV:1.10 / American Megatrends Inc., Version 3.3 / BIOS dated: Wed 23 May 2018 12:00:00 AM PDT

Dual Intel® Xeon® CPU E5-2690 0 @ 2.90GHz

LSI 9207-8i In IT Mode

1 6TB HGST SAS Drive Parity

7 6TB HGST SAS Drives (Data)

2 3TB HGST SATA Drives (Data)

1 1TB nvme (cache)

1 500GB nvme (Not Sure Yet)

 

64GB Ram

 

I just had a thought and I need to probably open the case to see... could it be the backplane? It's the one thing I had not thought about till just now.

 

Joshua

Drive is failing to initialize:

 

Apr  5 18:11:08 DeathStar kernel: .............................................................................................not responding...
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] ASC=0x4 ASCQ=0x22
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] ASC=0x4 ASCQ=0x22
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] 0 512-byte logical blocks: (0 B/0 B)
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] 0-byte physical blocks
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Test WP failed, assume Write Enabled
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Asking for cache data failed
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Assuming drive cache: write through
Apr  5 18:11:08 DeathStar kernel: sd 1:0:3:0: [sdg] Spinning up disk...
Apr  5 18:12:49 DeathStar kernel: ..................................................................................................not responding...
Apr  5 18:12:49 DeathStar kernel: sd 1:0:3:0: [sdg] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr  5 18:12:49 DeathStar kernel: sd 1:0:3:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Apr  5 18:12:49 DeathStar kernel: sd 1:0:3:0: [sdg] ASC=0x4 ASCQ=0x22
Apr  5 18:12:49 DeathStar kernel: sd 1:0:3:0: [sdg] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr  5 18:12:49 DeathStar kernel: sd 1:0:3:0: [sdg] Sense Key : 0x2 [current] [descriptor]
Apr  5 18:12:49 DeathStar kernel: sd 1:0:3:0: [sdg] ASC=0x4 ASCQ=0x22
Apr  5 18:12:49 DeathStar kernel: sd 1:0:3:0: [sdg] Attached SCSI disk

 

Try swapping cables/backplane slot whit another drive, if it still fails it's likely a drive issue.

Thanks, 

 

yeah I tried it in another spot on the backplane and it didn't work there either. The old drives work.

 

I am building a couple servers and have cables on the way. I'll try bypassing the backplane when they come today.

 

Joshua