Caffeinate The World writes:
> 
> --- Greg Oster <oster@cs.usask.ca> wrote:
> > > recon read failed
> > > panic: raidframe error at line 1314 file
> > > /usr/src/sys/dev/raidframe/rf_reconstruct.c
> > 
> > This *is* an error in reading from a block on sd1.  You might try 
> > doing:
> > 
> >  dd if=/dev/rsd1d of=/dev/null bs=1m 
> > 
> > and see whether that errors out too.  You might also check to see if 
> > any of the logs in /var/log have a mention of a failing read.
> 
> dd if=/dev/rsd1c of=/dev/null bs=1m
> sd1(isp0:0:2:0): Check condition on CDB: 0x08 01 82 80 80 00
>   SENSE KEY: Media Error
>  INFO FIELD: 99025
>    ASC/ASCQ: Data Synchronization Mark Error
>    FRU CODE: 0xd2
>        SKSV: Actual Retry Count: 264
>
> dd: /dev/rsd1c: Input/output error

"Bingo!".  Hardware problem. :(

> 48+0 records in
> 48+0 records out
> 50331648 bytes transferred in 7.687 seconds (6547632 bytes/sec)
> 
> dd if=/dev/rsd0c of=/dev/null bs=1m
> 8683+1 records in
> 8683+1 records out
> 9104953344 bytes transferred in 958.214 secs (9502004 bytes/sec)
> 
> sd0 seems to be ok. Anyway around that error on sd1?

None that are pretty.  The easiest way is probably do dump/restore
the data from filesystems on sd1 onto some other storage.  And *hopefully* 
the bad block in question isn't part of a file or of the meta-data.

Later...

Greg Oster