Reinstalling Ubuntu made it unbootable The 2019 Stack Overflow Developer Survey Results Are...
Can an undergraduate be advised by a professor who is very far away?
Output the Arecibo Message
What is the most efficient way to store a numeric range?
What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?
Getting crown tickets for Statue of Liberty
Likelihood that a superbug or lethal virus could come from a landfill
Pokemon Turn Based battle (Python)
A female thief is not sold to make restitution -- so what happens instead?
How to notate time signature switching consistently every measure
Does HR tell a hiring manager about salary negotiations?
Will it cause any balance problems to have PCs level up and gain the benefits of a long rest mid-fight?
Did any laptop computers have a built-in 5 1/4 inch floppy drive?
Match Roman Numerals
How to display lines in a file like ls displays files in a directory?
How to type this arrow in math mode?
How to translate "being like"?
How to obtain a position of last non-zero element
Why are there uneven bright areas in this photo of black hole?
Why not take a picture of a closer black hole?
What does Linus Torvalds mean when he says that Git "never ever" tracks a file?
Deal with toxic manager when you can't quit
Is Cinnamon a desktop environment or a window manager? (Or both?)
What is this business jet?
Ubuntu Server install with full GUI
Reinstalling Ubuntu made it unbootable
The 2019 Stack Overflow Developer Survey Results Are InHow to create EFI partition and install grub2 on second diskFile system is not clean (The partition is misaligned by 1024 bytes)Dual Boot - Windows does not showHow to configure existing raid after upgrading to 14.04 from 11Intel RAID5 array Shows < 50% spaceI tried to install Ubuntu following all the instructions, but still the installation says “you need at least 8.6gb…”Ubuntu windows 10 Dual boot problemunable to boot to windows 10 after installing kubuntu 18.04 on second hdd using lvmUbuntu on Second Drive Windows 10Extend filesystem after hdd-cloning 32GB to 500GBUnable to see Windows partition in File Manager Ubuntu 16.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Yesterday I decided to upgrade from Ubuntu 17.10 to 18.04 and to use a bootable USB drive to do that. The plan was to assign partitions of the 18.04 to the existing partitions of 17.10 but that's where I think I hit a snag.
First, a little bit about my setup - it was a dual-boot system spread over an SSD and an HDD. Only the documents were stored on the HDD (think downloads, pictures, basically the entire /home folder and it's Windows counterpart) - everything else was on the SSD.
Now, back to the problem - it looks to me like I created a second EFI partition by explicitly assigning the /boot location - which is how it used to be with 17.10, but it seems like it was installed in legacy mode. Here's what the fdisk used to say before the reinstall.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M Linux boot partition
Here's what it says now.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M EFI System
It looks like this might be the answer to my problem - to install the Linux EFI bootloader to the existing EFI system partition - but I wanted to double-check with the community if that's actually the issue. Thank you for any and all advice!
dual-boot partitioning 18.04 17.10
asked 5 mins ago
fandorfandor
113
New contributor
fandor 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 |
Yesterday I decided to upgrade from Ubuntu 17.10 to 18.04 and to use a bootable USB drive to do that. The plan was to assign partitions of the 18.04 to the existing partitions of 17.10 but that's where I think I hit a snag.
First, a little bit about my setup - it was a dual-boot system spread over an SSD and an HDD. Only the documents were stored on the HDD (think downloads, pictures, basically the entire /home folder and it's Windows counterpart) - everything else was on the SSD.
Now, back to the problem - it looks to me like I created a second EFI partition by explicitly assigning the /boot location - which is how it used to be with 17.10, but it seems like it was installed in legacy mode. Here's what the fdisk used to say before the reinstall.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M Linux boot partition
Here's what it says now.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M EFI System
It looks like this might be the answer to my problem - to install the Linux EFI bootloader to the existing EFI system partition - but I wanted to double-check with the community if that's actually the issue. Thank you for any and all advice!
dual-boot partitioning 18.04 17.10
asked 5 mins ago
fandorfandor
113
New contributor
fandor 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 |
Yesterday I decided to upgrade from Ubuntu 17.10 to 18.04 and to use a bootable USB drive to do that. The plan was to assign partitions of the 18.04 to the existing partitions of 17.10 but that's where I think I hit a snag.
First, a little bit about my setup - it was a dual-boot system spread over an SSD and an HDD. Only the documents were stored on the HDD (think downloads, pictures, basically the entire /home folder and it's Windows counterpart) - everything else was on the SSD.
Now, back to the problem - it looks to me like I created a second EFI partition by explicitly assigning the /boot location - which is how it used to be with 17.10, but it seems like it was installed in legacy mode. Here's what the fdisk used to say before the reinstall.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M Linux boot partition
Here's what it says now.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M EFI System
It looks like this might be the answer to my problem - to install the Linux EFI bootloader to the existing EFI system partition - but I wanted to double-check with the community if that's actually the issue. Thank you for any and all advice!
dual-boot partitioning 18.04 17.10
asked 5 mins ago
fandorfandor
113
New contributor
fandor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Yesterday I decided to upgrade from Ubuntu 17.10 to 18.04 and to use a bootable USB drive to do that. The plan was to assign partitions of the 18.04 to the existing partitions of 17.10 but that's where I think I hit a snag.
First, a little bit about my setup - it was a dual-boot system spread over an SSD and an HDD. Only the documents were stored on the HDD (think downloads, pictures, basically the entire /home folder and it's Windows counterpart) - everything else was on the SSD.
Now, back to the problem - it looks to me like I created a second EFI partition by explicitly assigning the /boot location - which is how it used to be with 17.10, but it seems like it was installed in legacy mode. Here's what the fdisk used to say before the reinstall.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M Linux boot partition
Here's what it says now.
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FCA82D3C-D3F2-41F8-A17A-16500CC996B8
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 381069758 380502463 181.4G Microsoft basic data
/dev/nvme0n1p4 381071360 382722047 1650688 806M Windows recovery environment
/dev/nvme0n1p5 382724096 498069503 115345408 55G Linux filesystem
/dev/nvme0n1p6 498069504 500117498 2047995 1000M EFI System
It looks like this might be the answer to my problem - to install the Linux EFI bootloader to the existing EFI system partition - but I wanted to double-check with the community if that's actually the issue. Thank you for any and all advice!
dual-boot partitioning 18.04 17.10
dual-boot partitioning 18.04 17.10
asked 5 mins ago
fandorfandor
113
New contributor
fandor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 mins ago
fandorfandor
113
New contributor
fandor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 mins ago
fandorfandor
113
New contributor
fandor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 mins ago
fandorfandor
113
asked 5 mins ago
fandorfandor
113
113
New contributor
fandor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
fandor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
fandor 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 |
0
active
oldest
votes
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
});
}
});
fandor 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%2f1133167%2freinstalling-ubuntu-made-it-unbootable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
fandor is a new contributor. Be nice, and check out our Code of Conduct.
fandor is a new contributor. Be nice, and check out our Code of Conduct.
fandor is a new contributor. Be nice, and check out our Code of Conduct.
fandor 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%2f1133167%2freinstalling-ubuntu-made-it-unbootable%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
