Thanks a *LOT* guys, it works and i now have all my lovely data back :)
On Mon, 29 May 2000, Mike Black wrote:
> Not if you haven't changed the RAID config from your initial setup. (i.e.
> havent' removed/added any drives).
> I've done this a couple of times with no problem.
> If you change the disk ordering in /etc/raidtab or have had to
> raidhotremove/raidhotadd any disks THEN it will destroy your data.
>
> ----- Original Message -----
> From: "Matthew Burke" <[EMAIL PROTECTED]>
> To: "James Manning" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, May 29, 2000 5:50 AM
> Subject: Re: HELP!!! Broken raid0
>
>
>
>
> On Mon, 29 May 2000, James Manning wrote:
>
> > Sure makes it look like hdc3 has some major issues. It has a partition
> > type of fd, but invalid raid superblock. Makes me wonder if e2fsck
> > didn't get run on hdc3 itself and it "fixed" that last part (hope not
> > since it may have done some real superblock damage). hdc itself looks
> > ok since hdc3 doesn't seem to have any problems, so I don't think it's
> > an actual drive problem. Unfortunately, since it appears that the raid
> > superblock (at a minimum) is broken on hdc3, the only thing I can think
> > to recommend is
> >
> > - mkraid --force /dev/md1 (rewrites raid superblocks)
>
> from the mkraid man page:
>
> Note that initializing RAID devices destroys all of the
> data on the consituent devices.
>
> -f, --force
> Initialize the consituent devices, even if they
> appear to have data on them already.
>
> isn't this just going to lose me everything?
>
>
>
