Bug 2035278

Summary: [abrt] blivet-gui-runtime: _add_parent_devices(): blivetgui.py:243:_reraise_exception:blivet.errors.DeviceTreeError: Failed to init blivet:
Product: [Fedora] Fedora Reporter: Jan Vlug <jan.public>
Component: blivet-guiAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: mkolman, vtrefny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/da20da04df926971fab49c8fb849c751c39b4423
Whiteboard: abrt_hash:aca8f1ff1467f0d3e1cdd70e9de9a95c42ccf297;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-04 15:23:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: blivet-gui-utils.log
none
File: blivet.log
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: program.log
none
Log file of journal lines containing sde none

Description Jan Vlug 2021-12-23 12:59:01 UTC 
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
Comment 1 Jan Vlug 2021-12-23 12:59:04 UTC 
Created attachment 1847568 [details]
File: backtrace
Comment 2 Jan Vlug 2021-12-23 12:59:04 UTC 
Created attachment 1847569 [details]
File: blivet-gui-utils.log
Comment 3 Jan Vlug 2021-12-23 12:59:05 UTC 
Created attachment 1847570 [details]
File: blivet.log
Comment 4 Jan Vlug 2021-12-23 12:59:07 UTC 
Created attachment 1847571 [details]
File: cpuinfo
Comment 5 Jan Vlug 2021-12-23 12:59:08 UTC 
Created attachment 1847572 [details]
File: environ
Comment 6 Jan Vlug 2021-12-23 12:59:09 UTC 
Created attachment 1847573 [details]
File: mountinfo
Comment 7 Jan Vlug 2021-12-23 12:59:10 UTC 
Created attachment 1847574 [details]
File: namespaces
Comment 8 Jan Vlug 2021-12-23 12:59:11 UTC 
Created attachment 1847575 [details]
File: open_fds
Comment 9 Jan Vlug 2021-12-23 12:59:12 UTC 
Created attachment 1847576 [details]
File: program.log
Comment 10 Vojtech Trefny 2021-12-27 14:08:16 UTC 
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.
Comment 11 Jan Vlug 2021-12-30 10:51:07 UTC 
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
Comment 12 Jan Vlug 2021-12-30 10:53:25 UTC 
Created attachment 1848316 [details]
Log file of journal lines containing sde

The output of:
# journalctl -b | grep sde
Comment 13 Vojtech Trefny 2021-12-31 14:41:23 UTC 
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.
Comment 14 Jan Vlug 2022-01-02 14:57:21 UTC 
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.
Comment 15 Vojtech Trefny 2022-01-04 15:23:12 UTC 
> 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.