I'm running NetBSD -current (about 1 month old) with a 4 disk raid0
partition (a news spool).  Last night one of the disks hiccupped.  Now the
raid0 set will not work.  The disk itself seems fine, but raidframe will
not let the disk back into the stripe.  It says "/dev/sd16e has a different
modfication count: 147 88".

Is there a way to force raidframe to accept this disk?  The data will be a
bit inconsistent, but fsck should fix that.  It's a news spool so a few
missing or corrupted files are okay.

I'm appending the dmesg output.

	-Kevin

Hosed component: /dev/sd16e
raid0: Component /dev/sd0e being configured at row: 0 col: 0
         Row: 0 Column: 0 Num Rows: 1 Num Columns: 4
         Version: 2 Serial Number: 99872 Mod Counter: 147
         Clean: No Status: 0
/dev/sd0e is not clean!
raid0: Component /dev/sd1e being configured at row: 0 col: 1
         Row: 0 Column: 1 Num Rows: 1 Num Columns: 4
         Version: 2 Serial Number: 99872 Mod Counter: 147
         Clean: No Status: 0
/dev/sd1e is not clean!
raid0: Component /dev/sd16e being configured at row: 0 col: 2
         Row: 0 Column: 2 Num Rows: 1 Num Columns: 4
         Version: 2 Serial Number: 99872 Mod Counter: 88
         Clean: No Status: 0
/dev/sd16e has a different modfication count: 147 88
/dev/sd16e is not clean!
raid0: Component /dev/sd17e being configured at row: 0 col: 3
         Row: 0 Column: 3 Num Rows: 1 Num Columns: 4
         Version: 2 Serial Number: 99872 Mod Counter: 147
         Clean: No Status: 0
/dev/sd17e is not clean!
RAIDFRAME: Configure (RAID Level 0): total number of sectors is 35549696 (17358 
MB)
RAIDFRAME(RAID Level 0): Using 12 floating recon bufs with no head sep limit