BDPM

It is the original install flash drive. May 2019 Might be a good idea to replace it. Regardless if it is the problem. Thanks!

Good Morning All, I went to update my nextcloud this morning, but before I run their updater I always like to make sure the docker container is up to date. When I went to login to Unraid, the normal login screen was gone. It was just plain text with some lines of encountered errors. I tried refreshing the url, nothing. The links were click-able, so I went to the terminal, did "sudo shutdown -r now". Unraid rebooted, and now seems to be back to normal. The only thing I notice is that it is now doing another parity drive check. It just did one the other day. I have it scheduled to run monthly on the first of the month. It takes about 12hrs. Anyway, I will add the text that I copied off the screen before I rebooted. Im going to make an attempt to look for log files to see if there is any indication in them. Although I have no idea what Im looking for or where to look for it. LOL. If anyone has any suggestions on what actions I should take, if any, I would be grateful. I have been using unraid for a few years now, and love it. Basically, set it and forget it after all of the initial setting up. Thank you all. Unraid_Errors.doc

I think i picked up the term resilver around ZFS or Freenas days. But yes, rebuild, same thing.

Custom Backup scripts. I will re-silver and then run the scripts. Thanks

Drive will be here in a day or two. Resilver or let backup scripts do it? Disk 3 is only for backup purposes.

Thanks all.. Diskspeed docker revealed problem below. So it looks like disk 3, my backup drive, is failing. That sucks, but I have critical data remotely backed up as well as locally. Non critical data will get backed up during the daily backup. My question now is, should I just replace the drive and let backup scripts do their job, or replace the drive and re-silver it?

yes. Still horribly slow. Ill try the speed test docker Total size:6 TB Elapsed time:10 minutes Current position:2.60 GB (0.0 %) Estimated speed:3.9 MB/sec Estimated finish:17 days, 14 hours, 29 minutes Sync errors corrected:0 I tried turning off all dockers and the vm that was running. It helped. Got up to around 9MB/sec LOL.. I canceled the check. Restarted the server. Started check again. Above is where I stand now.

Honestly, i dont know. Mover runs on a schedule I think. The daily data backup runs and is completed as normal. Weekly appdata backup isnt running. It has run before in 12hr. I dunno what has been changed.

Parity check 1 time a month. They used to run about 12 to 15 hrs. Now its saying 17 days to complete. I dont even know where to begin looking. Any suggestions would be greatly appreciated server-diagnostics-20200908-0431.zip

Well, damn. Thanks. I will check out that thread. Thanks.

I have several containers running, and today, for the third day in a row, every single linuxserver.io container has had an update. They've all been running great, for at least 6 months, and still are, even after updates. I have no problems. But, is this normal? I've noticed in the past that linuxserver.io updates more frequently than others, but this seems crazy. Just wondering if anyone else is having the same thing happen. BDPM

Thanks Saarg. I was typing when you were I guess.. Any advice for future non freaking out? LOL BDPM

Okay.. so I noticed that one of the cache drives in the cache pool was missing. I shutdown the server, jiggled the cables for the cache drives, made sure they had power and data cables were secure. They are the clippy kind so I dont know why they could have gotten loose, but when I rebooted, the cache pool started the rebuild of btrfs thing and all of the containers and appdata folder is restored. whew... that freaked me out for a few minutes there. Any input to prevent more freaking out in the future would be appreciated. I think I would rather have a bigger cache drive than pooling two 120's. BDPM

I did the following AFTER the 6.7.2 update, along with a radarr update I believe. I was watching a movie on my plex this morning. I also was checking sonarr and radarr this morning. Everything was working as far as I could tell. I went and ran some errands, stopped for lunch, then came home to plex locked up. It wouldnt restart. So I just rebooted the server. When it came back up all of my docker containers are gone and the appdata folder is empty... HELP!!! I do have appdata backup and it was successfully backed up last night, but I would like someone who is smarter than I to suggest method to get back up and running. BDPM BDPM Diagnostics.zip

Thank for the reply. Honestly, I have seen MIB mentioned in documentation, but I dont know what that is. LOL I went to observium IRC channel, asked around, and was told that I needed to add the agent to whatever server I wanted to monitor. I started to do that via this site https://docs.observium.org/unix_agent/ seems to me that it should work, but when I got to "restarting the service" I couldnt figure out how on unraid, so I just rebooted the server. When I went to continue the setup, I checked the observium_agent_xinetd file that had been scp over and edited. It was gone. So I tossed in the towel for the day. I used nerd tools to install xinetd, and it is still there. The edited file just poofs after reboot. Like I said previously, Observium working great, just missing the hard drive temps. I will attach a diagnostic file of my system if you wanna take a look. Much appreciated. Thank you for your time and efforts. BDPM BDPM-diagnostics.zip