I haven't found any answer that works in the HOWTO's, man pages or readme's. I messed
up somewhere, but can't find it.
Setup:
2.2.19 kernel w/ RAID support compiled in. (Slackware 7.1 to start)
raid tools 0.90
dual IBM 9.1 gig ultra-SCSI on a SuperMicro/Adapted 7895 on board controller.
RAID 1 personality registered.
/etc/raidtab:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
persistent-superblock 1
chunk-size 32
device /dev/sda3
raid-disk 0
device /dev/sdb3
raid-disk 1
-->eof
raidstart "--all" or "/dev/md0" or "--configfile /etc/raidtab" results in:
"/dev/md0: Invalid argument"
mkraid /dev/md0 (and all useful options, including "--force") results in:
"disk 0: /dev/sda3, xxxkB, raid suberblock at XXX
/dev/sda3 appears to be part of a RAID ... aborted ,see /proc/mdstat and syslog for
clues"
Well, /proc/mdstat shows raid1 personality registered and 3 inactive raids.
syslog, even after upping logging level shows nothing at all. I add that very early
on in this, on a 2.2.16 kernel, this raid was registered and active as a raid0. After
that, trying to change it ended up w/ this. I was using the older raidtools, too.
Now, even changing partition types, mke2fs as a normal linux partition,
re-partition... nothing changes.
Has anybody seen this before?
Thanks in advance.
Greg Neumann
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
