Red X On 1 Of 2 Parity Drives

[Compass]

1 hour ago, ChatNoir said:

The WebGUI should be simpler.

This is what I got, if I add the -L will I lose whatever is on disk2?

 

Edit: according to this , no I wont,

 

https://wiki.unraid.net/Manual/Storage_Management#Checking_a_File_System

 

Phase 1 - find and verify superblock...

Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

Edited August 22, 2021 by Compass

[Compass]

Disk2 mounted....everything seems to be there, parity re-sync started

[trurl]

11 hours ago, ChatNoir said:

The WebGUI should be simpler.

And more importantly, less error prone

[Compass]

Success on parity 2 and disk2 with rebuild/sync, see attached diag,

 

still a red X on disk1 so have done the following

 

Stop array

Unassign disabled disk

Start array so the missing disk is registered

Stop array

Reassign disabled disk

Start array to begin rebuild. If you start the array in Maintenance mode you will need to press the Sync button to start the rebuild.

 

and no errors yet, fingers crossed

 

 

tower-diagnostics-20210825-1121.zip

[Compass]

A win, both Parity disks back online, Parity is valid, I'm no expert, obviuosly, doesn't look to be any ATA errors and such, thanks for everyones help.

 

I'm going to put it down to and older PS/cables, have replaced both.

tower-diagnostics-20210826-1826.zip

[JorgeB]

7 minutes ago, Compass said:

doesn't look to be any ATA errors and such

Yep, log is clean.