Public bug reported:
Binary package hint: mdadm
I had created a RAID5 Array on Edgy:
/dev/sda4 - SATA
/dev/sdb1 - SATA
/dev/hda1 - PATA
/dev/hdb1 - PATA
It works flawlessly for two months with several reboots. On Friday, 13
April 2007 I upgraded to Feisty (bad day?) and run into the problems
with linux-image-2.6.14-23 which freezes on boot when scanning for the
SATA Drives. I waited until Saturday and upgraded to linux-
image-2.6.15-20 from a rescue System. After the upgrade the system
recognizes my SATA Drives, but failed to boot, because it could not
assemble the raid Array. The /dev/ entries changed from /dev/hd* to
/dev/sd* as documented. I removed the mdadm Start Script completly from
the intialramdisk so my system could start. Then I tried to assemble my
raid Array manually:
mdadm --assemble /dev/md0 /dev/sda4 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/sdc1 misses out due to wrong homehost
mdadm: superblock on /dev/sdd1 doesn't match others - assembly aborted
So I checked the Superblock of the Partitions:
/dev/sda4:
Magic : a92b4efc
Version : 00.90.00
UUID : 0b4ff2c9:63c85083:5d9fb26f:21588147 (local to host
desaster-area)
Creation Time : Thu Feb 15 19:56:28 2007
Raid Level : raid5
Device Size : 156288256 (149.05 GiB 160.04 GB)
Array Size : 468864768 (447.14 GiB 480.12 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Fri Apr 13 16:47:21 2007
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 2c9413b7 - correct
Events : 0.598129
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 254 4 2 active sync
0 0 0 0 0 active sync
1 1 3 65 1 active sync
2 2 254 4 2 active sync
3 3 8 17 3 active sync /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : 0b4ff2c9:63c85083:5d9fb26f:21588147 (local to host
desaster-area)
Creation Time : Thu Feb 15 19:56:28 2007
Raid Level : raid5
Device Size : 156288256 (149.05 GiB 160.04 GB)
Array Size : 468864768 (447.14 GiB 480.12 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Thu Apr 12 22:06:53 2007
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 2c930b41 - correct
Events : 0.598128
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 17 3 active sync /dev/sdb1
0 0 3 1 0 active sync
1 1 3 65 1 active sync
2 2 8 4 2 active sync /dev/sda4
3 3 8 17 3 active sync /dev/sdb
/dev/sdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : df53562e:f0eccc5e:a85502b6:021653a8
Creation Time : Thu Feb 15 19:56:28 2007
Raid Level : raid5
Device Size : 156288256 (149.05 GiB 160.04 GB)
Array Size : 468864768 (447.14 GiB 480.12 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Fri Apr 13 16:47:21 2007
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : b92f13a4 - correct
Events : 0.598129
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 0 0 0 active sync
0 0 0 0 0 active sync
1 1 3 65 1 active sync
2 2 8 4 2 active sync /dev/sda4
3 3 8 17 3 active sync /dev/sdb1
/dev/sdd1:
Magic : a92b4efc
Version : 00.90.00
UUID : df53562e:f0eccc5e:5d9fb26f:21588147 (local to host
desaster-area)
Creation Time : Thu Feb 15 19:56:28 2007
Raid Level : raid5
Device Size : 156288256 (149.05 GiB 160.04 GB)
Array Size : 468864768 (447.14 GiB 480.12 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Thu Apr 12 22:06:53 2007
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 8dbaeaa9 - correct
Events : 0.598128
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 3 65 1 active sync
0 0 3 1 0 active sync
1 1 3 65 1 active sync
2 2 8 4 2 active sync /dev/sda4
3 3 8 17 3 active sync /dev/sdb1
The SATA Drives have the same RAID UUID. The UUID of the PATA drives
differ. Interesting are the Major/Minors of the Devices which are
different. IMHO A Major of 3 are the old PATA IDs. The new valures are:
brw-rw---- 1 root disk 8, 4 2007-04-16 20:56 /dev/sda4
brw-rw---- 1 root disk 8, 17 2007-04-16 20:56 /dev/sdb1
brw-rw---- 1 root disk 8, 33 2007-04-16 20:56 /dev/sdc1
brw-rw---- 1 root disk 8, 49 2007-04-16 20:56 /dev/sdd1
My first idea was to use --update=uuid as it should set the UUIDs on
assembly but it did not work:
mdadm --assemble --update=UUID /dev/md0 /dev/sda4 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/sdc1 misses out due to wrong homehost
mdadm: superblock on /dev/sdd1 doesn't match others - assembly aborted
I googled most of Sunday, but find no solution. Even from a Ubuntu Edgy
Rescue CD, with old kernel, old mdadm and old PATA Driver the RAID could
not be assembled. I installed a clean Feisty on a free partition and
upgraded to kernel 2.6.20-15.27 with the same result.
** Affects: mdadm (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
https://bugs.launchpad.net/bugs/107080
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
