Jump to content

JorgeB

Moderators
  • Posts

    67,696
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Please use the existing plugin support thread:
  2. CRC errors are a connection problem, usually the SATA cable, if you've already replaced those it could be controller or disks, or some incompatibly issues, try the disks in different SATA ports and/or another PC.
  3. Uninstall the corefreq plugin, looks like that was the problem.
  4. Those errors are normal after the correcting scrub, reset them again and it should be fine now, errors were caused by one of the NVMe devices dropping offline some time in the past.
  5. 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/ If yes upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)). There are also issues with the pool, see below for better pool monitoring: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
  6. It's static unless you add or change any VM configuration.
  7. First try with the same USB drive, just recreate it.
  8. Syslog will list any uncorrectable files, these need to be deleted, restored from backups.
  9. This is usually a flash drive problem, backup config folder and recreate.
  10. You'll need to attach one to see where it's stopping.
  11. btrfs is detecting data corruption, first thing to do is to stop overclocking the RAM, see here for max supported speed for your config, then run memtest and a scrub on the pool.
  12. Do you see anything on the screen?
  13. Enable syslog server and post that log after a crash together with the diagnostics.
  14. First you need to shrink the array, then you can assign it as parity.
  15. If the repairs were successful it should be fine to continue with the current array, also check for lost+found folders on the disks, there might be lost/partial files there.
  16. If it's not a connection issue it's likely a bad drive, test in a different PC if available.
  17. Docker image can easily be recreated, libvirt should be backed up if you have VMs, if you don't it's not needed.
  18. Is that drive still on the onboard SATA? Disabling HPA doesn't work with some controllers, it should with onboard Intel.
  19. You can remove the HPA, but might still need some more fixing:
  20. You can also run a non correcting parity check, same result as an extended SMART test.
  21. First make sure it's not being passed to the VM, easy to check if the errors start after starting the VM, if it's not that try a different USB port, 2.0 preferred, or use a SATA device.
  22. If it's not RAM my next suspect would be the board, also where the controller is, and issues with the onboard SATA controller on some Ryzen boards and Linux are quite common, most cases the controller drops and you get read errors on all the disks, but the filesystem usually survives or it's easily fixed.
  23. Sep 29 23:09:10 Tower acpid: input device has been disconnected, fd 5 Sep 29 23:09:12 Tower kernel: md: disk1 write error, sector=26824 Sep 29 23:09:12 Tower kernel: md: disk1 write error, sector=26832 The flash drive assigned as disk1 is disconnecting or being passed through to a VM, and the docker image is there.
×
×
  • Create New...