updatenil

Thank you, @JorgeB. You're a beacon in my damn fog filled ocean of work. As a guide to my fellow Unraid Travellers, I tried installing Plex after a year thinking that this would be good for user experience. After just a few days, a Plex update rolled out. I installed it only to discover that the Plex database corrupted. Plex docker ended up consuming more space until it bottlenecked the other dockers, and corrupted the docker image. I decided to have the Docker service on a directory in an SSD moving forward. On a bright note, I was able to explore other dockers that I've been meaning to try, like gluetun - very cool. As for Plex, there are no words that can fully express my unrelenting fury. You kicked me while I was down with a lot of other work. If I could return the favour, I will.

I signed into Unraid and noticed that Docker consumed 100% of its RAM allocation. In this case, 50 GB. A number of dockers stopped working properly, and I rebooted the Unraid server. Upon reboot the Docker Service isn't starting up. What is the procedure to bring the Dockers up and running? atlus-diagnostics-20241019-1259.zip

@JorgeB Thanks for always being there even for fools like me. Rather than wait, I tried searching for a solution on my own and found this link: https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/ I followed the check procedure described on the two drives (sdr and sds) and there were a number of errors found. I followed the procedure and then started the array once more. Unfortunately, the drives mounted as pretty much fresh drives with no used data. I tried looking at the Lost and Found, but there were many folders and I wasn't sure I wanted to dig through all of them. I chose to commit to starting from the beginning on these drives and they're presently being rebuilt. I'm still choked that I suffered the most from what's probably an $8.00 cable. But, life is still moving, and I still have to keep it moving. Thanks again.

Well for lack of a better idea on my time off, I shut down the computer and looked over the cables. Sure enough I found a lightly cracked molex connector and readjusted the pins. I'll have to buy another one for the future. In the meantime I booted the computer back up and it seems the new drive I was trying to install, along with the 2 drives connected to the defective molex cable are seen and I started the array. Now Unraid says that I have 3 unmountable disks present, and it looks like it started some kind of data rebuild which seems to be going rather quickly. Afterwards, everything is backed up elsewhere. Is there any easy way to recover the 3 disks in question or should I just format them and start from scratch? atlus-diagnostics-20240714-1353.zip

Alright. So it's me again. For a while there I thought I was back in business and even added an extra parity drive for extra peace of mind. I traced the problem from the 2 drives to the cables in question: A "Y" type cable that is connected back to power with some daisy chained molex cables. I checked the connections and powered it back up, but it seemed fine. I didn't take the risk though so I changed them out. Since then I included an extra parity drive for some extra peace of mind which took quite some time. Enter the Problem: I decided I wanted to switch out a 12 TB drive with a new 20 TB drive so I opened up the PC. I installed the new drive and started the rebuild process last night. But, I suspect the molex cables in question are pressed by the PC panel when I close up the unit once more. I checked to see the rebuilt progress and everything appeared fine until this morning. Now the rebuild has stopped for the larger drive, plus the two drives in question appear with issues. What is the procedure to recover from this situation? If I do recover from this situation then I'll have to re-evaluate how I'm running those molex cables. Or I avoid completely closing that panel and slowly figure out if I want to move on to a new case one day. atlus-diagnostics-20240714-0854.zip

At a break here, I shut down the server and just pressed each power plug into the drives. After booting it up everything appears to be connected again. Big sigh. Now I'll have to set aside time to properly label all my drives and cables.

@JorgeB If you have a moment to take a look at this issue again, I would appreciate it very much. I believe the same drive is noted as failed, and the parity has kicked in. I'll include the diagnostics and I think this time I'll make plans to get a new drive. Since you mentioned back in Dec that there were two drives that were questionable, I'm just wondering if I should brace myself to get two drives instead of just one. Thank you! atlus-diagnostics-20240605-1028.zip

I would consider myself a hobbyist so please forgive some general ignorance since I have no idea what the issue is yet. When using Emby this past weekend, the server crashed and became unresponsive just as I wanted to play an AV1 file which would require some transcoding. I expect such a file to play normally. But, on this occasion the server stopped responding. When I go to sign into the Unraid GUI, the GUI appears to have stopped working as well. Other dockers that do not depend on the graphics card appear to be operating for some time. But, after about 30 minutes or so the rest of the dockers go down as well. I go to the server itself, where the computer is booted up with the GUI. I see that the GUI is down and the Unraid server is unresponsive to keyboard commands entirely. I forced the computer off by holding the power button, and started the system back up. I downloaded the diagnostic file afterwards which is here. Unfortunately a few days later, and while the Unraid server was running a parity check for errors, the same problem occurs once again. I was trying to play another AV1 file on Emby, and then the Emby server crashed once more along with the Unraid GUI. After that, the rest of the dockers crash some time later. Thank you all kindly for your time. atlus-diagnostics-20240428-2254.zip

After trying to sign into the server, I realize that I am no longer able to. I was timed out for 5 minutes. Is there a safe way to reboot the server under these circumstances?

Evening Recently I've been unable to load the Unraid Login page, and my TDARR page is not loading either so I suspect the docker has caused some kind of crash. I do see all other dockers functioning normally. I booted Unraid into the terminal last week and it's in the middle of a Parity check I'd rather not interrupt. Am I able to start up the Unraid GUI so I can get back in and maybe restart my TDARR docker? When I look at the server's screen there's a message: Thanks

I'm not sure why the same notice appeared in my Fix Common Problems Plugin. For what it's worth I'll include the diagnostics. From what I can tell everything seems to be working. atlus-diagnostics-20231222-0000.zip

Recap I upgraded a part in my server and potentially loosened a plug to a drive. After checking the plugs to each of the drives and the controllers, I followed the below steps from the link above to re-enable the effected drive. Depending on your set up, this process could take a few days. Thank you to @JorgeB as always for your help. Steps: Rebuilding a drive onto itself There can be cases where it is determined that the reason a disk was disabled is due to an external factor and the disk drive appears to be fine. In such a case you need to take a slightly modified process to cause Unraid to rebuild a 'disabled' drive back onto the same drive. Stop array Unassign disabled disk Start array so the missing disk is registered Important: If the drive to be rebuilt is a data drive then check that the emulated drive is showing the content you expect to be there as the rebuild process simply makes the physical drive match the emulated one. If this is not the case then you may want to ask in forums for advice on the best way to proceed. Stop array Reassign disabled disk (optional) Tick the box to start in Maintenance mode. If you start the array in Maintenance mode you will need to press the Sync button to trigger the rebuild. The advantage of doing this in Maintenance mode is that nothing else can write to the array while the rebuild is running which maximises speed. The disadvantage is that you cannot use the array in the meantime and until you return to normal mode cannot see what the contents of the disk being rebuilt will look like. Click Start to initiate the rebuild process and the system will reconstruct the contents of the emulated disk.

After I check the connections and start everything up again, how do I re-enable the drive in question? Are these instructions still good: https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

Thank you. I will double check the connections later to make sure I didn't pull something out.

atlus-diagnostics-20231218-0925.zip

I'd just wanted to add that another disk also has a similar message.

Hello Woke up to one of my drives reporting that it's disabled and the contents are emulated. I'm relatively new to servers and having such an event. A few days ago I was working inside the computer to install a GPU and I'm not sure if I could have knocked a plug loose? Or should I be preparing to shop for a new drive? Thanks for any insights in advance.

Hello According to the Fix Common Problems plugin, there appears to be a Machine Check Events Error. I don't have any other issues, and Unraid appears to be functioning normally at this time. I'm posting my diagnostic since I've never encountered this before and I'm just being cautious. Following Squid's post about this situation, I've included my diagnostics here: atlus-diagnostics-20230926-1657.zip

@JorgeB and @trurl I thank you both for your kind attention to my issue. I am very much a layperson with a keen interest in setting up my humble homelab that's grown to this point. I would never have reached this point without these communities. Thank you again. In summary, due to a long standing corruption in the cache from some power outages last year, the docker service finally stopped working. Solution: [1] stop docker and vm, [2] backup all important files from the impacted cache, [3] stop the array, [4] format the target cache, [5] return the files to the cache, and [5] restart docker. My issues resolved at this point and I had no other steps to take.

I'll back up what's on the cache. For my reference, I notice that there's a file share named system that is set to prefer cache. Is there a safe procedure for me to back up the contents, and then reformat the cache without causing any needless disruption?

I rebooted my router. I also shut off enable bonding under the Network Settings. (no idea if that helped with the earlier messages about bond0) At some point I am now able to log into the server from within the network, which as far as I'm concerned is progress. atlus-diagnostics-20230614-2037.zip

I tried to turn the docker service back on and I am unable to. I also rebooted the server and the docker service doesn't come back.

I haven't really interacted with network settings. Are there some settings I should look over? Is there a how-to to reset the network settings?

atlus-diagnostics-20230614-0831.zip Thanks. I normally interact with the GUI by accessing it on another computer on the network. When I booted up the server into the GUI it works normally. I was able to get a new diagnostics file. I realize I'm just not able to easily access the Unraid server on the network. I also notice that the server isn't able to reach GitHub. Thanks for your kind attention to this.

I took a photo of the output.