ml02026

Makes sense... Alright, thanks again! Much appreciated.

Oh okay, but was it supported when Unraid 7 came out, or perhaps in some of the betas? I remember seeing a new device type for ifs pools in the UI, where you could add a hot pare? I will remove it for now until it becomes available. Thanks for your help!

Here you go: However it is imported already so the output does make sense. If I stop and start the array, everything works as expected. I have to restart the whole server in order to run into the issue again. Here's the output after restarting the server, starting the array while obtaining the "Unmountable: wrong or no file system" on the tank pool: I remember doing one of these Zpool upgrade commands back when I had just switched to Unraid 7.0, surprised to see this again. Would it be the explanation behind all of this? Thanks

Hi, New here and unsure of the proper structure for requests like this one. Some time after I started playing with the 7.0 betas, back when there were no Stables or RCs, it started giving that error when rebooting my server and trying to start the array normally. My "tank" zpool doesn't mount while the others do. I thought upgrading to 7.0 stable and then several other releases since then, would fix the issue, but it still does it even in 7.1.0-beta2. If I open up a shell and use "zpool import tank", it works and all my data is accessible. However, in the array overview (main page) the pool shows as unmounted, I just see the drives. Only thing that can come to mind is that I did add a hot spare to the pool, through the Unraid UI at one point when it became available... And then it did issues where I could not even start the array, so I had to delete that hot spare and add it through ZFS and not using the Unraid UI. Maybe it messed something up with how Unraid reads the drives to mount them at first. Here's a quick screenshot of that pool: Thanks in advance! rawpower-diagnostics-20250331-2124.zip

I will try this out and come back with some news afterwards. Thanks a lot!

Thanks a lot for the quick reply! Any ideas or guesses on why it would've done that in the end? I know the nvme1n1p1 was not detected some times when booting up unraid (I had to reboot the server and it would eventually show up), but I thought it could have been a glitch in the RC release, as the drive itself seems to be working just fine, unless you see something else from the logs? So then, after reading your reply, I guess my best bet is to move the data from that pool somewhere else, delete the entire pool, format the drives and rebuild it. What I am worried about is that this happens again after a while. Thanks again

Hi, For the last month or so I have been having a lot of trouble with my unraid installation. It initially started a while after upgrading to the 6.10 rc2 but stayed around while trying to rollback to 6.9.2. Things like a not responsive Web UI, crashing nginx service, devices disappearing from additional cache pools I have setup or not being detected from time to time when rebooting the server. As of now, I would say that my biggest issue is that one of my pools is seen as "Unmountable : No file system" after booting up. This occurs about a third of the time and prevents me from running my docker containers (since my appdata share is hosted on them). I use two adata nvme m.2 ssd in raid 1. What I have tried: Removing one device at a time from the pool, formatting that device, adding it back to the pool and do the same with the second one. Changing the "balance mode" from raid 1 to raid 0 I ran several tests on the two ssds outside of unraid and they don't seem to be at their end of life or anything. This also happened with one of my nvme drives from the array cache pool. Ultimately, I have taken out my unraid flash drive from the server, wiped it out and restored one of the backups I had onto it to start fresh. It did a big difference in loading times and just the overall experience on the web ui. Some times it took as much as 2 minutes before being able to load the main page or any other pages and this is not a networking issue. The diagnostics file I am joining was taken after wiping my flash drive, but I also took one before, when I had other issues. Thanks in advance! rawpower-diagnostics-20220217-2352.zip