September 2, 20232 yr After a reboot my array won't start. I have a zpool set up with a topology that isn't supported by the UI, but it hasn't been a problem until now. The array just shows that it is in the "Starting" state, but it never finishes. nas-syslog-20230902-1521.zip
September 2, 20232 yr Community Expert Pool appears to be imported correctly, but then there's this error: Sep 2 10:17:13 NAS emhttpd: rdevStatus.37 not found Never seen this before, no idea what it means, try booting in safe mode and/or with the pool disks unassigned.
September 2, 20232 yr Author I've booted into safe mode and the array didn't try to start by default but it ran into the same error when I tried to start the array manually. The ZFS pool seems totally fine all the data is present and accessible. I'm at a loss for where to start troubleshooting.
September 2, 20232 yr Community Expert Solution To rule out any config issues backup and redo the flash drive and restore only the bare minimum, like the key, array and pool assignments, see if it starts like that, if still not it's not a config problem, and post new diags/syslog.
September 4, 20232 yr Author After starting from a fresh install the zfs pool has to be manually imported after each boot. Should I be adding it somehow in the GUI so it auto-imports? Also for some reason my docker containers no longer show the edit option in the GUI.
September 4, 20232 yr Community Expert Zfs pool just needs to be assigned, it should then import on array start.
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.