atlasalex

Ah, I may have quoted the wrong post as I was reading through this. Diagnostics are attached. It's just odd that it was working fine and then randomly stopped. tower-diagnostics-20231023-1206.zip

I'm in the same boat. I have a GTX 1060 that was working great for transcoding. I recently noticed that my GPU Statistics said "N/A" for everything and the GPU doesn't work anymore. I'm getting a ton of those RmInitAdapter failed messages now, but I didn't change anything with my BIOS or HW. Not sure why this would just start all of a sudden and it seems like it's happening to multiple people.

For everyone following this thread, I created a new a share to do some testing. I found online that supposedly authenticated SMB is more reliable for TimeMachine than using Guest access. I don't know if others are using Guest access for TimeMachine, but I was. Once I created a new share with an authenticated user, my TimeMachine is suddenly much faster. Hopefully this can help someone else while we wait for additional answers. Here is a video on how to set it up from scratch from Space Invader One:

@limetech You guys are awesome. Can we get an update on this issue please?

I've been trying to monitor mine and it still seems slow. It's estimating 2 hours to backup 450MB. Any update on this?

@limetech, hey there, any update? Is this being worked?

I agree. Any update?

Here it is with two devices trying to backup and hardlinks disabled. It appears that it's extremely bursty. It will go from 0b/s to 90 KB/s to 2MB/s and then back to zero constantly. Both backups are taking multiple hours to complete. tower-diagnostics-20200208-2244.zip

I am also having this same issue. I have attached my diagnostics while running a backup. (This is without disabling hardlinks. I can post another after disabling.) tower-diagnostics-20200208-1555.zip

Looks like it's alive! Rebuilt an entirely new USB with 6.8.2 on it and transferred over my /config. Then I had to boot it into Gui Safe mode and in the GUI turn off the bonding. Let it get an IP address, reboot into normal mode. Hit the tower via the DHCP address. Then had to turn bonding back on to get it to take it's static IP again for some reason. Then had to request a replacement license key. One question I had that I haven't been able to find an answer on: Is it best practice to stop the array before an OS Update (Unraid or NVidia)?

I used the UnRaid disk creator originally. The USB has had no issues until the reboot after the update. I have since built an entire new USB and will report back.

I even created a new USB and copied over the /config file. Then it would boot, but it would get a self-assigned 169 IP address... So I booted it into GUI safe mode, removed all of the bonding and static IP. Then I rebooted and it still gets that. No other devices on my network are having an issue.

Here are the diagnostics. Networking on the device seems very broken to me.... tower-diagnostics-20200204-0153.zip

Yes, it shows and I can navigate to the boot and the config