Hello,

I have a server that had a drive fail in its RAID array. After swapping the drive and allowing some time for the array to rebuild, I rebooted the server and discovered the pool that our SYS volume sits on would not mount. The original error was:

Sept 28, 2009 9:00:51am NSS<COMN>-3.25-xxxx: comnPool.c[2672]
Pool SYS: System data I/O error 20203(zio.c[554]).
Block 136757 (file block - 136757)(ZID 2176)

I performed a pool rebuild (nss /poolrebuild=sys) and received a scary red screen warning about losing data if I continued. I aborted the rebuild and rebooted the server to make sure all drives were ok, then I tried the nss rebuild again. It seemed to progress fine, until it got to about 66% where it froze. It's been sitting at this exact spot with no disk activity for about an hour. The logger screen shows the following messages:

Sep 28, 2009 12:15:46 pm NSS<COMN>-3.25-xxxx: comnPool.c[2672]
Pool SYS: System data I/O error 20204(zio.c[2260]).
Block 128992(file bock 2881)(ZID 3)

Sep 28, 2009 12:15:47 pm NSS<ZLSS>-3.25-1449: zfsVolumeData.c[212]
Error reading VolumeData Block 771010, status=20206.

Sep 28, 2009 12:15:47 pm NSS<ZLSS>-3.25-1449: zfsVolumeData.c[212]
Error reading VolumeData Block 771010, status=20206.

(this is repeated a number of times)

Sep 28, 2009 12:15:49 pm NSS<ZLSS>-3.25-1449: zlssLogicalVolume.c[4948]
Error reading PoolData Block 512646, status=20206.

Sep 28, 2009 12:15:49 pm NSS<ZLSS>-3.25-xxxx: zlssMSAP.c[524]
MSAP: Pool "SYS" read error 20206.


Server is NW 6.5 sp 6. I'm not sure how I should proceed with a locked up nss rebuild. Any assistance is greatly appreciated!

Mark