ValueError: new value non-existent xfs filesystem is not valid as a default fs type

Pane is dead

From what I read this is misleading and has to do with the fact that the initrd and kernel are mismatched.

This is a hard situation because for some older hardware I am using the Centos Plus kernel which has modules that I require for an older server/NIC.  This seems to have cropped up in the past few months and there is no simple fix which is quite frustrating.

I wish RHEL/Centos would provide a CentosPlus kernel for their PXE boot image as this essentially stops things from working and creates a PXEBoot/NetInstall scenario that cannot be relied on because it seems to pull other image data from the Centos repo which ends up breaking in the event that the repo has been updated and your kernel/initrd are mismatched.

But it worked before the whole time so something unexpected or undesirable has changed upstream unfortunately.  For now I am not sure of the solution short of creating my own PXEBoot initrd image and kernel.

Solution

It seems whether by bug or design that if you try installing a dated Centos 7 NetInstall vmlinuz and initrd that it just won't work.  It could just be that the version is no longer on most mirrors (an older Centos 7 version) so it breaks.

Just going to a mirror like this one and getting the latest vmlinuz and initrd from the NetInstall .iso will fix it

centos, pxeboot, netinstall, pane, deadvalueerror, existent, xfs, filesystem, valid, default, fs, misleading, initrd, kernel, mismatched, hardware, modules, server, nic, cropped, frustrating, rhel, centosplus, pxe, essentially, creates, relied, repo, updated, undesirable, upstream, creating,

Latest Articles