Hello, I have had a pool of two hard drives in a mirror pool for some time but the OS got corrupted and I reinstalled the OS. Now I am on Linux Mint and my pool does not appear any more. When I use zpool import it says no pool available to import, I have looked around online and found you can import a zpool by specifying the drives, so I used zpool import -f -d /dev/sda1 -f -d /dev/sdb1 internal I get back my pool
pool: internal
state: ONLINE
scan: scrub repaired 0B in 00:08:39 with 0 errors on Tue Jun 18 18:38:40 2024
config:
For anyone with ZFS related issues I’d honestly recommend just going to Jim’s site- https://discourse.practicalzfs.com/ which is invaluable. Lot more help and a trove of valuable info already exist there.
Thank you will have to look into that particular forum. Though my problem has been solved for now I will definitely have more things that come up in the future and that seems like just the place for this sort of thing.
The trick for this one is mount -t zfs -o zfsutil internal /mnt/some/path
Assuming the root dataset is mountable. If you have a -o canmount=off on the dataset it will refuse to mount.
If it’s -o mountpoint=legacy then you don’t need -o zfsutil, but still need to provide both the source and destination paths. Otherwise you’ll get the fstab error because mount can’t figure out what to mount or where to mount it.
Thank you so much, where did you find this bit of information? I have been trying to solve this problem for the past week or so, but my google foo failed me on this one. Was about to give up on this one.
I learned it accidentally trying to get root on an encrypted dataset working with systemd init without sd-zfs. This turns out to be how the zfs utility works internally to signal the driver “hey it’s okay, I’m a ZFS utility the user isn’t using mount directly”, and how you deal with mounting your root dataset to the temporary /sysroot while having its mountpoint set to / while in initramfs before pivoting root.
Obviously, don’t use that other than recovering your data, if you want to use this array you should figure out the mountpoints properly so ZFS does it automatically. It shouldn’t break anything but it’s gross, either set mointpoint=legacy and use fstab or set its mountpoint in ZFS and use zfs mount.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
It states it can’t find it in /etc/fstab. So do you have it there? And does it have the correct ID?
(I don’t know how zfs pools work, I’m just going of what the mount command said)
Maybe @jimsalter@fosstodon.org can help. I’m not in my pool right now.
For anyone with ZFS related issues I’d honestly recommend just going to Jim’s site- https://discourse.practicalzfs.com/ which is invaluable. Lot more help and a trove of valuable info already exist there.
Thank you will have to look into that particular forum. Though my problem has been solved for now I will definitely have more things that come up in the future and that seems like just the place for this sort of thing.
I guess you need to “zpool import -f” because your system has crashed before and did not shutdown properly.After reading again, I understand that your pool is alive and well. It is just not mounted anywhere.
Look into /etc/fstab if you find the correct mountpoint there. Then tell it to your ZFS with "zfs set mountpoint= "
The trick for this one is
mount -t zfs -o zfsutil internal /mnt/some/pathAssuming the root dataset is mountable. If you have a
-o canmount=offon the dataset it will refuse to mount.If it’s
-o mountpoint=legacythen you don’t need-o zfsutil, but still need to provide both the source and destination paths. Otherwise you’ll get the fstab error because mount can’t figure out what to mount or where to mount it.Thank you so much, where did you find this bit of information? I have been trying to solve this problem for the past week or so, but my google foo failed me on this one. Was about to give up on this one.
I learned it accidentally trying to get root on an encrypted dataset working with systemd init without sd-zfs. This turns out to be how the
zfsutility works internally to signal the driver “hey it’s okay, I’m a ZFS utility the user isn’t using mount directly”, and how you deal with mounting your root dataset to the temporary/sysrootwhile having its mountpoint set to/while in initramfs before pivoting root.Obviously, don’t use that other than recovering your data, if you want to use this array you should figure out the mountpoints properly so ZFS does it automatically. It shouldn’t break anything but it’s gross, either set
mointpoint=legacyand use fstab or set its mountpoint in ZFS and usezfs mount.