TDD

Members
 View Profile  See their activity

  • Posts

    75

  • Joined

  • Last visited

 Content Type 

Report Comments posted by TDD

    Unraid OS version 6.9.0-rc2 available

    in Prereleases

    Posted

    1 hour ago, TDD said:

     

     

    Quote

    Impossible.  Nothing internally was touched.  Only change was software.

     

    I will add the rebuild now (at 10%) under 6.8.3, still untouched and maxing the said drive and array over 14 disks has given zero log/drive errors.

     

    The logs were pretty clear about the connection being reset and the drive dropping - I have seen enough of them when it comes to sketchy hardware to pick out SATA errors over a link.  Clearly a driver/kernel issue - which may be troubling to deal with as the software as a whole marches ahead.  I will give this another go once we enter release of 6.9 and perhaps a shift to kernel 5.11?

     

     

     

     

    Quote

     

     

     

     

     

     

     

     

    took RC2 for a test run and all was well until the mpt2sas driver had an issue with my Seagate Ironwolf 8TB set up as parity (ST8000VN004-2M2101).

     

    No issues for weeks under 6.8.3.  I didn't manage to capture the logs (sorry!) for a myriad of reasons.  Looks like the driver <-> drive didn't like something and the drive dropped out, leading to read errors.

     

    I didn't see any errors under my other drives, all WD 40E* and 80E* units.

     

    Not sure if there is a quirk here with the drive.  Quick SMART test shows fine so i'm blaming the driver in 5.10.1.

    I'm rebuilding the parity now under 6.8.3 with the 4.19 kernel to give a solid test of things.

     

    FYI.

     

    TY!

     

    Kev.

     

     

    Unraid OS version 6.9.0-rc2 available

    in Prereleases

    Posted

    I took RC2 for a test run and all was well until the mpt2sas driver had an issue with my Seagate Ironwolf 8TB set up as parity (ST8000VN004-2M2101).

     

    No issues for weeks under 6.8.3.  I didn't manage to capture the logs (sorry!) for a myriad of reasons.  Looks like the driver <-> drive didn't like something and the drive dropped out, leading to read errors.

     

    I didn't see any errors under my other drives, all WD 40E* and 80E* units.

     

    Not sure if there is a quirk here with the drive.  Quick SMART test shows fine so i'm blaming the driver in 5.10.1.

    I'm rebuilding the parity now under 6.8.3 with the 4.19 kernel to give a solid test of things.

     

    FYI.

     

    TY!

     

    Kev.