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?
