My monthly parity check started at 04:00 and when I checked on the server when I woke up I was greeted by these messages

 

And this is what Array Devices shows

 

I attach the diagnostics zip

 

Can someone please help and tell me what to do next?
I am very new to this and at a complete loss 😕

 

Update: I read somewhere that is it often suggested to run and extended SMART test, so that is now running.

 

But in the meantime is it safe to eg watch things on Plex? Or should I use the server at little as possible?

bob-diagnostics-20230901-0813.zip

Edited September 1, 20232 yr by Stannis33
Additional info

Not sure from the diagnostics if you have a drive problem or not.

 

I would suggest that:

• You check the cabling (SATA and power) to the drive in case one of them is not fully seated.
• Run an extended SMART test of the drive (accessed by clicking on the drive in the Main tab).   It takes ~ 2 hours per TB so is quite lengthy.    If it fails that drive should be replaced.

Report back here for next steps if the SMART step is error free.

Ummmm. I presume if the extended SMART test gets to 10% completed and then seems to stop (there is no longer a % progress line and the start button is enabled again) that this is a very bad thing? 

 

Would what actually happened be written to any of the logs?

7 hours ago, Stannis33 said:

Ummmm. I presume if the extended SMART test gets to 10% completed and then seems to stop (there is no longer a % progress line and the start button is enabled again) that this is a very bad thing? 

 

Would what actually happened be written to any of the logs?

The extended SMART test progress only updates in 10% increments so there can be a long delay between updates to the percent.

if the test was aborted or errored out this should show when you look at the SMART history.

I wondered about the SMART history, but that is empty. As is the error log. And the last test result says "No self-tests logged on this disk"

 

I tried running the extended test 3 times and the progress always just disappeared after 10% and around 20 minutes

I just tried running the extended test again, and progress completely vanished after about 20 miinutes

 

I don't know if it means anything but this was in the file I got via the download report button

 

"SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               90%     18216         -
# 2  Short offline       Completed without error       00%     18216         -
# 3  Extended offline    Aborted by host               90%     18207         -
# 4  Extended offline    Aborted by host               90%     18206         -"

Make sure disk spin down is disabled and try again.

Aaaah. Thanks. Spin down was the issue with it stopping. It now claims to have completed without error - report attached

 

What do I do next?

Re-enable the disk and try another parity check?

ST8000VN004-2M2101_WSD26GRW-20230901-2039.txt

DIsk is OK, most likely this issue:

 

https://forums.unraid.net/topic/103938-69x-lsi-controllers-ironwolf-disks-disabling-summary-fix/

 

I believe nobody confirmed if this is still a problem with v6.12, I would recommend upgrading to v6.12.4 and then resync parity, if it happens again try the fix on that thread, and please post here an update either way.

Oh. Ummm. So that suggests I cannot just re-enable the disk and have everything working again, correct?
I see someone says "Getting it back on would require checking, unassigning, reassigning and rebuilding" - I don't actually know how to do that - can someone please elaborate?

 

I am very scared of upgrading - I seldom succeed at upgrading anything without strange things happening. I really don't know what I am doing with Unraid in general and if anything goes wrong I won't have the faintest idea how to fix it.

I know there are instructions for upgrading, but I got rather lost rather quickly. Does anything along the lines of "upgrading Unraid for dummies" exist anywhere?

 

I'm sorry if I am asking silly questions  

4 minutes ago, Stannis33 said:

So that suggests I cannot just re-enable the disk and have everything working again, correct?

With 6.9.2 it will happen again, it may not with v6.12

 

If you prefer not to upgrade do the fix in that thread.

How do I actually make it work again right now though, even if it happening again is likely? I don't actually know how to get my system out of the current disabled state.

 

If I just re enable the disk, will my parity actually be working or do I have to do "Getting it back on would require checking, unassigning, reassigning and rebuilding"?
And if the latter, what does that actually mean?

2 hours ago, Stannis33 said:

How do I actually make it work again right now though

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Brilliant. Thank you.