Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))
  2. Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  3. What drive(s) exactly do you want to replace?
  4. Enable the syslog server and post that after a crash.
  5. Do you mean the NVMe device drops offline? That would be a different issue.
  6. The is from mcelog, not Unraid, you can ignore, fixed for v6.11.
  7. You have 30 days from the activation day, then it can be extended twice for 15 days each time.
  8. Post new diags after checking the cables to see if there are still issues. A good quality single rail 550/600W PSU is enough for that, Corsair and Seasonic for example are usually well regarded, though avoid the cheapest models, go for a gold model.
  9. This is usually a flash drive problem.
  10. Reformat the flash drive, make sure it's using a USB 2.0 port, and if you get more issues replace it.
  11. Run again without -n or nothing will be done, if it asks for it use -L.
  12. It should discard and free any unused space when you run trim in the VM OS.
  13. Everything looks good in the beginning, then there's nothing else due to log spam: Aug 7 14:27:17 Ironhide kernel: vfio-pci 0000:0c:00.0: BAR 1: can't reserve [mem 0xb0000000-0xbfffffff 64bit pref] ### [PREVIOUS LINE REPEATED 1082469 TIMES] ###
  14. There's something reading from disk5, for better parity array performance you want to do one thing at a time.
  15. It's not logged as a disk problem, and SMART looks good, most likely power/connection issue.
  16. Possibly, using wipefs to delete just that info, but it's something I've never tried, so cannot help with.
  17. That is just the syslog, and it's being heavily spammed, reboot and post the complete diags after array start.
  18. This suggest the drive was previously used with Linux RAID and not properly wiped before using it with Unraid, it should still mount with Unraid, in the array or pool.
  19. @ilarionsplit you post here, as mentioned there FAQ thread is not for questions. It works with btrfs or xfs, which filesystem are you using?
  20. If you only get 10MB/s with turbo writes please post the diagnostics.
  21. Power down, run chkdsk on the flash drive (or re-format) and boot again, if you see flash drive errors again replace it.
×
×
  • Create New...