Bug 1381027

Summary: "ERROR: ddf1: wrong # of devices in RAID set" makes anaconda crash
Product: [Fedora] Fedora Reporter: Germano Massullo <germano.massullo>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 24CC: agk, anaconda-maint-list, bmr, g.kaviyarasu, heinzm, jonathan, lvm-team, mkolman, prajnoha, prockai, vanmeeuwen+fedora, zkabelac
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Alessio Nicosia
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:17:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
lshw none

Description Germano Massullo 2016-10-02 14:06:45 UTC
Description of problem:
I was starting anaconda in a live session to install Fedora on the affected system, when I got the following errors that made anaconda crash everytime I start it. Despite what you can read in the logs, the system does not have any RAID configuration installed.

[liveuser@localhost ~]$ liveinst 
ERROR: asr: seeking device "/dev/dm-2" to 18446744073709551104
ERROR: ddf1: seeking device "/dev/dm-2" to 18446744073709551104
ERROR: ddf1: seeking device "/dev/dm-2" to 18446744073709420032
ERROR: hpt37x: seeking device "/dev/dm-2" to 4608
ERROR: hpt45x: seeking device "/dev/dm-2" to 18446744073709545984
ERROR: isw: seeking device "/dev/dm-2" to 18446744073709550592
ERROR: jmicron: seeking device "/dev/dm-2" to 18446744073709551104
ERROR: lsi: seeking device "/dev/dm-2" to 18446744073709551104
ERROR: nvidia: seeking device "/dev/dm-2" to 18446744073709550592
ERROR: pdc: seeking device "/dev/dm-2" to 137438913024
ERROR: pdc: seeking device "/dev/dm-2" to 137438920192
ERROR: pdc: seeking device "/dev/dm-2" to 137438927360
ERROR: pdc: seeking device "/dev/dm-2" to 137438934528
ERROR: sil: seeking device "/dev/dm-2" to 18446744073709551104
ERROR: via: seeking device "/dev/dm-2" to 18446744073709551104
ERROR: ddf1: wrong # of devices in RAID set "ddf1_4c5349202020202010000073100092414711471177a25ae6" [1/3] on /dev/sda
Traceback (most recent call last):
  File "/usr/bin/anaconda-cleanup", line 84, in <module>
    devicetree.populate(cleanupOnly=True)
  File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 555, in populate
    self._populator.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1638, in populate
    self._populate()
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1701, in _populate
    self.addUdevDevice(dev)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 725, in addUdevDevice
    device = self.addUdevDMDevice(info)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 304, in addUdevDMDevice
    slave_devices = self._addSlaveDevices(info)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 245, in _addSlaveDevices
    raise NoSlavesError("no slaves found for device %s" % name)
blivet.errors.NoSlavesError: no slaves found for device ddf1_4c5349202020202010000073100092414711471177a25ae6
Starting installer, one moment...
anaconda 24.13.7-1 for Fedora 24 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
 * if the graphical installation interface fails to start, try again with the
   inst.text bootoption to start text installation
 * when reporting a bug add logs from /tmp as separate text/plain attachments
ERROR: asr: seeking device "/dev/dm-2" to 18446744073709551104
ERROR: ddf1: seeking device "/dev/dm-2" to 18446744073709551104                                                                                              
ERROR: ddf1: seeking device "/dev/dm-2" to 18446744073709420032                                                                                              
ERROR: hpt37x: seeking device "/dev/dm-2" to 4608                                                                                                            
ERROR: hpt45x: seeking device "/dev/dm-2" to 18446744073709545984                                                                                            
ERROR: isw: seeking device "/dev/dm-2" to 18446744073709550592                                                                                               
ERROR: jmicron: seeking device "/dev/dm-2" to 18446744073709551104                                                                                           
ERROR: lsi: seeking device "/dev/dm-2" to 18446744073709551104                                                                                               
ERROR: nvidia: seeking device "/dev/dm-2" to 18446744073709550592                                                                                            
ERROR: pdc: seeking device "/dev/dm-2" to 137438913024                                                                                                       
ERROR: pdc: seeking device "/dev/dm-2" to 137438920192                                                                                                       
ERROR: pdc: seeking device "/dev/dm-2" to 137438927360                                                                                                       
ERROR: pdc: seeking device "/dev/dm-2" to 137438934528                                                                                                       
ERROR: sil: seeking device "/dev/dm-2" to 18446744073709551104                                                                                               
ERROR: via: seeking device "/dev/dm-2" to 18446744073709551104                                                                                               
ERROR: ddf1: wrong # of devices in RAID set "ddf1_4c5349202020202010000073100092414711471177a25ae6" [1/3] on /dev/sda                                        


Version-Release number of selected component (if applicable):
24.13.7-1

Comment 1 Germano Massullo 2016-10-02 14:07:18 UTC
Created attachment 1206621 [details]
lshw

Comment 2 Germano Massullo 2016-10-02 14:50:06 UTC
Ok I have found out why Anaconda mentions RAID systems. One of the disks installed in the system was coming from a server with RAID enabled. But on the affected system there is no RAID installed/running

Comment 3 Fedora End Of Life 2017-07-25 23:19:20 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-08-08 19:17:30 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.