Hi there,

 

I did a big mistake by accidentally unplugging 2 disks in standby when the Server was online. I didnt see that there was something wrong untill 3 days after it happend. Now after a reboot 2 disks were shown as "new", so I let them rebuild into the array but at the process of rebuilding the parity 1 had many read errors. The first try of rebuild stopped at 10% and didnt want to go further. The second try stopped at 60%. Is there a way to not lose the entire array of data to this?

diagnostics-20230408-1014.zip

Problem with parity looks more like a power/connection issue, replace cables (power and SATA) then you can try re-enabling parity and try again to rebuild the disks:

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed
-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
-Stop array
-Unassign the disks 2 and 3
-Start array (in normal mode now) and post new diagnostics.

Thank you for the fast response. Here is the new diagnostics

diagnostics-20230408-1132.zip

Check filesystem on emulated disks 2 and 3.

I checked, but they were formatted before the second rebuilding try.. there is nothing

This is what it says

If you formatted the disks that data is gone, you can then just re-sync parity.

Just now, GK-ken said:

This is what it says

That is not the emulated disk, but if the disks were formatted they will be empty.

The rebuild stopped at 0,0% now. Im afraid...

diagnostics-20230408-1343.zip

Parity is still having issues, did you replace both cables like mentioned?

 

Also if the disks were formatted not much point in rebuilding them, you can re-sync parity instead, though still need to fix the parity disk problem first.

Its been a time, but I now had time to try it with new replaced cables. Now there is something else that seem wrong. The array just starts fine, but the perity with earlier read errors is now disabled and one of the formatted disks too. The other of the two formatted array disks shows up with no data but the array says its fine.

homepod-diagnostics-20230413-1646.zip

Disks were already disabled when the server last booted, but if new cables didn't help it can be PSU, controller, etc.

The PSU was swapped out to a new one with more power now. I have a new controller but no cables atm, need to order them. Is it posible to get rid of the disabled mark on these two disks?

You can rebuild them:

 

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

 

Emulated disk2 was formatted so it will be empty, if there was data there you could do a new config instead.

Since Disk 2 is empty because UnRaid already wanted me to format the disk every time it rebootet in order to be mountable, does that mean I could try to do a new config in order to get the data that is on the parity disk to work again?

27 minutes ago, GK-ken said:

Since Disk 2 is empty because UnRaid already wanted me to format the disk every time it rebootet in order to be mountable,

When a disk is unmountable formatting will always delete all data, if there's data there you should check filesystem instead.

 

28 minutes ago, GK-ken said:

does that mean I could try to do a new config in order to get the data that is on the parity disk to work again?

You could do a new config to get the data that was on the actual disk2, instead of the empty formatted emulated disk.

I think I understood that, but unfortunately disk2 is already empty and so is disk3. Only Data remaining is on parity1 but its disabled and I dont know how to bring it back. Is there a way to repair the parity or check it now in this config?

Parity has no data, disk2 is still disabled, so the actual disk should have the old data, at this point there's nothing to lose so go to Tools -> New Config -> Retain current configuration: All -> Apply, then back on main, confirm all disks are assigned, check "parity is already valid" and start the array, post new diags after array start.

Thank you for all your support. I got the array working again but now i have a new problem or many. Fox Common Problems says "Unable to write to disk2". My mover does nothing I can see. All my disks arent spinning down anytime and my disk setting is set to a 15 minute spin down delay. I would really like to find the problem myself, so i dont need to relate to others to solve my problem, but i dont really know how.

homepod-diagnostics-20230502-1904.zip

Also my last parity check finished like that:
Last check completed on Mon 01 May 2023 06:41:51 PM CEST (yesterday)
 Duration: 18 hours, 47 minutes, 18 seconds. Average speed: 147.9 MB/s
 Finding 45224462 errors

Check filesystem on disk2.

Did the check, found some errors and did the repair as mentioned in these instructions. Now the array seems fine filesystem wise. But the disks wont spin down when not in use. How do i figure that out?
 

homepod-diagnostics-20230503-2150.zip

Disable Docker and VM Manager in Settings and see if your disks will spin down that way.

Did that, pressed the "spin down" button for all disks and the hdds didnt spin down. All cache drives are spun down. Active streams doesnt show any activity and open files just has one process named "find" that is up and shows some paths in the cache.

I cant find anything that prevents the disks from spinning down. They stayed on all the night wihthout docker or vm even activated in settings