cpsmith516

docker ls netwrork (assuming typo should be network and a missing dash before ls) is not working. "Unable to parse logging level "s" ip a is attached recreated interface, with IP set to none on the host, still unable to use on any containers just as before.

You misunderstand the post. None is not what I selected, none is what it forced to because my desired bridge is not displayed as a choice. The desired bridge interface should be br0.4 (which corresponds to vlan 4 pictured in the above screenshot). Unraid / Docker will not display this as an option unless I put an IP on the interface on the Unraid host configuration, which I absolutely do not want, and have never had to have before 7.0. Adding screenshots of how it is forced to work in 7.0 for you.

Since upgrading to 7.0 I am no longer able to have a docker vlan interface with the IP address set to none and be able to use that network interface in containers. In previous versions, the Unraid host did not need an IP for Docker to allow me to use the interface on containers. Instead now I must set an IP on the host or use DHCP before Docker will allow me to use the vlan'd interface on containers. Was this an intentional change and if so, why? I only want my Unraid host to be addressable/accessible via it's IP, not over my container or virtual machine vlans. Attached two screenshots for reference of desired configuration and how the interface does not show up on the container for use (it previously did and worked on 6.12)

Will make new thread for visibility. Have figured out the bug/cause of the dns copy issue. Thank you all for your help in getting this figured out.

did that, now we're all green. copying over DNS name still hosed though. diags attached unraid-diagnostics-20250111-1110.zip

Same issue after export import. Disk still showing blue square.

I am on 7.0 stable release as of this morning; was on RC2 prior. I did see the files, and have already taken action on them; nothing critical there. Will try export and import (again) but I have done this already multiple times as part of reboots and so far nothing has changed, especially the ability to write large files out to shares via DNS name.

Ok new disk has been added to the array, resilvered, and pool is online again. However, Unraid does not seem to be in love with this new disk. It shows up as "new disk" on the Main page, instead of green online and healthy. Another side effect I'm now having, not sure if it's related at all or what's going on is I cannot reliably access over the DNS name. What I mean by this is, I can navigate shares, I can create small text files, but opening up a video file or copying large files like ISOs doesn't work; but if I do it over the IP address it works fine. This just started popping up after the issues with slow copy and subsequent failing disk which has now been replaced. I probably need to start a fresh thread for this new and separate issue, but just wanted to update the original thread with this information in case anyone that has already commented has seen something like this before and knows where to look to fix these two new issues.

Yep, already set the disk to offline before making the post actually. Way ahead of you there. Still same result with 0% transferred. Only thing I haven't done yet is reboot the server or stop/start the array since setting the disk to offline; and that's due to the rebalance script still running against one of the folders. It should be done overnight, which will have all my vdevs on an even keel now. I'll attempt a reboot tomorrow and see if I'm able to copy things over afterward. In the mean time a new disk is on the way but won't be here until Saturday. The wife is starting to get antsy not being able to backup her YouTube content and having it all sit on her SSD's.

I can access the share, when I copy a file from a windows device it sits on 0% and fails after some minutes with a try again button. I can copy files locally on device using ssh from one folder to another.

The plot thickens. Apparently I cannot copy anything to the array now over SMB. I can however make copies of files over SSH. I incorrectly assumed things would return to normal while this 1 bad disk was disabled, but that is not the case. Anyone have ideas on how to get things functional again while I wait on the replacement disk to arrive?

Thanks team, it looks like a bad disk has been located. It took running an inplace rebalance script to get it to completely fault out. Once it did, and offlined in the array, speeds a blisteringly fast now. Replacement disk has been ordered. That said, anyone know of a better way to sniff out a bad disk rather than having to wait on a symptom like this to show up?

Scrub runs monthly on the 1st; it last ran on Dec 1.

Came home from vacation and my wife was encountering issues uploading her camera footage (4k files) to our server which is an array of ZFS mirrors. It's been working fine for over a year now with no issues. To eliminate her PC as the issue, I attempted to copy from my PC to the server, and encountered the same. When writing these large files, the first 2GB or so flies, then the transfer falls on it's face to 0 b/s and after a few minutes fails completely on both Windows 11 and macOS. I was however able to create a small text file in the same share without issue so permissions were not the culprit. I then attempted rebooting the server, only to discover the array takes literal hours (up to 5) to start and fully mount up. This was all yesterday (Friday), and today I spent all day troubleshooting attempting to solve. Performing pv copies from a command line will transfer large files, but at very very slow speeds, Krusader, appears to hang, but maybe it works if I just let it sit long enough (we're talking up to an hour to move a 8 GB video file). Mid-afternoon today (Saturday) I have upgraded to the RC-2 of 7.0 to see if the ZFS upgrades would solve this problem; spoiler alert, they didn't. Attached are my diag zip, syslog, and a screenshot of the Windows error when I try to copy a large file after it sits for 2-3 minutes on 0 byte / sec speed. and I'm hoping for some guidance and help here as I've run out of ideas despite scouring the net and reddit for any ZFS related wisdom out there to help me figure out what's going on. unraid-diagnostics-20250104-1856.zip unraid-syslog-20250104-1755.zip

Anyone at all? I'm on the latest release of nvidia driver and unraid.