Jump to content

Kev600

Members
  • Posts

    55
  • Joined

  • Last visited

Report Comments posted by Kev600

  1. I have this issue right now on 6.12.4.. I've been moving about 4.5TB of data from a USB Unassigned Device to another NAS Device over LAN; and also running a parity check.. 
    I have 24GB of RAM, which I will MEMTest ASAP.. (The transfers are still in progress, despite most of the Console being unresponsive.. )

    The logs are filled/filling with memory related errors. 

    I have stopped Docker and VM services.

    Terminal window terminates a few seconds after opening it.

    My Log file is set to 128Mb.

     

    I recently migrated my Unraid server to new hardware, then upgraded to 6.12.4. (from 6.10 or 6.11).
    *I will disable Bonding on my NIC Interface after my transfers complete.

    kbnas-syslog-20231013-2221.zip

  2. Thanks so much for posting this!  It's answered the question on my 8TB HGST disk.

    Scrutiny actually provided this info too.. (I guess this drive is also missing from the smartctl db!)
    image.thumb.png.4fb2e21ee5b45c267462ea7fef7e42c8.png
    I now know it's pointless to do any deep scans of the disk.. despite already having precleared it prior to Parity-Sync..
    I guess the error is not catastrophic and the disk isn't going to die any time soon..

     

    I bought the disk, used, off Amazon, so I'm waiting to hear what they say against the 'returns available for 1 yr' policy..
    Wish me luck! :)

     

    Kev

×
×
  • Create New...