Description of problem: trying to select disk to install os to Version-Release number of selected component: anaconda-22.20.6-1 The following was filed automatically by anaconda: anaconda 22.20.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 949, in addUdevPartitionDevice raise UnusableConfigurationError(msg) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1223, in addUdevDevice device = self.addUdevPartitionDevice(info) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2177, in _populate self.addUdevDevice(dev) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2111, in populate self._populate() File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 277, in reset self.devicetree.populate(cleanupOnly=cleanupOnly) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1117, in storageInitialize storage.reset() File "/usr/lib/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 238, in run threading.Thread.run(self, *args, **kwargs) UnusableConfigurationError: failed to scan disk sdb Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: inst.repo=http://tealc.ausil.us/f21a/armhfp/os/ console=ttyS0,115200 dnf.rpm.log: Jan 01 00:04:18 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.armv7hl product: Fedora release: Cannot get release name. type: anaconda version: 22
Created attachment 1009668 [details] File: anaconda-tb
Created attachment 1009669 [details] File: anaconda.log
Created attachment 1009670 [details] File: dnf.log
Created attachment 1009671 [details] File: environ
Created attachment 1009672 [details] File: lsblk_output
Created attachment 1009673 [details] File: nmcli_dev_list
Created attachment 1009674 [details] File: os_info
Created attachment 1009675 [details] File: storage.log
Created attachment 1009676 [details] File: syslog
Created attachment 1009677 [details] File: ifcfg.log
Created attachment 1009678 [details] File: packaging.log
Created attachment 1009679 [details] File: program.log
It appears that blivet has detected a partition via udev and is addding it to the device tree. When it checks the disk, sdb, that the partition is supposed to be on, the disk does not seem to have any information about partitions at all. Another thing that is wrong with the disk is that it has negative size. 13:25:26,059 DEBUG blivet: DeviceTree.getDeviceByName returned existing -185.01 GiB disk sdb (31)
It is really unusual for a device to have a negative size and for parted device to show a negative length. Does changing the drive fix the problem? If it does, then raising the error is the correct thing to do, and the only issue is where it is proper to catch it.
/dev/sdb is a external usb drive with the factory setup in another system parted print gives. Model: WD My Passport 0820 (scsi) Disk /dev/sdd: 2000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 2000GB 2000GB primary ntfs
In that same other system can you check if blivet still fails in this way? Are you able to open a Python shell and >>> import blivet >>> b = blivet.Blivet() >>> b.reset() >>> [d for d in b.devicetree.devices if "sdb" in d.name] substituting for "sdb" in the above whatever name is appropriate? You should expect to fail w/ the same error on the b.reset() step.
There are really two issues here...blivet having problems with a very odd looking disk...and the exception that raises actually crashing anaconda. I think it's reasonable to expect it to exit more nicely on an unusable configuration, so I'll file that as a separate bug.
seems that the hard drive is failing, closing the bug