dcruff

It does appear that the problem is solved. I had to reboot the Netgear router and the Unraid server and now it has stayed up for a few hours, much longer than before.

This is a very quiet support channel. Maybe all of those who might know something about Unraid dockers are on vacation. Can anyone think of another docker that might be good to install that would allow me to look for similar behavior on the WAN?

OK, No responses. Now, I've been down for days. Should I just reinstall Emby and restore my settings? Or, could I go back a version in hopes of refreshing some setting? Does anyone have any ideas if this might be tied to the Unraid operating system rather than the EmbyServer docker? It would seem to be Emby because it gets temporarily fixed each time I restart the docker.

Emby has been working great for months, now it only works great on internal LAN. Each time I restart the Emby Docker, the external access only works for about an hour or so before shutting down and leaving the external users off-line. There are no noticeable errors with Emby or Unraid. The way that I know it is down externally is when I shut off my WiFi on my cell phone and access the Emby app. If it can't connect, I know that I have to restart the Emby docker again. I'd like to be able to access Unraid from my cell phone and just installed an Unraid Monitor App, but I don't know how to use it. The rest of my network throughout the home never fails and my son is a heavy duty gamer in the evenings. He hasn't experienced any hiccups.

I'd be interested in similar support. I'd much rather pay for someone to help me that spend days trying to figure out something that might only take minutes for someone with knowledge.

Well, since rebooting, the Log file is at 1%. Hopefully it was a one-off. And, I just updated the Emby Docker.

Just came back from a few day trip and had an error with my syslog. The dashboard shows Log Memory utilization at 100%. Getting ready to reboot, but the system suggested that I report for help on the forum along with my diagnostics. Here it is... embyserver-diagnostics-20221003-1354.zip

embyserver-diagnostics-20220914-1505.zipThe frustrations come from sometimes waiting days for a response. I have many family members who log into my server nightly and I wasn't able to get the server up as quickly as I wanted to. The responses on these threads are helpful but often not timely. I don't feel that anyone here owes me anything, which is why I was looking for someone who could give more immediate service for a fee. Part of my problem was just basic understanding of how the cache drive was being used. Once I gained a little more understanding, I chose not to try to recover any data on it and replaced the SSD with a new one. Then, I realized that it didn't mount automatically - again, neophyte issues. Once I mounted it, it became purely an Emby issue because Emby no longer saw it's configuration files and thought that it was a new install. I quickly found the backup files on disk 2 of the array and was able to restore the most recent configuration files. I thought that I was home-free and informed my users of such, but the Emby docker quickly utilized 100% of the processing resources. Several more attempts were made at clearing the SSD (reformatting it) and then doing the restore again with similar results - Emby server locking up within an hour. Final solution - partial restore of configuration (Media library locations and User account names- 24 listed users). Emby Server is now at 100% functionality with over 4500 films, almost 80 Series, hundreds of music CD's and much more. I've looked for dockers in the past that would help with file management and backups and tried some out that are no longer updated. They were inconsistent and locked up often. I haven't looked at that for a while because I've settled into a routine of using the LAN and mapped drives from this Windows computer. Maybe I should also look for some kind of a tutorial on scripting. I know that there is a lot of power in scripting, but I'm not there yet.

I did finally get my Emby/Unraid system up and running well. But it took me several days to get it back up when it might have only taken an hour if I had the experience/understanding/ or help that I needed. I know that everyone's situation is different, but mine is unique in simple ways. I only use my Unraid server as an Emby Media Server. I have disabled any use of my SSD cache for everything except 'appdata'. I have my media backed up externally and have Emby scheduled to back up it's configuration daily to one of the array drives - maybe I should send that limited configuration data backed up to the FLASH boot drive (or another FLASH usb drive) instead. I know that there are things that could be configured better, but it seems that having an experienced linux person actively helping would have brought me to where I am, and further, very much quicker. Emby Server management is not for the faint of heart. Unraid Server management is not for the faint of heart. I've done fairly well, but with far too many pitfalls. I considered several times returning to a Windows server but now I'm glad that I didn't. I love the benefits and performance of running my Emby server on Unraid, but I wish that I could do rudimentary tasks on it that were second-nature to me on Window (and DOS). Example, I still haven't been able to find a good way to back up my Unraid server to external USB drives - or to even access those external drives with routine file management (through a GUI or console commands) when directly connected to the Unraid Server. I currently back up the media on the array manually over my LAN and do all of my administration through mapped drives on Windows. It's not the most efficient, but it works. Some of these things that I mentioned don't need to be addressed quick/fast/today, but when my system is down because of a failure of an SSD cache drive, some experienced handholding would have been nice. I was able to have Amazon get a replacement SSD to me the same day, and yet my system was down for a week while my learning curve was waiting on cryptic forum responses. It's been frustrating and it seems that there are probably a lot of linux aficionados who might have been able to help but I have no effective way of accessing them. It cost me a lot of down time and frustration that might have been avoided. Maybe there is a professional support system that I'm just unaware of.

Are there any experienced Emby Docker people for hire? I believe that my issues are relatively simple for Unraid/Emby aficionados, and I don't have any trouble compensating someone who could help me bringing up my skills.

Are there some EMBY - Unraid specialists for hire that can help me with some Emby issues?

Well, now I am stuck. I tried clearing the cache SSD and re-formatting it so that Emby wouldn't see it's configuration settings in the appdata on the SSD. It seems to be finding it elsewhere and Emby locks up as soon as it starts to load. I'm wondering if I should just uninstall the Emby Docker and then re-install. Again, all of my 15 TB of Media are intact on the Array. And the Array holds my Emby settings an configuration in a backup directory.

Should I stay with the default XFS for the SSD cache?

I went ahead and replaced the SSD with a new one, and them formatted it with the default XFS file system. Then I went into EMBY and installed the "Configuration Backup" Pluggin and restored my most recent settings backup (9/5/22). Everthing seemed to be going fine as Emby was trying to load all of the images for all of the media, but now Emby won't get past a few blank icons in the My Media section and nothing is working. Unraid is not giving any errors but the 'Dashboard show 100% Utilization of 'CPU 8 - HT 9. and I see almost no activity on the other CPU's. Thinking that I may format the SSD again and try the restore again, but this time be particular as to what parts of the backup to restore, since it give me the option. Any ideas?

Thanks. I was thinking that everything on the SSD was to be considered temporary, and therefore was also somewhere else. Actually, I think that I have a configuration backup utility enabled on Emby, but I don't know where it is yet. I would probably have to completely start it up again and then locate the backup. But, it appears that I may be able to restore some of that, if not all, if I try to mount the SSD in read-only mode. I just verified that I have daily configuration backups on my array that include Users, userdata, library, pluggins, dlna, playlists, scheduledTasks. That appears to be my saving grace. Am I wrong to just move forward with a new SSD and then restore emby settings?

Question - Since I have chosen to not use the cache SSD for any of my data other than 'appdata', can I assume that the SSD only holds temporary data that is also elsewhere? Because this is only a media server, and I infrequently add new media, it seemed cleaner to just write straight to the array when I add new media. Also, the array has been performing wonderfully without using the cache. It's the lack of access to the appdata that Emby is complaining about because of the SSD being offline. Would it just respawn the data on a newly formatted SSD?

Thanks again. You were right on with memory speed. Now Memtest runs without any errors. Now to the SSD, I got another message that "If the disk is listed as being unmountable, and it has data on it, whatever you do do not hit the format button. Seek assistance HERE" What can I do now? When I press 'Here', it just leads me to the community forum for which I see no solutions. Are there any other resources available to help me solve this? I was going to put in my new SSD, but now I'm afraid to and want to know if there's a way to recover the data on the previous SSD, or is it mirrored elsewhere?

Thank you. I disabled XMP and am trying Memtest again.

It does appear that the system runs pretty well, even with these memory errors. I want to fix the problem and probably need some more memory sticks. Maybe I should just get one new memory stick and try it in each slot to see which one fixes the problems. Even with that, If I just put my new SSD drive in (I just received it) and formatted it, wouldn't that solve my current problem with the Appdata that is not able to go to the cache drive right now? I'm assuming that the data is in-tact on one of the other drives and just needs a functional cache drive to make my Emby docker function properly. Then the Emby program would come back up as normal. Am I correct in this thinking?

Here is my report. It looks bad. Is there a good way to know which memory stick might have problems? MemTest86-Report-20220905-195311.html

Will this also be trying to test my non-mounted SSD Drive?

Thank you for reminding me. I think that I had a different flash drive just for that purpose. I'm trying it now. I had thought that it was on my standard Unraid boot flash drive. Yep, I've got Memtest86 running now. Now I've just got to figure out what I'm looking for and what I'm seeing.

If it really is the SSD, can I just replace the SSD drive with a new one? Then just mount it?

I do have a new version of memtest on my flash drive that I placed there in June of this year, but now I'm not sure how to execute it. If I rename it to Memtest86+, will it operate from the boot menu? If so, what command line command allows me to rename the executable file?

When booting, I select 'Memtest 86+' but it just reboots again without running any memory test. I dealt with this before by using a different version of Memtest, but I'm trying to remember how I did it. Do I need to run memtest from the main console - not on the GUI terminal? I have always gotten some errors when running the weekly parity check, but it hasn't hurt performance, and those errors appeared to be on the main data drives and it always finishes saying 'Parity is Valid'. It takes almost 19 hours to do the parity check and generally reports about 1200 errors - It's always been that way. Now, it appears that the problem is with the SSD failing on me and not mounting.