disk read error - where do i go from here?

[Olymoly]

while at work, i received an email about a disk have a read error,

 

i pulled diagnostics, stopped docker to prevent anymore writes or reads. i ordered replacement drives, which should be here tomorrow. i didn't notice til after but there was a monthly scheduled parity that occurred after the fact.

 

my parity was listed as valid prior to this error but i doubt it was working since the disk status were disabled, i was told it was a likely a power issue, however i was unable to complete troubleshooting that parity issue. so here i am wondering how much damage has been done.

 

thanks for your help.

 

nastradamus-diagnostics-20210901-0546.zip

[Olymoly]

link to previous post regarding that parity issue,

 

 

[itimpi]

If a disk is disabled then it is ignored by a parity check.   In addition if the number of disabled drives is as large as your number of parity drives then the check becomes merely a read check of the remaining drives.

 

Do you have the scheduled check set to be correcting or non-correcting?   Non-correcting is recommended so that if you have a drive acting up it does not run the risk of corrupting parity.   The main purpose of the chevk is to alert you any time you have a non-zero number of errors during the run to the fact that you may have a problem that needs further investigation.

[Olymoly]

 

 

On 9/2/2021 at 2:51 AM, itimpi said:

If a disk is disabled then it is ignored by a parity check.   In addition if the number of disabled drives is as large as your number of parity drives then the check becomes merely a read check of the remaining drives.

 

Thanks for your help, that is good to know, Afaik The only disks that are disable are the parity disks, i have been unable to figure out why or how to fix this.  I've tried changing drive and switching slots. I have dual 920w PSUs in my supermicro case, i dont see how it was recommended to be a power issue and i havent been able to find reasonable replacements.

 

On 9/2/2021 at 2:51 AM, itimpi said:

Do you have the scheduled check set to be correcting or non-correcting?

 

The Scheduler seems to be set to be correcting. i disable it but it also set to yes. afaik i was enabled.

 

 

Ive also see that my Log is 100% at 188 GBs, i would like to restart the server but dont want to cause any more damage. Until i know what is going on with my parity, i trying to be cautious.

 

Considering my next step is to reboot? Maintenance mode and a smart check of the offending drive?

 

 

[trurl]

Post a screenshot of Main - Array Devices

[Olymoly]

[trurl]

The screenshots show some of your array disks disconnected and reconnected as different devices, and that is why they show up in Unassigned.

 

The screenshot doesn't agree with the Diagnostics you posted earlier though. Post new diagnostics.

 

 

 

[Olymoly]

im trying to download a new Diagnostics but it seems its hanging, or working.

 

could this be because the reason, and how can i fix it without removing important files related to about issue?

 

[Olymoly]

i am unable to get any download dialog for diagnostics, its just a busy icon.

 

should i just reboot?

[Olymoly]

rebooted and here is the most latest diagnostics

 

it takes about 20 mins to power down and then another 20 mins for disks to show up, to assign and start the array.

 

started in maintenance mode and running extended smart check on disk 6.

 

i am most worry about my data on disk 6, as my parity issue, seems to me to be a lost cause and i will have start over for me to get it to work. i plan to this when i have 2 week vacation at the end of the month.

 

i also received 2 drives that i will begin to preclear tonight. still havent decided how i want to handle them. however will decide in time.

 

first boot nastradamus-diagnostics-20210905-1201.zip

[ChatNoir]

1 minute ago, Olymoly said:

it takes about 20 mins to power down and then another 20 mins for disks to show up, to assign and start the array.

Is this normal for your system ?

[trurl]

On 9/3/2021 at 2:51 PM, Olymoly said:

could this be because the reason

Your log space was full before reboot, and shortly after reboot your log space is nearly 10% full even though syslog isn't very large. I don't quite remember exactly what shows up in diagnostics for your old version of Unraid, but there also doesn't seem to be any logs from docker or vm. You have those enabled but do you actually have any dockers or VMs?

 

My usual suspect for filling log would be atop from NerdPack, but you don't seem to have that either.

 

What do you get from command line with this?

du -h -d 1 /var/log

 

[Olymoly]

Is this normal for your system ?

The power down, no. The disks, i don't remember this being the case when I first built it and believe it started when I swapped motherboards about a year ago.

[trurl]

8 hours ago, trurl said:

What do you get from command line with this?

du -h -d 1 /var/log

 

 

[Olymoly]

[trurl]

8 hours ago, trurl said:

do you actually have any dockers or VMs?

 

[trurl]

What do you get from the command line with this?

ls -lah /var/log

 

[Olymoly]

I don't have VM, I have Dockers, however the array was started maintenance mode to run smart.

Smart.came.bacl.no errosnom the disk, I have nothing missing at a glance, I guess that reboot went a long way and fixed the immediate issue.

I'll post new diagnostics when I have a chance, since I'm at work atm

[trurl]

On 9/3/2021 at 12:41 PM, trurl said:

The screenshots show some of your array disks disconnected and reconnected as different devices, and that is why they show up in Unassigned.

Which controller are those disks on?

[Olymoly]

most up-to-date diagnostics, array started.

 

i have nerd tools etc

nastradamus-diagnostics-20210906-0342.zip

[Olymoly]

2 hours ago, trurl said:

Which controller are those disks on?

 

do you mean this? BPN-SAS2-836EL1

 

2 hours ago, trurl said:

What do you get from the command line with this?

ls -lah /var/log