This bug was fixed in the package partman-base - 192ubuntu1.2
---
partman-base (192ubuntu1.2) bionic; urgency=medium
* Move superblock wiping code from command_new_label to command_commit, as
the disk is not supposed to be written to until the latter is called.
partman-base
This bug was fixed in the package partman-base - 206ubuntu1.2
---
partman-base (206ubuntu1.2) disco; urgency=medium
* Move superblock wiping code from command_new_label to command_commit, as
the disk is not supposed to be written to until the latter is called.
partman-base
I've now done the testing asked for in comment #10, verifying that
additional disks are not touched by installing to one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828558
Title:
installing
I have verified the fix for bionic and disco by doing netinstalls with
apt-setup/proposed=true on the kernel command line with disk images that
had had a raid6 with 0.90 metadata created on them and watching the
output of wipefs $image outside of the VM. Immediatly before selecting
the "write
Hello lvm, or anyone else affected,
Accepted partman-base into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/partman-
base/206ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: partman-base (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828558
Title:
installing ubuntu on a former md raid volume makes
** Changed in: partman-base (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828558
Title:
installing ubuntu on a former md raid volume makes
Turns out my fix is wrong: it is clearing the superblocks in NEW_LABEL,
but really the disk should not be touched until COMMIT.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco
** Tags added: verification-failed verification-failed-bionic
Risky, but seems okay. Would like to see testing of some other, more
normal scenarios as part of verification too: installing on a regular
disk, possibly having like two different disks and installing on one
(making sure no data loss happened on the other?). At least for bionic.
** Description
Also just the usual thing of fixing a bug in all releases newer than the
one we really care about (which is bionic in this case)
** Changed in: partman-base (Ubuntu Bionic)
Status: New => In Progress
** Changed in: partman-base (Ubuntu Disco)
Status: New => In Progress
** Changed
*netboot
On Fri, 2 Aug 2019, 08:35 Dimitri John Ledkov, wrote:
> But netbook installs fetch partman-base udeb from the archive over the
> network from -updates on the fly.
>
> On Fri, 2 Aug 2019, 03:35 Timo Aaltonen, wrote:
>
>> I don't think disco will have a new image built anymore, so an
But netbook installs fetch partman-base udeb from the archive over the
network from -updates on the fly.
On Fri, 2 Aug 2019, 03:35 Timo Aaltonen, wrote:
> I don't think disco will have a new image built anymore, so an sru there
> seems a bit pointless?
>
> --
> You received this bug
I don't think disco will have a new image built anymore, so an sru there
seems a bit pointless?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828558
Title:
installing ubuntu on a former md raid
** Description changed:
- 18.04 is installed using GUI installer in 'Guided - use entire volume'
- mode on a disk which was previously used as md raid 6 volume. Installer
- repartitions the disk and installs the system, system reboots any number
- of times without issues. Then packages are
This bug was fixed in the package partman-base - 206ubuntu4
---
partman-base (206ubuntu4) eoan; urgency=medium
* parted_server.c: Wipe all known superblocks from device in
command_new_label. (LP: #1828558)
-- Michael Hudson-Doyle Fri, 02 Aug 2019
12:31:05 +1200
** Changed
** Also affects: partman-base (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: partman-base (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
parted upstream NACKed fixing it there, so here's an attempt to do it in
partman-base instead:
https://code.launchpad.net/~mwhudson/ubuntu/+source/partman-base/+git
/partman-base/+ref/wipey -- currently testing this.
** Changed in: partman-base (Ubuntu)
Assignee: (unassigned) => Michael
** Package changed: parted (Ubuntu) => partman-base (Ubuntu)
** Changed in: partman-base (Ubuntu)
Assignee: Michael Hudson-Doyle (mwhudson) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: ubiquity (Ubuntu) => parted (Ubuntu)
** Changed in: parted (Ubuntu)
Status: New => Triaged
** Changed in: parted (Ubuntu)
Importance: Undecided => High
** Changed in: parted (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received
Having looked into this a bit I'm a bit surprised -- assuming the drive
was previously part of a raid array with metadata version 0.90 -- that
your system ever booted at all. Partman creates a disk label with
ped_disk_new_fresh, which arranges for ped_disk_clobber to be called on
the disk. This
** Tags added: id-5cd5b7c3c1eeca1c0e6458ce
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828558
Title:
installing ubuntu on a former md raid volume makes system unusable
To manage notifications
Zeroing the md superblock in ubiquity - if that's what you are thinking
about, will fix this issue in my particular scenario, but what if disk
was partitioned in some other way? I am afraid it is a partial
workaround, the proper albeit more compex way of handling this issue is
to make sure that
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubiquity
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828558
Title:
installing ubuntu on a former md raid volume makes system
23 matches
Mail list logo
