Thanks for the update! I wasn't expecting the UEFI install to work but
happy to hear it does!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
Mainboard firmware update worked. Installable and bootable in both
legacy and uefi mode.
** Changed in: subiquity
Status: New => Fix Released
** Changed in: subiquity (Ubuntu)
Status: New => Fix Released
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You
Sorry for the delay. Installation continues and finishes in UEFI mode.
Now we ran into boot issues (SSD is the same model, but mainboard
isn't), but those are unlikely Software related (seems like an AHCI
Driver bug in the mainboard firmware) - so we can't confirm that the
installed OS boots.
--
So this issue can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
To manage notifications about this bug go to:
We'll try next week. Then i've physical access
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
To manage notifications about this bug go to:
The latest daily (i.e. 20200414) has the patches discussed here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
To manage notifications about
They're not on an ISO yet but if you can try with the edge snap, you'll
get a subiquity with these patches. https://discourse.ubuntu.com/t/how-
to-test-the-latest-version-of-subiquity/12428 has a few ways you can do
this.
I would not expect UEFI installs to work yet but hopefully the BIOS
install
As soon those patches are in the daily live iso - we would like to test
again. Please send us a notice, so we can report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block
This bug is fixed with commit 0832e4ef to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=0832e4ef
** Changed in: curtin
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/381963
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError
The crash file from the failed UEFI install is in comment #18, and
contains the probe data.
** Changed in: curtin
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can we get the /var/log/installer/block/probe-data*.json files?
Also, if you have the var-crash from your failed UEFI install, that would help
me fix the UEFI install.
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: curtin
Status: New => Incomplete
After you mentioned UEFI, we are now able to install in bios legacy mode.
ヽ(•‿•)ノ
We still have a second system, that can be used to test the latest ISO on UEFI
mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It never ends, the failure is now
+ grub-install --target=x86_64-efi --efi-directory=/boot/efi
--bootloader-id=ubuntu --recheck
Installing for x86_64-efi platform.
grub-install: warning: efivarfs_get_variable:
Well that worked for the block probing step :)
The device is now selectable and the installation process begins. :+1:
But the patched curtin (from your paste) seems to trip on a next error
during install:
Tags: focal uec-images
Title: install failed crashed with CalledProcessError
Traceback:
This tiny patch to curtin https://paste.ubuntu.com/p/fbJVRmdBjz/ gets
past this crash. If your expeditious colleague would like to try
patching the subiquity snap with that and trying again, I'd be
interested to hear if that works!
--
You received this bug notification because you are a member
So the udev data for /dev/nvme0n1 is:
/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1
N: nvme0n1
L: 0
S: disk/by-id/nvme-SAMSUNG_MZPLL3T2HAJQ-5_S4CCNE0M300015
S: disk/by-id/nvme-eui.344343304d300015002538450004
E: DEVPATH=/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1
E:
The crash is now
Traceback (most recent call last):
File
"/snap/subiquity/1999/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 144, in _probe
self._probe_once_task.task, 15.0)
File "/snap/subiquity/1999/usr/lib/python3.6/asyncio/tasks.py", line 358, in
My colleague manually patched probert in the subiquity snap (fictional
snap revision 1999 based on 1626 and your PR above) and we get a
different stacktrace now.
** Attachment added: "probert patch applied"
I created https://github.com/CanonicalLtd/probert/pull/86 which is
hopefully a workaround/fix for this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError
Sorry for the slow response and thanks for the offer but I think we have
enough information to go on to debug this. Other things just keep on
coming up! Hopefully I can look at this tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Even if my last comment was sent on April 1st - it was no joke :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
To manage notifications about
Hi Michael,
would it help to grant you SSH access into the installation session
(daily-live current iso) on that machine?
Regards
Malte
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
23 matches
Mail list logo