-
Pool device locked and reporting wrong encryption key after system lockup
I'm having trouble reformatting the drives. I've created a completely new pool and selected ZFS - encrypted as the filesystem but when I start the array and select the option to format the unmountable drives, it errors out saying that the encryption key is wrong.
-
Pool device locked and reporting wrong encryption key after system lockup
Something else I noticed in the the uploaded diagnostic logs were segmentation faults: Nov 13 14:26:11 Gondolin kernel: rc.diskinfo[13950]: segfault at 152a38204824 ip 00000000008db485 sp 00007ffd9c015e00 error 4 in php[600000+3b3000] likely on CPU 0 (core 0, socket 0) Nov 13 14:26:11 Gondolin kernel: Code: 0f 1f 44 00 00 8b 47 04 83 f8 1a 75 0d f6 47 11 02 74 0e 48 8b 7f 08 8b 47 04 a9 10 fc ff ff 74 78 48 8b 7b 18 48 85 ff 74 10 <f6> 47 04 40 75 0a 83 2f 01 75 05 e8 2b 75 fc ff 48 83 c3 20 49 39 Nov 13 14:26:43 Gondolin kernel: rc.diskinfo[16116]: segfault at 146741a04824 ip 00000000008db485 sp 00007ffefde51af0 error 4 in php[600000+3b3000] likely on CPU 0 (core 0, socket 0) Nov 13 14:26:43 Gondolin kernel: Code: 0f 1f 44 00 00 8b 47 04 83 f8 1a 75 0d f6 47 11 02 74 0e 48 8b 7f 08 8b 47 04 a9 10 fc ff ff 74 78 48 8b 7b 18 48 85 ff 74 10 <f6> 47 04 40 75 0a 83 2f 01 75 05 e8 2b 75 fc ff 48 83 c3 20 49 39 Nov 13 14:27:05 Gondolin kernel: php-fpm[12750]: segfault at 14ac698be740 ip 00000000008b19db sp 00007ffdf30559a0 error 6 in php-fpm[600000+3c0000] likely on CPU 3 (core 3, socket 0) I'm guessing that's indicative of some kind of hardware failure?
-
Pool device locked and reporting wrong encryption key after system lockup
No luck on the other pool device either. Guess I'll be reformatting! Just for future reference, would it be prudent to use this script to backup the LUKS headers? It seems like that would have potentially allowed me to recover from this error?
-
Pool device locked and reporting wrong encryption key after system lockup
Yes. But entering the passphrase results in a "No key available with this passphrase" message.
-
Pool device locked and reporting wrong encryption key after system lockup
Yeah, that's what I figured. I'm also worried that the abruptness indicates some kind of hardware failure that reformatting won't address.
-
Pool device locked and reporting wrong encryption key after system lockup
I did not. The only commands I tried when the system initially locked up were "poweroff" and "shutdown", neither of which worked. After rebooting and encountering the error, I tried "zpool status" and "zfs list". Unfortunately none of the zfs commands do anything. When the array is mounted, the pool devices both have an "Unmountable: Unsupported or no file system" error message.
-
Pool device locked and reporting wrong encryption key after system lockup
Unfortunately the output of zpool status is "no pools available".
-
Pool device locked and reporting wrong encryption key after system lockup
Hello! My system randomly locked up earlier today during a large file transfer. The WebUI was completely non-responsive and while I was able to SSH into the server, restart/shutdown commands failed to execute. I hard shutdown the system using the power button. After rebooting, I started the array in maintenance mode only to encounter my single pool device (2x 500GB SSD in ZFS Mirror) locked and reporting the wrong encryption key. The array itself was successfully unlocked. Subsequent WebUI reboots have not resolved the issue. Diagnostics are attached. diagnostics.zip
-
[Plugin] Tailscale
Whoops forgot to do that. Here you go.
-
[Plugin] Tailscale
I seem to be having a problem where the "Accept DNS - Yes" plugin setting is not actually being applied according to the Info tab. Am I correct in interpreting that setting as automatically applying `tailscale set --accept-dns=true`?