Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,598

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    There are some recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
  2. JorgeB
    Syslog is after rebooting but that's likely the common Ryzen SATA controller problem, look for a BIOS update and also update to latest Unraid. Mar 13 17:40:34 Tower kernel: BTRFS info (device sdf1): bdev /dev/sdc1 errs: wr 52893, rd 16563, flush 0, corrupt 0, gen 0 One of your cache devices dropped offline at some point in the past, see here for more info, if the scrub doesn't fix it you might need to backup and re-format the pool.
  3. JorgeB
    Yes. Sorry no, never used any SAS disks with Unraid.
  4. JorgeB
  5. JorgeB
    Unraid only disables as many disks as there are parity devices.
  6. JorgeB
    There's more info below, you can always do a clean install and copy just the needed files from the old one: https://wiki.unraid.net/Upgrading_to_UnRAID_v6
  7. JorgeB
    Looks more like a connection/power issue, replace/swap cables to rule them out and you can rebuild on top, just make sure the emulated disk is mounting and contents look correct before doing it.
  8. JorgeB
    Disk looks clean, most likely not a disk problem, diags could give more clues.
  9. JorgeB
    You can do that, but if you don't find the problem should then still run it in the server as is.
  10. JorgeB
    Ideally 24H, but if there's a considerable problem it should be found quickly.
  11. JorgeB
    Another NIC, switch, and yes if those don't help a different PC as Unraid, you just need to boot a PC with the Unraid flash drive and have an available disk for testing.
  12. JorgeB
    There's likely some hardware issue causing the data corruption, could even be unrelated to the server, like a network problem, but since I don't see any errors on the log you'd need to try various different things, like different source PC, NIC, switch, cables, etc, you can even boot another PC with the Unraid flash and test until you find the problem.
  13. JorgeB
    Once a disk is disabled it must be rebuilt.
  14. JorgeB
    Cache=prefer moves data from array to cache, you want cache=yes, see the GUI help for more details.
  15. JorgeB
    Cache is completely full, free up some space then re-start docker service.
  16. JorgeB
    Good to see you back! And hope you're feeling better.
  17. JorgeB
    Don't see any errors logged, problem could be the source computer, or some issue with the network.
  18. JorgeB
    If it keeps getting corrupt start by running memtest.
  19. JorgeB
    Diags are with the array stopped so can't see the problem, but if you can't start it with the cache device assigned you'll likely need to re-format it, there are some recovery options here if needed.
  20. JorgeB
    Long test completed wihout error, disk should be OK, at least for now.
  21. JorgeB
    You have the GPU bound to vfio-pci, when you add the NVMe device the devices change and you're now binding the NIC, hence why it's not available to Unraid.
  22. JorgeB
    870 QVO is QLC, so very slow writes after the small SLC cache is used, you'd likely get much better results with 4 EVO drives.
  23. JorgeB
    SMART test passed so disk is OK for now, but you want to keep an eye on these attributes: Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 354 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 66 If they keep climbing there will likely be more errors soon.
  24. JorgeB
    Something is using that space, btrfs usage agrees with the GUI, if you're not sure what is a way to find out is to move the files to the array one file or folder at a time.
  25. JorgeB
    Diags saved on the flash drive would confirm but there have been a couple of reports where it looks like the shutdown time-out is not being honored, i.e., Unraid forces the shutdown after a couple of seconds even if the set time is much higher, changing the setting (Settings -> Disk Settings) to re-apply it fixes the issue.
×
×
  • Create New...