mustava

I can confirm i have the same issue after updating. Removed all my disks to downgrade. look forward to 7.0.1...

Hi All, Ive waited almost a year before making this thread. Ive been seeing a lot of threads about SMB not working in specific scenarios (mac/windows etc) but haven't seen much concrete advice being passed around. What is up with SMB in Sept 2024? has there been a root cause identified that's causing people so many issues? In my specific scenario, for some time now I have been completely unable to use SMB across mac & windows (ventura, Sequoia, win11, Wired, Wifi) My settings are stock but i have tried various configs, tweaking signing, and other things without any success. - When i copy files, the transfer freezes for minutes, even if the file is only a few KB - When i view video files across the network, they constantly buffer and freeze up. Plex container can stream perfectly well though. - Directory loading is painfully slow, often locking up explorer and finder, even if dir cache is enabled and disks are spinning Basically its gotten to the point that SMB cannot be used at all, any other system that runs an SMB server runs perfectly fine (Windows sharing, freenas etc) All though i could go down a rabbit hole of trying to tune and fix the issue, should something be done at the product level? Any word from devs? I love unraid and would hate to move away but the sole purpose for me is file sharing. Thanks for any commentary

is there anyway i can force the plugin to use the old 460 drivers?

After some further research, it seems to be a Linux/Unix/VMware/Nvidia driver issue. GPU works fine passed through to windows. As per the previous users issues, apparently driver version 460 was the last confirmed working. Apparently the new beta versions worked if the opensource kernel modules are used?

Hi All, I have just installed a 1660Super into my Unraid (6.11.4) server and am following the process outlined in this thread to get it up and running, but am experiencing a few issues. Although my GPU is shown in my system devices, once I have installed the nvidia-driver (driver 525.53) plugin, anytime anything interacts with the GPU the whole server hands and i need to reboot. This is both with the array started and stopped. This includes: - Generating diagnostics (when nvidia-driver is installed) - Launching the plugin settings page The devices is shown in System-devices as: [10de:21c4] 1c:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] (rev a1) A few notes: I am running under vmware, but pass-through works seamlessly on 3-4 other devices including PCI devices, and iGPU. I have attached the diagnostics I can access, but I cannot generate them with the plugin install, as it gets stuck on nvidia-smi.txt Appreciate any advice tower-diagnostics-20221119-2354.zip

I am now getting this error too. I have checked my DNS and everything else is resolving fine.

Wow ok - I just found the issue by chance two minutes after writing this, despite trying to fix it for hours.... Due to the new ESX installation, the vSwitch for my LAN network had the 'MAC address changes' security setting set to 'Reject'. Reject. If the guest OS changes the effective MAC address of the virtual machine to a value that is different from the MAC address of the VM network adapter (set in the .vmx configuration file), the switch drops all inbound frames to the adapter. If the guest OS changes the effective MAC address of the virtual machine back to the MAC address of the VM network adapter, the virtual machine receives frames again. I guess due to the OS having existing values, and the new install/new NIC's were assigned different values and frames were being blocked by the switch. The more interesting thing is why it worked, slowly, rather than at all...

Hi All, I successfully upgraded from esx 6.7 u2to esx 7.0 Last night. I had a bit more of a bumpy experience, Thus far: Had an issue updating the existing usb bases esx install... installed as per normal upgrade process, successfully booted from USB into esx 7.0 and started up all my VM's including unraid 100% perfect. Needed to reboot the server to toggle pass-through on a device... ESX never came back up (vmware recovery error) and forced me to start from scratch Re-installed ESX 7.0 and re-registered VM's. Boot unraid perfectly, everything comes back up perfectly including my RDM's for onboard attached sata drives. (I have a mix of RDM's and pass through drives which have been rock solid in 6.7) From this point, I have started noticing super slow performance. First in plex, and now upon further inspection even just browsing my shares. It takes a full minute to even open a share or sub folder. This is true even with nothing else is running on the server. Any one have any ideas? I cant see any suspect errors in the logs. Good luck to anyone taking the plunge!

Yes still same issue, even if i stop everything using the Disk / Array I still cant shutdown the server cleanly. Is there a way to restart the Unassigned Plugin?

Hi All, I am encountering an issue where each morning, I log into Unraid to find Unassigned devices unresponsive. Everything in the GUI and array is responsive, except the one disk mounted via unassigned devices and the GUI for unassigned devices. (just the loading animation). The disk is being used by a VM to write to over night as a bit of a scratch disk. I Also am unable to shutdown or reboot the server in this state, I am required to do a hard power off in order to restart everything. I am worried doing this is going to cause problems pretty quickly. Has anyone had this issue before?