Replies: 2 comments 4 replies
-
My immediate guess, quickly and blindly, would be that you took disks out of or put disks into enclosures that lie about the disk's physical size, leading to it screaming. I could be wrong, because this seems like it should be the on-disk representation, not the disk's reported one, but that'd be my quick guess other than "some metadata got very unhappy." That assertion, if I understand it right, is intended to be a safeguard against trying to free something that's not an allocation size the vdev should have allowed - that is, if your vdev (and disks) were configured with ashift 12 (4096B sector size), and you tried only freeing 512B, that would be very incorrect, because you shouldn't have been able to make that allocation in the first place. Which is why I'm guessing you changed how the disks were connected, to/from something that lies about their minimum allocation size. |
Beta Was this translation helpful? Give feedback.
-
I am also getting this exact same message. My Proxmox machine was having hardware issues that caused irregular system crashes. Eventually my machine would fail to finish booting and I got this message. New to this ecosystem, I did a backup of my boot drive and reinstalled Proxmox. After attempting to import the pool, I got the same message again. Is there any advice to troubleshoot this further or get everything working again? I appreciate it.
|
Beta Was this translation helpful? Give feedback.
-
I am unable to import a pool of 2 mirrored disks because of the following kernel panic:
Pool setup:
I'm using 2.1.22 so the line in question should be: https://github.com/openzfs/zfs/blob/zfs-2.1.12/module/zfs/metaslab.c#L5341
The disks themselves seem fine (short SMART test completed without errors), though the situation might be caused by some recent power outages.
I'm wondering what
asize
andashift
actually are and of course how to fix this issue and successfully import the pool.dmesg trace:
Beta Was this translation helpful? Give feedback.
All reactions