Stop the read check then post another screenshot of Array Operation.

4 minutes ago, trurl said:

did you let parity2 rebuild finish? It would have taken many hours.

 

Thank you.

4 minutes ago, trurl said:

Stop the read check then post another screenshot of Array Operation.

OK

Your diagnostics and screenshots seem out-of-sync.

 

Post a new screenshot of Main - Array Devices and new diagnostics.

Also post a screenshot of Unassigned Devices

tower-diagnostics-20220806-1318.zip

Dev1 is a SSD used for the main OS of the computer.

Dev2 was the original parity disc 

Your diagnostics shows original disk1 still attached, and its SMART report looks OK. Probably you disturbed connections when you were mucking about inside.

 

I still would like you to confirm that you let parity2 rebuild finish and it took many hours.

When I first removed disc1 (4TB HDD) it was showing in unassigned. Now it is not listed there...It is still connected via sata and power though.

Yes, Parity2 was in for approximately 1 week and showed valid before I removed parity (6TB) from the assignment.

I'll take a while to go through the syslog, it was already having connection problems with disk1 and disk9 when you booted 2 days ago. I'm going to eat some lunch first.

OK, thank you very much for looking at this. I will do the same and check back in an hour.

Disable Docker in Settings and leave it disabled until we get things fixed.

Do you have backups of anything important and irreplaceable?

Not for any of the media.

docker disabled

 

So, this is what is says now on Dashboard.

But on Main it shows.

I looked at SMART for disk9, those are just CRC errors. These are recorded by the disk when it receives inconsistent data (checksum), almost always connection problems. You can click on that 👎to acknowledge those and it will warn again if they increase.

 

You have a couple of Marvell controllers. These are not recommended anymore but I don't think they are causing the problems. Disk1 wasn't connected to them anyway.

 

Some corruption on emulated disk1 and on disk5, but both are mounted and show plenty of data.

 

Not sure why it says parity isn't valid. Maybe it thinks you should replace/rebuild the 1st parity disk. We can worry about that later. The fact that missing disk1 is being emulated well enough to mount makes me think parity2 should be OK.

 

If you click on the View icon at far right for disk1 (and for disk5) you should be able to drill down into its folders. Take a look and see if they look OK.

 

 

 

Yes, both show the files listed.

 

How do I know if the controllers are Marvell? I will look for alternatives.