Sorry, there was a problem examining the storage devices of this system.

Bug #1997473 reported by geole0
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned

Bug Description

Hello.
A few weeks ago, I had downloaded the server version from this site https://ubuntu.com/download/server
I had begun to understand the presentation grids of the discs but I had not been able to validate the reformatting of the discs. It's actually my first use.

This week, I wanted to continue.
But the welcome grid presenting the discs is not displayed.
Instead it the error message shown above "Sorry, there was a problem examining the storage devices of this system."

So I decided to download the other versions 20.04 and 22.10 in addition to version 22.04
The problem is the same.

I validated several times the action to inform you of this bad execution.

I tried with another computer. The problem is the same. In this computer, I could not inform you because the connection is only wifi and the link did not work.

I tried with a third computer. The problem is the same. In this computer, I was able to inform you.
I went a little further by using the "online help" function (at the top and right in the screen)

I saw that there were several incidents titled BLOCK DEVICE PROBE FAILURE

by detailing more, there are a lot of lines and a small sequence with the trace of the CRASH.
I hope it is transmitted automatically.

However, I did not understand what is wrong with the format of the partitions which cause the incident and I do not know how to identify them in this trace.
There are several of them.

I noticed similar messages in bug 1893818 and 1861655 but the environment seems different to me.

I hope you can easily identify the problem, otherwise I will try to "capture more" crash lines with their numbers and that soon the problem will have a solution.

Thanks for reading me.

Revision history for this message
geole0 (geole0) wrote :

Manually reporting the traces

ERROR root:37 finish: subiquity/filesystem/_probe/probe_once: FAIL: cancelled
ERROR block-discover:596 block probing failed restricted=False
Traceback (most recent call last):
    File "/snap/subiquity/4003/lib/python3.8/site-packages/subiquity/server/controllers/filesystem.py", line 590, in _probe
         await asyncio.wait_for (self.probe_once_task.task, timeout)
    File "/snap/subiquity/4003/usr/lib/pyrthon3.8/asyncio/task.py", line 501, in wait_for
         raise exceptions.TimeoutError()

It is the same error for all the disks

Revision history for this message
geole0 (geole0) wrote :

I looked at the crashes of versions 18.04 and 20.04. The line numbers are not the same and the causes do not seem identical to me. I don't want to waste time on these old versions.

When I use the standard 22.04 version, disk detection is good but I can't get the sequence to create raids to work. This is why I chose to update the software.

Revision history for this message
Dan Bungert (dbungert) wrote :

Thanks for the thoughtful report, @geole0.
I think we need to see the full logs to make some progress on this.

If the network isn't quite working probably the easiest thing to do is to just tar up the contents of /var/log and attach here. There are a few log files and I'm not sure at the moment which one is the interesting one.

Changed in subiquity:
status: New → Incomplete
Revision history for this message
geole0 (geole0) wrote :

Hello
Thank you for your proposal
This is the wifi only computer crash in version 22.10

Tomorrow, I will try the other two computers if you confirm that the content suits you.

But

https://bugs.launchpad.net/launchpad/+bug/1998627

Revision history for this message
geole0 (geole0) wrote :

Hello
When i attach the file

Oops!

Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

If you can't login, join us on #launchpad IRC channel at irc.libera.chat, e-mail us or visit our feedback page.

If you report this as a bug, please include the error ID below, preferably by copying and pasting it rather than by taking a screenshot.

(Error ID: OOPS-91bbd511380e684bff770fd9bceb725b)

https://bugs.launchpad.net/launchpad/+bug/1998627

Revision history for this message
geole0 (geole0) wrote :

Hello
It is when i want to attach this file
9,7M -rw-r--r-- 1 root root 9,7M déc. 2 18:15 BUG.tar

Hello
It is when i attach this file
9,7M -rw-r--r-- 1 root root 9,7M déc. 2 18:15 BUG.tar

Oops!

Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

If you can't login, join us on #launchpad IRC channel at irc.libera.chat, e-mail us or visit our feedback page.

If you report this as a bug, please include the error ID below, preferably by copying and pasting it rather than by taking a screenshot.

(Error ID: OOPS-0feee0444980b44d4f7b10a27dea2f70)

https://bugs.launchpad.net/subiquity/+bug/1997473/+addcomment
Oops!

Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

If you can't login, join us on #launchpad IRC channel at irc.libera.chat, e-mail us or visit our feedback page.

If you report this as a bug, please include the error ID below, preferably by copying and pasting it rather than by taking a screenshot.

(Error ID: OOPS-0feee0444980b44d4f7b10a27dea2f70)

https://bugs.launchpad.net/subiquity/+bug/1997473/+addcomment

Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
  • wtmp Edit (2.2 KiB, application/octet-stream)
Revision history for this message
geole0 (geole0) wrote :
  • apt Edit (23.0 KiB, application/octet-stream)
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :

installer-10

Revision history for this message
geole0 (geole0) wrote :

installe-11

Revision history for this message
geole0 (geole0) wrote :

installer-12

Revision history for this message
geole0 (geole0) wrote :

But for system-journal
Oops!

Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

If you report this as a bug, please include the error ID below, preferably by copying and pasting it rather than by taking a screenshot.

(Error ID: OOPS-fbf6e6f963922be0d480a149b15cbf31)

Revision history for this message
geole0 (geole0) wrote :
Revision history for this message
geole0 (geole0) wrote :

Hello
Tar.file of installer directory of a second computer

Revision history for this message
geole0 (geole0) wrote :

Hello
Tar.file of installer directory of the third computer.

Revision history for this message
geole0 (geole0) wrote :

Hello
Tar.file of log directory of the third computer.

Dan Bungert (dbungert)
Changed in subiquity:
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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