Thanks for testing!
** Changed in: subiquity (Ubuntu)
Status: Triaged => 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/1876848
Title:
Installation of Focal on a linux raid consi
The installation now completes successfully with RAID1 on these disks
with bogus/invalid WWN.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876848
Title:
Installation of Focal on a linux raid consi
Thanks, that worked!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876848
Title:
Installation of Focal on a linux raid consistently fails
To manage notifications about this bug go to:
https://bugs
On Tue, 19 May 2020, 21:26 Stian Brattland, <1876...@bugs.launchpad.net>
wrote:
> What's the process of getting this incorporated into subiquity, and
> consequently release it as part of the 20.04 installer?
>
You should be offered an upgrade during the install, if you say yes this
bug should be
What's the process of getting this incorporated into subiquity, and
consequently release it as part of the 20.04 installer?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876848
Title:
Installation
This bug was fixed in the package curtin - 19.3-68-g6cbdc02d-0ubuntu1
---
curtin (19.3-68-g6cbdc02d-0ubuntu1) groovy; urgency=medium
* New upstream snapshot.
- Makefile: make adjustments to call lint/style tools via python module
- block-discover: ignore invalid id_serial/id
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/383648
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876848
Title:
Installation of Focal on a linux raid
This bug is fixed with commit 145e4939 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=145e4939
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/383547
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876848
Title:
Installation of Focal on a linux raid
Yes, I had two questions really: 1) where to exclude "bogus" values (I
think I agree that curtin's block-discover stuff is right) and 2) how to
define "bogus" exactly. We could just exclude the values from this
report and wait for the next bug report I guess...
--
You received this bug notificati
@Stian
No worries; it's nothing you configured/changed as far as I can tell.
We look up device paths to disk via serial or wwn; as it turns out your
two disks have different serials, but a duplicate (and invalid WWN); so
we'll need to fix our code to ignore these invalid WWN and not include
them i
Hi all,
Thank's for following up!
The disks are very clearly labeled Corsair, so I believe they are
original disks and not OEM. I have no idea why they do not have that WWN
number set? The disks were bought as a regular consumer product.
I don't really know what that number is, or how it is read
** Changed in: subiquity (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876848
Title:
Installation of Focal on a linux raid consistently fails
To manage notif
> Or at least we should ignore duplicate WWNs from non-multipathed
drives.
I think this makes sense, I'm not sure where to jam this in though.
Probably curtin's extract_storage_config stuff? That doesn't really
conceptually look at disks as a set but I'm sure we can hack it in.
--
You received t
Is the drive actually Corsair_Force or some white-label OEM who bought
bulk Corsair_Force drives and were supposed to configure the WWNs before
shipping the drives?
I think we should reject WWNs 0x0, or like things with consecutive
numbers. Cause I remember in whoopsie database we had lots of devi
We are sorry we assumed World Wide Name to be unique World Wide =/ but
also we understand that "your drives are not unique enough" is not a
good enough vendor response in such situation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wow what a confusing error message, I'm sorry about this!
This seems to be caused by the fact that both disks in the curtin config
have the same wwn:
- {ptable: gpt, serial: Corsair_Force_GS_1320790797410026, wwn:
'0x',
path: /dev/sda, preserve: true, name: '', grub_d
17 matches
Mail list logo
