joey911

Google is telling me support ended on my card with this version so this doesn't seem like the bug I thought it was.

Howdy. I just noticed I'm also stuck on an old driver like the person above. Image and diagnostics attached. Thanks. unraid-diagnostics-20260413-0632.zip

Howdy, I'm on 7.2.3 as I write this. I've been frustrated with the Timemachine backup speeds on macOS 26.3, so I've done a lot of digging, and using AI, to find a way to get more than 26mbs across my link. I'm going from my macbook with a 2.5g ethernet connection, to a 10g switch, to Unraid with a 2g bonded (aggregated) link. I've attached Unraid SMB Extras I'm using and the macos /etc/nsmb.conf file that I've settled on. I'm leaving these here in hopes they might help someone. unraid-smb-extras.txt nsmb.conf.txt

Support had me test without my USB expansion drives and V7 boots so it appears it is something related to not finding the flash USB during the mount process.

Generally same issue. Generic v7 image doesn't boot on my Dell PowerEdge T430. I've had a support issue #6232 open since the day of the release. V6 works, upgrade does not, V7 generic does not, v7 with config copy does not. I also completely remade the USB and that didn't help. NOTE: This is bare metal, not virtualized.

On my system it looks like only that file exists there so perhaps it not necessary to backup system then.

It looks like that didn't work as I expected. I was hoping it would just exclude that file. What I'm attempting to do is also backup the system file since I only have one cache drive.

Thanks! It looks like it came along because I specified /mnt/user/system/ as part of the backup. I've added it to the global exclusion section.

Hi, You answered the wrong question. My question was ...can you amend the store description to note that addtional setup is required and to see the support form? And add something like

Running Appdata Backup with "stop all containers, backup, start" and I'm getting this error in the log: I'm not sure what to do here since everything is stopped. Shared Debug Log as 9e627b20-3451-48f4-982d-c6e39fc17a20 Full log: [20.02.2024 09:12:41][ℹ️][Main] 👋 WELCOME TO APPDATA.BACKUP!! [20.02.2024 09:12:41][ℹ️][Main] Backing up from: /mnt/user/appdata [20.02.2024 09:12:41][ℹ️][Main] Backing up to: /mnt/user/Appdata.Backup/ab_20240220_091241 [20.02.2024 09:12:41][ℹ️][Main] Selected containers: Channels-DVR, Plex-Media-Server, calibre-web [20.02.2024 09:12:41][ℹ️][Main] Saving container XML files... [20.02.2024 09:12:41][ℹ️][Main] Method: Stop all container before continuing. [20.02.2024 09:12:41][ℹ️][Plex-Media-Server] Stopping Plex-Media-Server... done! (took 8 seconds) [20.02.2024 09:12:49][ℹ️][Channels-DVR] Stopping Channels-DVR... done! (took 5 seconds) [20.02.2024 09:12:54][ℹ️][calibre-web] Stopping calibre-web... done! (took 4 seconds) [20.02.2024 09:12:58][ℹ️][Main] Starting backup for containers [20.02.2024 09:12:58][ℹ️][Plex-Media-Server] Should NOT backup external volumes, sanitizing them... [20.02.2024 09:12:58][ℹ️][Plex-Media-Server] Calculated volumes to back up: /mnt/user/appdata/Plex-Media-Server [20.02.2024 09:12:58][ℹ️][Plex-Media-Server] Backing up Plex-Media-Server... [20.02.2024 09:13:32][ℹ️][Plex-Media-Server] Backup created without issues [20.02.2024 09:13:32][ℹ️][Plex-Media-Server] Verifying backup... [20.02.2024 09:13:51][ℹ️][Channels-DVR] Should NOT backup external volumes, sanitizing them... [20.02.2024 09:13:51][ℹ️][Channels-DVR] Calculated volumes to back up: /mnt/user/appdata/channels-dvr [20.02.2024 09:13:51][ℹ️][Channels-DVR] Backing up Channels-DVR... [20.02.2024 09:15:42][ℹ️][Channels-DVR] Backup created without issues [20.02.2024 09:15:42][ℹ️][Channels-DVR] Verifying backup... [20.02.2024 09:16:08][ℹ️][calibre-web] Should NOT backup external volumes, sanitizing them... [20.02.2024 09:16:08][ℹ️][calibre-web] Calculated volumes to back up: /mnt/user/appdata/calibre-web [20.02.2024 09:16:08][ℹ️][calibre-web] Backing up calibre-web... [20.02.2024 09:16:08][ℹ️][calibre-web] Backup created without issues [20.02.2024 09:16:08][ℹ️][calibre-web] Verifying backup... [20.02.2024 09:16:08][ℹ️][Main] Set containers to previous state [20.02.2024 09:16:08][ℹ️][calibre-web] Starting calibre-web... (try #1) done! [20.02.2024 09:16:10][ℹ️][Channels-DVR] Starting Channels-DVR... (try #1) done! [20.02.2024 09:16:15][ℹ️][Plex-Media-Server] Starting Plex-Media-Server... (try #1) done! [20.02.2024 09:16:19][ℹ️][Main] Backing up the flash drive. [20.02.2024 09:16:57][ℹ️][Main] Flash backup created! [20.02.2024 09:16:58][ℹ️][Main] VM meta backup enabled! Backing up... [20.02.2024 09:16:58][ℹ️][Main] Done! [20.02.2024 09:16:58][ℹ️][Main] Backing up extra files... [20.02.2024 09:28:14][❌][Main] tar creation failed! Tar said: tar: /mnt/user/system/docker/docker.img: file changed as we read it [20.02.2024 09:28:15][ℹ️][Main] Checking retention... [20.02.2024 09:28:15][ℹ️][Main] DONE! Thanks for using this plugin and have a safe day [20.02.2024 09:28:15][ℹ️][Main] ❤️

Thanks, yeah I misspoke there. I am using the NAS aspect for backups. I don't need HA. I have appdata installed and backing up my VMs only. My single cache drive is BTRFS.

Howdy all. Background: I built my new system apparently looking at the old style documentation (prefer cache) and I must have hit things mid-cycle because I overlooked cache pools; I just saw cache disk (singular). I'm looking for some thoughts on how to improve my setup since I just installed Plex. I also want to pick your brain for how I might make this setup a bit better. Hardware: 40 core Xenon CPUs 128gig DDR 4 memory 8 Bay tower 1TB SSD cache drive 2 Parity Drives 2 highly populated 4TB drives from my previus Unraid server 3 new 2TB enterprise disks barely populated 8 Bay USB 3 extension tower 8 barely populated disks of various sizes Nvidia card for transcoding Problem 1: Any time I make any changes or updates to Docker applications, my system freezes. Nothing responds until Docker is done. Problem 2: Docker apps are generally slow Plex is VERY slow. Calibre is slow. Channels DVR is not slow but I plan to give this up in favour of Plex. What I've done: Moved Plex transcoding to the cache drive Moved Timemachine backups to the cache drive (to relieve the array from constant usage) Other Information: Because I only have 1 SSD cache drive, I did not move system and appdata because if the cache drive fails, I'm toast. I wish there was a way to back it up to the array in case it fails so I don't lose anything. Maybe there is and I haven't found it yet? (See that question below) Because of the previous line, I also didn't bypass fuse by specifying /mnt/cache. The original intent of the server has been for NAS purposes. Because of this, I highly value data redundancy. The introduction of DVR workloads is new but it's been successful with the family so I'm going to continue this. I have some VMs running on the cache disk and I'm worried about being able to recover if I lose the cache (see further down). Things that I've been considering: Adding another SSD and add it to the cache pool enabling me to move over system and appdata I'd have to evacuate and remove a lower sized disk from the USB array and then move one of the disks from the tower. I'd hate to move one of the high quality new disks but that would be the easiest. This choice is a bit of a pain due to the tower but I can do this. Remove 2 or 3 of the new enterprise disks from the array and make them a new cache pool and move over system and appdata. Things I don't understand and could use some guidance on: Is there a way to backup the cache pool such that if it dies the system will use the array? i.e. a "copier" vs a "mover" Is data replicated across the cache pool so if I have two cache pool disks and I lose one the system will continue to function? I really appreciate any guidance you can provide me. Thanks!

@ich777 Thanks for this plugin! In the App description would you please add "additional setup required for Docker, see forums" or something? Took me a while to find the key values and such but once I did it worked like a charm.

I discovered a bunch of .fuse-hidden files that couldn't be rm -rf .* so I stopped and then started the array and was able to remove all the files in the share. Hoping this line of thought helps others. Currently time machine is backing up. It's quite possible that I assumed that rm -rf * worked and in fact left a sparse bundle around.

I discovered smbdiagnose. It generated a pcap that is saying there's a server error regarding files. I'll go nuke everything in that share and try again. I did that once but maybe it'll work this time.