-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"status: Mismatch between pool hostid and system hostid on imported pool." #16878
Comments
"That" has appeared to help with one problem. Exporting and Importing the pool has created another problem however... zpool status
errors: No known data errors My drives refuse to import by Disk ID as they were before. Edit: I exported again and tried sudo zpool import -d /dev/disk/by-id -aN and got this, which I will accept. zpool status
errors: No known data errors |
Just make sure to rebuild your initrd. |
Ok, thank you for the reminder. I did and I got this. dracut-install: Failed to find module 'zfs' |
Old kernel? No modules present built by dkms? |
dkms status gives this, it looks like it is there and installed: dkms status |
I'm not a fedora user and don't know dracut well enough. |
System information
Describe the problem you're observing
I created a new Zpool on 4 SSDs after seeing this message returned after "zpool status"
zpool status
pool: Tank
state: ONLINE
status: Mismatch between pool hostid and system hostid on imported pool.
This pool was previously imported into a system with a different hostid,
and then was verbatim imported into this system.
action: Export this pool on all systems on which it is imported.
Then import it to correct the mismatch.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-EY
scan: scrub repaired 0B in 00:03:43 with 0 errors on Sun Dec 15 13:14:52 2024
config:
errors: No known data errors
That's half true. I did export the pool while building and installing RC4 from RC3, but the pool is on the exact same system. There have been no changes other than Fedora updates. After seeing that message I destroyed the pool after making sure my backup was up to date, and then recreated the pool. After a restart, this message has returned. Considering this is a brand new pool that has never been anywhere other than this machine, I can only assume this is a bug of some sort. There has never been any other systems to which this pool was attached. The pool does appear healthy and to be operating correctly.
Describe how to reproduce the problem
What I did was build a DKMS-RPM of 2.3 RC4 following the newly updated instructions to do so, and installed it. This then happened after a restart or two. Not sure exactly when.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: