*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Thanks for the answer, but now that I think about it, I'm not sure
NEW_LABEL alone would cause wholesale RAID array corruption. Correct me
if I'm wrong because I'm not an expert on how parted works, but that
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
NEW_LABEL was used, but the change that caused this to always zero the
first 9KiB of the disk was a change in parted 2.1, committed upstream on
13 November 2009 and introduced to Ubuntu on 26 February 2010.
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
possibly related to bug 569900
--
Non-selected Raid Array Corruption from Installer
https://bugs.launchpad.net/bugs/568183
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
This might well be bug 542210, recently fixed. If so, then it is
certainly not bug 191119 since bug 542210 was introduced much more
recently than that.
--
Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Yup, that bug is likely the cause of the corruption of the RAID
partitions. If I had to make a guess, that NEW_LABEL command was being
used on the incorrectly detected file systems, thus overwriting RAID
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Thanks for taking the time to help investigate this. Check out my reply
to you in the mailing list thread for suggestions on recreating the bug.
Number 3 especially is required.
--
Non-selected Raid Array
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
BTW, please use post to bug #191119. Subscribers to this bug will be
notified if you post there, but not vice-versa.
--
Non-selected Raid Array Corruption from Installer
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Attempted to recreate this failure and was unable to do so.
Following as closely as I could to Alvin's description, I had a system
running Karmic with a root partition and a second data partition. I
moved
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
I have no idea what you mean by 'loader-RAID5'...
It likely doesn't matter what type of RAID is being used. I also tested
on the live CD with the same problem. mdadm isn't present on the live
CD and the
** This bug is no longer a duplicate of bug 191119
Installer corrupts raid drive
--
Non-selected Raid Array Corruption from Installer
https://bugs.launchpad.net/bugs/568183
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Description changed:
In short this really isn't a bug I found but just one that came up on a
mailing list, so for those who want to read the original post should go
through the archives of the Ubuntu user technical support, not for
general discussions ubuntu-us...@lists.ubuntu.com
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
** This bug has been marked a duplicate of bug 191119
Installer corrupts raid drive
--
Non-selected Raid Array Corruption from Installer
https://bugs.launchpad.net/bugs/568183
You received this bug
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Please don't remove the duplicate tag. There are 3 parts to every bug
report:
1. an initial set of conditions
2. a procedure that was followed
3. actual results which differ from expected results
The
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
This IS a loader-RAID5 problem. It appears to be on a server version of
10.04 and the writer wonders if earlier versions may also have this bug.
It appears it is only a bug to users that have RAID5 hard
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Dup of bug #191119
** This bug has been marked a duplicate of bug 191119
Installer corrupts raid drive
--
Non-selected Raid Array Corruption from Installer
https://bugs.launchpad.net/bugs/568183
You
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
This bug is not a duplicate of 191119. 191119 is a Bios problem. This
bug is all about linux software raid with no fake raid involvment. How
do you unmark the duplicate.
--
Non-selected Raid Array
*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Yes, this is a a dup of 19119. Just because his hardware RAID is
reporting the problem it doesn't follow that the hardware caused the
problem.
--
Non-selected Raid Array Corruption from Installer
17 matches
Mail list logo
