Skip to content
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

Investiagte failures where rootfs is not mounted because of some error #465

Closed
musamaanjum opened this issue Oct 10, 2024 · 2 comments
Closed
Assignees

Comments

@musamaanjum
Copy link

An example:

[    7.620629] Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/ram0" or unknown-block(1,0)
[    7.630182] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.10.14-rc1 #1
[    7.636531] Hardware name: BCM2835
[    7.639927] Call trace:
[    7.639943]  unwind_backtrace from show_stack+0x10/0x14
[    7.647707]  show_stack from panic+0x10c/0x388
[    7.652158]  panic from mount_root_generic+0x2a0/0x2a8
[    7.657306]  mount_root_generic from prepare_namespace+0x1fc/0x254
[    7.663493]  prepare_namespace from kernel_init+0x1c/0x12c
[    7.668986]  kernel_init from ret_from_fork+0x14/0x28
@musamaanjum musamaanjum self-assigned this Oct 10, 2024
@musamaanjum musamaanjum converted this from a draft issue Oct 10, 2024
@nuclearcat
Copy link
Member

I think this issue related to faulty devices (we removed them recently). Is there any others who dont boot?

@musamaanjum
Copy link
Author

Yeah, it should be solved. I'll keep this ticket open until I prepare next stable-rc report to be 100% sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants