UnBeastRaid

unraidbeast-diagnostics-20251105-1714.zip Just to be clear, I have not changed any settings or configurations from previous UnRaid versions. @phunky1 is experiencing a different isolated issue.

Hello After updating to Unraid v7.2 (stable), file transfers from my Windows 10 VM (running on Proxmox) to the Unraid server consistently fail with an error, regardless of file size. This issue did not occur on previous Unraid releases. Interestingly, the transfer succeeded once immediately after restarting the Windows VM, even for files exceeding 4 GB. Subsequent attempts reproduced the error. Has anyone else encountered this behavior on v7.2? This file is 4.2GB This file is 18.5KB

Any reason the checksum is failing when upgrading to v560.28.03?

I'm curious to know if anyone else has issues with Fix Common Problems reporting on Docker memory. What is happening with the docker memory usage, the timestamps of the notifications are from last night when I was watching a movie via plex. Any insights would be appreciated. fix_common_problems.mp4

So I ended up just moving all files from the unassigned drive into cache, formatting the new drive and moved everything back. Worked like a charm.

Here are the steps I have taken: Tried to resize btrfs patition to max but got an error?

Hello, I use an unnasigned SSD to store the appdata for various services. I recently started using Photoprism and it started eating up the 500gb quickly due to thumbnails. So I decided to upgrade the drive to 2TB. I have an offline cloning device that I used to clone the 500GB --> 2TB drive. Now, when using the 2TB SSD in the server, it still shows up as 512GB total. How do I expand the drive to the full 2TB? Thank you

Came home to find my server shutdown but everything else around was on and fine. I've ran through logs via unraid CLI (var/log/syslog etc...) but what I found were the logs post reboot. I need logs that took place before the unclean shutdown happened. Diagnostics logs created post reboot. Where can I find such historical logs? Thanks!

Hello, what is the reason appdata backup keeps terminating the backup process? I have an unassigned disk that holds my plex appdata that I'd like to back up. Any thougths? One of the lines below says "should NOT backup ext volumes" is this the root of the issue? Thanks! 17.05.2023 18:34:15][Main][info] Method: Stop/Backup/Start [17.05.2023 18:34:15][Main][debug] Not executing script: Not set! [17.05.2023 18:34:15][Plex-Media-Server][info] Stopping Plex-Media-Server... [17.05.2023 18:34:24][Plex-Media-Server][info] done! (took 9 seconds) [17.05.2023 18:34:24][Plex-Media-Server][debug] Backup Plex-Media-Server - Container Volumeinfo: Array ( [0] => /transcode:/transcode:rw [1] => /mnt/user/:/data:rw [2] => /mnt/disks/plex_appdata:/config:rw ) [17.05.2023 18:34:24][Plex-Media-Server][info] Removing container mapping "/mnt/disks/plex_appdata" because it is a source path! [17.05.2023 18:34:24][Plex-Media-Server][debug] usorted volumes: Array ( [0] => /mnt/user [1] => /transcode ) [17.05.2023 18:34:24][Plex-Media-Server][debug] Should NOT backup ext volumes, sanitizing them... [17.05.2023 18:34:24][Plex-Media-Server][info] Plex-Media-Server does not have any volume to back up! Skipping [17.05.2023 18:34:24][Plex-Media-Server][info] Starting Plex-Media-Server... (try #1) [17.05.2023 18:34:29][Main][info] VM meta backup enabled! Backing up... [17.05.2023 18:34:29][Main][debug] tar return: 0 and output: 1 [17.05.2023 18:34:29][Main][info] Done! [17.05.2023 18:34:29][Main][info] Checking retention... [17.05.2023 18:34:29][Main][debug] toKeep after slicing: Array ( [0] => /mnt/user/backups/Plex AppData Backup/ab_20230517_183415 [1] => /mnt/user/backups/Plex AppData Backup/ab_20230517_181430 ) [17.05.2023 18:34:29][Main][debug] Delete backups older than 20230510_183429 [17.05.2023 18:34:29][Main][debug] Discarding /mnt/user/backups/Plex AppData Backup/ab_20230517_183415, because its newer or already in toKeep [17.05.2023 18:34:29][Main][debug] Discarding /mnt/user/backups/Plex AppData Backup/ab_20230517_181430, because its newer or already in toKeep [17.05.2023 18:34:29][Main][debug] Resulting toKeep: /mnt/user/backups/Plex AppData Backup/ab_20230517_183415, /mnt/user/backups/Plex AppData Backup/ab_20230517_181430 [17.05.2023 18:34:29][Main][debug] Resulting deletion list: [17.05.2023 18:34:29][Main][debug] Not executing script: Not set! [17.05.2023 18:34:29][Main][info] DONE! Thanks for using this plugin and have a safe day ;) [17.05.2023 18:34:29][Main][info] ❤️

The VM is always on. Only actively read/write at 24:00hrs

Thanks for your help guys. The Proxmox server backs up my proxmox nodes nightly at 24:00hrs

Ok..here is the diagnostics file. The 2.15TB in the domains share belongs to my proxmox backup server. unraidbeast_diagnostics_post_mover_2.zip

just to be clear, post diagnostics without turning on VM manager & Docker...correct?

Only 500GB. 2 nvme in raid 1

Here are the new diagnostics post mover completion. Cache usage is at 34GB. The docker image hasn't occupied the cache drive...or does it? unraidbeast_diagnostics_post_mover.zip