squarepeg

Members
  • Posts

    6
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

squarepeg's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Dropped in an LSI 9211 in IT mode and that seems to have solved it.
  2. Same thing happened again overnight so I guess that is not my issue. alphao-diagnostics-20210105-0804.zip
  3. I do now, and those definitely looks like good attributes to monitor. I wish every support community was this helpful.
  4. Here is my diag zip, thanks! alphao-diagnostics-20210104-2217.zip
  5. I searched around and could not find an answer, or possibly craft the correct search string. Either way here is my situation: I have a system set up with 2 parity drives and 5 data drives. These are spread across 3 motherboard SATA ports and 4 SATA ports on a PCIE card. This system has been a rock for years and was recently upgraded to v6. During a Parity-Check with write corrections to parity enabled the motherboard ports all stopped working (parity 1, disk 3 and 4) the sync error count was getting ridiculously high as well as the read error count on the drives that had disconnected. I also noticed the temps were no longer being displayed for the affected disks. I took a look at the array and saw a bunch of files were missing. I immediately shut the system down cleanly and started searching the net to find out what the problem could be. After reading about the Marvell issue I powered the system on, went into the BIOS and disabled virtualization extensions. Upon booting into unRAID all the data and parity disks were accounted for and green, the array came on-line as usual and the missing files were present and intact. I started a Parity-Check with write corrections to parity disabled. It is not very far in and I have zero read errors but the sync errors are in the 5 digits and climbing towards the massive number I saw before I initially shut down the system. I need a quick sanity check to make sure I understand the Parity-Check / write corrections to parity function. If I restart my Parity-Check with write corrections enabled will it simply overwrite the parity errors with the correct parity? Or do I need to worry about it corrupting currently valid files on the array? Since I did not have to rebuild I assume this is correct but want to make sure. Any advice would be much appreciated. side note: an LSI card is now on the way