[Sticky: Ye Olde Laundry List]

I would like to second Joe L.'s security point.  The system is great but just waaaayyyy to open right now.

[Questions about errors!!]

I just setup a brand spankin' new pro array.  Right now I'm only using 4 drives and trying to get the feel of the product.  I have a WD 500gb parity drive annd 3 Seagate 320gb drives all SATA and all hooked to a Promise SATA300 TX4.   As I have been copying data over the the array I have been getting occasional errors - about 1-2 for every 50gb of data.  I have attached a screenshot and my log below.

 

Specific Questions:

• What does "errors" mean on the web page? Write errors? Read Errors?  The log shows two read errors.
  
• I read that read errors are reconsructed using the parity info - what happens with a write error?
  
• Does it retry? Fail?
  
• What does the read error below indicate?
  

[br]

If I have hardware or setup issues I really want to knwo now before I move all my data over.  Thanks in advance.

 

One more thing: YES I did use search...

 

Dan Stroot

 

------------------------------

 

 

root@Tower:~# tail -f /var/log/syslog

Nov 19 05:54:52 Tower kernel:  I/O error: dev 08:31, sector 16239472

Nov 19 05:54:52 Tower kernel: md3: read error!

Nov 19 05:54:52 Tower kernel: end_read_request 16239472/3, count: 2, uptodate 0.

Nov 19 06:28:37 Tower kernel: ata4: status=0x50 { DriveReady SeekComplete }

Nov 19 06:28:37 Tower kernel: SCSI disk error : host 4 channel 0 id 0 lun 0 return code = 8000002

Nov 19 06:28:37 Tower kernel: Current sd08:41: sns = 70  0

Nov 19 06:28:37 Tower kernel: Raw sense data:0x70 0x00 0x00 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

Nov 19 06:28:37 Tower kernel:  I/O error: dev 08:41, sector 82644432

Nov 19 06:28:37 Tower kernel: md0: read error!

Nov 19 06:28:37 Tower kernel: end_read_request 82644432/0, count: 2, uptodate 0.