Anaconda Incorrectly Detects dmraid

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greetings,

We are seeing an issue with anaconda-11.1.2.36 (CentOS 5.0), where it incorrectly detects dmraid on our Dell 2900s (and, 1950s, 2950s). (We were able to track it down to that issue based on the message "Specified nonexistent disk sda in partition command," and /tmp/anaconda.log.) I am not sure why Anaconda detects dmraid. I suspect it looks for a piece of metadata somewhere on the disk, and by pure hapstance our data matches the signature of a dmraid disk set. Has anyone seen this before? Any ideas on how to fix it? We have not seen this issue with RHEL 4u2, or CentOS 4u4, and we have been running/imaging those for the past 1.5 years.

Here's a example log from two identical machines, one with the issue, and one without.

-- Falsely detects dmraid. --

DEBUG   : starting dmraids
DEBUG   : self.driveList(): ['sda', 'sdb']
DEBUG   : DiskSet.skippedDisks: []
DEBUG   : DiskSet.skippedDisks: []
DEBUG   : starting all dmraids on drives ['sda', 'sdb']
DEBUG   : scanning for dmraid on drives ['sda', 'sdb']
DEBUG : got raidset <block.device.RaidSet instance at 0xb7d173ac> (sda sdb)
DEBUG   :   valid: True found_devs: 2 total_devs: 2
DEBUG : adding mapper/ddf1_44656c6c202020201028001510281f0332b494acaae97d7b to isys cache DEBUG : adding mapper/ddf1_44656c6c202020201028001510281f0332b494acaae97d7b to isys cache()
DEBUG   : adding sda to dm cache
DEBUG   : removing sda from isys cache
DEBUG   : adding sdb to dm cache
DEBUG   : removing sdb from isys cache

## it detected dmraid?!?!
-->>DEBUG : starting raid <block.device.RaidSet instance at 0xb7d173ac> with mknod=True

DEBUG : done starting dmraids. Drivelist: ['mapper/ddf1_44656c6c202020201028001510281f0332b494acaae97d7b']
INFO    : Running kickstart %%pre script(s)
INFO    : All kickstart %%pre script(s) have been run

-- Correctly, does not detect dmraid. --

DEBUG   : starting dmraids
DEBUG   : self.driveList(): ['sda', 'sdb']
DEBUG   : DiskSet.skippedDisks: []
DEBUG   : DiskSet.skippedDisks: []
DEBUG   : starting all dmraids on drives ['sda', 'sdb']
DEBUG   : scanning for dmraid on drives ['sda', 'sdb']
DEBUG   : done starting dmraids.  Drivelist: ['sda', 'sdb']
INFO    : Running kickstart %%pre script(s)
INFO    : All kickstart %%pre script(s) have been run


In the meantime, to get around this issue I just commented out all calls to startDmRaid(). I will continue to decipher the code (anaconda, python-pyblock, dmraid-devel) , but I wanted to ask here first.



Thanks,
Christopher

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux