Description of problem: Trying to inspect an sd-card that via a USB convertor was inserted in the Fedora 35 system. Version-Release number of selected component: blivet-gui-runtime-2.3.0-3.fc35 Additional info: reporter: libreport-2.15.2 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-blivet\x2dgui-37889.scope cmdline: /usr/bin/python3 /usr/bin/blivet-gui crash_function: _add_parent_devices exception_type: blivet.errors.DeviceTreeError executable: /usr/bin/blivet-gui interpreter: python3-3.10.1-1.fc35.x86_64 kernel: 5.15.10-200.fc35.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: #1 [/usr/lib/python3.10/site-packages/blivet/populator/populator.py:119] _add_parent_devices #2 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock #3 [/usr/lib/python3.10/site-packages/blivet/populator/helpers/lvm.py:60] run #4 [/usr/lib/python3.10/site-packages/blivet/populator/populator.py:270] handle_device #5 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock #6 [/usr/lib/python3.10/site-packages/blivet/populator/populator.py:464] _populate #7 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock #8 [/usr/lib/python3.10/site-packages/blivet/populator/populator.py:419] populate #9 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock #10 [/usr/lib/python3.10/site-packages/blivet/blivet.py:140] reset
Created attachment 1847568 [details] File: backtrace
Created attachment 1847569 [details] File: blivet-gui-utils.log
Created attachment 1847570 [details] File: blivet.log
Created attachment 1847571 [details] File: cpuinfo
Created attachment 1847572 [details] File: environ
Created attachment 1847573 [details] File: mountinfo
Created attachment 1847574 [details] File: namespaces
Created attachment 1847575 [details] File: open_fds
Created attachment 1847576 [details] File: program.log
We are trying to get information about /dev/sde3 from udev which fails. I assume sde is the SD card. Is it possible it got disconnected before (or during) blivet-gui start? We log lsblk output in blivet-gui-utils.log and I don't see sde there. Check dmesg and journal for some errors or disconnect messages, this really looks like a hardware/connection issue.
This crash happened today again. My system has not been rebooted in the meantime. lsblk does not show sde. I now tried to connect an external hard disk via the USB port. Because it was not mounted correctly, I opened blivet-gui, and this crash happened again. I will attach the output of: # journalctl -b | grep sde
Created attachment 1848316 [details] Log file of journal lines containing sde The output of: # journalctl -b | grep sde
There is a lot of IO errors in the log: Dec 23 13:26:43 nyx kernel: blk_update_request: I/O error, dev sde, sector 2281084 op 0x1:(WRITE) flags 0x5800 phys_seg 2 prio class 0 Dec 23 13:26:43 nyx kernel: blk_update_request: I/O error, dev sde, sector 2281324 op 0x1:(WRITE) flags 0x5800 phys_seg 2 prio class 0 And also XFS errors and failed mount Dec 23 13:26:43 nyx kernel: XFS (sde2): log recovery write I/O error at daddr 0x64c len 4096 error -5 Dec 23 13:26:43 nyx kernel: XFS (sde2): failed to locate log tail Dec 23 13:26:43 nyx gnome-shell[2924]: Unable to mount volume 1.1 GB Volume: Gio.IOErrorEnum: Error mounting /dev/sde2 at /run/media/jan/4f916657-cbf3-4b36-99c7-9659fb0bf918: can't read superblock on /dev/sde2 So I think sde is mostly likely dying. Blivet definitely shouldn't just crash in this case (we already have some issues and work in progress patches for that), but underlying issue is hardware related.
I think that the hardware problems stem from the fact that I accidentally removed the power supply from a connected external USB disk. I leave it up to Vojtech to decide if this issue can be closed, or should stay open because Blivet crashes on it.
> I think that the hardware problems stem from the fact that I accidentally removed the power supply from a connected external USB disk. Yes, that sounds like it cause these issues. > I leave it up to Vojtech to decide if this issue can be closed, or should stay open because Blivet crashes on it. We have an upstream issue for blivet, so I'll close this one. Thanks for the report and for the help with the investigation.