daydreamingdude

A few weeks ago, my server showed errors on disks 2 and 3. After a restart, disk 2 came back fine, but disk 3 was emulated. Both were old 2TB drives, so I replaced disk 3 with a new larger drive and it rebuilt successfully—problem solved, or so I thought. Today, both disks errored again. I found both were connected to an M.2 SATA expansion card. After swapping cables and ports, disk 2 is fine, but disk 3 remains emulated no matter what. I suspect the M.2 card is flaky, especially since I was doing heavy downloads last night, possibly overloading it. I plan to replace it with a PCIe SATA card and new cables. Is it safe to plug the drives into the new card and rebuild disk 3? Any other steps or things I should check? Diagnostics are attached. And yes I know my appdata lives on my drive and that is not good, I was made aware of that after my last topic concerning disk 3 and planned to come back to it, but work got me instead. tower-diagnostics-20250526-1838.zip

Gotchya. Sounds simple enough then. Thanks for your help and flagging that other issue. I'll reach out once I am ready to tackle that (or if I have any issues with swapping out the disks)

Thank you for breaking that down. I agree that should be secondary after the rebuild. It may take me a second to get to the rebuild. Full time job and all that, so I will bump this topic once I have done that. But for the rebuild, sounds like the "Replacing failed/disabled disk(s)" section is what I want. Once I swap out the new disk in that disk spot, I shouldn't have to rebuild parity, right? And does it matter in terms of speed if I preclear or don't the new disk?

Disk has been disabled since the 8th actually. So if everything looks okay, then would following the "Replacing failed/disabled disk(s)" guide generally be what I want? I think I would probably replace the SATA cable as well, just to be sure. And for the appdata and system shares, that seems not great. Is there a safe and easy way to relocate them elsewhere? Would I want to move them to the flash drive? Seems like it might break a lot of the volume path files.

Attached tower-diagnostics-20250512-1139.zip

So I have a disk that is device disabled/ emulatedcontents enabled. I am actually not really interested in troubleshooting this disk, because it is a very small (compared to the others) drive that I bought back in 2017. I have been meaning to replace it and another of the same kind for some time, because they are so old and small. So with that being said, I am not really sure of the protocol to do this. I have read over https://docs.unraid.net/unraid-os/manual/storage-management/ and obviously the "Replacing failed/disabled disk(s)" is what I would want, but it says that it wont fix any device that is showing as unmountable. I don't think that my drive is showing as unmountable, but I want to be sure. It looks like this (Disk 3): So if it is mountable, just to clarify, is that I power down, replace the old drive with new drive, and then when I start the machine again, will it still show disk 3 the way it is above, but then I basically take the new drive in the unassigned devices pool, assign it to that spot in the array, and then Unraid does its things and imprints the emulated contents onto that drive. If I do that, is parity then maintained? I don't need to rebuild it from scratch? Also, how does this work if I do/don't pre-clear the new drive? Sorry if this is super basic, just want to make sure I'm not going to mess up the array or cause data loss.