On Mon, 7 Feb 2000, Mike Iglesias wrote:
> I have a system running Redhat 6.0 that had a RAID 0 disk set on it
> (2 disks). The system is dual boot with windows 95, and I needed to
> do something with windows. After doing the windows stuff, I rebooted
> linux and now the RAID 0 will not mount. When I run raidstart by
> hand, I get this:
>
> Feb 4 10:03:33 xx kernel: (read) sda1's sb offset: 2117824 [events: f2d8e687]
> Feb 4 10:03:33 xx kernel: md: invalid raid superblock magic on sda1
> Feb 4 10:03:33 xx kernel: md: sda1 has invalid sb, not importing!
> Feb 4 10:03:33 xx kernel: could not import sda1!
> Feb 4 10:03:33 xx kernel: autostart sda1 failed!
> Feb 4 10:03:33 xx kernel: huh12?
>
> The raid set is sda1 and sdb1, which are not configured in Windows. Linux
> appears to have shut down normally before I ran Windows.
>
> Is there any hope of getting this raid set back, or getting a new superblock
> on sda1? I realize that more of the disk structure could be trashed, but
> I'd like to at least get far enough to run fsck and see.
>
> There's nothing critical on the raid, but I'd rather not have to redo
> what I had before if I don't have to. There are no backups, of
> course.
You can use the mkraid program with the --force option, which will
forcably put the superblocks back, but you NEED TO ENSURE that the
contents of /etc/raidtab is correct, or it will trash it once and forever.
But... i'd be very worried why windows trashed the info in the first
place. What partition types are your raid volumes set to ?
("`-/")_.-'"``-._ Ch'marr, a.k.a.
. . `; -._ )-;-,_`) Chris Cogdon <[EMAIL PROTECTED]>
(v_,)' _ )`-.\ ``-'
_.- _..-_/ / ((.' FC1.3: FFH3cmA+>++C++D++H++M++P++R++T+++WZ++Sm++
((,.-' ((,/ fL RLCT acl+++d++e+f+++h++i++++jp-sm++
