A *very* strange thing suddenly happened.
Around the upgrade to
Linux thor 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010
x86_64 GNU/Linux
my device mapping suddenly changed:
1) before the three identical partitions for raid0 were /dev/sda1, sdb1,
sdc1, and the system booted from /dev/sdd
2) now these partitions became /dev/sdb1, sdc1, sdd1 (I need not mention that
the raid is not functioning; mdam
gets crazy), the system boots from /dev/sda
Thus my raid survives from one kernel upgrade to the other.
I give below the output of mdadm; notice that it shows sda1 in the array and
simultaneously complains it is not,
sdd1 is in, but never reported as such:
r...@thor:~# mdadm --misc --examine /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : 7f9cbbf0:56c4865f:59180514:05d76d73 (local to host thor)
Creation Time : Tue Jun 29 19:46:11 2010
Raid Level : raid0
Used Dev Size : 0
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Update Time : Tue Jun 29 19:46:11 2010
State : active
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Checksum : 76d18393 - correct
Events : 1
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 1 0 active sync /dev/sda1
0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1
2 2 8 33 2 active sync /dev/sdc1
r...@thor:~# mdadm --misc --examine /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : 7f9cbbf0:56c4865f:59180514:05d76d73 (local to host thor)
Creation Time : Tue Jun 29 19:46:11 2010
Raid Level : raid0
Used Dev Size : 0
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Update Time : Tue Jun 29 19:46:11 2010
State : active
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Checksum : 76d183a5 - correct
Events : 1
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 17 1 active sync /dev/sdb1
0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1
2 2 8 33 2 active sync /dev/sdc1
r...@thor:~# mdadm --misc --examine /dev/sdd1
/dev/sdd1:
Magic : a92b4efc
Version : 00.90.00
UUID : 7f9cbbf0:56c4865f:59180514:05d76d73 (local to host thor)
Creation Time : Tue Jun 29 19:46:11 2010
Raid Level : raid0
Used Dev Size : 0
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Update Time : Tue Jun 29 19:46:11 2010
State : active
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Checksum : 76d183b7 - correct
Events : 1
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 8 33 2 active sync /dev/sdc1
0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1
2 2 8 33 2 active sync /dev/sdc1
r...@thor:~# mdadm --misc --examine /dev/sda1
mdadm: No md superblock detected on /dev/sda1.
--
GRUB writes to wrong MBR and destroys RAID setup
https://bugs.launchpad.net/bugs/601305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
