The following was filed automatically by anaconda:
anaconda 18.104.22.168 exception report
Traceback (most recent call first):
File "/usr/lib/python2.6/site-packages/parted/__init__.py", line 276, in freshDisk
peddisk = disk_new_fresh(device.getPedDevice(), ty)
File "/usr/lib/anaconda/storage/devices.py", line 721, in __init__
ty = platform.getPlatform(None).diskType)
File "/usr/lib/anaconda/storage/devicetree.py", line 1112, in addUdevDiskDevice
initcb=cb, initlabel=initlabel, **kwargs)
File "/usr/lib/anaconda/storage/devicetree.py", line 1194, in addUdevDevice
device = self.addUdevDiskDevice(info)
File "/usr/lib/anaconda/storage/devicetree.py", line 1691, in populate
File "/usr/lib/anaconda/storage/__init__.py", line 302, in reset
File "/usr/lib/anaconda/storage/__init__.py", line 102, in storageInitialize
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext
File "/usr/lib/anaconda/gui.py", line 1339, in nextClicked
DiskLabelException: /dev/sda: unrecognised disk label
Created attachment 358260 [details]
Attached traceback automatically from anaconda.
Do you have a filesystem on /dev/sda without any partitions involved?
No, but I think this may be related to BUG# 518719, which anaconda is failing to handle (anaconda fails to re-initialise the partition table).
518719 is a kernel bug, not an anaconda bug. Since sda (which is the drive involved in this bug report) is attached to a device whose kernel driver is having problems, I'm thinking that the kernel problem is the underlying problem here. Once that's fixed up, anaconda should be fine. If not, we can reopen this bug and continue to investigate.
Agreed 518719 is a kernel bug, but anaconda should handle the situation of an invalid partition table gracefully whatever the reason it occurred. If anaconda cannot find any media to install to it should say so and NOT take a dive!