Bug 531052

Summary: [anaconda] Live: Error processing drive: /dev/dm-0
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: high    
Version: rawhideCC: angelo.neacsu, awilliam, caiqian, cqbkaju, duffy, hdong, jlaska, lili, notting, petersen, phiporiphic, vanmeeuwen+fedora, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 539305 (view as bug list) Environment:
Last Closed: 2009-11-04 08:09:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 531381    
Description Flags
Anaconda storage log file
anaconda.log (anaconda-12.41-1.fc12)
program.log (anaconda-12.41-1.fc12)
storage.log (anaconda-12.41-1.fc12) none

Description Joachim Frieben 2009-10-26 16:56:32 UTC
Description of problem:
When searching for storage devices during a live CD install from yesterday's snapshot desktop-i386-20091024.19, an error window pops up complaining that an error has occurred while processing drive /dev/dm-0 (see attached screenshot).
After clicking "Ignore drive" for /dev/dm-0 and likewise for the subsequent error message for /dev/dm-1, the install proceeds as expected.
Clicking "Re-initialize drive" will keep the installer stuck in this step.

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

How reproducible:

Steps to Reproduce:
1. Boot system from desktop-i386-20091024.19 live media.
2. Lauch /usr/bin/liveinst.
3. Proceed to storage step.
Actual results:
Installer reports error processing drive: /dev/dm-0.

Expected results:
Installer launches partitioning tool.

Additional info:
This issue is fairly recent and was not encountered using the F12 Alpha Snap3 live CD.

Comment 1 Joachim Frieben 2009-10-26 16:58:11 UTC
Created attachment 366125 [details]
Anaconda storage log file

Comment 2 dongjibing 2009-10-28 02:46:24 UTC
Please try the newest F12 Beta

Comment 3 Qian Cai 2009-10-28 09:44:42 UTC
Humphrey, 20091024 version supposes to be newer than F12 Beta. From the page,

Beta was announced in 20 Oct.

Comment 4 Phip 2009-10-28 22:56:36 UTC
I believe I have encountered this issue as well. I was running the beta live cd installer to replace my F11 installation. (I updated anaconda to latest 12.39-1 before proceeding.)

My old setup was as follows, create by F11 anaconda except for /home which was kept from a F9 or F10 install.
/dev/sda1 ext3 196MB /boot
/dev/sda4 ext4 7993MB / (encrypted)
/dev/sda2 swap 1537MB
/dev/sda3 ext3 66589MB /home (encrypted)

As the OP described, the "Error processing drive" message comes up twice, in my case reading:

Linux device-mapper (snapshot)

Linux device-mapper (snapshot)

I did not recoginize the 3067MB size as any of my own, so the first time the message came up I suspected a problem with the persistent live image. I re-copied the image and got the error once again. This time I clicked "Re-Initalize Drive". The dialog went away immediately, it did not seem like it did anything to my hard disk. At that point I exited the installer and booted from my local disk. /boot and / mounted correctly, but for /home:

fsck.ext3: bad magic number in super-block while trying to open /dev/mapper/luks-90a5cc4a-...
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid ... then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

So, that's where I am for now. Strange that only one of my partitions was impacted. I hold out hope I could get /home to mount again, but am currently stumped. It is hard to believe all 60GB were wiped out in about a second, but maybe that is the case. I at least wanted to report what seems like a serious problem with F12Beta live / anaconda.

Comment 5 Jens Petersen 2009-10-29 02:52:54 UTC
I see this myself too with current rawhide spins.

I think this is a F12Blocker candidate.

Comment 6 Chris Lumens 2009-10-29 14:24:05 UTC
Can you attach the output of ls -l /dev/live* to this bug report?  Thanks.

Comment 7 James Laska 2009-10-29 17:47:35 UTC
(In reply to comment #6)
> Can you attach the output of ls -l /dev/live* to this bug report?  Thanks.  

Testing with anaconda-12.41-1.fc12.i686

# ls -l /dev/live*
lrwxrwxrwx. 1 root root 3 2009-10-29 13:38 /dev/live -> sr0

Comment 8 James Laska 2009-10-29 17:55:13 UTC
Created attachment 366674 [details]
anaconda.log (anaconda-12.41-1.fc12)

After clicking "ignore" for both /dev/dm-0 and /dev/dm-1, I am able to proceed with the installation.  Attaching the anaconda.log, storage.log and program.log that demonstrate clicking "ignore".

Comment 9 James Laska 2009-10-29 17:55:40 UTC
Created attachment 366675 [details]
program.log (anaconda-12.41-1.fc12)

Comment 10 James Laska 2009-10-29 17:56:23 UTC
Created attachment 366676 [details]
storage.log (anaconda-12.41-1.fc12)

Comment 11 Máirín Duffy 2009-10-29 19:56:51 UTC
this happened to me with the 28-oct-2009 nightly desktop live cd just now.

Comment 12 Joachim Frieben 2009-10-30 06:40:11 UTC
Testing with anaconda-12.39-1.fc12.i686

$ ls -l /dev/live*
lrwxrwxrwx. 1 root root 3 2009-10-30 03:28 /dev/live -> sr0

Comment 13 David Lehman 2009-10-30 16:19:52 UTC
Fixed by commits 447db7bf1f6c and 080f12b6d4ee, which will be in anaconda-12.42-1.

Comment 14 Adam Williamson 2009-10-30 16:41:19 UTC
Discussed at blocker meeting, accepted as a blocker. Please re-test when the next anaconda build is available and included in images.

Fedora Bugzappers volunteer triage team

Comment 15 Adam Williamson 2009-10-31 04:51:56 UTC
this is in the 12.42 build:


tag request:


Fedora Bugzappers volunteer triage team

Comment 16 Bill Nottingham 2009-11-02 21:28:29 UTC
This will be in tomorrow's (20091103) rawhide - please retest with that!

Comment 17 Adam Williamson 2009-11-04 02:24:43 UTC
can someone please confirm this is fixed with today's Rawhide?

spins are at:



Fedora Bugzappers volunteer triage team

Comment 18 Liam Li 2009-11-04 08:09:40 UTC
this issue fixed on liveCD 2009-11-03, so close rawhide

Comment 19 Dave Jones 2009-11-19 20:18:52 UTC
This bug appears to be back.
I am booting from a live-usb and it is trying to initialize the USB stick.
Ignoring the error lets the install continue.


Comment 20 Angelo Neacsu 2009-12-07 10:26:05 UTC
I have the same issue with my upgrade from a preupgrade utility:
Error processing drive:

RAID1 Array

I don't want to test a click on Re-initialize drive :)

Comment 21 Dave Jones 2010-03-10 21:44:08 UTC
mv'ing /lib/udev/rules.d/70-anaconda.rules to /lib/udev/rules.d/70-anaconda.rules.old
to fix "Bug 453095 - Cd tray is closed automatically after ejecting"
was the cause in my case.

Putting 'echo "dev.cdrom.autoclose = 0" >> /etc/sysctl.conf' in my kickstart file instead looks like it may solve both issues.