pancho

Upgraded today from rolledback version (6.8.3) to the latest version 6.9.2, unfortunately same issue as above where a single CPU core locks at @ 100% endlessly. The 100% Single CPU core occurred whether the array was loaded or not. Attached new diagnostics. Anyone have any suggestions? Thanks. mediabackup-diagnostics-20210408-1422.zip

Any Suggestions here? Thanks.

Apologies... re-uploaded. mediabackup-diagnostics-20210316-1208.zip

Hello! I have a backup Unraid server recently upgraded to version 6.9.1 (spec's in my signature). Post upgrade, the S3 sleep function no longer worked (system would start sleep - and then immediately power back up). Further troubleshooting showed a single CPU core maxed out @ 100%. The 100% Single CPU core occurred whether the array was loaded or not. Ran a diagnostics (attached). Rolled back to version 6.8.3, the CPU cores now operates properly (as does my sleep function). What is strange is that I have 2 other unraid servers (same identical motherboard) running v6.9.1 that do not experience these issues. Ideas? Thanks. Frank mediabackup-diagnostics-20210316-1208.zip

Hello! I currently have a backup Unraid server that I recently upgraded to version 6.9.1. Backup server spec's: ASRockRack C236 WSI (bios v2.70) i3-6100 CPU 8GB ECC RAM 2 VM's (all powered off) Docker - Not installed Post upgrade, the Dynamix S3 sleep function no longer worked (system would start sleep - and then immediately power back up). Further troubleshooting showed a single CPU core was maxed out @ 100%. The 100% Single CPU core occurred whether the array was loaded or not. Ran a diagnostics (attached). Rolled back to version 6.8.3, the CPU cores now operates properly (as does my sleep function). What is strange is that I have 2 other unraid servers (using identical motherboard) that work with S3 sleep (no CPU maxing out either). Is it possible this is an issue with the Flash boot drive (need to wipe clean and reload)? Any other Ideas? Thanks. Frank mediabackup-diagnostics-20210316-1208.zip

Nano, I also struggled with this for my Xeon E3-1275 & ASRockRack C236WSI. Now that you have the device passed through correctly to the Emby Docker, you need to specify a transcode directory: Create a New Share (SSD Cache Only) called Transcode (or whatever you want to call it) Stop Emby Docker Add new path to your transcode share: Start Emby Docker Inside Emby Server Admin - change the Transcoding temporary path directory to your new path: See if your transcoding performance improves. Pancho

James, I struggled with this for quite a while as well with my duckdns subdomain & letsencrypt configuration. Here is the config I pieced together from several places that finally worked. I placed it here: \Appdata\letsencrypt\nginx\proxy-confs airsonic.subdomain.conf Replace XXXXXX with your own domain name Replace proxy_pass ip with the IP of your server (mine was 192.168.0.30) ---------------- # Redirect HTTP to HTTPS server { listen 80; server_name XXXXXXX.duckdns.org; return 301 https://$server_name$request_uri; } server { listen 443 ssl; listen [::]:443 ssl; server_name XXXXXXXXX.duckdns.org; include /config/nginx/ssl.conf; client_max_body_size 0; # Proxy to the Airsonic server location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header Host $http_host; proxy_max_temp_file_size 0; proxy_pass http://192.168.0.30:4040; proxy_redirect http:// https://; } }

Johnnie, Just wanted to give a big thank you for all the help. It was indeed my Seagate sata cache disk that went belly up. I tried everything to read the data, in the end the drive was faulty. Swapped it out with a new SSD and I am back online. Running a parity check to be safe. Have to rebuild my dockers tomorrow. Lesson learned for not backing up the appdata folder. Will make sure I have backups for the future. Thanks again. Pancho

Here is the updated diagnostics file (captured right after I started the array). I also ran a memtest on the server (2 passes), no errors. mediahub-diagnostics-20190313-1317.zip Ideas? Thanks.

Hello! I have recently encountered an issue with one of my most reliable unraid 6.6.7 servers. Over the past week, this server has periodically "dropped off the network" where I can no longer access the ip (unable to ping) or use the console keyboard. The power is on, but without keyboard response, I have to shut it down forcefully. I have been trying to troubleshoot what exactly is causing the server to sporadically 'freeze' (hardware failure, etc.). Tonight, after an 'unclean' shutdown, I am now no longer able to load the array. The server will hang at 'mounting disks'. I have tried everything, but have had no success. I just see the following screen (shown in safe mode): I am stumped if this is due to an XFS disk error, or something else. Attached is the most recent diagnostics dump. mediahub-diagnostics-20190312-2031.zip Anyone have any suggestions? Thanks. Pancho Server Asrock C236WSI - Xeon E3-1275 - 16GB ECC RAM- Dual onboard nics (LACP team) - 1 - 8TB Parity - 5 - 6TB Array Drives- 1 - Samsung EVO SSD (sata)

Hello! I am running ControlIR 2.9.1 and upgraded (from ver 6.4.0) to Unraid 6.5.0 today on one of my Unraid servers and I am no longer to see the running Dockers or VM's on my android app (S8+ - running Oreo),I just see the message 'No dockers are installed or they are currently unavailable. If I connect to another server (running version 6.4.0), I can see the Dockers/VM's without issue. Any suggestions on how to resolve? Thanks. Pancho

Great deal over at Amazon: http://www.amazon.com/gp/product/B00D1GYNT4?psc=1&redirect=true&ref_=ox_sc_act_title_2&smid=ATVPDKIKX0DER HDD Specs: 5900 RPM 64MB Cache 3 Year Warranty The HDD typically runs about $90. I use them in in my Unraid 6.1.4 server without issue. Pancho

After troubleshooting, I finally discovered the way to make this work was in the order it was completed: PRIOR TO MOUNTING ARRAY AND DOCKERS 1. PuTTY into unraid console 2. Enter in commands to remote share: mkdir /mnt/newmovies mount -t cifs //192.168.0.XX/mediastaging /mnt/newmovies -o username=XXX,password=XXX 3. Validate remote access with the following command: ls -al /mnt/newmovies 4. Mount Array 5. Start Dockers 6. Emby docker will now connect to remote share without issue. 7. When rebooting remember to remove share (or remove after reboot and before loading array & dockers): umount /mnt/newmovies This now works every time. Pancho

I'm sorry I should have mentioned, I do have the path substitution already setup (for the newmovies share), but no success. Any other ideas? Pancho

I am having a strange issue with the Emby Docker container seeing external shares on another computer in the local environment. I recently upgraded from unRaid 5.06 to 6.01 without issue. I began utilizing the EMBY server docker with version 6.01. All of my movies/music, reside on the Unraid server and I can access those with no issue. I maintain a single Windows 8.1 share in my environment where I store 'newmovies', basically raw blu-ray rips of movies. I use this as a basic staging area of movies (before I decide to run the handbrake MKV process and move them to the unraid tower). In order to access my remote share, I utilized the info provided by other forum posts with these commands. mkdir /mnt/newmovies mount -t cifs //192.168.0.XX/mediastaging /mnt/newmovies -o username=XXX,password=XXX I created the corresponding volume mapping within the EMBY docker and this worked perfectly until I rebooted the server. When the server came back online I could no longer see the local windows share. I figured this was caused by not adding the mount info into the GO file. At the console, I manually entered in the mount command with my passwords info and I can browse the share via the ls -al /mnt/newmovies command. However, the Emby docker will not see the share. What is even more strange is within the Emby Docker config, I can browse the remote share without issue (see attached). In the Emby Server config, it doesn't see anything. I am just baffled by this. Here is my docker command: root@localhost:# /usr/bin/docker run -d --name="EmbyServer" --net="host" -e TZ="America/Denver" -p 8096:8096/tcp -v "/mnt/newmovies/":"/newmovies":rw -v "/mnt/disk1/CONFIG/EMBY/":"/config":rw -v "/mnt/user/MEDIA/":"/mnt":rw -v "/mnt/disk3/VIDEOS/":"/mnt2":rw emby/embyserver Any suggestions how to resolve? Thanks. Pancho