I recently added a parity disk to my server and after 3 days fo syncing it finished and said the parity was valid, i turend off the server to mov it and when i restarted it said the parity disk was dissabled so i remved the disk and re added it using instruction on  a post on here and rebuilt the disk another 3 days it completed last night and said the parity was valid after a reboot this morning it again says the parity is valid but the disk is again dissbled  as can be seen in the screenshot, both the shutdown and the reboot have been clean and the disk is brand new and when i plug it into a caddie the smart report is healthy.

 

have i cnfigured the parity worng or could somthing else be the issue?

Chris M

Please post the diagnostics.

Sorry i throught it was attached 

origin-diagnostics-20221206-1215.zip

Disk was already disabled on boot, suggesting the problem happened during last shutdown, also because of the RAID controller there's no SMART, enable the syslog server to see if it catches the next time it happens, but RAID controllers should be avoided when possible.

how do i enable syslog server?

 

the server is a 14 bay server and without the raid card i cant use all the bays

 

5 minutes ago, Chrism2015 said:

how do i enable syslog server?

Follow the link.

 

5 minutes ago, Chrism2015 said:

the server is a 14 bay server and without the raid card i cant use all the bays

You could use a HBA instead, like an LSI.

 

is there anyway to see the syslog from before the reboot?

I have just noticed a load of these in the syslog now and i think i saw some this morining could it have anythig to do with the problem?

 

Dec 6 14:33:13 Origin kernel: XFS (md7): Metadata CRC error detected at xfs_dir3_block_read_verify+0x7c/0xf1 [xfs], xfs_dir3_block block 0x45b10a050

That's filesystem corruption on disk7, check filesystem.

 

9 minutes ago, Chrism2015 said:

is there anyway to see the syslog from before the reboot?

Nope, but you can enable the syslog server to it if it happens again.