I transitioned from a SM X10DRH-IT after a power surge left that MB dead.  I've transitioned everything over to the new r730xd (with a big CyberPower battery/conditioner) but lost 3 drives in the process.

 

Parity 1: no device - previously 14TB (2BG0-DM6F)

Disk 8: no device - previously 10TB (JEKZ-3Z7Z)

Disk 9: no device - previously 8TB (

Disk 11: unassigned - I think this was previously populated by a 14TB that's now in Disk 12 - 14TB (2BG7-HAJE)

 

I'm very new to the new Dell iDRAC/bios but proficient with the settings.  If I could get the Parity 1 rewritten, I don't care about disk 8&9.  I'd like to at least be able to start the array and then deal with replacing lost data.

 

How do I remove the Disk 11: unassigned error?  This error came from building a JBOD and has just been lingering.

tower-diagnostics-20241120-1248.zip

you may need to use new conf option and preserv certain disk assigments.

Based on the logs and the issue described, here's a breakdown and steps you can follow to address your Unraid array issues:

 

Identifying Missing Drives:

Your new Dell R730xd may have different configurations or BIOS/RAID controller settings compared to your old Supermicro motherboard. The following steps ensure the drives are detected:

BIOS Settings:

Verify that the drives are recognized in the BIOS.

Ensure the SATA mode is set to AHCI and not RAID, as Unraid requires direct access to drives.

RAID Controller:

If the R730xd has a RAID controller (like a PERC H730), set it to HBA (Host Bus Adapter) mode or configure it as JBOD for all drives. This allows Unraid to see the drives individually.

*Make sure the raid sytem in in IT MOde for unraid software raid...
 

Addressing Disk Errors

For the specific drives with issues (Parity 1, Disk 8, Disk 9, and Disk 11):

Parity 1:

If the parity drive is missing, Unraid cannot provide fault tolerance. However, you can rebuild parity if the array has valid data.

In Unraid, mark the parity drive as "no device" and start the array in maintenance mode to confirm data integrity.

Disk 8 and Disk 9:

If these are missing and you are not concerned about their data, you can remove them from the array configuration.

Go to Tools > New Config and rebuild the array configuration, excluding the missing drives.

Disk 11 Issue:

This might be related to a stale configuration.

Assign the correct drive to Disk 11 or set it to "no device."

If Disk 11’s data is now in Disk 12, you can either remove Disk 11 from the configuration or keep Disk 12 as the active data drive.

 

Start the Array

Maintenance Mode:

Start the array in maintenance mode to prevent writes and verify drive integrity.

Use the xfs_repair tool if any drives show filesystem errors.

Parity Rebuild:

Assign a new drive as Parity 1.

Begin the parity sync process to rebuild parity.

Remove Old Drive Errors:

If errors persist (e.g., Disk 11 lingering), use Tools > New Config to redefine the array layout and exclude unused slots.

 

Post-Recovery Checks

SMART Tests:

Run SMART tests on all drives to ensure no physical issues.

Data Recovery:

Use a tool like Unraid's built-in Unassigned Devices plugin to mount old drives and copy data.

Drive Management:

Label and document drive serial numbers to avoid future confusion.

 

Troubleshooting Hints from Logs:

Ensure the PCIe ACS override settings are compatible with your R730xd.

Look for drive initialization or error messages in the logs to pinpoint specific issues with drive detection or controller settings

9 hours ago, jongregory75 said:

How do I remove the Disk 11: unassigned error?

If you don't care about the data in disks 8, 9 and 11, you can do a new config and re-sync parity.

I ran a new config, Fixed all the drive errors. Rebuilt parity.  Lost about 15TB data but no clue what was lost.  QB/Sonarr/Radarr will figure that out.

 

I still have a 14TB, and 3 8 TB drives that the bios won't pick up.  It's not a topic for this forum.  I plugged them into my windows machine and it showed the directories that were currently on the 8TB drives.  The 14TB drive doesn't respond at all.