#going bald - dracut stuck on boot, not recognizing my disk (Custom Kernel)
1 messages · Page 1 of 1 (latest)
The only slightly related problem that i've ever encountered happened due to mkinitcpio failing midway to create the boot image.
Turned out that my "/boot" ran out of space and the vmlinuz image was corrupt due to it.
my /efi part has +1G, i don't think it could be the problem
and theese above are the only messages i got after booting,
ugrd makes smaller images if you're out of space
and will do more to confirm you have the kmods you need
this you?
mkinitcpio?
that is different from dracut
also that picture says you don't have the bdev fs, i think you need nvme drivers
if you run ugrd it should tell you
I solved my problem, long ago.
Just thought about sharing something similar.
i think using ugrd may help point you in the right direction
because it checks fora lot of this stuff
if not i will patch it 😛
Will check on that
Sure
maybe i'll just settle on no initramfs at all haha
i have all my stuff compiled into kernel anyways for security measures
not using lvm, neither disk encryption
why not
`CONFIG_NVME_COMMON=y
CONFIG_NVME_CORE=y
CONFIG_BLK_DEV_NVME=y
CONFIG_NVME_MULTIPATH=y
CONFIG_NVME_VERBOSE_ERRORS is not set
CONFIG_NVME_HWMON=y
CONFIG_NVME_FABRICS=y
CONFIG_NVME_FC=y
CONFIG_NVME_TCP=y
CONFIG_NVME_AUTH=y`
didn't tried it yet, but read somewhere it might be the IOMMU kernel config, i set it to strict which might be the issue
I'll test with the lazy option
based on the error, idk
tbh i would first confirm dist-kernel works
that helps isolate any issues that are not kernel related
except if dist-kernel doesn't work for you (unlikely)
this specifically looks like a dracut issue, one i've never seen
which could actually be related to userspace issues
it does
so it must be the kernel config somewhere
hmmm that is strange, idk why there are errors in dracut's init
ugrd should make any issues more clear tho
well, installing it now then
tried to generate with your(Thanks for contribution) ugrd, and it tells me there is no xfs module, well it is build in the kernel not as module, error:
`ValueError: Required module cannot be imported and is not builtin: xfs
- Failed to generate initramfs`
the config for xfs:
`CONFIG_XFS_FS=y
CONFIG_XFS_SUPPORT_V4 is not set
CONFIG_XFS_SUPPORT_ASCII_CI is not set
CONFIG_XFS_QUOTA is not set
CONFIG_XFS_POSIX_ACL is not set
CONFIG_XFS_RT is not set
CONFIG_XFS_ONLINE_SCRUB is not set
CONFIG_XFS_WARN is not set
CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS is not set`
maybe it's just better for me don't use initramfs at all?
it doesn't see it's builtin
are you sure it is?
how are you running ugrd?
via installkernel
you sure you didn't rebuild and forget to reinstall?
run make modules_install again (even if you added something builtin)
i have no modules, all is compiled
i did, still the same issue
otherwise things have no way of knowing what is builtin to the kernel
what does modinfo -k <kver> xfs say
right now i'm reinstalling and i'll try to do the setup without initramfs at all, will tell how it went
it should be fine without an initramfs
if you're on top of maintaining your kernel config
but if it doesn't work with an initramfs it probably won't work without one
unless it's a bug with the intiramfs
also ugrd has a no_kmod option you can use
if you want to force it to work without kmods
but that disables a lot of the validaiton which would help you here (possibly)
well, not sure why it booted clean as ever with no initramfs, got an another error from open-rc caused by my screw-up so i'm doing a clean install
what screw up?
and ugrd probably would have worked if you set no_kmod, if it didn't that could help identify if userspace stuff is built wrong
which was my first guess based on how dracut was breaking
ah, it wasn't my screw up just another problem, managed to get it past that without initramfs, but getting an open-rc failed to init message:
OpenRC **starting up** mkdir '/run/openrc/' read only file system mkdir /run/ioenrc/starting: No such file or directory and so on
are you using openrc-init?
isn't it built in?
oh sure
read somewhere it's in defaults
will try to run it with openrc-init thanks
so what should i do then
i use sysvinit
did you edit your fstab?
on the installation, i did
i'll post it
/dev/nvme0n1p1 /efi vfat umask=0077 0 2 /dev/nvme0n1p2 none swap sw 0 0 /dev/nvme0n1p3 / xfs defaults,noatime 0 1
that looks fine
the thing is that it ran without a problem with a dist kernel, so maybe i should change something because i run no initramfs?
if you run it with ugrd i can prob help you debug this more
it tends to give helpful info when things break
it should work if you tell it to ignore kmods
sure
and you can add the "recovery" arg to your kernel command line so it should give you a shell
the init is also very simple so if it complains about something missing it shoud be clear what is
you have the tmpfs kmod right?
yeah i do
so that is needed for your run mount
ugrd should let you know if it can't do that
sure
if it does, and works, that is honestly really strange
but yeah openrc needs that dir to be working to be functional, and it's often mounted pre-init, but should not be a requirement
so INODE and QUOTA is needed?
i have all the options turned on except theese two
you figure anything out?
went to sleep, back to it now haha
I'll try to compile it with localmod config, if it boots 'll then compare the differences in my config and find the issue
I have no idea anymore... Compiled allyes config, and also localmod config, neither of those work, i always get
ERROR | Required module cannot be imported and is not builtin: xfs from ugrd
tried no_kmod and it generated initramfs, but still the same error on boot,
okay... a new thing, tried to boot the localmod config despite the error from urgd, and it somehow booted correctly, the problem must be laying in my kconfig
the thing is i have to go through all my configs and try to find the option i must've missed
well, all this debugging and it all came down to making a new kernel config, thanks for help
should work if I manage to configure the drivers
what?
so it somehow works with kmods?
sorry for a mess, yeah ugrd** works now, i had to spend a day tweaking the kernel config and it boots up 😄
switched to efi stub too, anyway thanks for help and for your contribution to ugrd,
so everything works now? i wonder if the dracut issue still exists
do you know for certain what you did to fix it? ugrd shouldn't fix things as much as it exposes issues (unless this is a dracut bug)
basically threw my previous kernel config, and made a new one trying new options, can't tell exactly, propably some drivers for nvme or pci were missing
looks like it
for now everything works
possibly, the nice thing about having some kmods is that ugrd can read them adn tell you if somerthing important is missing
also if you have stuff that requires firmare, it's often nice to just leave it as a kmod so you don't need to build the firmare into the kernel
the linux kernel is essentially designed to use kmods no matter what, while it's technically possible to entirely avoid them you sometimes hit strange issues