I was running a parity check and I got some read errors. After a while, my disk went offline. Parity is almost finishing but I'm not sure what I should do next to keep my files safe. Has my HD gone bad? What steps should I take to make my array protected again? I'm attaching diagnostics and some screenshots. I'm running Unraid on Proxmox.

magonhacloud-diagnostics-20251104-0741.zip

Looks more like a power connection issue, but the SATA controller is being virtualized, and running in IDE mode.

That's not recommended; ideally, you would pass through a controller to Unraid.

I thought I had passtrhu the devices correctly?

What should I do? Is it safe do reboot unraid and try to start the array again?

02:00.0 and 04:00.0 are my NVMES used in cache. 1f.2 is my entire sata controller from motherboard

Edited November 4, 2025Nov 4 by lelejau

32 minutes ago, lelejau said:

1f.2 is my entire sata controller from motherboard

In that case check the board BIOS and change from IDE to AHCI.

36 minutes ago, JorgeB said:

In that case check the board BIOS and change from IDE to AHCI.

It was already set as AHCI. Maybe something wrong in proxmox config?

Edited November 4, 2025Nov 4 by lelejau

Sorry, took another look and saw the wrong controller before:

00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010]
	Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix

This is the one being used:

00:1b.0 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 05)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: ahci

And it is in AHCI mode, so I would just check/replace cables for now.

3 minutes ago, JorgeB said:

Sorry, took another look and saw the wrong controller before:

00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010]
	Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix

This is the one being used:

00:1b.0 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 05)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: ahci

And it is in AHCI mode, so I would just check/replace cables for now.

Funny it says 1b.0 and I passedtrhu 1f.0. Does that mean anything? I'm not too familiarized with this subject.

So I read about rebuilding the drive onto itself. That's what I need to do now to fix the array right? If so, I will first buy a new pair of sata cables before doing this process again, to avoid any new errors. Is a PSU problem even a thing to consider here? Not enough power? I have a 500w PSU (not any certified fancy font though) I'm also running an extended smart test. Short test completed with no errors.

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

Edited November 4, 2025Nov 4 by lelejau

1 minute ago, lelejau said:

Funny it says 1b.0 and I passedtrhu 1f.0. Does that mean anything? I'm not too familiarized with this subject.

That should not matter.

I would replace the cables first, then rebuild on top, assuming the emulated disk is still mounting and contents look correct.

Replaced my PSU for a better one. Rebuilt my drive, everything seems to be fine now. Probably my bad PSU must have caused issues in the first place. Ran an extended smart test and rebuilt the drive, 0 errors, 0 warnings. 100% success.

Thanks for your help, I'm glad my unraid server is now back to normal again. I had some issues with case insensitive share names, but I found your solution in another thread. Moved the cfg file to tmp folder and re-applied settings from the GUI. Cfg was re-created and everything works now.

I think this is the best software purchase I ever did, the support here is outstanding. I couldn't thank everybody enough.