Skip to content
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

Open
Thorazin opened this issue Dec 17, 2024 · 7 comments
Open
Labels
Type: Defect Incorrect behavior (e.g. crash, hang)

Comments

@Thorazin
Copy link

Thorazin commented Dec 17, 2024

System information

Type Version/Name
Distribution Name Fedora
Distribution Version Workstation
Kernel Version 6.12.4-200.fc41.x86_64
Architecture x86
OpenZFS Version zfs-2.3.0-rc4
zfs-kmod-2.3.0-rc4

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:

NAME                                             STATE     READ WRITE CKSUM
Tank                                             ONLINE       0     0     0
  raidz1-0                                       ONLINE       0     0     0
    ata-Samsung_SSD_870_EVO_1TB_S75BNS0W505504K  ONLINE       0     0     0
    ata-CT1000MX500SSD1_2320E6D7C60A             ONLINE       0     0     0
    ata-CT1000MX500SSD1_2320E6D5F0ED             ONLINE       0     0     0
    ata-CT1000MX500SSD1_2321E6D9DD98             ONLINE       0     0     0

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

@Thorazin Thorazin added the Type: Defect Incorrect behavior (e.g. crash, hang) label Dec 17, 2024
@AllKind
Copy link
Contributor

AllKind commented Dec 17, 2024

Does this or that help?

@Thorazin
Copy link
Author

Thorazin commented Dec 17, 2024

"That" has appeared to help with one problem. Exporting and Importing the pool has created another problem however...

zpool status
pool: Tank
state: ONLINE
scan: scrub repaired 0B in 00:03:43 with 0 errors on Sun Dec 15 13:14:52 2024
config:

NAME        STATE     READ WRITE CKSUM
Tank        ONLINE       0     0     0
  raidz1-0  ONLINE       0     0     0
    sda     ONLINE       0     0     0
    sdb     ONLINE       0     0     0
    sdc     ONLINE       0     0     0
    sdd     ONLINE       0     0     0

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
pool: Tank
state: ONLINE
scan: scrub repaired 0B in 00:03:43 with 0 errors on Sun Dec 15 13:14:52 2024
config:

NAME                        STATE     READ WRITE CKSUM
Tank                        ONLINE       0     0     0
  raidz1-0                  ONLINE       0     0     0
    wwn-0x5002538f33502093  ONLINE       0     0     0
    wwn-0x500a0751e6d7c60a  ONLINE       0     0     0
    wwn-0x500a0751e6d5f0ed  ONLINE       0     0     0
    wwn-0x500a0751e6d9dd98  ONLINE       0     0     0

errors: No known data errors

@AllKind
Copy link
Contributor

AllKind commented Dec 17, 2024

Just make sure to rebuild your initrd.

@Thorazin
Copy link
Author

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'
dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.oVhfTy/initramfs -H --kerneldir /lib/modules/6.11.10-300.fc41.x86_64/ -m zfs
dracut[F]: installkernel failed in module zfs

@AllKind
Copy link
Contributor

AllKind commented Dec 17, 2024

Kernel Version 6.12.4-200.fc41.x86_64

modules/6.11.10-300.fc41.x86_64/

Old kernel? No modules present built by dkms?

@Thorazin
Copy link
Author

Kernel Version 6.12.4-200.fc41.x86_64

modules/6.11.10-300.fc41.x86_64/

Old kernel? No modules present built by dkms?

dkms status gives this, it looks like it is there and installed:

dkms status
openrazer-driver/3.9.0, 6.11.10-300.fc41.x86_64, x86_64: installed
openrazer-driver/3.9.0, 6.11.11-300.fc41.x86_64, x86_64: installed
openrazer-driver/3.9.0, 6.12.4-200.fc41.x86_64, x86_64: installed
zfs/2.3.0, 6.11.11-300.fc41.x86_64, x86_64: installed
zfs/2.3.0, 6.12.4-200.fc41.x86_64, x86_64: installed

@AllKind
Copy link
Contributor

AllKind commented Dec 17, 2024

I'm not a fedora user and don't know dracut well enough.
Your favorite search engine might help...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Defect Incorrect behavior (e.g. crash, hang)
Projects
None yet
Development

No branches or pull requests

2 participants