Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,662

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It's not a device problem, btrfs is detecting data corruption, most likely the result of you having overclocked RAM (or just bad RAM), see here first: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  2. JorgeB
    Cache filesystem is corrupt, log shows previous write errors to one of the devices: Jun 13 13:31:06 Valhalla kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 875, rd 0, flush 0, corrupt 0, gen 0 Best bet is to backup and restore the pool, also see here for better pool monitoring.
  3. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  4. JorgeB
    That should remain enable when an NVMe device is used in the M.2 slot, disable if you use a SATA M.2 device.
  5. JorgeB
    You can post the current diags to confirm.
  6. JorgeB
    That's all you need to do.
  7. JorgeB
    Yep.
  8. JorgeB
    SMART looks fine, there are some UDMA CRC errors which suggests a SATA cable problem, though they could be old, full diags of when the disk got disabled could give more clues.
  9. JorgeB
    If the previous balance finished it shouldn't need a new one, if it does something weird is going on, it's also not normal for one of the devices to become unassigned after the update.
  10. JorgeB
    It's not, devices are likely from different productions runs and serial size changed, as for the temp, it's not always accurate for low end devices, most likely one of them is reading wrong.
  11. JorgeB
    I didn't mention there were errors, just that Unraid reports what the device itself is reporting: Device Model: SPCC Solid State Disk Serial Number: AA000000000000001686 ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 194 Temperature_Celsius -O---K 100 100 050 - 40
  12. JorgeB
    Btrfs restore is mostly used to restore files from a corrupt filesystem, not to restore deleted files, for that you need UFS explorer or a similar deleted file recovery app.
  13. JorgeB
    This should be the serial number as reported by the device, same for temps, diagnostics would confirm.
  14. JorgeB
    Ohh, and for this you just specify one one the devices, the other ones will mount together, if available.
  15. JorgeB
    Don't forget to unmount this first.
  16. JorgeB
    You can do this: Stop the array, if Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
  17. JorgeB
    Pool data is part raid0, part single, balance to whichever you prefer, there should only be one data profile in use.
  18. JorgeB
    Missed that part, that should not happen if you assigned the same original devices, and it suggests pool is rebalancing, would need diags to say more.
  19. JorgeB
    See if this applies to you: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  20. JorgeB
  21. JorgeB
    Can't say why one the pool devices was unassigned, especially without diags, but if it happens again you can do this: If Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
  22. JorgeB
    You can run a filesystem check on both disks, but if the server is hanging there are other issues.
  23. JorgeB
    Then I think you're only option would be using a file recovery util, like UFS explorer.
  24. JorgeB
    Enable syslog mirror to flash then post that log after a crash.
  25. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
×
×
  • Create New...