storage probe validation - "Couldn't find partition entry in table"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Triaged
|
High
|
Unassigned | ||
subiquity |
Triaged
|
High
|
Unassigned |
Bug Description
Several users in private bugs have run into a common problem, where curtin fails to parse the initial storage configuration with the following error:
File "/snap/
await asyncio.
File "/snap/
return fut.result()
File "/snap/
return await meth(self, **kw)
File "/snap/
self.
File "/snap/
self.reset()
File "/snap/
self.
File "/snap/
found_cfgs, found_errs = parser.parse()
File "/snap/
entry = self.asdict(data)
File "/snap/
raise RuntimeError(
RuntimeError: Couldn't find partition entry in table
The issue can be reproduced with dry-run based on the ProbeData.txt in LP: #2017524 and presumably others.
Changed in subiquity: | |
status: | New → Triaged |
Changed in curtin: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in subiquity: | |
importance: | Undecided → High |
tags: | added: foundations-todo |
summary: |
- curtin crash - "Couldn't find partition entry in table" + probe storage validation - "Couldn't find partition entry in table" |
summary: |
- probe storage validation - "Couldn't find partition entry in table" + storage probe validation - "Couldn't find partition entry in table" |
I've merged many bug reports with similar symptoms to this bug report. I'm not sure if they all have the same root cause though.
If you are one of the affected people, we'd be interested to know what software you used to create the installation media. If you're using Ventoy or another software that allows to "dynamically" boot the installer, we'd be happy to know as well please.
Thanks!
Olivier