Jump to content

JorgeB

Moderators
  • Posts

    67,710
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If you keep getting filesystem corruption without an apparent reason there's likely some hardware issue, start by running memtest.
  2. Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)).
  3. Sync errors will be correct on parity disk only, nothing is written to any data disk (well except sometimes if there's a read error on a data disk, but you still need to run a correcting check now)
  4. Run a correcting check, a few sync errors after an unclean shutdown are normal. Oct 1 20:50:16 PhelpsTower emhttpd: unclean shutdown detected
  5. Diags are after rebooting but the btrfs dev stats do suggest that one of the devices dropped offline before, this is not necessarily a device problem, you can redo the pool and if it happens again post new diags before rebooting.
  6. Please post the complete diagnostics, the earlier syslog snippet is irrelevant for this and looks like the device dropped offline, and that is missing.
  7. I would expect it does, but don't have one to confirm nor do I remember someone else confirming it. Looks like it.
  8. Btrfs is detecting data corruption, running Ryzen with above max officially supported speeds is known to cause data corruption is some cases, see here.
  9. Try replacing or swapping cables with a different disk, but possibly disk is really failing, despite a good looking SMART.
  10. Test failed, disk should be replaced.
  11. LSI 93xx HBAs support trim, but only on devices with deterministic trim support. You can check that yourself: https://forums.unraid.net/topic/74493-samsung-ssd-hba-trim/?do=findComment&comment=713011
  12. Array devices can't be trimmed, not currently anyway, you can still use them there but there could be some write speed degradation with time. Just disable SMART attribute 197 monitoring.
  13. Try uninstalling the plugin, delete the /boot/config/plugins/ipmi folder, then re-install it.
  14. I'm also using Chrome, and it still works with rc1, this server has multiple NICs, so I'll attach the diags in case it helps. test2-diagnostics-20211114-1437.zip
  15. Not showing the IP address when hovering over the server name, like it did with rc1:
  16. This looks like a RAID controller, it might work if you set up the volumes individually, but it's not recommended.
  17. You have this option set at boot: Nov 13 10:56:55 Unraid kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot ixgbe.allow_unsupported_sfp=1,1,1,1,1 And it's not being accepted by the driver: Nov 13 10:56:55 Unraid kernel: ixgbe: `1,1,1,1,1' invalid for parameter `allow_unsupported_sfp' So it's not loading.
  18. Do it if it still doesn't come up after a power cycle.
  19. 00:1f.1 IDE interface [0101]: Intel Corporation 631xESB/632xESB IDE Controller [8086:269e] (rev 09) Subsystem: Dell 631xESB/632xESB IDE Controller [1028:01b8] Kernel driver in use: ata_piix Kernel modules: ata_piix 00:1f.2 IDE interface [0101]: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller [8086:2680] (rev 09) Subsystem: Dell 631xESB/632xESB/3100 Chipset SATA IDE Controller [1028:01b8] Kernel driver in use: ata_piix Kernel modules: ata_piix Also look in the BIOS for an AHCI option for the SATA controller, if there isn't one look for a RAID option.
  20. Yes. When they appear in the BIOS Unraid will recognize them.
  21. There's a firmware problem with false positives about pending sectors, it has nothing to do with reliabilty.
  22. I never enabled the "Enable Network Connection" option, not exactly sure what's for, but everything works for me with that option disable.
  23. See if this applies to you, 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)), or see below for more info.: 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/
  24. Yes! I await my prize, hint, I don't need another license For many years I've been reusing the smaller disks leftover from upgrades, I still have servers with 2 and 3TB disks, even one with some 1TB disks, part of why I have so many, all those small disks together are still a lot of storage space I can use, but now I'm am at the limit, no space for any more servers.
×
×
  • Create New...