Thank you, I will try it again.
-- Greg
On Sat, Dec 10, 2011 at 9:06 AM, Phillip Susi wrote:
> Yes, it has been at least as far back as 9.04, I thought all the way
> back to 8.04, but I could be mistaken.
>
> --
> You received this bug notification because you are subscribed to the bug
> rep
Yes, it has been at least as far back as 9.04, I thought all the way
back to 8.04, but I could be mistaken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191119
Title:
Installer corrupts raid drive
Is that an option now? The installer didn't let me install to the raid
array before and I have been reluctant to try again since it screwed things
up so badly before.
-- Greg
On Mon, Oct 10, 2011 at 10:53 AM, Phillip Susi wrote:
> Correct me of I'm wrong, but it sounds like this problem beg
[Expired for parted (Ubuntu) because there has been no activity for 60
days.]
** Changed in: parted (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191119
Correct me of I'm wrong, but it sounds like this problem begins with
choosing to install Ubuntu to one of the individual disks comprising the
raid array, instead of to the array as a whole. If that is the case,
that is user error, not a bug.
If that is not the case, please reproduce this, and the
Could someone take a look at this? This was a pretty serious issue that
seems to have just fizzled out as far as response goes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191119
Title:
Installer
(copying comment from bug 568183)
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 bug
with NEW_LABEL would only overwrite the RAID superbl
Linux000, don't bother; I have practically written a dissertation on why
it isn't likely to be a grub problem in one of these bugs.
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/191119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
First off, I don't have the hardware to try this, but there is a chance
of grub wiping over information in the RAID controller(like a catalog to
retrieve information form multiple disks)and rendering the data
unreadable, which would only affect raid arrays, and creating a new file
system would work
Note that in bug 560152, NickJ's problem is actually this bug.
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/191119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Yup, and I thank you for it. And if this bug does get fixed, I imagine
those people whose data won't be hosed as a result would thank you too.
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/191119
You received this bug notification because you are a member of Ubuntu
Bugs, which
FWIW, I do not use sparse files on my VMs... I allocate the full size
prior and build each drive prior to use, so in my case, a 20GB drive is
actually 20GB, not 1GB with a 20GB limit... but it was worth a shot at
least... I tried.
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/1
It probably won't work in a VM, because of the way a VM's virtual
storage devices work. They discard everything that's not being used at
that moment, otherwise you'd have to allocate the full size of the
drive. Thus, you probably couldn't have any defunct file systems
sitting around.
--
Install
> Top-posting for (my) convenience on this one...
>
> It's nice to see someone actually trying to recreate the bug instead of
> just flapping their gums trying to sound smart. If you have the time,
> could you try recreating it again? I have some suggestions to make it
> more like my scenario (i
I'm adding this message from the thread to provide as much information
for people trying to recreate this bug as possible;
Top-posting for (my) convenience on this one...
It's nice to see someone actually trying to recreate the bug instead of
just flapping their gums trying to sound smart. If y
Logic 101:
There is nothing in this report that would even remotely suggest that it's a
GRUB problem. By your logic, it could be anything that writes directly to the
hard drive, not just GRUB. While it's true that the absence of evidence is not
evidence of absence, the absence of evidence *sho
Reading the original report here, I think it is a possibility that the
problem was caused by grub overwriting part of the fakeRAID control
area. A contributing factor may be a hardware environment that causes
different drive orders to be recognized by BIOS, grub and kernel(s).
I don't know this fo
I forgot to mention in my first post that once the problem shows itself,
it persists indefinitely across attempts to install Ubuntu. The way I
was able to fix the problem at that point was to physically zero out the
defunct file system on the disk. This should be obvious, but I'll say
it anyway:
Name-calling people is unfortunately not helping. Note that there are
quite few people capable of fixing code on this kind of low level
software. There is also always limited amount of people who are both
able to fix the problem, who have the affected hardware and are
motivated enough to fix it on
Please see bug #568183 for steps on recreating the issue.
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/191119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
No, it is NOT fucking fixed. I can't believe it's been OVER TWO YEARS
and no one has bothered to even look at this easily reproducible issue?
And because of it my (and who knows how many other people's) data is
hosed. What issues DO you investigate, if you don't investigate
corrupted file system
** Changed in: parted (Ubuntu)
Status: New => Incomplete
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/191119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Was assigned to ubiquity, but it looks like its /sbin/parted that does
the dirty work.
** Changed in: parted (Ubuntu)
Sourcepackagename: ubiquity => parted
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/191119
You received this bug notification because you are a member of Ubunt
I have the same problem. I don't know how I'm going to recover my
partitions yet. The bug is apparently in the parted package since it
happened while using the gparted program that supposedly calls
/sbin/parted.
--
Installer corrupts raid drive
https://bugs.launchpad.net/bugs/191119
You receive
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at [WWW]
https://wiki.ubuntu.co
26 matches
Mail list logo
