Astatine

I am getting the same error. Noticed it right after upgrading to v7.3.0 Scrub found no errors for me too Pool status shows pool status:ONLINE - ERRORS The pool only has 1 SSD. It is only used as a place to download stuff to before being moved to the array so I am safe from data perspective but am concerned if it is fixable or do I need to haul ass and get a new SSD.

So the power went out & when I tried bringing the array up after it came back, I was doing so from my mobile which offers what basically is the desktop version of the unRAID UI highly zoomed out. I clicked something by mistake & didn't realize that both of my cache SSDs [1 SSD/pool] got unmounted somehow. The server had been running for almost 24 hours since this occurred. Now only I realized the mistake when docker services was up but no containers were there. I did bring the array down & remounted the cache drives & rebooted the server but no luck getting the containers back. Now I can see all the appdata in the cache drive. Also there is a docker.img present in /mnt/user/system/docker directory but the docker container are lost. The containers are gone as Cleanup Appdata plugin list all the appdata folders even the once that I have docker containers for. I have stopped the array for now to avoid further damage. What could be wrong here? And how should I fix this? Really don't want to spin up everyone container freshly. One difference I saw was that the docker.img in the cache drive is timestamped to be earlier than the one sitting in HDD in the array. They are front the same day but differ by multiple hours. Diagnostics attached! tower-diagnostics-20250605-0034.zip

Understood. I'll go through the release notes to understand the new way to do bridging. Anyways, what should I do with the potentially corrupt config? My server renamed itself to 'Tower'. ident.cfg file lists name as 'Tower'. I don't know what else might have been reset back to default. Do I need to start with 'New Config'?

I previously had issues with docker containers, thread linked. Which was solved by switching to macvlan. If I go back to that, can you suggest how to avoid the DNS issue again? I'll try switching back to ipvlan this evening and see if it makes things better

So, I was moving houses and couldn't pay attention to my UNRAID server for quite some time. I have since replaced a corrupt USB drive. Transferred my key to a new USB. It was working properly for some time but soon after that I started noticing that the server would "freeze" as in the docker services would be running but a couldn't access server using the IP. I also noticed that during boot there are these number list (my guess memory block list) which reads so: I don't understand what this is. Then the situation worsened. Now, docker containers would just randomly stop working and when tried to restart them, I would receive popup either saying "403" or "Execution error". I then either had to restart the docker service or the whole server to be able to get them to work. My guess was that the docker file is corrupted. But I couldn't still act to fix that due to life. Then the whole server started freezing. I couldn't access it over the IP, same for docker containers until I restart the machine which resulted in a ton of unclean shutdowns. And as of yesterday, after restart, the docker containers are only working for 5-10 minutes and my unraid machine name went back to "Tower" which according to this could be config issue: Server name changed from "N2" to "Tower" - General Support - Unraid Also, I am no longer able to access the server over https://[IP] but http://[IP] is showing the login screen but after entering the credentials, it doesn't take me in. Just keeps redirecting to login screen. I convinced that something is seriously off in the /config in the USB. Can someone help me track down the issue and fix it? or is it better to start from scratch? If so, when I do 'New Config' and assign the devices to their current purpose, will my data be retained? both array and cache? I understand that new config will definitely rebuild the parity. I try to somehow get the diag. report from the server directly and post it here soon Here are the diagnostics: tower-diagnostics-20240119-1839.zip Also, when I clicked 'Download' on the diagnostics page, I saw the following error on the server cli screen: Please help. It is getting very frustrating to deal with!!!!

Ah, I see. I just restarted in Safe Mode without Maintenance and can see the disks. Guess I turned on Maintenance Mode earlier. I didn't find something on Google hence posted. Sorry for the inconvenience.

Hi everyone, I am running unRAID 6.12.6 and after a reboot just now, none of the drives are showing up in /mnt I can see the drive in 'Main' tab and cannot even see the "drive explorer" button for the drives. (screenshot of Main tab) But I cannot see any shares or disks mounts in /mnt folder Please help me figure this out as to why I cannot see the none of the disk, cache or otherwise. The SMART report in the report is looking good to me but maybe I am wrong. The diagnostics report is attached to the post: astatine-diagnostics-20231216-2241.zip Thank you in advance!

Just had a weird this happen to me. I pulled up the UNRAID web UI, everything working as usual. I go Apps tab and the page is upside down. The banner/header was still in the right orientation. I switch between tabs, no effect. I restart the browser and go back to Apps tab and I see a popup asking me 'Yes' or 'No' about continuing the International Bat Appreciation Day celebration. The popup dialog had a link to this webpage: https://nationaltoday.com/international-bat-appreciation-day/ Has anyone else seen this?

Well look at that. Changing 'ipvlan' to 'macvlan' to fixed the issue. I kept all the other settings as is. Now, I am more curious as to why ipvlan had that issue and it didn't occur for the first few minutes after reboot.

@JorgeB So, I did what you asked and turns out the test unRAID flash drive has 0 issues. And after going through what @autumnwalker mentioned above, I feel like it's a known issue with how docker handles networking and hasn't been fixed yet. I'll test this theory before anything else.

@autumnwalker Yes, I am using ipvlan + host access to custom networks because I want the prowlarr, jackett containers on Host IP to communicate with some containers that are on a different IP setup using br0 interface. I'll turn off the "host access to custom networks" and see if the issue gets fixed like it did for the folks you mentioned

Thanks. I'll get back to you once I've tried it.

Well, with all due respect, I find it hard to believe that it is not an unRAID issue. I booted the server to a live ubuntu USB and left it to ping google.com, cloudflare.com & unraid.net for more than a day and the packet loss are as follows: 0% for google.com, 0.00383547% packet loss for unraid.net & 0.00153467% packet loss for cloudflare.com. So, I believe this rules out the possibility of a hardware issue. - Not a router issues as all my other devices are working just fine connecting to the outside world - Not a switch issue as all the other devices connected to the switch are working fine + unRAID server also get connection for 10-15 minutes after reboot and then loses DNS - Not a hardware issue as booting into live ubuntu USB doesn't seem to have the same DNS resolution issue as the unRAID server With this new information on hand, I can confidently say that it is an unRAID issue, whether it originates from the OS or a corrupted config file, that's a different story. ping_cloudflare.txt ping_google.txt ping_unraid.txt

I am open to setting up everything from the scratch. How can I have a fresh start without using the limited USB Key resets? I believe all the parity data, appdata, etc. will just remain the same in the new install so long as I assign the correct drive back to the same purpose. As for docker container install, I am willing to do it again and point the new containers to old appdata to bring server back to my latest state. Is there a way to accomplish the above?

Yeah, totally agreed. Time sync issue seems to have occurred due to loss of connection and not the other way around. However, I there something else that comes to mind in how to diagnose the real issue? I'm going to try booting into a live ubuntu install later in the evening and observe if something similar happens in that too. In the meantime, I was also wondering if there is way to do a fresh install of unRAID while keeping my config and settings intact. That way, if there is a corrupt file somewhere, it would be fixed. Thoughts?