mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 07:05:56 +03:00
[GH-ISSUE #1628] SystemRescueCD 12 is unable to boot, kernel panics due to no root file system? #2086
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#2086
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @UntouchedWagons on GitHub (May 24, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1628
[✅]: This bug persists when memory is increased beyond 8GB.
Describe the bug
A Proxmox VM that tries to PXE boot SystemRescueCD 12 immediately kernel panics due to a missing file system (I think)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect SystemRescueCD to not kernel panic due to a missing file system.
Screenshots
Additional context
I don't know what else would be useful to add.
@Znuff commented on GitHub (May 25, 2025):
To add to this, the hypervisor used doesn't matter. I see the same thing on vmware and proxmox:
This happens both on UEFI and BIOS, but obviously on BIOS it doesn't have the pretty blue screen, just black on white.
@antonym commented on GitHub (May 27, 2025):
Should be fixed in latest development menus.
@UntouchedWagons commented on GitHub (Jul 18, 2025):
I'm still not able to PXE boot SystemRescueCD 12