https://bugzilla.novell.com/show_bug.cgi?id=638532 https://bugzilla.novell.com/show_bug.cgi?id=638532#c0 Summary: after upgrading kernel, mdadm won't identify md1 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 After I upgraded from 2.6.34 to 2.6.34.4 recently, I had to use a rescue boot to fix an issue (unrelated). As part of fixing that issue, I had to use 'mkinitrd' in a chrooted environment. Since then, regardless of which kernel I use, I can't get the system to identify /dev/md1 as /dev/md1. It always comes up as /dev/md125. This is what I see during boot: <6>[ 3.526529] md: md125 stopped. <6>[ 3.529639] md: bind<sda1> <6>[ 3.532005] md: bind<sdb1> <6>[ 3.535542] raid1: raid set md125 active with 2 out of 2 mirrors <6>[ 3.547215] md125: bitmap initialized from disk: read 12/12 pages, set 0 bits <6>[ 3.549221] created bitmap (179 pages) for device md125 <6>[ 3.579607] md125: detected capacity change from 0 to 3002073088 <6>[ 3.582546] md125: unknown partition table and later mdadm: /dev/md1 not identified in config file. mdadm: /dev/md1 not identified in config file. mdadm: /dev/md125 has been started with 2 drives. resume device not found (ignoring) Waiting for device /dev/md1 to appear: ..............................Could not find /dev/md1. Want me to fall back to /dev/md125? (Y/n) Waiting for device /dev/md125 to appear: ok and maybe this is useful: turnip:~ # mdadm --detail /dev/md125 /dev/md125: Version : 0.90 Creation Time : Wed Mar 24 08:06:20 2010 Raid Level : raid1 Array Size : 2931712 (2.80 GiB 3.00 GB) Used Dev Size : 2931712 (2.80 GiB 3.00 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 125 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Fri Sep 10 09:58:30 2010 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 5d52dc0e:c75ca914:93290e43:000e38f8 (local to host turnip) Events : 0.58558 Number Major Minor RaidDevice State 0 8 17 0 active sync /dev/sdb1 1 8 1 1 active sync /dev/sda1 turnip:~ # turnip:~ # cat /etc/mdadm.conf DEVICE /dev/hd*[a-h][0-9] /dev/sd*[a-h][0-9] /dev/nbd*[0-9] /dev/sd[a-h] /dev/md* HOMEHOST turnip ARRAY /dev/md0 metadata=1.00 name=turnip:2 UUID=41a25d00:b230bfd4:66317f89:50db83b0 ARRAY /dev/md1 metadata=0.90 UUID=5d52dc0e:c75ca914:93290e43:000e38f8 ARRAY /dev/md3 metadata=1.01 spares=1 name=turnip:3 UUID=fd039b07:e90e90f7:fe3554bc:17f1bbfe turnip:~ # I can't use mdadm -r to change the boot device back to /dev/md1 ('no such device') and yet it is "mounted" properly: /dev/md1 on / type ext3 (rw,noatime,nodiratime) Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.