Live USB error “you need to load the kernel first”
I've got an mkusb live USB (Ubuntu 18.04 with persistence) that boots fine on some of my computers. On one laptop I get the following error:
error: disk `hd0,4' not found.
error: you need to load the kernel first.
What do I need to do to, "load the kernel first"?
EDIT: I only get this boot error when booting with the mkusb live USB. No problems when booting normally (without the live USB).
Answers to other questions
Computer:
HP 14" i3 Laptop Model 14-DF0023CL link here
mkusb settings:
- From Ubuntu 18.04.1 LTS command line run
dus
- Screen 1: Click OK
- Screen 2: Double-Click on the i option Install (make a boot device)
- Screen 2: Double-Click on the p option Persistent Live and select my Ubuntu 18.04 .iso file
- Screen 3: Tick the USB device to install to and click OK
- Screen 4: Click "Use defaults" and let mkusb decide what's best
- Screen 5: Enter the percentage of USB drive space to be 100% persistence file
- Screen 6: Tick the Go radio button and click Go.
- Screens 7-8: Just click Ok and let mkusb do its thing.
18.04 live-usb bios persistent mkusb
add a comment |
I've got an mkusb live USB (Ubuntu 18.04 with persistence) that boots fine on some of my computers. On one laptop I get the following error:
error: disk `hd0,4' not found.
error: you need to load the kernel first.
What do I need to do to, "load the kernel first"?
EDIT: I only get this boot error when booting with the mkusb live USB. No problems when booting normally (without the live USB).
Answers to other questions
Computer:
HP 14" i3 Laptop Model 14-DF0023CL link here
mkusb settings:
- From Ubuntu 18.04.1 LTS command line run
dus
- Screen 1: Click OK
- Screen 2: Double-Click on the i option Install (make a boot device)
- Screen 2: Double-Click on the p option Persistent Live and select my Ubuntu 18.04 .iso file
- Screen 3: Tick the USB device to install to and click OK
- Screen 4: Click "Use defaults" and let mkusb decide what's best
- Screen 5: Enter the percentage of USB drive space to be 100% persistence file
- Screen 6: Tick the Go radio button and click Go.
- Screens 7-8: Just click Ok and let mkusb do its thing.
18.04 live-usb bios persistent mkusb
1. In what computer are there problems? Please specify brand name and model; 2. Please tell me which settings you used, when you created the persistent live drive. If you cannot remember, and have another USB pendrive or a memory card (and a USB card adapter), please create a new persistent live drive and use the default settings (when asked by mkusb); 3. Please check in the grub menu environment, as suggested in the answer by @Jos,grub> ls... and report the result by editing your original question.
– sudodus
8 hours ago
4. In what operating system (distro and version, for example Ubuntu 18.04.1 LTS) are you running mkusb? I'm asking because I need these data in order to find the cause of this problem (if possible reproduce the problem); 5. If you have a USB pendrive or memory card with at least 16 GB, you can try a new compressed image file. Use mkusb to clone from that file into a pendrive or card, and check if that system works in the computer with problems.
– sudodus
8 hours ago
6. Are there more than one USB pendrives with persistent live systems connected to the computer, when you boot? In that case, there may be confusion with the drives and partitions.
– sudodus
7 hours ago
1
@sudodus updated my post to answer those questions. This is the only live USB drive attached to the system. Although there are other SD cards attached to the system I haven't tried removing. I'll try that! And report back tomorrow.
– Jason Hunter
7 hours ago
Thanks for the details about tasks/questions #1,2,4 :-) It should work in that computer. For example I have tested in a NUC computer with an M2 drive. I use mkusb a lot in 18.04.1 LTS. -- What about the other tasks/questions (#3,5,6)? 7. And a new task about the filemountpoint/boot/grub/grub.cfgin partition #3 of the persistent live drive: Please mount the partition and copy/paste thatgrub.cfgfile to your original question and indent each line 4 spaces to render it as 'code'.
– sudodus
5 hours ago
add a comment |
I've got an mkusb live USB (Ubuntu 18.04 with persistence) that boots fine on some of my computers. On one laptop I get the following error:
error: disk `hd0,4' not found.
error: you need to load the kernel first.
What do I need to do to, "load the kernel first"?
EDIT: I only get this boot error when booting with the mkusb live USB. No problems when booting normally (without the live USB).
Answers to other questions
Computer:
HP 14" i3 Laptop Model 14-DF0023CL link here
mkusb settings:
- From Ubuntu 18.04.1 LTS command line run
dus
- Screen 1: Click OK
- Screen 2: Double-Click on the i option Install (make a boot device)
- Screen 2: Double-Click on the p option Persistent Live and select my Ubuntu 18.04 .iso file
- Screen 3: Tick the USB device to install to and click OK
- Screen 4: Click "Use defaults" and let mkusb decide what's best
- Screen 5: Enter the percentage of USB drive space to be 100% persistence file
- Screen 6: Tick the Go radio button and click Go.
- Screens 7-8: Just click Ok and let mkusb do its thing.
18.04 live-usb bios persistent mkusb
I've got an mkusb live USB (Ubuntu 18.04 with persistence) that boots fine on some of my computers. On one laptop I get the following error:
error: disk `hd0,4' not found.
error: you need to load the kernel first.
What do I need to do to, "load the kernel first"?
EDIT: I only get this boot error when booting with the mkusb live USB. No problems when booting normally (without the live USB).
Answers to other questions
Computer:
HP 14" i3 Laptop Model 14-DF0023CL link here
mkusb settings:
- From Ubuntu 18.04.1 LTS command line run
dus
- Screen 1: Click OK
- Screen 2: Double-Click on the i option Install (make a boot device)
- Screen 2: Double-Click on the p option Persistent Live and select my Ubuntu 18.04 .iso file
- Screen 3: Tick the USB device to install to and click OK
- Screen 4: Click "Use defaults" and let mkusb decide what's best
- Screen 5: Enter the percentage of USB drive space to be 100% persistence file
- Screen 6: Tick the Go radio button and click Go.
- Screens 7-8: Just click Ok and let mkusb do its thing.
18.04 live-usb bios persistent mkusb
18.04 live-usb bios persistent mkusb
edited 7 hours ago
Jason Hunter
asked 10 hours ago
Jason HunterJason Hunter
372410
372410
1. In what computer are there problems? Please specify brand name and model; 2. Please tell me which settings you used, when you created the persistent live drive. If you cannot remember, and have another USB pendrive or a memory card (and a USB card adapter), please create a new persistent live drive and use the default settings (when asked by mkusb); 3. Please check in the grub menu environment, as suggested in the answer by @Jos,grub> ls... and report the result by editing your original question.
– sudodus
8 hours ago
4. In what operating system (distro and version, for example Ubuntu 18.04.1 LTS) are you running mkusb? I'm asking because I need these data in order to find the cause of this problem (if possible reproduce the problem); 5. If you have a USB pendrive or memory card with at least 16 GB, you can try a new compressed image file. Use mkusb to clone from that file into a pendrive or card, and check if that system works in the computer with problems.
– sudodus
8 hours ago
6. Are there more than one USB pendrives with persistent live systems connected to the computer, when you boot? In that case, there may be confusion with the drives and partitions.
– sudodus
7 hours ago
1
@sudodus updated my post to answer those questions. This is the only live USB drive attached to the system. Although there are other SD cards attached to the system I haven't tried removing. I'll try that! And report back tomorrow.
– Jason Hunter
7 hours ago
Thanks for the details about tasks/questions #1,2,4 :-) It should work in that computer. For example I have tested in a NUC computer with an M2 drive. I use mkusb a lot in 18.04.1 LTS. -- What about the other tasks/questions (#3,5,6)? 7. And a new task about the filemountpoint/boot/grub/grub.cfgin partition #3 of the persistent live drive: Please mount the partition and copy/paste thatgrub.cfgfile to your original question and indent each line 4 spaces to render it as 'code'.
– sudodus
5 hours ago
add a comment |
1. In what computer are there problems? Please specify brand name and model; 2. Please tell me which settings you used, when you created the persistent live drive. If you cannot remember, and have another USB pendrive or a memory card (and a USB card adapter), please create a new persistent live drive and use the default settings (when asked by mkusb); 3. Please check in the grub menu environment, as suggested in the answer by @Jos,grub> ls... and report the result by editing your original question.
– sudodus
8 hours ago
4. In what operating system (distro and version, for example Ubuntu 18.04.1 LTS) are you running mkusb? I'm asking because I need these data in order to find the cause of this problem (if possible reproduce the problem); 5. If you have a USB pendrive or memory card with at least 16 GB, you can try a new compressed image file. Use mkusb to clone from that file into a pendrive or card, and check if that system works in the computer with problems.
– sudodus
8 hours ago
6. Are there more than one USB pendrives with persistent live systems connected to the computer, when you boot? In that case, there may be confusion with the drives and partitions.
– sudodus
7 hours ago
1
@sudodus updated my post to answer those questions. This is the only live USB drive attached to the system. Although there are other SD cards attached to the system I haven't tried removing. I'll try that! And report back tomorrow.
– Jason Hunter
7 hours ago
Thanks for the details about tasks/questions #1,2,4 :-) It should work in that computer. For example I have tested in a NUC computer with an M2 drive. I use mkusb a lot in 18.04.1 LTS. -- What about the other tasks/questions (#3,5,6)? 7. And a new task about the filemountpoint/boot/grub/grub.cfgin partition #3 of the persistent live drive: Please mount the partition and copy/paste thatgrub.cfgfile to your original question and indent each line 4 spaces to render it as 'code'.
– sudodus
5 hours ago
1. In what computer are there problems? Please specify brand name and model; 2. Please tell me which settings you used, when you created the persistent live drive. If you cannot remember, and have another USB pendrive or a memory card (and a USB card adapter), please create a new persistent live drive and use the default settings (when asked by mkusb); 3. Please check in the grub menu environment, as suggested in the answer by @Jos,
grub> ls ... and report the result by editing your original question.– sudodus
8 hours ago
1. In what computer are there problems? Please specify brand name and model; 2. Please tell me which settings you used, when you created the persistent live drive. If you cannot remember, and have another USB pendrive or a memory card (and a USB card adapter), please create a new persistent live drive and use the default settings (when asked by mkusb); 3. Please check in the grub menu environment, as suggested in the answer by @Jos,
grub> ls ... and report the result by editing your original question.– sudodus
8 hours ago
4. In what operating system (distro and version, for example Ubuntu 18.04.1 LTS) are you running mkusb? I'm asking because I need these data in order to find the cause of this problem (if possible reproduce the problem); 5. If you have a USB pendrive or memory card with at least 16 GB, you can try a new compressed image file. Use mkusb to clone from that file into a pendrive or card, and check if that system works in the computer with problems.
– sudodus
8 hours ago
4. In what operating system (distro and version, for example Ubuntu 18.04.1 LTS) are you running mkusb? I'm asking because I need these data in order to find the cause of this problem (if possible reproduce the problem); 5. If you have a USB pendrive or memory card with at least 16 GB, you can try a new compressed image file. Use mkusb to clone from that file into a pendrive or card, and check if that system works in the computer with problems.
– sudodus
8 hours ago
6. Are there more than one USB pendrives with persistent live systems connected to the computer, when you boot? In that case, there may be confusion with the drives and partitions.
– sudodus
7 hours ago
6. Are there more than one USB pendrives with persistent live systems connected to the computer, when you boot? In that case, there may be confusion with the drives and partitions.
– sudodus
7 hours ago
1
1
@sudodus updated my post to answer those questions. This is the only live USB drive attached to the system. Although there are other SD cards attached to the system I haven't tried removing. I'll try that! And report back tomorrow.
– Jason Hunter
7 hours ago
@sudodus updated my post to answer those questions. This is the only live USB drive attached to the system. Although there are other SD cards attached to the system I haven't tried removing. I'll try that! And report back tomorrow.
– Jason Hunter
7 hours ago
Thanks for the details about tasks/questions #1,2,4 :-) It should work in that computer. For example I have tested in a NUC computer with an M2 drive. I use mkusb a lot in 18.04.1 LTS. -- What about the other tasks/questions (#3,5,6)? 7. And a new task about the file
mountpoint/boot/grub/grub.cfg in partition #3 of the persistent live drive: Please mount the partition and copy/paste that grub.cfgfile to your original question and indent each line 4 spaces to render it as 'code'.– sudodus
5 hours ago
Thanks for the details about tasks/questions #1,2,4 :-) It should work in that computer. For example I have tested in a NUC computer with an M2 drive. I use mkusb a lot in 18.04.1 LTS. -- What about the other tasks/questions (#3,5,6)? 7. And a new task about the file
mountpoint/boot/grub/grub.cfg in partition #3 of the persistent live drive: Please mount the partition and copy/paste that grub.cfgfile to your original question and indent each line 4 spaces to render it as 'code'.– sudodus
5 hours ago
add a comment |
1 Answer
1
active
oldest
votes
If you get to a grub prompt, it means that grub can't find the boot files that it expects. The sequence of commands to load the files and boot when grub doesn't do that for you goes something like this. First, find all partitions that grub sees:
grub> ls
(hd0) (hd0,msdos2) (hd0,msdos1)
This lists disks and partitions on the disks. One of these partitions holds your Linux system. Say it is (hd0,1). Then do:
grub> set root=(hd0,1)
grub> linux /boot/vmlinuz-4.15.0-45-generic root=/dev/sda1
Replace (hd0,1), the version number and the partition (/dev/sda1) by what is valid for your system. In the case of vmlinuz you can just type vmlinuz- and press Tab.
grub> initrd /boot/initrd.img-3.13.0-29-generic
The version string should be identical to the one for vmlinuz.
grub> boot
should now boot up your system.
I should've mentioned my system boots fine when not utilizing the live USB. I only get the error when I try and boot off the live USB. Is your answer still applicable to my circumstance? If yes, I will try that tonight and get back with you. Thank you.
– Jason Hunter
9 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117391%2flive-usb-error-you-need-to-load-the-kernel-first%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you get to a grub prompt, it means that grub can't find the boot files that it expects. The sequence of commands to load the files and boot when grub doesn't do that for you goes something like this. First, find all partitions that grub sees:
grub> ls
(hd0) (hd0,msdos2) (hd0,msdos1)
This lists disks and partitions on the disks. One of these partitions holds your Linux system. Say it is (hd0,1). Then do:
grub> set root=(hd0,1)
grub> linux /boot/vmlinuz-4.15.0-45-generic root=/dev/sda1
Replace (hd0,1), the version number and the partition (/dev/sda1) by what is valid for your system. In the case of vmlinuz you can just type vmlinuz- and press Tab.
grub> initrd /boot/initrd.img-3.13.0-29-generic
The version string should be identical to the one for vmlinuz.
grub> boot
should now boot up your system.
I should've mentioned my system boots fine when not utilizing the live USB. I only get the error when I try and boot off the live USB. Is your answer still applicable to my circumstance? If yes, I will try that tonight and get back with you. Thank you.
– Jason Hunter
9 hours ago
add a comment |
If you get to a grub prompt, it means that grub can't find the boot files that it expects. The sequence of commands to load the files and boot when grub doesn't do that for you goes something like this. First, find all partitions that grub sees:
grub> ls
(hd0) (hd0,msdos2) (hd0,msdos1)
This lists disks and partitions on the disks. One of these partitions holds your Linux system. Say it is (hd0,1). Then do:
grub> set root=(hd0,1)
grub> linux /boot/vmlinuz-4.15.0-45-generic root=/dev/sda1
Replace (hd0,1), the version number and the partition (/dev/sda1) by what is valid for your system. In the case of vmlinuz you can just type vmlinuz- and press Tab.
grub> initrd /boot/initrd.img-3.13.0-29-generic
The version string should be identical to the one for vmlinuz.
grub> boot
should now boot up your system.
I should've mentioned my system boots fine when not utilizing the live USB. I only get the error when I try and boot off the live USB. Is your answer still applicable to my circumstance? If yes, I will try that tonight and get back with you. Thank you.
– Jason Hunter
9 hours ago
add a comment |
If you get to a grub prompt, it means that grub can't find the boot files that it expects. The sequence of commands to load the files and boot when grub doesn't do that for you goes something like this. First, find all partitions that grub sees:
grub> ls
(hd0) (hd0,msdos2) (hd0,msdos1)
This lists disks and partitions on the disks. One of these partitions holds your Linux system. Say it is (hd0,1). Then do:
grub> set root=(hd0,1)
grub> linux /boot/vmlinuz-4.15.0-45-generic root=/dev/sda1
Replace (hd0,1), the version number and the partition (/dev/sda1) by what is valid for your system. In the case of vmlinuz you can just type vmlinuz- and press Tab.
grub> initrd /boot/initrd.img-3.13.0-29-generic
The version string should be identical to the one for vmlinuz.
grub> boot
should now boot up your system.
If you get to a grub prompt, it means that grub can't find the boot files that it expects. The sequence of commands to load the files and boot when grub doesn't do that for you goes something like this. First, find all partitions that grub sees:
grub> ls
(hd0) (hd0,msdos2) (hd0,msdos1)
This lists disks and partitions on the disks. One of these partitions holds your Linux system. Say it is (hd0,1). Then do:
grub> set root=(hd0,1)
grub> linux /boot/vmlinuz-4.15.0-45-generic root=/dev/sda1
Replace (hd0,1), the version number and the partition (/dev/sda1) by what is valid for your system. In the case of vmlinuz you can just type vmlinuz- and press Tab.
grub> initrd /boot/initrd.img-3.13.0-29-generic
The version string should be identical to the one for vmlinuz.
grub> boot
should now boot up your system.
answered 9 hours ago
JosJos
14.4k53950
14.4k53950
I should've mentioned my system boots fine when not utilizing the live USB. I only get the error when I try and boot off the live USB. Is your answer still applicable to my circumstance? If yes, I will try that tonight and get back with you. Thank you.
– Jason Hunter
9 hours ago
add a comment |
I should've mentioned my system boots fine when not utilizing the live USB. I only get the error when I try and boot off the live USB. Is your answer still applicable to my circumstance? If yes, I will try that tonight and get back with you. Thank you.
– Jason Hunter
9 hours ago
I should've mentioned my system boots fine when not utilizing the live USB. I only get the error when I try and boot off the live USB. Is your answer still applicable to my circumstance? If yes, I will try that tonight and get back with you. Thank you.
– Jason Hunter
9 hours ago
I should've mentioned my system boots fine when not utilizing the live USB. I only get the error when I try and boot off the live USB. Is your answer still applicable to my circumstance? If yes, I will try that tonight and get back with you. Thank you.
– Jason Hunter
9 hours ago
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117391%2flive-usb-error-you-need-to-load-the-kernel-first%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1. In what computer are there problems? Please specify brand name and model; 2. Please tell me which settings you used, when you created the persistent live drive. If you cannot remember, and have another USB pendrive or a memory card (and a USB card adapter), please create a new persistent live drive and use the default settings (when asked by mkusb); 3. Please check in the grub menu environment, as suggested in the answer by @Jos,
grub> ls... and report the result by editing your original question.– sudodus
8 hours ago
4. In what operating system (distro and version, for example Ubuntu 18.04.1 LTS) are you running mkusb? I'm asking because I need these data in order to find the cause of this problem (if possible reproduce the problem); 5. If you have a USB pendrive or memory card with at least 16 GB, you can try a new compressed image file. Use mkusb to clone from that file into a pendrive or card, and check if that system works in the computer with problems.
– sudodus
8 hours ago
6. Are there more than one USB pendrives with persistent live systems connected to the computer, when you boot? In that case, there may be confusion with the drives and partitions.
– sudodus
7 hours ago
1
@sudodus updated my post to answer those questions. This is the only live USB drive attached to the system. Although there are other SD cards attached to the system I haven't tried removing. I'll try that! And report back tomorrow.
– Jason Hunter
7 hours ago
Thanks for the details about tasks/questions #1,2,4 :-) It should work in that computer. For example I have tested in a NUC computer with an M2 drive. I use mkusb a lot in 18.04.1 LTS. -- What about the other tasks/questions (#3,5,6)? 7. And a new task about the file
mountpoint/boot/grub/grub.cfgin partition #3 of the persistent live drive: Please mount the partition and copy/paste thatgrub.cfgfile to your original question and indent each line 4 spaces to render it as 'code'.– sudodus
5 hours ago