torch2k

Both servers are running on 6.8.3 and overall work great. Issue is trying to access my shares from Windows 10 File Explorer. The newest server, located at \\torch, allows me to access my shares instantly. Shows up as TORCH in Network panel. However, the older server at \\tower never shows up in the Network panel. And, it takes several attempts of trying to get \\tower, \\TOWER, etc. over about 30 seconds or so, and then I can access the server and my shares without issue at that point. I'm wondering if it's maybe the server taking time to spin up disks, but if that was the case, I thought that it would still show me something at \\tower right away. Any thoughts? tower-diagnostics-20201005-1437.zip

I'm a bit of a tinkerer and I'm interested in giving FreeNAS a go right now. Is it reasonable for me to think that I could fire up my server with a FreeNAS boot disk and have it import my zfs pool I currently have on Unraid without any hitches? What if I wanted to come back to Unraid later on?

followup, here's something I've tried in the meantime, but without success yet. created a disk image of the droplet via the command: ssh [email protected] "dd if=/dev/vda1 | gzip -1 -" | dd of=image.gz I unzipped and renamed to vdisk2.img. Moved vdisk2.img to the Unraid server and re-configured VM to use it after setting the correct ownership and permissions on the file. Tried booting a pre-exisitng Ubuntu 18 VM off of the new image, but it just wants to re-install at Grub. Any thoughts?

Just looking for ideas on how to accomplish this, and if it's possible. Essentially, I'd like to move a 2GB Digital Ocean droplet over to a an identical VM running on Unraid. Is there a backup and restore option that's possible? Would I need to create the VM first, and then perform an rsync of the entire drive?

Sounds right. Would be great is you guys (LSIO) rolled out an alternative like NOIP, etc.

Anyone else having issues today? It appears that DuckDNS is offline this morning.

It actually never crossed my mind to use that method. Perhaps the SMB method would work well within a VM, but I've been having a pretty miserable time with SMB lately, actually (see my others posts). I'll try that method and see if it will get me up and running. Perhaps unique to my issue is that the VM in question is running off of a pass-through disk. Accessing the Unraid shares is vital in this scenario so that I can backup files off of the VM and onto the protected array.

I think by disabling NetBIOS the glitch has gone away, i'll continue to monitor it.

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?

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

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

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

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?

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?

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)

Yup, same power and same sas cable.

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

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

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.

That did the trick! Thank you.

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

That worked, thanks!

My motherboard currently has eth0 and eth1 set as a br0 bond. I've added a new 10Gb NIC that is showing up as eth2 and eth3. I believe I can edit my Dockers and tell them to use the new br3 bond, but what about my SMB shares? I would like to connect to my shares over the local network using the new 10Gb NIC, not sure how to tell Unraid to use that connect over the motherboard's. network-rules.cfg network.cfg

@dlandon what is the correlation between using UD's "mount" and "auto mount" buttons, and passing through a device to a VM? I currently have a new ubuntu install that follows the same steps as earlier, but this time on reboot, the drive did not corrupt. As far as I know, the only different is that this time, I've booted up the VM and have left both UD devices as unmounted on the main unraid screen. I'm afraid that if I click "mount" in UD it will break everything. Any thoughts?

I've repeated this a third time, but now by using a different SAS drive to ensure it wasn't the SSD failing.