I've been getting lots of errors on my disks and parity it has been a while but i left the server like that, today i decided to do open the server tower and remove all the dust from it but i've been troubleshooting all day and can't firgure why my log is at 100%.

 

Also i can't access my share's and bee getting lots of errors from my disks, i'm about to just format everything and start from scratch but i wanna try and save some files that i have.

 

Below i attatched the diagnostics file to have it checked for you guys.

 

Hope i can address everything.

manucaserver-diagnostics-20210604-2201.zip

For your log is being spammed by errors on disk0 and disk2, that's why it is full.

Jun  4 20:11:27 manucaserver kernel: md: disk2 read error, sector=66200680
Jun  4 20:11:27 manucaserver kernel: md: disk2 read error, sector=66200688
Jun  4 20:11:27 manucaserver kernel: md: disk2 read error, sector=66200696
Jun  4 20:11:27 manucaserver kernel: md: disk0 read error, sector=66200696
Jun  4 20:11:27 manucaserver kernel: md: disk0 read error, sector=66200704
Jun  4 20:11:27 manucaserver kernel: md: disk0 read error, sector=66200712

 

While you were in the system, did you check your disk connections Data and Power, on both sides ?

On 6/5/2021 at 2:44 AM, ChatNoir said:

For your log is being spammed by errors on disk0 and disk2, that's why it is full.

Jun  4 20:11:27 manucaserver kernel: md: disk2 read error, sector=66200680
Jun  4 20:11:27 manucaserver kernel: md: disk2 read error, sector=66200688
Jun  4 20:11:27 manucaserver kernel: md: disk2 read error, sector=66200696
Jun  4 20:11:27 manucaserver kernel: md: disk0 read error, sector=66200696
Jun  4 20:11:27 manucaserver kernel: md: disk0 read error, sector=66200704
Jun  4 20:11:27 manucaserver kernel: md: disk0 read error, sector=66200712

 

While you were in the system, did you check your disk connections Data and Power, on both sides ?

Sorry for the long delay, went on a business travel but i'm back now.

 

I did check actually making sure everything was properly connected and screws were all in place as well.

 

Kind worried if my disks are damaged at this point.

You should check if the error still appear in your log.

It is quite possible that it is just CRC errors and that the drives and their data is OK. We are just lacking information to decide.

 

Try to run Extended SMART tests on the drives with S/N ending in 6Y0 and T0G. When both are done, share a new set of Diagnostics.