GParted PXE Boot Fails at Root FS mount - Kernel Panic
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
https://imgur.com/a/caCiVue
I have GParted setup almost identically to as described in the website help:
https://gparted.org/livepxe.php
The only difference between that the root directory is not / rather /GParted
The vmlinuz and initrd seem to boot ok.
The filesystem.squashfs is loaded via http and I can successfully wget it.
However, when it try to mount of the filesystem.squashfs, I have a problem as shown in the red box.
Mounting root file system ... /init: .: line 225: can't open '/scripts/GParted/live'
I'm not sure where /scripts/GParted/live is. I'm also not sure how it would get a directory in front of my root /GParted However, the system manages to find /scripts/init-premount
My PXE default here:
LABEL GParted Live
MENU LABEL GParted Live
kernel GParted/live/vmlinuz
APPEND initrd=GParted/live/initrd.img boot=GParted/live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
ENDTEXT
Where have I gone astray?
gparted
add a comment |Â
up vote
1
down vote
favorite
https://imgur.com/a/caCiVue
I have GParted setup almost identically to as described in the website help:
https://gparted.org/livepxe.php
The only difference between that the root directory is not / rather /GParted
The vmlinuz and initrd seem to boot ok.
The filesystem.squashfs is loaded via http and I can successfully wget it.
However, when it try to mount of the filesystem.squashfs, I have a problem as shown in the red box.
Mounting root file system ... /init: .: line 225: can't open '/scripts/GParted/live'
I'm not sure where /scripts/GParted/live is. I'm also not sure how it would get a directory in front of my root /GParted However, the system manages to find /scripts/init-premount
My PXE default here:
LABEL GParted Live
MENU LABEL GParted Live
kernel GParted/live/vmlinuz
APPEND initrd=GParted/live/initrd.img boot=GParted/live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
ENDTEXT
Where have I gone astray?
gparted
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
https://imgur.com/a/caCiVue
I have GParted setup almost identically to as described in the website help:
https://gparted.org/livepxe.php
The only difference between that the root directory is not / rather /GParted
The vmlinuz and initrd seem to boot ok.
The filesystem.squashfs is loaded via http and I can successfully wget it.
However, when it try to mount of the filesystem.squashfs, I have a problem as shown in the red box.
Mounting root file system ... /init: .: line 225: can't open '/scripts/GParted/live'
I'm not sure where /scripts/GParted/live is. I'm also not sure how it would get a directory in front of my root /GParted However, the system manages to find /scripts/init-premount
My PXE default here:
LABEL GParted Live
MENU LABEL GParted Live
kernel GParted/live/vmlinuz
APPEND initrd=GParted/live/initrd.img boot=GParted/live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
ENDTEXT
Where have I gone astray?
gparted
https://imgur.com/a/caCiVue
I have GParted setup almost identically to as described in the website help:
https://gparted.org/livepxe.php
The only difference between that the root directory is not / rather /GParted
The vmlinuz and initrd seem to boot ok.
The filesystem.squashfs is loaded via http and I can successfully wget it.
However, when it try to mount of the filesystem.squashfs, I have a problem as shown in the red box.
Mounting root file system ... /init: .: line 225: can't open '/scripts/GParted/live'
I'm not sure where /scripts/GParted/live is. I'm also not sure how it would get a directory in front of my root /GParted However, the system manages to find /scripts/init-premount
My PXE default here:
LABEL GParted Live
MENU LABEL GParted Live
kernel GParted/live/vmlinuz
APPEND initrd=GParted/live/initrd.img boot=GParted/live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
ENDTEXT
Where have I gone astray?
gparted
gparted
asked Aug 21 at 16:13
user3242295
61
61
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
The /scripts/init-premount
lives inside the GParted initrd.img
file.
The error message suggests the system is running into trouble on line 225 of script /init
within the initrd image.
The line 225 of that script is:
. /scripts/$BOOT
And the $BOOT
variable gets its value from the boot=
boot parameter earlier.
So, the mistake is in assuming that if you put the filesystem.squashfs
file into a sub-directory on the web server, you need to adjust the value of the boot=
option to match. That is incorrect.
The boot=
option specifies the boot mode: local
, nfs
, or live
. This causes the script system (= initramfs-tools
from Debian) to run the corresponding script in the /scripts/
directory. /scripts/live
exists in the initrd.img file, but /scripts/GParted/live
doesn't.
So, change the APPEND line of your PXE bootloader configuration to:
APPEND initrd=GParted/live/initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
...and then it should work.
add a comment |Â
up vote
0
down vote
That was it. I didn't realize the boot= was a parameter as opposed to the initial boot directory holding initrd. Thank you.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The /scripts/init-premount
lives inside the GParted initrd.img
file.
The error message suggests the system is running into trouble on line 225 of script /init
within the initrd image.
The line 225 of that script is:
. /scripts/$BOOT
And the $BOOT
variable gets its value from the boot=
boot parameter earlier.
So, the mistake is in assuming that if you put the filesystem.squashfs
file into a sub-directory on the web server, you need to adjust the value of the boot=
option to match. That is incorrect.
The boot=
option specifies the boot mode: local
, nfs
, or live
. This causes the script system (= initramfs-tools
from Debian) to run the corresponding script in the /scripts/
directory. /scripts/live
exists in the initrd.img file, but /scripts/GParted/live
doesn't.
So, change the APPEND line of your PXE bootloader configuration to:
APPEND initrd=GParted/live/initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
...and then it should work.
add a comment |Â
up vote
0
down vote
The /scripts/init-premount
lives inside the GParted initrd.img
file.
The error message suggests the system is running into trouble on line 225 of script /init
within the initrd image.
The line 225 of that script is:
. /scripts/$BOOT
And the $BOOT
variable gets its value from the boot=
boot parameter earlier.
So, the mistake is in assuming that if you put the filesystem.squashfs
file into a sub-directory on the web server, you need to adjust the value of the boot=
option to match. That is incorrect.
The boot=
option specifies the boot mode: local
, nfs
, or live
. This causes the script system (= initramfs-tools
from Debian) to run the corresponding script in the /scripts/
directory. /scripts/live
exists in the initrd.img file, but /scripts/GParted/live
doesn't.
So, change the APPEND line of your PXE bootloader configuration to:
APPEND initrd=GParted/live/initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
...and then it should work.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
The /scripts/init-premount
lives inside the GParted initrd.img
file.
The error message suggests the system is running into trouble on line 225 of script /init
within the initrd image.
The line 225 of that script is:
. /scripts/$BOOT
And the $BOOT
variable gets its value from the boot=
boot parameter earlier.
So, the mistake is in assuming that if you put the filesystem.squashfs
file into a sub-directory on the web server, you need to adjust the value of the boot=
option to match. That is incorrect.
The boot=
option specifies the boot mode: local
, nfs
, or live
. This causes the script system (= initramfs-tools
from Debian) to run the corresponding script in the /scripts/
directory. /scripts/live
exists in the initrd.img file, but /scripts/GParted/live
doesn't.
So, change the APPEND line of your PXE bootloader configuration to:
APPEND initrd=GParted/live/initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
...and then it should work.
The /scripts/init-premount
lives inside the GParted initrd.img
file.
The error message suggests the system is running into trouble on line 225 of script /init
within the initrd image.
The line 225 of that script is:
. /scripts/$BOOT
And the $BOOT
variable gets its value from the boot=
boot parameter earlier.
So, the mistake is in assuming that if you put the filesystem.squashfs
file into a sub-directory on the web server, you need to adjust the value of the boot=
option to match. That is incorrect.
The boot=
option specifies the boot mode: local
, nfs
, or live
. This causes the script system (= initramfs-tools
from Debian) to run the corresponding script in the /scripts/
directory. /scripts/live
exists in the initrd.img file, but /scripts/GParted/live
doesn't.
So, change the APPEND line of your PXE bootloader configuration to:
APPEND initrd=GParted/live/initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://10.1.200.1/GParted/live/filesystem.squashfs
...and then it should work.
answered Aug 23 at 11:00
telcoM
11.6k11333
11.6k11333
add a comment |Â
add a comment |Â
up vote
0
down vote
That was it. I didn't realize the boot= was a parameter as opposed to the initial boot directory holding initrd. Thank you.
add a comment |Â
up vote
0
down vote
That was it. I didn't realize the boot= was a parameter as opposed to the initial boot directory holding initrd. Thank you.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
That was it. I didn't realize the boot= was a parameter as opposed to the initial boot directory holding initrd. Thank you.
That was it. I didn't realize the boot= was a parameter as opposed to the initial boot directory holding initrd. Thank you.
answered Aug 29 at 0:31
user3242295
61
61
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f463909%2fgparted-pxe-boot-fails-at-root-fs-mount-kernel-panic%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password