I have been in this situation before but not in a long time.  Have a power failure last night and the Tower upon re-boot attempted to do a parity check and failed.  When I got to the box this morning it was not reachable.  I re-booted and finally got the box up BUT parity was now shown as invalid.  I attampted to run a parity and it failed again and locked up the box.  I then ran yet another parity with a syslog tail running and here is what I showed when it failed.  Can anyone help me figure this out, I'm running without any parity right now.

 

smb(647)

Jul  2 23:12:03 Tower smbd[1413]:  Error writing 4 bytes to client. -1. (Connec

tion reset by peer)

Jul  2 23:34:20 Tower kernel: hdk: dma_intr: status=0x51 { DriveReady SeekComple

te Error }

Jul  2 23:34:20 Tower kernel: hdk: dma_intr: error=0x10 { SectorIdNotFound }, LB

Asect=455290687, high=27, low=2305855, sector=455290624

Jul  2 23:34:22 Tower kernel: hdk: dma_intr: status=0x51 { DriveReady SeekComple

te Error }

Jul  2 23:34:22 Tower kernel: hdk: dma_intr: error=0x10 { SectorIdNotFound }, LB

Asect=455290687, high=27, low=2305855, sector=455290624

Jul  2 23:34:24 Tower kernel: hdk: dma_intr: status=0x51 { DriveReady SeekComple

te Error }

Jul  2 23:34:24 Tower kernel: hdk: dma_intr: error=0x10 { SectorIdNotFound }, LB

Asect=455290687, high=27, low=2305855, sector=455290624

Jul  2 23:34:26 Tower kernel: hdk: dma_intr: status=0x51 { DriveReady SeekComple

te Error }

Jul  2 23:34:26 Tower kernel: hdk: dma_intr: error=0x10 { SectorIdNotFound }, LB

Asect=455290687, high=27, low=2305855, sector=455290624

Jul  2 23:34:26 Tower kernel: hdk: DMA disabled

Jul  2 23:34:26 Tower kernel: hdl: DMA disabled

Jul  2 23:34:26 Tower kernel: PDC202XX: Secondary channel reset.

Messages indicate disk10 is reporting errors.

 

What unRAID version are you using?

Messages indicate disk10 is reporting errors.

 

What unRAID version are you using?

 

3.0 final...!

 

And don't you mean disk 6 not disk 10....?

Yes, disk6.

 

Please send your 'config/super.dat' file to me: [email protected]

 

Tom,

 

I pulled out disk 6 and replaced it with another drive and got a parity to run just fine.  Do you still need my super.dat file.....?  I do have another (new) problem however, read in a seperate post.

No.  I thought it was in a state where Parity was marked 'invalid' somehow & prevented you from rebuilding a new disk6.  Apparently you were able to rebuild it, correct?

Yes its built .. but it is slow on build