ZFS Online but unable to import

entilza said:
You were on to something when you tried the read only.. just that message wasnt good.. was thos zfs damaged when removed somehow...
Click to expand...
I didn't properly export it when I was moving it machines, was the only thing that I can think of. Or that when i imported it into OMV it formatted it differently than when I first created it on the proxmox host. So when I fkd up the OMV vm it also somehow messed up the zfs pool. Doesn't make much sense to me, but that's all that really happened from what I can remember.

If I can get it to read-only that's all I really need, i have an external drive on my PC i can transfer it all to then wipe and remake the pool.
 
Potatoes1921 said:
If I can get it to read-only that's all I really need, i have an external drive on my PC i can transfer it all to then wipe and remake the pool.
Click to expand...
Maybe you can binary copy (GParted Live or dd) the first partition of one of the there drives to that external drive. Then copy it back to the internal drive but without partitioning, so that it matches the pool configuration (which appears to be whole drive instead of a partition). If you can do that also for a second internal drive then the pool should be accessible but degraded until you fix the third drive.
I cannot guarantee that it will work and/or not destroy your data if something goes wrong but maybe you can fix the drives to match the pool setup in this (or similar) way.
 
Bit of a revive, decided to give it another look and saw this article https://www.truenas.com/community/threads/cannot-import-existing-pool-insufficient-replicas.111436/
Seems pretty similar to what I'm going through.
Looking into it more, I ran systemctl | grep zfs-import and found that the cache service isn't loaded properly, couldnt find a fix that properly worked, but I found this article https://forum.proxmox.com/threads/failed-to-start-import-zfs-pool.109347/ but didn't end up working

I also tried deleting the partitions on those drives using fdisk, which didn't seem to cause any issues even after reboot, but didn't fix the issue
1708738121416.png
 
Last edited:
You must log in or register to reply here.
Top Bottom