mkyb14

Looking for some insights into why hydra2 stopped working after what seems like years.... no changes made to the server other than auto updates for the docker img... Anyone else have it stop working?

checking in to see if any of the screenshots or info make any sense?

Trurl, here's the screenshot. Nothing seems abnormally large. How would I find out what's taking up the rest of the space within the docker file (30gig)?

I've been reading about the docker image filling for a while now, making changes to what I thought was the correct way to setup over the years... but it always seems to be growing. Think it's set to 30GB atm. Looking to see if someone can look at the images below and give a quick (ah-ha) moment to understand what I might be missing. Current setup is a SM-846 with only 5 HD's and 2x 500gb ssd for cache. Currently docker is around 85%, and only seems to really go up when I download something new to plex. I thought all my settings were correct to have the Cache for appdata and downloads so that it's fast and move everything to rust when mover runs... but it would seem I'm either missing something or not understanding if my setup is correct. I'm guessing it's plex, and I'm guessing it's library files...

Checking back to see if I have this setup correctly ?

Couldn't tell you why, thought it was for speed and being close to the appdata for dockers (relative paths). If that's incorrect, I'm fine making changes, just looking to know what the ideal setup is for what I would consider a standard unraid setup. SSD Cache, drives, dockers and vm's.

Believe this is it.

diagnostics posted. to be honest, once unraid was up and running, never really had a problem. but in backing up my system, I was just concerned that the downloads folder was so large. I thought everything was setup with the SSD Cache drives mostly for docker and downloads to make sure they were as fast as possible. Mover running once a week or month to get it off to the spinning rust. Second server was to backup using proxmox and zfs. tower-diagnostics-20200713-1939.zip

Looking to make sure I understand the folder structure and why files are in certain directories. I know this has been covered probably many times, but didn't find a quick answer when looking. Currently I have another NAS that I'm backing up CA Backup plugin to (Unassigned Devices plugin). In doing so I was curious to the USB / libvert.img sizes and then the backup location which showed plex having 18GB... so running on that largest folder I noticed that the downloads folder was even larger #du -sh -- * /mnt/user/appdata/Downloads 169GB Completed 5.6GB Incomplete 0 Unzipped_Torrents Running mover, still has 200+GB on the drives. Guess I was under the impression the Downloads folder once mover was run would clear out, but there are many older files and folders still in there. Is that normal? Am I missing a setup in my config?

Ignore that, just figured out my own stupidity after another cup of coffee. files are mounted in /disks and for some reason I was dyslexic. rsync -av --progress --human-readable /mnt/user/Movies/ /mnt/disks/PVE_BigData_Files/Movies/ rsync -av --progress --human-readable /mnt/user/Movies/ /mnt/disks/PVE_BigData_Files/Movies/ works. now to let this run for a year

I always forget how I did it, and or can't find on google what's going wrong. Setup is a Proxmox ZFS share in SMB (confirmed it's mounted and works. have multiple time machine backups hitting folders within this share) Unraid 6.8.3, and mounted that share locally on the MAIN page. lists the share as //pve/BigData. What I'm not getting is that I was expecting to see a local mount point in /mnt and thought I would be doing a local rsync between the /user/Movies within unraid to /mnt/Movies etc.... but I don't see /mnt/otherserver smb share listed there... what am I missing? unraid is 192.168.22.20 Proxmox ZFS is 192.168.22.21 with a SMB share direct from within proxmox /BigData. Side note: I then tried just straight up from unraid in ssh terminal: rsync -avP --dry-run ~/Movies [email protected]:~/BigData/Movies/ [email protected]'s password: sending incremental file list rsync: link_stat "/root/Movies" failed: No such file or directory (2) created directory /home/Apollo/BigData/Movies sent 18 bytes received 62 bytes 22.86 bytes/sec total size is 0 speedup is 0.00 (DRY RUN) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1189) [sender=3.1.3] not sure why it's looking at /root/Movies and trying to create a directory within proxmox in /home/Apollo/BigData/Movies when it's in the root of the system when I look at the terminal there. Simply just trying to mass move from Unraid to a ZFS share 100TB

I never added any data to those disks. I installed them, forgot about them and when SMART ran it found they were bad. so I disabled them. Doing a new config would be wiping everything? I remember reading about it, but not fulling understanding if I was going to lose everything. I'm guessing based on what I remember, and your comment. That doing so would allow me to remove the disks, but the whole thing would need to rebuild from parity less the disks I removed, and would take what ever amount of time unraid does for my data set (30hrs).

got it, thank you. There's no easy way to remove that correct? Thanks again for the answer, sorry it took so long to come back around and give thanks. New kid, new focus in the house.

Looking for some guidence on why my parity is showing as invalid. Been running unraid for 2 years now, no real issues. just noticed that I got the orange triangle. Did a manual scan last night and it has 0 errors. Only thing I can think of is that I put an old drive in a while back and it failed, (no data on it) I was just adding it to the system for eventual use. IF that's the reason, can I not simply remove the drive from the array since there's no data on it with out blowing everything up? Never removed a drive in unraid before.

ok, so manually typing everything in worked.... I even made sure after pasting it in previously to delete and spacing and re-type the last letter to make sure there were no spaces... ok, back in business! Thank you.