Jump to content

JorgeB

Moderators
  • Posts

    67,863
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Just go to Tools -> update OS select "stable" branch and then "check for updates"
  2. Yours is a different case than the others, others have a problem when there are two devices installed because they have the same nsid, so Unraid only shows one device, and that can be fixed with a "quirk", you lose both devices because they have no bran/model output with this kernel, not sure if/how that can be fixed by LT.
  3. Sep 30 10:33:14 HomeServer nginx: 2022/09/30 10:33:14 [error] 2177#2177: *110 open() "/usr/local/emhttp/homeserver-flash-backup-20220930-1033.zip" failed (2: No such file or directory) while sending to client, client: 192.168.1.101, server: , request: "GET /homeserver-flash-backup-20220930-1033.zip HTTP/1.1", host: "homeserver.local", referrer: "http://homeserver.local/Main/Settings/Flash?name=flash" Not sure what this is about, any ideas @Squid @bonienl?
  4. Like this: https://forums.unraid.net/topic/128492-multiple-disabled-disks/?do=findComment&comment=1170517
  5. Everything limited to around 70MB/s independent of the device used still suggests a LAN issue, despite the iperf results, do you have another NIC you could try with?
  6. If you can boot using the GUI mode use that to configure the LAN, if not disable the onboard NICs in the board BIOS and reboot, if still issues delete/rename /config/network.cfg and /config/network-rules.cfg
  7. Run a scrub on the pool, check that all errors are corrected, after that delete and re-create the docker image.
  8. That is single stream, multiple stream can give erroneous results since it's doing multiple tests at the same time.
  9. Yep, but they usually take some time to grow, there are reports that defragging the file system also helps, but only if there are no snapshots.
  10. If it's the docker image I would suggest just re-creating it, it's easier and faster: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  11. Assuming it was a single stream test yes. Yep.
  12. Yep, 6.11.1 which is expected soon *should* fix that.
  13. Image file types can grow with time, move everything to the array and check what was using the most space, then copy back with cp --sparse=always.
  14. You can also enable the syslog server and post that after it crashes, it should show if it's an overheating problem.
  15. That's fine, we will need to manually re-enable at least one of them anyway, you currently have 3 invalid disks with dual parity, so not possible to rebuild as is.
  16. Diags are after rebooting so we can't see what happened, but disks 16 and 19 look mostly OK, disable disk spin down and run an extended test on both, then post new diags.
  17. This is rather strange, stock Unraid doesn't have any fan control, please try booting in safe mode to rule out any plugins.
  18. My advice is still getting an addon NIC, ideally Intel, and trying with that.
  19. From where/how are you transferring the data? If you enable turbo write and transfer directly to the array are speeds better or the same?
  20. Again if the CPU is overheating it's a cooling issue, it should not overheat even if all cores were at 100%, but it might not even be that.
  21. You need to remove any reference to that device by editing the VM XML, it's normal if the hardware changed.
  22. Disk looks OK, could be a preclear issue, just add it to the array and let Unraid clear it, you can also run an extended SMART test first if you want.
  23. The fact that it worked once makes me thing it could still be a power/cable issue, but I understand you already tested with different power and SATA cable? Do you have another controller you could test with? A cheap 2 port Asmedia/JMB controller would do.
  24. Post diags but it the CPU overheats when maxing out a core there are cooling issues, clean the cooler and check the thermal paste.
×
×
  • Create New...