Jump to content

JorgeB

Moderators
  • Posts

    67,726
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Please use the existing plugin support thread:
  2. Previous issue was logged as a disk problem, but the extended test pass so it should be OK for now.
  3. -device vfio-pci,host=0000:05:00.0,id=hostdev1,bus=pci.0,addr=0x9 \ 05:00.0 RAID bus controller [0104]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: Fujitsu Technology Solutions HBA Ctrl SAS 6G 0/1 [D2607] [1734:1177] Kernel driver in use: mpt3sas Kernel modules: mpt3sas The LSI is being passed though to the VM, so when you start it Unraid loses access to it and the disks.
  4. Correct, e.g. Corsair CX and TX series used different modular cables, using the wrong one will fry the components.
  5. Since it's a different issue you should make a new post in the KVM section.
  6. Preclearing is going to wipe everything, so it doesn't matter.
  7. Strange, It's working fine for me, both the 9211-8i and 9300-8i.
  8. If it boots in safe mode it suggests an issue with a plugin, first thing to try is to remove them all and test, if it boots re-add one by one.
  9. Macvlan call traces are usually the result of having dockers with a custom IP address, 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/
  10. Should be. Disk5 dropped offline so there's no SMART, power cycle the server and post new diags.
  11. Since it mentions the UD plugin you should repost in the existing plugin support thread:
  12. Please use the existing docker support thread:
  13. You can copy/past from the GUI/CLI, or just see if the disk now mounts.
  14. Some workarounds discussed there, mostly disable NFS if enable and not needed or you can change everything to SMB.
  15. Looks like some writes were lost to that device, best bet it to backup the disk, re-format to create a new filesystem then restore the data back.
  16. Please don't ask questions in the FAQ thread, there's a FAQ feedback thread or just create a new thread. Probably not that complicated, but I know almost nothing about scripts, feel free to post here if you or anyone else can make one.
  17. Did you try with the latest rc? Don't remember if this has been fixed or not, I flashed that controller to IT mode so no way of testing for now.
  18. You're welcome, I also didn't notice that when you posted the command, or would have brought it up.
  19. There's known issue with those not showing temps on v6.9..x, did you try v6.10-rc2?
  20. You didn't need that, in the link I posted first thing it mentions is to format the drive, but looks like you went directly to the end of the thread where it mention the PSID, but that is only for SED drives.
×
×
  • Create New...