Recent searches
Search options
I'm sure it's #RedHat #ImageBuilder that's awesome and it's me that's confused but omg it does really feel like it's the other way around ...
Cannot mount sysroot you say? Bad superblock? Yeah well ... can't really write anything else in those [[customizations.filesystem]] now can I :/
So this is a vmdk image built by Image Builder. The VMware hard disk drivers (nVME, SATA, SCSI .. ) all claim there are I/O errors when trying to mount the root partition (or any, actually. The schema creates /, /home, /data, /var and /app partitions). RH8.6.
I'm running out of ideas here. And no, can't update to RH8.7 just for kicks either.
No kickstart - I do assume Image Builder activates the logical volumes ... ?
Still confused. Having attached the vmdk in another VM and investigated the disk, layout, VG, VL etc I can only conclude that there really is something wrong with how the contents were created and the "bad superblock" message is correct.
#osbuild / image builder does seem a little bit shaky in various places.
well well well
With no other changes made to the blueprint, building a qcow2 instead of vmdk and then directly converting the qcow2 to vmdk worked.
So at this moment I would wager that there's an issue in Red Hat 8.6 osbuild / image builder when it comes to generating vmdk type filesystems.