• Content count

  • Joined

  • Last visited

  • Days Won

    78 last won the day on November 21 had the most liked content!

Community Reputation

586 Guru


  • Rank
    I'm a helper, like that glove that makes hamburgers


  • Gender

Recent Profile Visitors

1335 profile views
  1. Disk in Error State - Next Steps Clarification

    I would replace it ASAP. By the way it happened, i.e., it started with a read error and when this happens unRAID tries to write the data back to those sectors using parity plus all other data disks to calculate what should be there, so it looks like it didn't happened while writing new files to that disk, if it did you'd need to have checksums or be using btrfs to check for corruption, unRAID does it's best to start writing to the emulated disk without losing anything, but depending on how a disk fails corruptions is possible on the file being written at the moment it switches to the emulated disk. Yes, but you can skip step 2.
  2. Issues with Mover from ssd cache on unraid

    Also and in case you didn't noticed there are read errors on disk4.
  3. File delete on reboot (SOLVED)

    They are not being deleted, /etc is stored on RAM, so it's gone after every reboot. You can use e.g. the user scripts plugin to copy the keys from your flash drive at every array start.
  4. System freezes with no log entry

    Have you tried disabling C-states? Though I don't use Ryzen and IIRC some users can only run it stable with C-states disable, more info on this thread, on can just read the last couple of pages:
  5. Disk read errors on parity drive

    It failed the extended SMART test so there are bad sector(s), you can try preclearing it and then re-running the SMART test, if it passes you can use it, though it's more likely to fail again in the near future than a disk that never had issues..
  6. unprotected data on a share which doesn't use cache?

    Shares are just top folders, someone or maybe some docker created a media folder on cache.
  7. unprotected data on a share which doesn't use cache?

    The means that a "media" folder exists on cache (with or without files inside it), change the share to cache "yes", run the mover and when done change it back to cache "no".
  8. [SOLVED] array wont start

    Nothing you can do about it, unless you get a new board, but this type of error is usually harmless.
  9. SSD Cache drive recommendation help

    You can still use them to make a cache pool for the dockers/VMs, just don't enable cache for the media shares so unRAID writes straight to the array.
  10. Disk with errors (but green) during parity rebuild

    They look more like cable/connection issues, though the LSI driver is not very helpful at showing the error type.
  11. [SOLVED] array wont start

    Call traces are bios related: Nov 22 10:28:41 Tower kernel: Your BIOS is broken; RMRR ends before it starts! Check for a bios update or ignore.
  12. IIRC auto start works without parity: Settings -> Disk Settings -> Enable auto start
  13. [SOLVED] array wont start

    You need to grab the diagnostics after starting the array by typing diagnostics on the console/SSH.
  14. SSD Cache drive recommendation help

    They may be useful if you plan to use dockers or VMs, for caching data they are small and also 40GB SSDs usually have a low sequential writing speed, likely slower than a modern HDD.
  15. unRAID OS version 6.4.0-rc13 available

    If you need help with that you should start a thread on the general support forum and post the diagnostics.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.