Bug 229158 - dmraid stopped from working after kernel upgrade
dmraid stopped from working after kernel upgrade
Status: CLOSED DUPLICATE of bug 196828
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-18 20:08 EST by Jarkko
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-25 06:07:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jarkko 2007-02-18 20:08:03 EST
Description of problem: dmraid stopped from working after kernel upgrade. Worked
with Fedora 7 Test1 kernel. 

Version-Release number of selected component (if applicable):
kernel-2.6.20-1.2932.fc7

How reproducible: Always (done twise).

Steps to Reproduce:
1. get Fedora 7 Test1 CD
2. install using dmraid
3. yum upgrade kernel + reboot
  
Actual results: /dev/mapper/ does not contain the raid devices anymore.

Expected results: /dev/mapper/ should continue to contain the raid devices.

Additional info: I _only_ updated the kernel package, so I am 100% sure that
"yum upgrade kernel" broke this.
Comment 1 Jarkko 2007-02-18 20:48:07 EST
- Working kernel: kernel-2.6.19-1.2914.fc7

- Same issue happens also with: kernel-xen-2.6.19-1.2898.2.3.fc7 (see bug #229161)
Comment 2 Jarkko 2007-02-21 16:32:02 EST
The currently latest kernel-2.6.20-1.2936.fc7 doesn't work either.
Comment 3 Jarkko 2007-02-23 22:04:24 EST
The currently latest kernel-2.6.20-1.2940.fc7 doesn't work either.
Comment 4 Jarkko 2007-02-24 11:52:12 EST
The currently latest kernel-2.6.20-1.2942.fc7 doesn't work either.
Comment 5 Jarkko 2007-02-24 15:33:54 EST
I extracted the initrd images and compared them. The cause for this problem has
been found:

--- initrd-2.6.19-1.2914.fc7/init       2007-02-24 22:19:23.000000000 +0200
+++ initrd-2.6.20-1.2942.fc7/init       2007-02-24 22:19:43.000000000 +0200
@@ -76,10 +76,7 @@
 echo "Loading dm-snapshot.ko module"
 insmod /lib/dm-snapshot.ko
 mkblkdevs
-rmparts sdb
-rmparts sda
-dm create ddf1_4c534920202020201000005500000000330a535300000a28 0 974608384
mirror core 2 131072 nosync 2 8:0 0 8:16 0
-dm partadd ddf1_4c534920202020201000005500000000330a535300000a28
+resume LABEL=swap
 echo Creating root device.
 mkrootdev -t ext3 -o defaults,ro dm-2
 echo Mounting root filesystem.
Comment 6 Jarkko 2007-02-25 06:07:42 EST

*** This bug has been marked as a duplicate of 196828 ***

Note You need to log in before you can comment on or make changes to this bug.