[SOLVED] Help please. Red balled drive replaced. Same failures.

[petjek]

You are so right. I wrote rebuild but what I really meant was that as disk2 was red-balled all copied data came from parity drive. At least that is what I understood when reading this thread. The external backup drive was connected to my Mac and copied them over network by mounting //server/disk2. Copy speed was between 5 - 10 MB/s so it took many hours to copy almost 1 TB.

As I didn't preclear the new 3 TB drive when I installed it I thought it might be a good idea to catch up now. So my idea was to stop the array, unassign disk2, preclear it, reasign to array and start rebuild.

But I'm not sure if this is necessary any more as it seems some magic self healing thing happened.

 

 

As you can see disk2 seems to be in perfect condition now. It wasn't last week but it is now.

 

UPDATE: syslog.1 added

syslog.zip

[trurl]

So the drive was emulated when you did the copy. OK

 

I'm not seeing an image in your latest post. Are you saying the drive is no longer redballed?

 

Since the drive's SMART looks OK you might just skip the preclear, do the rebuild, check the SMART again, then do a non-correcting parity check and check the SMART again. That should be a pretty good test of the drive and will also be a good test of the rebuilt data.

[trurl]

And after you get your array stable again, see this important message.

[petjek]

Yes, it is no longer red-balled.

Just started the non-correcting parity check. This will take sooome time. 

 

I already spend some time reading about the update procedure to v6. But that's next step.

[petjek]

Parity check is finished with no errors. SMART looks good too. So what ever problem it was it's gone.

But still I have no idea what happened.

[petjek]

Hard to believe but the drive is red-balled again! What the hell is going on here?

 

http://up.picr.de/27529016fu.jpg

syslog.zip

[JorgeB]

Problem with disk2 started with CRC errors, you should replace the SATA cable and try to rebuild again.

 

Nov 24 18:24:38 hightower avahi-daemon[5568]: Invalid response packet from host 192.168.10.103.
Nov 24 18:25:06 hightower kernel: ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Nov 24 18:25:06 hightower kernel: ata6.00: irq_stat 0x08000000, interface fatal error
Nov 24 18:25:06 hightower kernel: ata6: SError: { UnrecovData 10B8B BadCRC }
Nov 24 18:25:06 hightower kernel: ata6.00: failed command: READ DMA
Nov 24 18:25:06 hightower kernel: ata6.00: cmd c8/00:18:70:03:86/00:00:00:00:00/ef tag 0 dma 12288 in
Nov 24 18:25:06 hightower kernel:          res 50/00:00:6f:03:86/00:00:0f:00:00/ef Emask 0x10 (ATA bus error)
Nov 24 18:25:06 hightower kernel: ata6.00: status: { DRDY }
Nov 24 18:25:06 hightower kernel: ata6: hard resetting link
Nov 24 18:25:06 hightower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 24 18:25:06 hightower kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Nov 24 18:25:06 hightower kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Nov 24 18:25:06 hightower kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Nov 24 18:25:06 hightower kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Nov 24 18:25:06 hightower kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Nov 24 18:25:06 hightower kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Nov 24 18:25:06 hightower kernel: ata6.00: configured for UDMA/133
Nov 24 18:25:06 hightower kernel: ata6: EH complete
Nov 24 18:25:08 hightower kernel: ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Nov 24 18:25:08 hightower kernel: ata6.00: irq_stat 0x08000000, interface fatal error
Nov 24 18:25:08 hightower kernel: ata6: SError: { UnrecovData 10B8B BadCRC }
Nov 24 18:25:08 hightower kernel: ata6.00: failed command: READ DMA
Nov 24 18:25:08 hightower kernel: ata6.00: cmd c8/00:38:a0:5c:87/00:00:00:00:00/ef tag 0 dma 28672 in
Nov 24 18:25:08 hightower kernel:          res 50/00:00:9f:5c:87/00:00:0f:00:00/ef Emask 0x10 (ATA bus error)
Nov 24 18:25:08 hightower kernel: ata6.00: status: { DRDY }
Nov 24 18:25:08 hightower kernel: ata6: hard resetting link
Nov 24 18:25:08 hightower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 24 18:25:08 hightower kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Nov 24 18:25:08 hightower kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Nov 24 18:25:08 hightower kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Nov 24 18:25:08 hightower kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Nov 24 18:25:08 hightower kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Nov 24 18:25:08 hightower kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Nov 24 18:25:08 hightower kernel: ata6.00: configured for UDMA/133
Nov 24 18:25:08 hightower kernel: ata6: EH complete
Nov 24 18:25:08 hightower kernel: ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Nov 24 18:25:08 hightower kernel: ata6.00: irq_stat 0x09000000, interface fatal error
Nov 24 18:25:08 hightower kernel: ata6: SError: { UnrecovData 10B8B BadCRC }
Nov 24 18:25:08 hightower kernel: ata6.00: failed command: READ DMA EXT

[RobJ]

Hard to believe but the drive is red-balled again! What the hell is going on here?

 

Many drive issues are not actually issues with the drive, but are actually issues with the interface to the drive.  I wrote an article to help with this, and just expanded its preface to better answer your question.  My apologies if some of it seems too technical.  At least read the starting paragraphs.

 

  The Analysis of Drive Issues

 

That page is still not finished though ...