ReadyNas volume is Degrading

[Pbedford83]

Hey Guys, 

I know this has been asked before, but I havent found a solution.

I have a readynas 204 with 4 3TB drives, all the same model and age. My volume is degraded, However I cant seem to find which drive is causing the issue. I have downloaded the logs but not sure exactly what I am looking for. 

Could someone point me in the right direction? 

Thanks in advance. 

Paul

[cpu8088]

run raidar it will show u which drive does not have a tick

or in the main ui go system performance and u can see red dot instead of green showing which drive is bad

[Pbedford83]

Thanks, however it doesnt. 

All drives are showing as green on the back end and all are ticked on RaidAR. 

Is there anything in the logs which will pinpont the drive causing issues?

Thanks

[Retired_Member]

There is

- disk_info.log giving you the health data for the disks

- mdstat.log has some more info about drives as part of raid and whether they might be active or failed

Just download the logs and have a look. If already done, please ignore message.

[Retired_Member]

Volume.log might also be interesting. This one has a maintenance history (defrag, balance, scrub) at the bottom, to see whether something went wrong during these activities. 

[Pbedford83]

Thanks for the responses guys. 

I have gone through all the logs, the only one that says anything is the volume log which says its degraded, but says all drives have passed tests and all show exactly the same stats with regards to sectors etc. 

Literally stumped. 

[StephenB]

Try PMing @mdgm-ntgr (using the messages link on the upper right), and see if he is willing to analyze your logs.

[Pbedford83]

Thanks I will try that

[mdgm-ntgr]

If you send in the logs zip (see the Sending Logs link in my sig) I will take a look 

[Pbedford83]

Thanks! I  have just sent them through!

Appreciate it, 

[mdgm-ntgr]

Disk 1 in your system is faulty.

You can see this by looking at e.g. mdstat.log and seeing that sda is considered faulty. You can then look at disk_info.log and see that sda is disk 1. You can also look at e.g. smart_history.log and see how key SMART values grew over time. In this case it is the Current Pending Sector Count.

You can also see kernel errors for sda in kernel.log and systemd-journal.log