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 |
1 Answer
1
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,4241851
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 |
protected by Community♦ Feb 16 at 11:54
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1 Answer
1
active
oldest
votes
1 Answer
1
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,4241851
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,4241851
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,4241851
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,4241851
answered May 12 '18 at 16:32
Michael BlasiusMichael Blasius
562
edited May 12 '18 at 21:02
earthmeLon
6,4241851
edited May 12 '18 at 21:02
earthmeLon
6,4241851
edited May 12 '18 at 21:02
earthmeLon
6,4241851
6,4241851
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 |
protected by Community♦ Feb 16 at 11:54
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
