fmok

Hi there, Premise: I am still very new to Unraid and self-hosting. I have one 4TB parity HDD and one array composed of a 2TB and a 4TB HDDs. The HDDs are in an USB enclosure - I am aware it's not ideal and soon I'll move to a server with integrated slots. All was going well but earlier today I received a write error on the 4TB and "deviced is disabled, content emulated error". Attaching diagnostics. The HDD is new, I bought and add it to my array less than 1 week ago. I stopped the array and that 4TB disk did not appear at all in the dropdown menu. I restarted the server as I had similar issues before with disks not being detected after an array stop. This time it was detected, so I Created a new config (preserving all assignments) Reassigned the disks to the correct slots in the array Checked "parity is already valid" The array started, but the dockers were empty. I freaked out (my bad) and tried the same again. I tried to manually mount without starting the array and the disk that had a write error is seen by lsblk but does not have a partition table. The other array HDD has. I am not sure how to proceed. I was thinking to try to restore the disk from the partition, but I am afraid of messing everything up (my parity disk is my "backup" , I don't have others) - so that's why I need some expert opinion. I am thinking about rsync'ing the data from the 2 disks to a backup HDD but I am not sure how to access the data of the 4TB HDD as it doesn't seem to have a partition table so I don't know how to mount it. Thanks heaps tower-diagnostics-20250223-1433.zip

Sure - attached. As I said, the setup is currently working but I have not assigned back the parity disk at this point. tower-diagnostics-20250214-1942.zip

Thanks @trurl After a few more rebooting and disk shuffling now they are visible. But I am aware that this is very precarious and far from being a safe solution. Unfortunately, I need to stick to this hardware for now, but I will follow your suggestion and will move to a setup without a USB enclosure and with HDDs to replace my SSDs as soon as I can. Anyway, any idea of why the disks are not available to be selected in the array while they are actually detected?

Hi trurl, Thanks for your response. This is the Yottamaster and yes, the parity disk is that 10TB one. I confirm that I had nothing assigned to disk1 and my data disks were in disk2 and disk3. Yes, I am planning to add more HDDs.

tower-diagnostics-20250214-1215.zip

Hi there, Let me premise that I am still inexperienced at self-hosting and only moved to Unraid months ago from a very simple rasbpi server. Today I noticed a partity disk error (first time I have it in - parity disk added a few weeks ago), which I was not quite sure how to solve and I just tried to reboot the system. Once it rebooted, the HDD that I used for parity was not detected anymore, and same goes for one of the two SSDs in my array I use for data. I tried shutting down and moving them to a different slot (I am using a Yottamster enclosure) but that didn't really change (this "trick" actually helped once in the past when I had a similar undetected disk issue). At first I thought it was a connection issue possibly caused by the enclosure but then I tried to lsblk and the two undetected disks were actually there, so I tried to manually mount the SSD and all was good, I could browse its content. I tried to follow the suggestion of this post but that didn't help. I have tried moving around the disks again and this time the parity HDD is detected (not the SSD) but I can't allocate it to the parity in the array, only to the data disk. Not sure how to proceed - I will try attaching the diagnostic file as a response to this comment, I don't seem to be able to attach it now. Thanks to anyone who could help with this.