trurl

Moderators
  • Posts

    43888
  • Joined

  • Last visited

  • Days Won

    137

Posts posted by trurl

  1. If you want to "fill the gap" where disk4 was by changing the assignments do so now, then

    3 minutes ago, Piemanpm said:

    leave "Parity is already valid" unticked and then start it up?

    While parity is rebuilding, on Main - Array Devices, you should see lots of Reads from all assigned data disks, lots of Writes to both parity disks, zeros in the Errors column.

     

    If it looks like there are problems, post new diagnostics.

  2. You should add attributes 1 and 200 for monitoring on all your WD drives. When you do, you will see several drives with SMART ( 👎 ) warnings on the Dashboard page.

     

    And setup Notifications to alert you by email or other agent as soon as a problem is detected.

  3. 12 hours ago, MrCrispy said:

    I was hoping the change would take place AFTER 12am Mar 27 US time. Is LimeTech NZ based? thats news to me.

     

    16 hours ago, TheMantis said:

    A quick check says that is well into the 27th of March (20 hours time difference so 9AM?) in California, USA where Lime Tech is based.

     

  4. 12 minutes ago, trurl said:

    Nothing can move open files. Disable Docker and VM Manager in Settings. 

     

    Also, Mover ignores any share where there is no Mover Action specified, which is what you have for all of those.

    appdata                           shareUseCache="only"    # Share exists on cache, disk4
    domains                           shareUseCache="only"    # Share exists on disk4
    isos                              shareUseCache="only"    # Share exists on disk4
    P-------e                         shareUseCache="no"      # Share exists on disk3
    P---------V                       shareUseCache="no"      # Share exists on disk4
    system                            shareUseCache="only"    # Share exists on disk4

    They need to be Primary:cache; Secondary:array; Mover Action:array->cache

  5. 53 minutes ago, goinsnoopin said:

    Last check incomplete on Tue 26 Mar 2024 06:30:01 AM EDT (yesterday), finding 25752 errors.
    Error code: -4

    That seems to correspond with when parity check was paused.

    Mar 26 06:30:01 Tower kernel: mdcmd (39): nocheck pause
    Mar 26 06:30:01 Tower kernel: 
    Mar 26 06:30:01 Tower kernel: md: recovery thread: exit status: -4
    

    Later on syslog says

    Mar 27 00:30:01 Tower kernel: md: recovery thread: check P Q ...
    ...
    Mar 27 03:57:12 Tower kernel: md: sync done. time=12431sec
    Mar 27 03:57:12 Tower kernel: md: recovery thread: exit status: 0