-
Notifications
You must be signed in to change notification settings - Fork 46
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
Btrfs / not found #219
Comments
Could you please change the last kernel boot parameter to A few comments regarding your config file:
|
OK, thanks first for the answer. universal: false
modules: btrfs,nvidia
mount_timeout: 20s
extra_files: fsck,fsck.btrfs,busybox
vconsole: true the debug output print too many message, so maybe this will be enought? If not I will try a way to take the others
|
I can't find a way to collect the logs to the next boot as in this one no disk is mounted, I tried to stop the output with Ctrl+s but no chance that it stops |
I need more debug logs to tell exactly what is going on. Ideally I need a few dozens last messages from booster: For the logs you shared I only see one error with nvidia module. To get rid of PS Please use github compatible markup (see short description here https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). In particular for quotations use either single backtick ("`") or triple backtick for multiline quotation. |
Also one you get into booster's busybox please share the output of |
I assume you use the latest booster (0.10). I looked through the images and I can't find where a storage device is detected. What storage hardware the root file system uses? Is it a regular nvme over pci? Or it something less typical? In the latter case you might need to find what drivers are used by the device and add them to booster config file. Please post |
Thank you to taking the time to help me (in particular when reading images) :) I think it a common nvme over pci, never looked about it, but I will try to search about it. Here is the output of
|
Before going to more debugging could you please confirm that:
Also what Linux distro you are using? Okay, I looked through the screeshots you posted and I do not see where the I think it is the issue. First please post output of If |
When boot fails, the
I've this modules when booting with an mkinitcpio image, maybe some of those are missing:
|
Yeah, most likely some of the modules needed to enumerate NVMe devices are missed. But I am not fully sure which one. My guess is that the parent bus kernel module is required. I suggest to run |
I've take a look with lshw and found this
then I've tried to add |
Returning back to this issue. I think some of the drivers are not included in the image. And we need to find which one. I just added a feature that allows such debugging easier. 0a71268 added @Tarch1 please pull |
Not sure if this is your issue, but I had an issue mounting btrfs with |
Interesting. It might point to an issue with GPT table parsing. |
I can only second that. For btrfs I ended up needing to specify the root in the kernel parameter. |
Hi,
I've struggling when I use booster with a btrfs volume for the root partition, with mkinitcpio I've added btrfs in modules, then I'm using this kernel parameters in
/boot/refind_linux.conf
rw root=PARTUUID=4178b813-afe7-475e-8c9d-73063b623044 rootfstype=btrfs rootflags=subvol=@ initrd=intel-ucode.img initrd=initramfs-%v.img nvidia-drm.modeset=1
and with booster
rw root=PARTUUID=4178b813-afe7-475e-8c9d-73063b623044 rootfstype=btrfs rootflags=subvol=@ initrd=intel-ucode.img initrd=booster-linux.img nvidia-drm.modeset=1 booster.log=error,console
but after rebooting it hang after not seeing the root /
My booster.yaml is
No error reported with universal: true it say
booster: Timeout waiting for root filesystem
The text was updated successfully, but these errors were encountered: