18.04 clean server installation fails on `curtin command block-meta'
I used an Ubuntu 16.04 desktop installation as a server for a while, but with the release of 18.04 I decided to do a clean install of the server edition. So this is a single-disk, single-boot system, where I want to replace 16.04 desktop with 18.04 server.
The Ubuntu 18.04 server installer however fails during the partitioning step, both with default partitioning of an entire disk and with manually picked partitions. The log shows a Python stacktrace: the util.file_size function from curtil fails on the line
with open(path, 'rb') as fp:
with error OSError: [Errno 6] No such device or address: '/dev/sda2'. This is the (still functioning) extended partition containing the current 16.04 desktop installation. I could not find relatable cases on google, SO or askubuntu, and I have no clue why the device reads as nonexistent. If I exit to shell from the installer and try to mount /dev/sda2, I get the error
mount: /bla: /dev/sda2 is not a valid block device
truncated output from fdisk -l /dev/sda:
...
Device Boot ... Type
/dev/sda1 * Linux
/dev/sda2 Extended
/dev/sda5 Linux LVM
Any idea what causes the error, and how can I circumvent the issue?
server partitioning system-installation
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
add a comment |
I used an Ubuntu 16.04 desktop installation as a server for a while, but with the release of 18.04 I decided to do a clean install of the server edition. So this is a single-disk, single-boot system, where I want to replace 16.04 desktop with 18.04 server.
The Ubuntu 18.04 server installer however fails during the partitioning step, both with default partitioning of an entire disk and with manually picked partitions. The log shows a Python stacktrace: the util.file_size function from curtil fails on the line
with open(path, 'rb') as fp:
with error OSError: [Errno 6] No such device or address: '/dev/sda2'. This is the (still functioning) extended partition containing the current 16.04 desktop installation. I could not find relatable cases on google, SO or askubuntu, and I have no clue why the device reads as nonexistent. If I exit to shell from the installer and try to mount /dev/sda2, I get the error
mount: /bla: /dev/sda2 is not a valid block device
truncated output from fdisk -l /dev/sda:
...
Device Boot ... Type
/dev/sda1 * Linux
/dev/sda2 Extended
/dev/sda5 Linux LVM
Any idea what causes the error, and how can I circumvent the issue?
server partitioning system-installation
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
add a comment |
I used an Ubuntu 16.04 desktop installation as a server for a while, but with the release of 18.04 I decided to do a clean install of the server edition. So this is a single-disk, single-boot system, where I want to replace 16.04 desktop with 18.04 server.
The Ubuntu 18.04 server installer however fails during the partitioning step, both with default partitioning of an entire disk and with manually picked partitions. The log shows a Python stacktrace: the util.file_size function from curtil fails on the line
with open(path, 'rb') as fp:
with error OSError: [Errno 6] No such device or address: '/dev/sda2'. This is the (still functioning) extended partition containing the current 16.04 desktop installation. I could not find relatable cases on google, SO or askubuntu, and I have no clue why the device reads as nonexistent. If I exit to shell from the installer and try to mount /dev/sda2, I get the error
mount: /bla: /dev/sda2 is not a valid block device
truncated output from fdisk -l /dev/sda:
...
Device Boot ... Type
/dev/sda1 * Linux
/dev/sda2 Extended
/dev/sda5 Linux LVM
Any idea what causes the error, and how can I circumvent the issue?
server partitioning system-installation
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
I used an Ubuntu 16.04 desktop installation as a server for a while, but with the release of 18.04 I decided to do a clean install of the server edition. So this is a single-disk, single-boot system, where I want to replace 16.04 desktop with 18.04 server.
The Ubuntu 18.04 server installer however fails during the partitioning step, both with default partitioning of an entire disk and with manually picked partitions. The log shows a Python stacktrace: the util.file_size function from curtil fails on the line
with open(path, 'rb') as fp:
with error OSError: [Errno 6] No such device or address: '/dev/sda2'. This is the (still functioning) extended partition containing the current 16.04 desktop installation. I could not find relatable cases on google, SO or askubuntu, and I have no clue why the device reads as nonexistent. If I exit to shell from the installer and try to mount /dev/sda2, I get the error
mount: /bla: /dev/sda2 is not a valid block device
truncated output from fdisk -l /dev/sda:
...
Device Boot ... Type
/dev/sda1 * Linux
/dev/sda2 Extended
/dev/sda5 Linux LVM
Any idea what causes the error, and how can I circumvent the issue?
server partitioning system-installation
server partitioning system-installation
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
asked May 5 '18 at 21:42
SebastiaanSebastiaan
11314
11314
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I had the same error with the installer trying to remove an LVM partition.
After the install fails, select go to command line. From there:
$ sudo fdisk -l (to see the drive name and see the partitions)
$ sudo parted
p
select /dev/sda (or whatever your drive is named)
p (too show the partitions and their numbers)
rm 1
rm 2
(etc until they are all gone)
q
$ sudo fdisk -l (verify the partitions are gone)
Reboot and install again.
edited May 12 '18 at 21:02
earthmeLon
6,3741851
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
1
It's much easier to help when you take advantage of proper formatting.
– earthmeLon
May 12 '18 at 21:01
Yep, like the removed rant-y comment said, LVM was to blame, although I do not completely understand why. I ended upfdisk-ing the partitions manually after which everything went smooth. Thanx for your help!
– Sebastiaan
May 14 '18 at 14:00
earthmeLon, thank you. This was my first post and it was done from a phone. I'll improve my future posts, hopefully.
– Michael Blasius
May 14 '18 at 14:11
add a comment |
I am not able to remove the partition either by executing rm 1 getting following error:
Partitions 1,2 on /dev/sda have been written, but we have been unable to inform the kerenel of the change, probably because it/they are in use. As a result, the old partitions will remain in use. You should reboot now before making further changes.
What should I do I am a newbie and can not comment that's why I pasted here in the answer
answered 8 mins ago
ShashankShashank
1
New contributor
Shashank 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
});
}
});
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%2f1032551%2f18-04-clean-server-installation-fails-on-curtin-command-block-meta%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same error with the installer trying to remove an LVM partition.
After the install fails, select go to command line. From there:
$ sudo fdisk -l (to see the drive name and see the partitions)
$ sudo parted
p
select /dev/sda (or whatever your drive is named)
p (too show the partitions and their numbers)
rm 1
rm 2
(etc until they are all gone)
q
$ sudo fdisk -l (verify the partitions are gone)
Reboot and install again.
edited May 12 '18 at 21:02
earthmeLon
6,3741851
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
1
It's much easier to help when you take advantage of proper formatting.
– earthmeLon
May 12 '18 at 21:01
Yep, like the removed rant-y comment said, LVM was to blame, although I do not completely understand why. I ended upfdisk-ing the partitions manually after which everything went smooth. Thanx for your help!
– Sebastiaan
May 14 '18 at 14:00
earthmeLon, thank you. This was my first post and it was done from a phone. I'll improve my future posts, hopefully.
– Michael Blasius
May 14 '18 at 14:11
add a comment |
I had the same error with the installer trying to remove an LVM partition.
After the install fails, select go to command line. From there:
$ sudo fdisk -l (to see the drive name and see the partitions)
$ sudo parted
p
select /dev/sda (or whatever your drive is named)
p (too show the partitions and their numbers)
rm 1
rm 2
(etc until they are all gone)
q
$ sudo fdisk -l (verify the partitions are gone)
Reboot and install again.
edited May 12 '18 at 21:02
earthmeLon
6,3741851
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
1
It's much easier to help when you take advantage of proper formatting.
– earthmeLon
May 12 '18 at 21:01
Yep, like the removed rant-y comment said, LVM was to blame, although I do not completely understand why. I ended upfdisk-ing the partitions manually after which everything went smooth. Thanx for your help!
– Sebastiaan
May 14 '18 at 14:00
earthmeLon, thank you. This was my first post and it was done from a phone. I'll improve my future posts, hopefully.
– Michael Blasius
May 14 '18 at 14:11
add a comment |
I had the same error with the installer trying to remove an LVM partition.
After the install fails, select go to command line. From there:
$ sudo fdisk -l (to see the drive name and see the partitions)
$ sudo parted
p
select /dev/sda (or whatever your drive is named)
p (too show the partitions and their numbers)
rm 1
rm 2
(etc until they are all gone)
q
$ sudo fdisk -l (verify the partitions are gone)
Reboot and install again.
edited May 12 '18 at 21:02
earthmeLon
6,3741851
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
I had the same error with the installer trying to remove an LVM partition.
After the install fails, select go to command line. From there:
$ sudo fdisk -l (to see the drive name and see the partitions)
$ sudo parted
p
select /dev/sda (or whatever your drive is named)
p (too show the partitions and their numbers)
rm 1
rm 2
(etc until they are all gone)
q
$ sudo fdisk -l (verify the partitions are gone)
Reboot and install again.
edited May 12 '18 at 21:02
earthmeLon
6,3741851
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
edited May 12 '18 at 21:02
earthmeLon
6,3741851
edited May 12 '18 at 21:02
earthmeLon
6,3741851
edited May 12 '18 at 21:02
earthmeLon
6,3741851
6,3741851
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
562
1
It's much easier to help when you take advantage of proper formatting.
– earthmeLon
May 12 '18 at 21:01
Yep, like the removed rant-y comment said, LVM was to blame, although I do not completely understand why. I ended upfdisk-ing the partitions manually after which everything went smooth. Thanx for your help!
– Sebastiaan
May 14 '18 at 14:00
earthmeLon, thank you. This was my first post and it was done from a phone. I'll improve my future posts, hopefully.
– Michael Blasius
May 14 '18 at 14:11
add a comment |
1
It's much easier to help when you take advantage of proper formatting.
– earthmeLon
May 12 '18 at 21:01
Yep, like the removed rant-y comment said, LVM was to blame, although I do not completely understand why. I ended upfdisk-ing the partitions manually after which everything went smooth. Thanx for your help!
– Sebastiaan
May 14 '18 at 14:00
earthmeLon, thank you. This was my first post and it was done from a phone. I'll improve my future posts, hopefully.
– Michael Blasius
May 14 '18 at 14:11
1
1
It's much easier to help when you take advantage of proper formatting.
– earthmeLon
May 12 '18 at 21:01
It's much easier to help when you take advantage of proper formatting.
– earthmeLon
May 12 '18 at 21:01
Yep, like the removed rant-y comment said, LVM was to blame, although I do not completely understand why. I ended up
fdisk-ing the partitions manually after which everything went smooth. Thanx for your help!– Sebastiaan
May 14 '18 at 14:00
Yep, like the removed rant-y comment said, LVM was to blame, although I do not completely understand why. I ended up
fdisk-ing the partitions manually after which everything went smooth. Thanx for your help!– Sebastiaan
May 14 '18 at 14:00
earthmeLon, thank you. This was my first post and it was done from a phone. I'll improve my future posts, hopefully.
– Michael Blasius
May 14 '18 at 14:11
earthmeLon, thank you. This was my first post and it was done from a phone. I'll improve my future posts, hopefully.
– Michael Blasius
May 14 '18 at 14:11
add a comment |
I am not able to remove the partition either by executing rm 1 getting following error:
Partitions 1,2 on /dev/sda have been written, but we have been unable to inform the kerenel of the change, probably because it/they are in use. As a result, the old partitions will remain in use. You should reboot now before making further changes.
What should I do I am a newbie and can not comment that's why I pasted here in the answer
answered 8 mins ago
ShashankShashank
1
New contributor
Shashank 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 |
I am not able to remove the partition either by executing rm 1 getting following error:
Partitions 1,2 on /dev/sda have been written, but we have been unable to inform the kerenel of the change, probably because it/they are in use. As a result, the old partitions will remain in use. You should reboot now before making further changes.
What should I do I am a newbie and can not comment that's why I pasted here in the answer
answered 8 mins ago
ShashankShashank
1
New contributor
Shashank 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 |
I am not able to remove the partition either by executing rm 1 getting following error:
Partitions 1,2 on /dev/sda have been written, but we have been unable to inform the kerenel of the change, probably because it/they are in use. As a result, the old partitions will remain in use. You should reboot now before making further changes.
What should I do I am a newbie and can not comment that's why I pasted here in the answer
answered 8 mins ago
ShashankShashank
1
New contributor
Shashank is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am not able to remove the partition either by executing rm 1 getting following error:
Partitions 1,2 on /dev/sda have been written, but we have been unable to inform the kerenel of the change, probably because it/they are in use. As a result, the old partitions will remain in use. You should reboot now before making further changes.
What should I do I am a newbie and can not comment that's why I pasted here in the answer
answered 8 mins ago
ShashankShashank
1
New contributor
Shashank is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 8 mins ago
ShashankShashank
1
New contributor
Shashank is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 8 mins ago
ShashankShashank
1
answered 8 mins ago
ShashankShashank
1
1
New contributor
Shashank is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Shashank is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Shashank 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 |
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%2f1032551%2f18-04-clean-server-installation-fails-on-curtin-command-block-meta%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
