Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About torch2k

  • Rank
    Advanced Member
  1. I think by disabling NetBIOS the glitch has gone away, i'll continue to monitor it.
  2. Yup, I have Enhanced macOS interoperability turned on. I also have Enable NetBIOS turned on, maybe that should be disabled to force SMB v2 or newer?
  3. I've been noticing repeated SMB disconnect/re-connects that seem very glitchy. I'm on macOS 10.15.2, connecting to Unraid 6.8.2 over a wired 1GB connection. A link to a video of what I'm experiencing. It happens at very beginning and again at the very end of the clip. https://imgur.com/a/trwJUsq Is there a way to prevent this? tower-diagnostics-20200225-1111.zip
  4. Just wanted to bump this, I haven't been able to figure it out yet. So just to reiterate: - When unraid share is not passed through, networking works, enp1s0 exists and the VM receives an IP from DHCP. - When unraid share is passed through, networking fails, enp1s0 does not exist and the VM does not receive an IP from DHCP. I just can't figure out what the conflict is. VM XML's attached with and without share passed through. vm.xml vm-with-share.xml
  5. My Ubuntu Server VM was working perfectly and had its own DHCP IP on the network. Today, I added an "Unraid Share" passthrough and the NIC disappears on boot. If I remove the share and generate a new MAC address, the NIC reappears and I get an IP on boot. Not sure how to fix? vm.xml
  6. Thank you. To properly correct my hardware issues (too many drives on not enough cables), what do I need to do? Should I be getting my hands on a 4U / 24-bay SAS enclosure instead of my Rosewill L4500 + EVGA PSU?
  7. Ok -- I believe you. Now that I've fixed that power cable, I've rebooted. My problem is that I don't remember which disks were in slot 8 and 20. And no matter what disk I slide into that slot, it's marked blue, meaning it will wipe it and insert it as a new disk, right? If that's correct, I think I need to do the following: - generate a new config with those two slots removed - let parity run - when parity is complete, mount the two problem disks with UD and attempt to copy the files back to the array Can you confirm that's a good course of action, or show me the right way?
  8. I took the power cable apart since I made it. All of my ends seem to be fine, but the wires on the feeding end practically fell out when I removed the cap. (From factory)
  9. Since last night I started to have a disk show some read errors. At first I tried to migrate files away from that disk using Unbalance, but that failed / froze. I don't even recall everything I tried at this point, but basically everything I tried, failed. Errors. This morning I have two disabled drives and one drive that was stuck in the middle of a parity rebuild. Even though I have dual parity, I think i'm in a worst-case scenario right now with data loss. On the most recent reboot, I can't even seem to get Unraid to respond normally - it's sluggish. Am I having a string of old drives failing all at once? or is this something bigger, like my SAS card failing? I don't know what to do. tower-diagnostics-20200219-0904.zip
  10. I believe this had only started happening to me since 6.8.2 but I'm not completely sure. Connect to Unraid over SMB, open a share, and it will disconnect a few seconds later. Rinse and repeat and quickly try to grab my files before it disconnects. Eventually, sometimes, it will stay put. Diagnostics attached, and link to video of it happening for reference: https://imgur.com/a/PQW9v2C Edit: I might be using the wrong terminology - even though the Finder window in macOS closes out like it's disconnected, you'll see in the video that the network share still appears to be mounted when I click back to the Unraid server. tower-diagnostics-20200217-1447.zip
  11. Is there any way to mount with rclone but have the mounted files owned by nobody:users? I'm not able to see anything over SMB/shares due to the ownership of mounted files being root.
  12. That did the trick! Thank you.
  13. Just clicked Update all and after pulling down the images, each Docker update is coming back with the following: Error: could not get decompression stream: fork/exec /usr/bin/unpigz: no such file or directory The attached logs seem to show something corresponding to network bridging, maybe connected to a NIC change I made recently? tower-diagnostics-20200213-1851.zip