TechnoBabble28

After trying several things to get some sort of output from the server I decided to just nuke the flash drive. It was not giving me any output past the post screen nor was I given the normal blue unraid boot options screen to pick how i'd like to boot. Somehow, when I uninstalled the qbittorrent docker last night it must have just completely corrupted the files on my drive. Don't know how or why but I don't have any other explanation at this point. I have spent the last little while thoroughly testing the flash drive and that seems to be just fine so I am confident I can reuse it. My config folder, however, is completely missing from the flash drive and several other files/folders appear to be seriously corrupted. I just reformatted the flash drive and did a fresh install of unraid. It booted right up no problem. Now I just need to figure out how to get a replacement key since I was unable to copy over the key file. I can't register for a trial key because the GUID is already attached to my original key, but there is no option for me to request a replacement anywhere that I can find. Anyone know the proper way to go about this? EDIT: Found my registration email and was successfully able to reapply the key file.

Ive run chkdsk but it did not return any errors or indicate that any corrections needed to be made. I am in the process of pulling the server out of the closet now so i can get a monitor hooked up. Is there anything that can be done from the CL that may help to shed some light on this? Am I able to reformat the USB and reinstall unraid while still preserving the data? It appears the issue is OS related and not data drive related so is there any chance of fixing this issue without losing my data?

Hey all, I am low-key panicking at the moment. I just finished removing a qbittorrent docker container from UnRaid since it was giving me problems (downloads weren't starting). I replaced it with the binhex delugevpn container and was in the middle of testing out my configuration. I had added a movie and a tv show to download and was just waiting for them to be done so I could make sure the post-processing was working. About halfway through though, I got a warning from UnRaid saying that my docker img was at 75% capacity, and then 76%, and then 77%. I stopped both downloads and then stopped the deluge container so i could double check my downloads path. However, when I attempted to go into the deulge container to edit the settings, i was instead redirected to the docker settings page. There was a warning displayed and an orange triangle next to one of the settings but I did not get a chance to comprehend any of it because my entire server subsequently shut off for some, as of yet, unknown reason. After confirming the power shut off wasn't some sort of weird power issue, I powered the server back on. This is when I started to panic. As of right now, I am unable to get to the web UI of the server. I let the server run for about 30 minutes just to make sure it was fully booted but there was no difference. In a bit of a heightened panic, I did a hard reboot of the server. No change. I then logged in to my Unifi controller and verified that the link to the server is up so it is not a connectivity issue. This is where I have just about lost my s***. I am not able to SSH in to the server at all BUT I am able to connect via sftp (Filezilla). The server runs headless but does have a cheapo graphics card in it for emergencies, however, I can't plug a monitor in right now because the server is conveniently located in the closet of my 1yr old sons room and my wife would probably castrate me if I woke him up. Anyway, using Filezilla, I attempted to navigate to my cache drive and, well.....it doesn't exist. As a matter of fact, NONE of my shares exist. What the hell happened?! Who knows?! Someone please tell me everything is going to be alright so I don't have to rock myself to sleep tonight whilst sucking on my wife's thumb... Also, no, I do not have a back up of my flash drive, because I am a dumb dumb. The last log that I could pull off of the flash drive just shows this repeating continuously... "Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/Downloads.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/Movies.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/Pictures.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/TV Shows.cfg Feb 9 21:42:33 MediaServer emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Feb 9 21:42:33 MediaServer emhttpd: Starting services... Feb 9 21:42:33 MediaServer emhttpd: shcmd (40513): /etc/rc.d/rc.samba restart Feb 9 21:42:35 MediaServer root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: Not a directory Feb 9 21:42:35 MediaServer root: cp: cannot stat '/boot/config/machine-id': Not a directory Feb 9 21:42:35 MediaServer root: Starting Samba: /usr/sbin/smbd -D Feb 9 21:42:35 MediaServer root: /usr/sbin/nmbd -D Feb 9 21:42:35 MediaServer root: /usr/sbin/winbindd -D Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/Downloads.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/Movies.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/Pictures.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/TV Shows.cfg Feb 9 21:42:36 MediaServer emhttpd: error: put_config_idx, 619: Not a directory (20): fopen: /boot/config/shares/appdata.cfg Feb 9 21:42:36 MediaServer emhttpd: Starting services..." Anyone have any idea of where I can even start? OR If the config is totally jacked up, am I still able to read from the drives if I plug them into a windows machine? TIA

I kept trying each RC until I found a stable one. RC4 had been the most stable with an uptime of about 2 weeks which usually means I am in the clear. I just upgraded to RC5 a couple days ago and that has been solid as well so far.

I had been running on 6.5.3 for many months without issue and without any sort of zenstates or c-states modifications. I never had any issues with my Ryzen build other than some bad RAM sticks early on. I updated to the F23 gigabyte BIOS a few months back but never looked through it until the other day. After disabling global c-states and adjusting the power supply power to "typical", 6.7 rc1 was stable for several days. It only started crashing again once I updated to rc2. I am using FCP to gather logs so when it inevitably crashes in the next 16 hours or so I can hopefully see what's going on. I also see that gigabyte released a F25 BIOS a little while ago but I am hesitant to change to the new BIOS until I figure out why the system is crashing. From what I can see, the biggest change is some tweaks for athalon based systems and an AGESA update from 1.0.0.4 to 1.0.0.6. It also mentions a requirememt to update the chipset driver which I cannot do. I know one of you mentioned a mellanox card and having some problems. I am also running a mellanox card but haven't encountered any issues. However, I do not have any VMs running and I am not using the mellanox card for internet, only direct file transfers between my desktop and server.

I was stable on 6.7rc1 for a couple days then went to rc2. RC2 has crashed twice now all within 24 hours of uptime. I am now running FCP in troubleshooting mode to capture logs and will upload once it happens again.

Server has been up and running for almost 18 hours as of now. That's the longest it's stayed on thus far. So far so good. Nothing unusual in the logs.

I saw that while I was looking for the global c-states setting and set mine to typical also. Figured it was worth a shot. It's still up so far, fingers crossed.

Will do. Just rebooted into 6.7. I think my longest up-time previously was about 12.5 hours so we will see if we make it that far.

You sir were correct. It was buried in the overclocking settings under "advanced cpu core settings". Have just disabled it and will re-update to 6.7.

I have no such option anywhere in the Bios for global c-states. These are my only c-states settings.

Changed Status to Closed

Nope, that just hard locks the system every 20 minutes lol. I think ill just go back to 6.5.3. That's a bummer since the new dashboard is pretty nice. I'll close this thread.

C6 was set to auto in this new Bios version so i have reset it to disabled. Will see if that fixes the problem.

Bios was updated to lasted at the beginning of December and i haven't had any issues with it. I am running a zenstates script to fix the turbo boost issue and had previously disabled c-states in bios when i first set the system up. However, I have not checked the c-states since this bios update to see if they have been changed, mainly because everything was stable in 5.6.3 even after the bios update. I will check that now.