starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-25 07:05:56 +03:00

[GH-ISSUE #224] Unable to mount root fs with RancherOS and Set Github User menu boot #1636

New issue

Closed

opened 2026-03-01 18:35:03 +03:00 by kerem · 6 comments

kerem commented

2026-03-01 18:35:03 +03:00

Owner

Originally created by @jpastuszek on GitHub (Mar 14, 2018).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/224

I am trying to get RancherOS booting with custom could-config URL using Set Github User feature.
When booting RancherOS form built-in menu it works OK.
If I boot using chain command from failsafe debug iPXE menu and point it to URL of my custom.ipxe it also boots OK.
If I boot from same config file using Set Github User menu it fails to boot with missing root volume:
VFS: Unable to mount root fs on unknown-block(0,0)

Is there anything special that netboot does to the environment that could make it fail that way?

I am using Virtual Box and custom.ipxe:

#!ipxe
dhcp
set base-url https://releases.rancher.com/os/latest
kernel ${base-url}/vmlinuz printk.devkmsg=on rancher.debug=true rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 rancher.state.mdadm_scan console=ttyS1,115200n8 rancher.autologin=ttyS1 rancher.network.interfaces.eth*.dhcp=true rancher.cloud_init.datasources=[configdrive,ec2,gce,packet,digitalocean]
initrd ${base-url}/initrd
boot

I have also tried to just copy content the archeros.ipxe from this repository to my custom.ipxe but I got same problem.
I am using netboot.xyz v.1.0.4; I have also tired master branch of this repository using Test netboot.xyz branch.

Originally created by @jpastuszek on GitHub (Mar 14, 2018). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/224 I am trying to get RancherOS booting with custom could-config URL using `Set Github User` feature. When booting RancherOS form built-in menu it works OK. If I boot using `chain` command from failsafe debug iPXE menu and point it to URL of my `custom.ipxe` it also boots OK. If I boot from same config file using `Set Github User` menu it fails to boot with missing root volume: ```VFS: Unable to mount root fs on unknown-block(0,0)``` Is there anything special that netboot does to the environment that could make it fail that way? I am using Virtual Box and `custom.ipxe`: ``` #!ipxe dhcp set base-url https://releases.rancher.com/os/latest kernel ${base-url}/vmlinuz printk.devkmsg=on rancher.debug=true rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 rancher.state.mdadm_scan console=ttyS1,115200n8 rancher.autologin=ttyS1 rancher.network.interfaces.eth*.dhcp=true rancher.cloud_init.datasources=[configdrive,ec2,gce,packet,digitalocean] initrd ${base-url}/initrd boot ``` I have also tried to just copy content the `archeros.ipxe` from this repository to my `custom.ipxe` but I got same problem. I am using netboot.xyz v.1.0.4; I have also tired master branch of this repository using `Test netboot.xyz branch`.

kerem

2026-03-01 18:35:03 +03:00

closed this issue
added the
bug

investigate
labels

kerem commented

2026-03-01 18:35:03 +03:00

Author

Owner

@jpastuszek commented on GitHub (Mar 14, 2018):

To reproduce OK boot:

Press m to get into failback mode and select iPXE Debug Shell. Type:

dhcp
chain http://goo.gl/bkF6V4

http://goo.gl/bkF6V4 points to https://raw.githubusercontent.com/jpastuszek/netboot.xyz-custom/master/custom.ipxe of following content:

#!ipxe
dhcp
set base-url https://releases.rancher.com/os/latest
kernel ${base-url}/vmlinuz printk.devkmsg=on rancher.debug=true rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 rancher.state.mdadm_scan console=ttyS1,115200n8 rancher.autologin=ttyS1 rancher.network.interfaces.eth*.dhcp=true rancher.cloud_init.datasources=[configdrive,ec2,gce,packet,digitalocean]
initrd ${base-url}/initrd
boot

You should see RancherOS login prompt.

Failed boot:

Let netboot.xyz boot full.
Go to Utilities -> Set Github User and type: jpastuszek.
Then go to iPXE shell and type same chain URL:

chain http://goo.gl/bkF6V4

Kernel will panic.

@jpastuszek commented on GitHub (Mar 14, 2018): To reproduce OK boot: Press `m` to get into failback mode and select `iPXE Debug Shell`. Type: ``` dhcp chain http://goo.gl/bkF6V4 ``` http://goo.gl/bkF6V4 points to https://raw.githubusercontent.com/jpastuszek/netboot.xyz-custom/master/custom.ipxe of following content: ``` #!ipxe dhcp set base-url https://releases.rancher.com/os/latest kernel ${base-url}/vmlinuz printk.devkmsg=on rancher.debug=true rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 rancher.state.mdadm_scan console=ttyS1,115200n8 rancher.autologin=ttyS1 rancher.network.interfaces.eth*.dhcp=true rancher.cloud_init.datasources=[configdrive,ec2,gce,packet,digitalocean] initrd ${base-url}/initrd boot ``` You should see RancherOS login prompt. Failed boot: Let netboot.xyz boot full. Go to `Utilities` -> `Set Github User` and type: `jpastuszek`. Then go to `iPXE shell` and type same chain URL: ``` chain http://goo.gl/bkF6V4 ``` Kernel will panic.

kerem commented

2026-03-01 18:35:04 +03:00

Author

Owner

@jpastuszek commented on GitHub (Mar 14, 2018):

Actually by just going to Utilities and coming back will cause boot failure.

@jpastuszek commented on GitHub (Mar 14, 2018): Actually by just going to `Utilities` and coming back will cause boot failure.

kerem commented

2026-03-01 18:35:04 +03:00

Author

Owner

@jpastuszek commented on GitHub (Mar 14, 2018):

Actually going to any menu and coming back will make this OS fail to boot...

@jpastuszek commented on GitHub (Mar 14, 2018): Actually going to any menu and coming back will make this OS fail to boot...

kerem commented

2026-03-01 18:35:04 +03:00

Author

Owner

@jpastuszek commented on GitHub (Mar 14, 2018):

Same issue with real Dell PC.

@jpastuszek commented on GitHub (Mar 14, 2018): Same issue with real Dell PC.

kerem commented

2026-03-01 18:35:04 +03:00

Author

Owner

@antonym commented on GitHub (Mar 20, 2018):

Good find, I was able to repro. I think it might need an imgfree before loading the kernels, giving that a try.

@antonym commented on GitHub (Mar 20, 2018): Good find, I was able to repro. I think it might need an imgfree before loading the kernels, giving that a try.

kerem commented

2026-03-01 18:35:04 +03:00

Author

Owner

@antonym commented on GitHub (Mar 20, 2018):

This appeared to fix it: github.com/antonym/netboot.xyz@e4d041323a. If you continue to have issues with it, please reopen.

Thanks!

@antonym commented on GitHub (Mar 20, 2018): This appeared to fix it: https://github.com/antonym/netboot.xyz/commit/e4d041323ae9725dd1f3476aba81495c090ab87d. If you continue to have issues with it, please reopen. Thanks!

kerem referenced this issue

2026-03-01 18:38:26 +03:00

[GH-ISSUE #1636] netbootxyz booting on Proxmox VM / Broken menu items #2092

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#1636

No description provided.

Rows
Columns