Boot Ubuntu 18.04 from SSD Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)Cannot boot Ubuntu from SSD in ASUS K55VDIssues with dual boot (Ubuntu + Windows), UEFI and SSDUnexpected boot sequence with two cloned hard drivesInstalling Ubuntu to /sdb internal M.2 SSD - Bootloader QuestionUbuntu doesn't boot from second hard disk installed on LaptopCan't boot Ubuntu in dual boot Windows 10/Ubuntu 16.04Booting on secondary drive rather than primary driveHow to boot to new, cloned SSD and not old, source HDDGRUB loads Ubuntu installation from wrong SSDcloned SSD to NVME but system boots from SSD everytime
Why doesn't SQL Optimizer use my constraint?
How would a mousetrap for use in space work?
How do I use the new nonlinear finite element in Mathematica 12 for this equation?
Are all finite dimensional hilbert spaces isomorphic to spaces with Euclidean norms?
Can anything be seen from the center of the Boötes void? How dark would it be?
Multiple OR (||) Conditions in If Statement
Hangman Game with C++
Why do we bend a book to keep it straight?
How does light 'choose' between wave and particle behaviour?
Is there hard evidence that the grant peer review system performs significantly better than random?
Did Deadpool rescue all of the X-Force?
How do I make this wiring inside cabinet safer?
Is CEO the "profession" with the most psychopaths?
Why aren't air breathing engines used as small first stages?
How fail-safe is nr as stop bytes?
Do I really need to have a message in a novel to appeal to readers?
How does the math work when buying airline miles?
Using et al. for a last / senior author rather than for a first author
Does lack of seasonality imply random time series?
Do Fourier frequencies actually exist in real life in form of "instantaneous frequency"?
Dating a Former Employee
How to compare two different files line by line in unix?
How do I find out the mythology and history of my Fortress?
Is there a kind of relay only consumes power when switching?
Boot Ubuntu 18.04 from SSD
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)Cannot boot Ubuntu from SSD in ASUS K55VDIssues with dual boot (Ubuntu + Windows), UEFI and SSDUnexpected boot sequence with two cloned hard drivesInstalling Ubuntu to /sdb internal M.2 SSD - Bootloader QuestionUbuntu doesn't boot from second hard disk installed on LaptopCan't boot Ubuntu in dual boot Windows 10/Ubuntu 16.04Booting on secondary drive rather than primary driveHow to boot to new, cloned SSD and not old, source HDDGRUB loads Ubuntu installation from wrong SSDcloned SSD to NVME but system boots from SSD everytime
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Good day,
Using Ubuntu 18.04 on Dell Optiplex 1710 with 500Gb HD and 250 Gb SSD.
I cloned my original installed Ubuntu HD (now : sdb) to an SSD (now : sda).
When the SSD is the only option (HD disconnected) it correctly boots from the SSD.
When the original HD is also connected it boots from the original HD.
I changed with grub-optimizer the boot sequence to boot from sda. wrote it to MBR on hda and hdb.
When booting with both drives, it boots from sdb = HD.
I tried to many options / changed a lot but i can not get a boot from the SSD.
Boot options when starting shows option to boot from hda.
Would appriciate help , any tips ?
Thank you.
boot
asked Apr 13 at 13:45
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Good day,
Using Ubuntu 18.04 on Dell Optiplex 1710 with 500Gb HD and 250 Gb SSD.
I cloned my original installed Ubuntu HD (now : sdb) to an SSD (now : sda).
When the SSD is the only option (HD disconnected) it correctly boots from the SSD.
When the original HD is also connected it boots from the original HD.
I changed with grub-optimizer the boot sequence to boot from sda. wrote it to MBR on hda and hdb.
When booting with both drives, it boots from sdb = HD.
I tried to many options / changed a lot but i can not get a boot from the SSD.
Boot options when starting shows option to boot from hda.
Would appriciate help , any tips ?
Thank you.
boot
asked Apr 13 at 13:45
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
I suggest you read en.wikipedia.org/wiki/Power-on_self-test , en.wikipedia.org/wiki/BIOS , en.wikipedia.org/wiki/Master_boot_record , en.wikipedia.org/wiki/GUID_Partition_Table , en.wikipedia.org/wiki/UEFI . One will have the Answer. Read the others to understand that one. Your BIOS looks at the disk controllers and the disk drives, one at a time, starting at 0, and checks each partition on each disk for the first one with the "BOOT" flag, and boots from that one.
– waltinator
Apr 13 at 14:00
1
You cannot keep a cloned drive plugged in when you reboot. You have duplicate UUIDs which are not allowed and system may boot one or the other depending on which partition is seen first. Then you get installs out of sync and may have bigger issues. You can change UUIDs or every partition and fstab entries and maybe some other places if you want to keep it bootable. Generally clone is not the best backup procedure. exclude snaps list of UUIDslsblk -af |grep -sv loop
– oldfred
Apr 13 at 14:48
thank you for your answers. UUIDS where different. Also i used Gparted to set the SSD to " Boot" . I noticed the superblock where damaged. Going for a new install of the SSD.
– Rnee
Apr 13 at 16:13
add a comment |
Good day,
Using Ubuntu 18.04 on Dell Optiplex 1710 with 500Gb HD and 250 Gb SSD.
I cloned my original installed Ubuntu HD (now : sdb) to an SSD (now : sda).
When the SSD is the only option (HD disconnected) it correctly boots from the SSD.
When the original HD is also connected it boots from the original HD.
I changed with grub-optimizer the boot sequence to boot from sda. wrote it to MBR on hda and hdb.
When booting with both drives, it boots from sdb = HD.
I tried to many options / changed a lot but i can not get a boot from the SSD.
Boot options when starting shows option to boot from hda.
Would appriciate help , any tips ?
Thank you.
boot
asked Apr 13 at 13:45
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Good day,
Using Ubuntu 18.04 on Dell Optiplex 1710 with 500Gb HD and 250 Gb SSD.
I cloned my original installed Ubuntu HD (now : sdb) to an SSD (now : sda).
When the SSD is the only option (HD disconnected) it correctly boots from the SSD.
When the original HD is also connected it boots from the original HD.
I changed with grub-optimizer the boot sequence to boot from sda. wrote it to MBR on hda and hdb.
When booting with both drives, it boots from sdb = HD.
I tried to many options / changed a lot but i can not get a boot from the SSD.
Boot options when starting shows option to boot from hda.
Would appriciate help , any tips ?
Thank you.
boot
boot
asked Apr 13 at 13:45
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 13 at 13:45
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 13 at 13:45
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 13 at 13:45
RneeRnee
11
asked Apr 13 at 13:45
RneeRnee
11
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
I suggest you read en.wikipedia.org/wiki/Power-on_self-test , en.wikipedia.org/wiki/BIOS , en.wikipedia.org/wiki/Master_boot_record , en.wikipedia.org/wiki/GUID_Partition_Table , en.wikipedia.org/wiki/UEFI . One will have the Answer. Read the others to understand that one. Your BIOS looks at the disk controllers and the disk drives, one at a time, starting at 0, and checks each partition on each disk for the first one with the "BOOT" flag, and boots from that one.
– waltinator
Apr 13 at 14:00
1
You cannot keep a cloned drive plugged in when you reboot. You have duplicate UUIDs which are not allowed and system may boot one or the other depending on which partition is seen first. Then you get installs out of sync and may have bigger issues. You can change UUIDs or every partition and fstab entries and maybe some other places if you want to keep it bootable. Generally clone is not the best backup procedure. exclude snaps list of UUIDslsblk -af |grep -sv loop
– oldfred
Apr 13 at 14:48
thank you for your answers. UUIDS where different. Also i used Gparted to set the SSD to " Boot" . I noticed the superblock where damaged. Going for a new install of the SSD.
– Rnee
Apr 13 at 16:13
add a comment |
2
I suggest you read en.wikipedia.org/wiki/Power-on_self-test , en.wikipedia.org/wiki/BIOS , en.wikipedia.org/wiki/Master_boot_record , en.wikipedia.org/wiki/GUID_Partition_Table , en.wikipedia.org/wiki/UEFI . One will have the Answer. Read the others to understand that one. Your BIOS looks at the disk controllers and the disk drives, one at a time, starting at 0, and checks each partition on each disk for the first one with the "BOOT" flag, and boots from that one.
– waltinator
Apr 13 at 14:00
1
You cannot keep a cloned drive plugged in when you reboot. You have duplicate UUIDs which are not allowed and system may boot one or the other depending on which partition is seen first. Then you get installs out of sync and may have bigger issues. You can change UUIDs or every partition and fstab entries and maybe some other places if you want to keep it bootable. Generally clone is not the best backup procedure. exclude snaps list of UUIDslsblk -af |grep -sv loop
– oldfred
Apr 13 at 14:48
thank you for your answers. UUIDS where different. Also i used Gparted to set the SSD to " Boot" . I noticed the superblock where damaged. Going for a new install of the SSD.
– Rnee
Apr 13 at 16:13
2
2
I suggest you read en.wikipedia.org/wiki/Power-on_self-test , en.wikipedia.org/wiki/BIOS , en.wikipedia.org/wiki/Master_boot_record , en.wikipedia.org/wiki/GUID_Partition_Table , en.wikipedia.org/wiki/UEFI . One will have the Answer. Read the others to understand that one. Your BIOS looks at the disk controllers and the disk drives, one at a time, starting at 0, and checks each partition on each disk for the first one with the "BOOT" flag, and boots from that one.
– waltinator
Apr 13 at 14:00
I suggest you read en.wikipedia.org/wiki/Power-on_self-test , en.wikipedia.org/wiki/BIOS , en.wikipedia.org/wiki/Master_boot_record , en.wikipedia.org/wiki/GUID_Partition_Table , en.wikipedia.org/wiki/UEFI . One will have the Answer. Read the others to understand that one. Your BIOS looks at the disk controllers and the disk drives, one at a time, starting at 0, and checks each partition on each disk for the first one with the "BOOT" flag, and boots from that one.
– waltinator
Apr 13 at 14:00
1
1
You cannot keep a cloned drive plugged in when you reboot. You have duplicate UUIDs which are not allowed and system may boot one or the other depending on which partition is seen first. Then you get installs out of sync and may have bigger issues. You can change UUIDs or every partition and fstab entries and maybe some other places if you want to keep it bootable. Generally clone is not the best backup procedure. exclude snaps list of UUIDs
lsblk -af |grep -sv loop– oldfred
Apr 13 at 14:48
You cannot keep a cloned drive plugged in when you reboot. You have duplicate UUIDs which are not allowed and system may boot one or the other depending on which partition is seen first. Then you get installs out of sync and may have bigger issues. You can change UUIDs or every partition and fstab entries and maybe some other places if you want to keep it bootable. Generally clone is not the best backup procedure. exclude snaps list of UUIDs
lsblk -af |grep -sv loop– oldfred
Apr 13 at 14:48
thank you for your answers. UUIDS where different. Also i used Gparted to set the SSD to " Boot" . I noticed the superblock where damaged. Going for a new install of the SSD.
– Rnee
Apr 13 at 16:13
thank you for your answers. UUIDS where different. Also i used Gparted to set the SSD to " Boot" . I noticed the superblock where damaged. Going for a new install of the SSD.
– Rnee
Apr 13 at 16:13
add a comment |
1 Answer
1
active
oldest
votes
My problem was that the "Disk Identifier" from fdisk -l were different.
That is not the UUID !
List the UUID with lsbik and use that identifier.
I changed the entry in /etc/fstab and the Grub entry to the correct disk UUID and now it works.
Thanks for the hints.
answered Apr 13 at 18:09
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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
);
);
Rnee is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1133537%2fboot-ubuntu-18-04-from-ssd%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
My problem was that the "Disk Identifier" from fdisk -l were different.
That is not the UUID !
List the UUID with lsbik and use that identifier.
I changed the entry in /etc/fstab and the Grub entry to the correct disk UUID and now it works.
Thanks for the hints.
answered Apr 13 at 18:09
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
My problem was that the "Disk Identifier" from fdisk -l were different.
That is not the UUID !
List the UUID with lsbik and use that identifier.
I changed the entry in /etc/fstab and the Grub entry to the correct disk UUID and now it works.
Thanks for the hints.
answered Apr 13 at 18:09
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
My problem was that the "Disk Identifier" from fdisk -l were different.
That is not the UUID !
List the UUID with lsbik and use that identifier.
I changed the entry in /etc/fstab and the Grub entry to the correct disk UUID and now it works.
Thanks for the hints.
answered Apr 13 at 18:09
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
My problem was that the "Disk Identifier" from fdisk -l were different.
That is not the UUID !
List the UUID with lsbik and use that identifier.
I changed the entry in /etc/fstab and the Grub entry to the correct disk UUID and now it works.
Thanks for the hints.
answered Apr 13 at 18:09
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 13 at 18:09
RneeRnee
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 13 at 18:09
RneeRnee
11
answered Apr 13 at 18:09
RneeRnee
11
11
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Rnee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Rnee is a new contributor. Be nice, and check out our Code of Conduct.
Rnee is a new contributor. Be nice, and check out our Code of Conduct.
Rnee is a new contributor. Be nice, and check out our Code of Conduct.
Rnee is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1133537%2fboot-ubuntu-18-04-from-ssd%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
2
I suggest you read en.wikipedia.org/wiki/Power-on_self-test , en.wikipedia.org/wiki/BIOS , en.wikipedia.org/wiki/Master_boot_record , en.wikipedia.org/wiki/GUID_Partition_Table , en.wikipedia.org/wiki/UEFI . One will have the Answer. Read the others to understand that one. Your BIOS looks at the disk controllers and the disk drives, one at a time, starting at 0, and checks each partition on each disk for the first one with the "BOOT" flag, and boots from that one.
– waltinator
Apr 13 at 14:00
1
You cannot keep a cloned drive plugged in when you reboot. You have duplicate UUIDs which are not allowed and system may boot one or the other depending on which partition is seen first. Then you get installs out of sync and may have bigger issues. You can change UUIDs or every partition and fstab entries and maybe some other places if you want to keep it bootable. Generally clone is not the best backup procedure. exclude snaps list of UUIDs
lsblk -af |grep -sv loop– oldfred
Apr 13 at 14:48
thank you for your answers. UUIDS where different. Also i used Gparted to set the SSD to " Boot" . I noticed the superblock where damaged. Going for a new install of the SSD.
– Rnee
Apr 13 at 16:13