aragorn18

Thank you! I mistakenly assumed that I was on the latest version.

When I try to enter 'use_ssl no' at an SSH prompt, I get the following error: -bash: use_ssl: command not found

After 2 hours of running, the dockers came back up this time. So, I'm not sure if this is a relevant log file but I've attached it anyways. I'll let it run tonight and see if it works better. backupdiag.log

Correct

root@Tower:~# cat /var/lib/docker/unraid-autostart binhex-nzbhydra2 binhex-plexpass binhex-radarr binhex-sabnzbd binhex-sonarr Netdata ombi organizr

Unraid 6.6.5. I have confirmed that the docker containers are definitely not running. They do start up when I manually start them though. Here are all of the CA Backup/Restore messages from my syslog from last night: Line 2960: Dec 2 05:00:01 Tower CA Backup/Restore: ####################################### Line 2961: Dec 2 05:00:01 Tower CA Backup/Restore: Community Applications appData Backup Line 2962: Dec 2 05:00:01 Tower CA Backup/Restore: Applications will be unavailable during Line 2963: Dec 2 05:00:01 Tower CA Backup/Restore: this process. They will automatically Line 2964: Dec 2 05:00:01 Tower CA Backup/Restore: be restarted upon completion. Line 2965: Dec 2 05:00:01 Tower CA Backup/Restore: ####################################### Line 2966: Dec 2 05:00:01 Tower CA Backup/Restore: Stopping binhex-nzbhydra2 Line 2975: Dec 2 05:00:05 Tower CA Backup/Restore: docker stop -t 120 binhex-nzbhydra2 Line 2976: Dec 2 05:00:05 Tower CA Backup/Restore: Stopping binhex-plexpass Line 2977: Dec 2 05:00:06 Tower CA Backup/Restore: docker stop -t 120 binhex-plexpass Line 2978: Dec 2 05:00:06 Tower CA Backup/Restore: Stopping binhex-radarr Line 2987: Dec 2 05:00:09 Tower CA Backup/Restore: docker stop -t 120 binhex-radarr Line 2988: Dec 2 05:00:09 Tower CA Backup/Restore: Stopping binhex-sabnzbd Line 2997: Dec 2 05:00:11 Tower CA Backup/Restore: docker stop -t 120 binhex-sabnzbd Line 2998: Dec 2 05:00:11 Tower CA Backup/Restore: Stopping binhex-sonarr Line 3007: Dec 2 05:00:14 Tower CA Backup/Restore: docker stop -t 120 binhex-sonarr Line 3008: Dec 2 05:00:14 Tower CA Backup/Restore: Stopping Netdata Line 3009: Dec 2 05:00:17 Tower CA Backup/Restore: docker stop -t 120 Netdata Line 3010: Dec 2 05:00:17 Tower CA Backup/Restore: Stopping ombi Line 3019: Dec 2 05:00:24 Tower CA Backup/Restore: docker stop -t 120 ombi Line 3020: Dec 2 05:00:24 Tower CA Backup/Restore: Stopping organizr Line 3029: Dec 2 05:00:31 Tower CA Backup/Restore: docker stop -t 120 organizr Line 3030: Dec 2 05:00:31 Tower CA Backup/Restore: Stopping tautulli Line 3039: Dec 2 05:00:38 Tower CA Backup/Restore: docker stop -t 120 tautulli Line 3040: Dec 2 05:00:38 Tower CA Backup/Restore: Backing Up appData from /mnt/user/appdata/ to /mnt/user/CommunityApplicationsAppdataBackup/[email protected] Line 3041: Dec 2 05:00:48 Tower CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar -cvaf '/mnt/user/CommunityApplicationsAppdataBackup/[email protected]/CA_backup.tar.gz' --exclude 'docker.img' * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress Line 3142: Dec 2 05:51:35 Tower CA Backup/Restore: Backup Complete Line 3143: Dec 2 05:51:35 Tower CA Backup/Restore: Verifying backup Line 3144: Dec 2 05:51:35 Tower CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar --diff -C '/mnt/user/appdata/' -af '/mnt/user/CommunityApplicationsAppdataBackup/[email protected]/CA_backup.tar.gz' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress Line 3150: Dec 2 06:07:09 Tower CA Backup/Restore: ####################### Line 3151: Dec 2 06:07:09 Tower CA Backup/Restore: appData Backup complete Line 3152: Dec 2 06:07:09 Tower CA Backup/Restore: ####################### Line 3153: Dec 2 06:07:09 Tower CA Backup/Restore: Backup / Restore Completed

I don't see anything about turning auto restart on or off in the settings.

Starting last week I noticed that when CA Appdata Backup/Restore takes down my docker containers for backup, they're not being automatically restarted. The Backup/Restore status claims that it's trying to start the containers but I don't see that in the container logs. Are there log files that I should be looking at to help diagnose this?

Ok, I'll give memtest a try. Thanks.

Earlier today I had my cache drive start going read-only. After stopping and restarting the array it would work for a few minutes and then go read-only again. I tried doing a btrfs repair but that didn't help. I figured my drive was failing so I pulled it out, replaced it with another SSD that I knew worked and restored from backup. Well, about 6 hours later the second drive started doing the same thing. However, now I can't even get that second drive to mount at all. It currently says "Unmountable: No file system" I looked at my syslog and there are all kinds of errors from btrfs in there but I don't know what to do about them. I have attached my diagnostics from when the cache drive went read-only. tower-diagnostics-20181124-2358.zip

Full disclosure: This was a hypothetical. I have some old small drives that are likely to fail at some point due to old age and I'm not really interested in replacing them with a new drive because I have so much free space otherwise. But, I didn't want to go into all the details in my first post. Sorry for the subterfuge.

Thanks everyone. I have the information I need.

I was hoping there was a way without breaking parity.

I have a failed drive and it is very small. I would prefer to simply move the data that was on the failed drive to the remaining free space on the array and remove the failed drive. Is there an easy way to do that?

I had a network drop today on 6.6.3 with a Realtek NIC. I had to log in to the console and restart rc.inet1 and then the connection came back.

Thanks! That looks exactly like my problem.

Ever since I upgraded to 6.6.0 I have been having problems with my server where the network connection just drops out. Originally the server was using DHCP and it would lose its address and go to a 169.x.x.x address. I have tried changing the IP to static and that didn't fix the problem. I can log in to the console but I can't ping the local gateway. Sometimes restarting rc.inet1 fixes the problem. Sometimes I have to restart it multiple times. But, sometimes the only thing that fixes it is to fully reboot the server. I have looked through syslog and I can't find any records around the times when the network connection drops. I have attached the anonymized statistics to this post. I had a network drop sometime in the middle of the night that I had to log in and restart the inet1 service but I don't know the exact time. Please help. tower-diagnostics-20181020-1443.zip

When I built my unRAID server I originally didn't have a cache drive so all of my shares were on the array, including appdata. Later, I added a cache drive and I wanted to move the appdata share to it so that the array disks could spin down. I set the appdata share to prefer the cache disk and the majority of the files were automatically moved to the cache disk. However, some files remain on disk 1 and disk 2. I have tried setting the share to Only use the cache disk and that didn't help anything. I also tried shutting down the docker container and rerunning the mover and there are still files on disks 1 and 2. I have checked the Open Files plugin and the files are definitely open on disks 1 and 2. I am running unRAID 6.4rc8q. Any suggestions?