raid 1 on Sun E250 running 3.0 sparc r1 (kernel 2.4.18 - patched)

[<daren@adoptionmedia.com>]

All,

I am trying to mirror our root disk. I am on Debian
3.0, r1 kernel 2.4.18 with patches running on an E250
sun box.

Building the raid works fine (mkraid /dev/md0), and
has no complaints. Rebooting the system shows that the
raid is auto-detected and syncs just fine. mkfs.ext3
/dev/md0 runs fine as well. When I try and mount -o
error=remount-ro -t ext3 /dev/md1 /mnt (or any other
variation of mount) however- I get a kernel panic (See
/var/log/messages entry below).

the actual device partitions (/dev/sdb1, /dev/sdc1)
are set to 0xfd (Linux Raid Autodetect)

here is the /dev/md1 entry from /etc/raidtab

raiddev /dev/md1
        raid-level      1
        nr-raid-disks   2
        nr-spare-disks  0
        persistent-superblock   1
        chunk-size      4
        device /dev/sdb1
        raid-disk       0
        device /dev/sdc1
        raid-disk       1



I am at my wits end here. I have other raid partitions
running raid 5 , and they mount fine. I can even build a raid5 using these
same disks and it does not complain.

Thank you in advance for your help
-Daren Eason
daren@adoption.com
480.446.0500

<SNIP /var/log/messages>
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
data_access_exception: SFSR[0000000000801009]
SFAR[fffff800cbb095fc], going.
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
\|/ ____ \|/
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
"@'/ .. \`@"
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
/_| \__/ |_\
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
\__U_/
Jan 24 11:04:49 SNIP_HOSTNAME kernel: mount(20385):
Dax
Jan 24 11:04:49 SNIP_HOSTNAME kernel: TSTATE:
0000004411009600 TPC: 0000000002010c9c TNPC:
0000000002010ca0 Y: 07000000    Tai
nted: P
Jan 24 11:04:49 SNIP_HOSTNAME kernel: g0:
000000000000000f g1: fffff8007dd70018 g2:
0000000000000001 g3: fffffffffffffff8
Jan 24 11:04:49 SNIP_HOSTNAME kernel: g4:
fffff80000000000 g5: fffee0004dd99600 g6:
fffff800646f8000 g7: 0000000000000014
Jan 24 11:04:49 SNIP_HOSTNAME kernel: o0:
0000000000000002 o1: fffff8007dd7001c o2:
fffff8007ea1a5e0 o3: fffff80002299980
Jan 24 11:04:49 SNIP_HOSTNAME kernel: o4:
0000000000000002 o5: 0000000000000001 sp:
fffff800646fac61 ret_pc: fffff8007dd70020
Jan 24 11:04:49 SNIP_HOSTNAME kernel: l0:
fffff8007dd70000 l1: fffff8007dd70448 l2:
000000000062e000 l3: 0000000000000002
Jan 24 11:04:49 SNIP_HOSTNAME kernel: l4:
0000000000000000 l5: 0000000000626fe0 l6:
00000000effffb98 l7: 0000000000000000
Jan 24 11:04:49 SNIP_HOSTNAME kernel: i0:
0000000000000008 i1: fffee0004dd995dc i2:
0000000000000000 i3: 0000000000000000
Jan 24 11:04:49 SNIP_HOSTNAME kernel: i4:
0000000000000002 i5: fffff8007dd70000 i6:
fffff800646fad21 i7: 0000000002010e80
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[0000000002010e80]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[00000000020003c0]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[00000000004e7a10]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[00000000004e7b00]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[00000000004e7cd0]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[000000000046787c]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[0000000000493790]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[000000000046afa4]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[000000000046b5b0]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[000000000047e8b0]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[000000000047ebe8]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[000000000042de48]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[0000000000410af4]
Jan 24 11:04:49 SNIP_HOSTNAME kernel:
Caller[000000000001288c]
Jan 24 11:04:49 SNIP_HOSTNAME kernel: Instruction
DUMP: f84763d8  b2067fdc  84073fff <c606400f> 80a0e000
 12480013  b938a000
c4064009
 80a0a000
</SNIP>