Public bug reported:
Running Linux 2.6.20-15-server #2 SMP 32bit
First, I also had the "UUID of raid devices have changed after upgrade
to Feisty", which I "fixed" by editing mdadm.conf with the new id. After
that I started the array which rebuilt itself.
I thought everything was allright, until a hard crash. I rebooted, array was
dirty AND degraded, and I had to manually re-add a drive. (mind you, the drive
that faults is random, so there arn't any real bad drive here)
Even display image disappears when it crashes.
I don't really know where to look for information on the crash, or even
what is causing it, all I know it was not happening in 6.10 and might be
mdadm/raid5 related. I'm also using cryptsetup for 128 bit AES
encryption on top of this raid5.
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
** Tags: crash feisty mdadm
** Description changed:
- Running Linux desk-dfs 2.6.20-15-server #2 SMP 32bit
+ Running Linux 2.6.20-15-server #2 SMP 32bit
First, I also had the "UUID of raid devices have changed after upgrade
to Feisty", which I "fixed" by editing mdadm.conf with the new id. After
that I started the array which rebuilt itself.
I thought everything was allright, until a hard crash. I rebooted, array was
dirty AND degraded, and I had to manually re-add a drive. (mind you, the drive
that faults is random, so there arn't any real bad drive here)
Even display image disappears when it crashes.
I don't really know where to look for information on the crash, or even
what is causing it, all I know it was not happening in 6.10 and might be
mdadm/raid5 related. I'm also using cryptsetup for 128 bit AES
encryption on top of this raid5.
** Tags added: crash feisty mdadm
--
Feisty crash possibly related to mdadm/raid5
https://bugs.launchpad.net/bugs/110304
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
