Ubuntu Linaro Evaluation Build

Installer crashes request to /storage/v2?wait=true crashed with KeyError (ptable unsupported)

Bug #2067754 reported by rduke15 on 2024-05-31

202

This bug affects 43 people

Affects		Status	Importance	Assigned to	Milestone
	subiquity	Incomplete	Undecided	Unassigned
	Ubuntu Linaro Evaluation Build	New	Undecided	louie tijerina

Bug Description

Installer crashes after "Install recommended proprietary software?". It always crashes, whether the checkboxes are checked or not.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.498
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Fri May 31 16:44:42 2024
DesktopInstallerRev: 171
ExecutablePath: /snap/ubuntu-desktop-bootstrap/171/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-bootstrap/171/usr/bin/python3.10
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Dell Inc. PowerEdge T330
ProcAttrCurrent: snap.hostname-desktop-bootstrap.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-bootstrap/171/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-bootstrap/171/etc/subiquity/postinst.d
ProcEnviron:
LANG=C.UTF-8
LD_LIBRARY_PATH=<set>
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1
PythonDetails: N/A
SnapChannel:

SnapRevision: 171
SnapUpdated: False
SnapVersion: 0+git.2d119e1b3
SourcePackage: subiquity
Title: request to /storage/v2?wait=true crashed with KeyError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/03/2018
dmi.bios.release: 2.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.0
dmi.board.name: 06FW8M
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 17
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd05/03/2018:br2.5:svnDellInc.:pnPowerEdgeT330:pvr:rvnDellInc.:rn06FW8M:rvrA05:cvnDellInc.:ct17:cvr:skuSKU=NotProvided;ModelName=PowerEdgeT330:
dmi.product.name: PowerEdge T330
dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge T330
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

rduke15 (rduke15) wrote on 2024-05-31:

BootstrapLog.txt Edit (13.0 KiB, text/plain; charset="utf-8")
CrashDB.txt Edit (162 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (83.8 KiB, text/plain; charset="utf-8")
DesktopInstallerLog.txt Edit (15.7 KiB, text/plain; charset="utf-8")
InstallerJournal.txt Edit (244.7 KiB, text/plain; charset="utf-8")
InstallerServerLog.txt Edit (74.5 KiB, text/plain; charset="utf-8")
InstallerServerLogInfo.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (48.9 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (369 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (454 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (14.2 KiB, text/plain; charset="utf-8")
ProbeData.txt Edit (36.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (2.0 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (205.1 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (566.2 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Zhou Boxu (a8211) wrote on 2024-06-21:

I met it the same :(

Revision history for this message

Chris Peterson (cpete) wrote on 2024-06-21:

Hi and thanks for your report. It looks like the installer crashed because your USB stick has been formatted in a way that Curtin doesn't support. Could you describe how you formatted your usb and possibly try performing it again? The output of the command `sudo parted --list` would be particularly useful.

summary:	Installer crashes request to /storage/v2?wait=true crashed with KeyError + (ptable unsupported)
tags:	added: ptable

Chris Peterson (cpete) on 2024-06-28

Changed in subiquity:
status:	New → Incomplete

Revision history for this message

milosz m. (gandeldalf) wrote on 2024-07-12:

I have the exact same issue. Anyone found a solution for it yet?

Revision history for this message

milosz m. (gandeldalf) wrote on 2024-07-12:

I would also like to add that the USB stick has been formatted correctly. I did the command that @cpete put in here. Interestingly enough one of my drives isn't being detected, probably because it was used as ntfs before. I will check if removing the drive will fix this issue.

ubuntu@ubuntu:~$ sudo parted --list
Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 250GB 250GB ext4

Error: /dev/sdb: unrecognised disk label
Model: ATA ST4000NE001-2MA1 (scsi)
Disk /dev/sdb: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags:

Model: USB DISK 2.0 (scsi)
Disk /dev/sdg: 8007MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 8007MB 8006MB primary fat32 boot, lba

Revision history for this message

milosz m. (gandeldalf) wrote on 2024-07-13:

After removing the drive it solved the issue and I haven't received the issue anymore.

For other people with the issue, you have to remove the NTFS drive from the PC or reformat the drive to solve the issue.

I hope it helped

Revision history for this message

sim (yamatogatedarksim) wrote on 2024-07-14:

I have the same problem. However, I do not have NTFS drives. My drive are both un-formatted. I have this problem with both AMD and Intel.

Revision history for this message

Dan Bungert (dbungert) wrote on 2024-07-15:

A question to the affected people by this bug report - I would appreciate information about how the affected drive is being created. We should be able to make this robust - bare minimum ignore the affected drive - but to do so it would be best if we were able to create the drive in a similar fashion for testing purposes. Thanks.

Note from the data available at this point that these "PMBR" drives appear to be GPT partitioned drives where the GPT is damaged, so only the protective MBR remains.

Revision history for this message

Tim Karlsen (tkarlsen) wrote on 2024-07-17:

Having the exact same issue. Dell Inspiron 16 plus 7630, with M.2 PCIe SSD

The booted Ubuntu from USB drive recognizes the SSD: /dev/nvme0n1
Was reading in other comments to sweep drive to get installer to work.
Did that with sgdisk --zap-all
and additional dd if=/dev/zero of=/dev/nvme0n1
this all ran through without problem.
Bug persisted with installer crashing (although SSD is recognized)

louie tijerina (ghostpy) on 2024-07-23

affects:	subiquity → ubuntu-leb
Changed in ubuntu-leb:
assignee:	nobody → louie tijerina (ghostpy)
status:	Incomplete → New

Dan Bungert (dbungert) on 2024-08-09

Changed in subiquity:
status:	New → Incomplete

Revision history for this message

Tom Meerholz (tmeerholz) wrote on 2024-08-10:

#10

On my initial install, install was proceeding well until I lost power. Upon subsequent attempts the install failed at this point. I recreated the usb but problem continued. Then looked at the HDD. GParted reported the error "Libparted Rrror--Invalid argument during seek for read on /dev/sdc. The backup GPT is corrupt, but the primary appears OK, so that will be used." I recreated the partition table on the HDD and that solved my problem. The install now is proceeding as it should.

Revision history for this message

Andy Jones (the-rivit) wrote on 2024-08-11:

#11

OK, so as a test, I removed my Highpoint Rocketraid 2720A raid card (attached to 40TB of active storage) from my system.

Lo and behold, the installer did not fault and I was able to install Ubuntu.

The take away from this.

How sloppy, presumptuous and ignorant of the person / team who has / have written the 24.04 installer to assume that every single disk in a system will be immediately readable and usable when the installer runs.
.... VERY SHODDY!!!

This in itself is an extreme red flag and disappointment to someone who is just starting to learn Linux and had decided to investigate Ubuntu for potentially replacing their Win 11 plex server..

At least when I did a test install of the latest iteration of Mint, it's installer behaved perfectly, accepting that the raid disks although visible to the system, where not readable etc. until a driver would be installed later on.

Something to think about Ubuntu dev team!!!!!!

Revision history for this message

Jwtiyar Nariman (jwtiyar) wrote on 2024-10-27:

#12

My problem was Sddc card was inserted i didn't know, removed it and everything goes well.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.