February 20Feb 20 I recently had a power outage. My Unraid server is connected to a UPS and properly shut down during the outage.When I started it up again, I got this error when trying to start:Wrong pool statedata - invalid configdata is a ZFS mirror with 2 x 20TB Seagate Exos X20 drives.It turns out that for some reason, one of the drives was no longer in the pool! I had to re-add the missing drive to the pool, remove Unraid's config for the pool, then re-add it in the UI. Now it's working fine and the drive that was missing is resilvering. I left it overnight and now it's around 50% done.Unraid should have a better error message than just "invalid config". Why is the config invalid? In my case, I think it's because the state of the pool in Unraid's config (two drives) didn't match reality (just one drive).What could have caused this? I searched the forum and saw there's several monitoring scripts for ZFS (which is something Unraid should really have built-in!) but they only look for degraded or faulted pools, which wouldn't have caught this. The pool was in an online state, just with one drive completely missing.
February 20Feb 20 Community Expert Possibly an issue with the flash drive, the pool cfg was incorrectly saved or updated.If it happens again, one of the devices being unassigned, you can just reimport the pool to avoid the resolver.on main click on the first device for that pool and then "remove pool"back on main, create a new pool with the same name and number of slotsassign the pool device(s), leave the filesystem set to autostart the array to import the pool
February 20Feb 20 Author 2 hours ago, JorgeB said:If it happens again, one of the devices being unassigned, you can just reimport the pool to avoid the resolver.The drive was missing from the ZFS pool itself. zpool status only showed one drive. It immediately started resilvering after I added the drive back using zpool add.2 hours ago, JorgeB said:Possibly an issue with the flash drive, the pool cfg was incorrectly saved or updated.I verified against a backup, and the config hadn't changed.
February 21Feb 21 Community Expert 10 hours ago, Daniel15 said:The drive was missing from the ZFS pool itself.That would mean the pool was already degraded before the reboot.You can use this for better pool monitoring for now:https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.