RAIDZ problems

[farscapesg1]

So.. I decided to add a new set of 4 drives to my OI+Nappit VM in a striped mirror setup. These new drives were connected to a different HBA, and the existing RAIDZ drives were not touched. Suddenly the RAIDZ drives have the wrong info as shown below..

c3t1d0 2.00 TB RAIDZ_datastore raidz via dd ONLINE c3 configured Error: S:0 H:36 T:0 ATA WDC WD20EADS-00R - 
c3t2d0 2.00 TB RAIDZ_datastore raidz via dd ONLINE c3 configured Error: S:0 H:36 T:0 ATA WDC WD20EADS-00R - 
c3t3d0 2.00 TB RAIDZ_datastore basic via dd ONLINE c3 configured Error: S:0 H:36 T:0 ATA WDC WD20EADS-00R - 
c3t4d0 2.00 TB RAIDZ_datastore basic via dd ONLINE c3 configured Error: S:0 H:36 T:0 ATA WDC WD20EADS-00R - 
c3t9d0 2.00 TB RAIDZ_datastore spares via dd INUSE c3 configured Error: S:0 H:0 T:0 ATA WDC WD20EADS-00R - 
c3t9d0 2.00 TB RAIDZ_datastore spares via dd INUSE c3 configured Error: S:0 H:0 T:0 ATA WDC WD20EADS-00R -

Considering I'm completely unknowledgable in the realm of Solaris, is there a way to correct this without blowing out the array and rebuilding it? For some reason it lists the spare drive twice, and two of the data drives are being listed as basic. Also, the Hard errors just began showing after this occured..

 

[staticlag]

post the results of

 zpool history

and

 zpool status

 

[farscapesg1]

zpool history

History for 'RAIDZ_datastore':
2011-08-09.16:35:13 zpool create -f RAIDZ_datastore raidz c3t1d0 c3t2d0 c3t3d0 c3t4d0
2011-08-09.16:35:13 zfs set reservation=0.53T RAIDZ_datastore
2011-08-09.16:35:18 zfs set refreservation=0.53T RAIDZ_datastore
2011-08-09.19:03:51 zfs create -o snapdir=hidden -o casesensitivity=insensitive -o nbmand=off -o sharesmb=off -o atime=off -o compression=off RAIDZ_datastore/ZFS_datastore
2011-08-09.19:03:51 zfs set sharesmb=name=ZFS_datastore,guestok=true RAIDZ_datastore/ZFS_datastore
2011-08-09.19:03:56 zfs set aclinherit=passthrough RAIDZ_datastore/ZFS_datastore
2011-08-09.19:04:18 zfs set sharenfs=on RAIDZ_datastore/ZFS_datastore
2011-08-29.22:42:41 zfs set sync=disabled RAIDZ_datastore
2011-09-24.11:25:25 zfs set sync=standard RAIDZ_datastore
2011-09-24.13:09:03 zfs create -o snapdir=hidden -o casesensitivity=insensitive -o nbmand=off -o sharesmb=off -o atime=off -o compression=off RAIDZ_datastore/Storage
2011-09-24.13:09:03 zfs set sharesmb=name=Storage RAIDZ_datastore/Storage
2011-09-24.13:09:08 zfs set aclinherit=passthrough RAIDZ_datastore/Storage
2011-09-24.13:14:54 zfs set sharenfs=on RAIDZ_datastore/Storage
2011-09-24.13:15:14 zfs set sharenfs=off RAIDZ_datastore/Storage
2011-09-24.13:15:53 zfs destroy -r -f RAIDZ_datastore/Storage
2011-09-24.13:16:14 zfs create -o snapdir=hidden -o casesensitivity=insensitive -o nbmand=off -o sharesmb=off -o atime=off -o compression=off RAIDZ_datastore/Storage
2011-09-24.13:16:14 zfs set sharesmb=name=Storage,guestok=true RAIDZ_datastore/Storage
2011-09-24.13:16:19 zfs set aclinherit=passthrough RAIDZ_datastore/Storage
2011-10-04.22:35:39 zfs create -o snapdir=hidden -o casesensitivity=insensitive -o nbmand=off -o sharesmb=off -o atime=off -o compression=off RAIDZ_datastore/Wii
2011-10-04.22:35:40 zfs set sharesmb=name=Wii,guestok=true RAIDZ_datastore/Wii
2011-10-04.22:35:45 zfs set aclinherit=passthrough RAIDZ_datastore/Wii
2011-10-23.18:42:38 zpool add RAIDZ_datastore spare c3t9d0
2011-11-02.12:38:02 zfs set sync=disabled RAIDZ_datastore

zpool status

pool: RAIDZ_datastore
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
RAIDZ_datastore ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
c3t1d0 ONLINE 0 0 0
c3t2d0 ONLINE 0 0 0
spare-2 ONLINE 0 0 0
c3t3d0 ONLINE 0 0 0
c3t9d0 ONLINE 0 0 0
c3t4d0 ONLINE 0 0 0
spares
c3t9d0 INUSE currently in use

errors: No known data errors

 

[staticlag]

Ya dude sorry I'm not sure what could have happened. Did you update any existing firmware or BIOSes? That can change Drive info

 

[farscapesg1]

Nope, no BIOS or hardware changes other than adding the additional HBA and connecting 4 additional drives to it. I even thought I was being smart by adding the new drives to a seperate controller card to avoid causing any issues with the existing arrays.

Oh well, I was looking for a good excuse to rebuild the storage VM with OI 151 anyways Luckily I haven't started migrating much data to the new storage anyways, and what I had I've already moved back off in preparation to having to blow out the array and rebuild.