I had a drive throwing errors and replaced it with another. During the rebuild process mt server through a bunch of Call Trace errors and a bunch of stuff disappeared from my library. I stopped the array and restarted. When I got the system going again "Disk 8" no longer had 1.45TB of data on it. It was empty and asked for formatting. Is there anything I can do to get that data back? Is it still on the parity drive? Where did those Call Trace errors come from? Any help would be greatly appreciated.

tower-diagnostics-20170708-0851.zip

Call traces were related to filesystem corruption on disk8, you formatted disk8, you lost all data on disk8 (unless the old disk is still readable).

Also;

 

Disk7 should be replaced:

 

Device Model:     ST3000DM001-1CH166
Serial Number:    W1F1H4QJ
183 Runtime_Bad_Block       0x0032   095   095   000    Old_age   Always       -       5
184 End-to-End_Error        0x0032   086   086   099    Old_age   Always   FAILING_NOW 14

There are recent UDMA_CRC errors on the parity disk, replace SATA cable.

  9 Power_On_Hours          0x0032   069   069   000    Old_age   Always       -       12665
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       1062

Error 1062 occurred at disk power-on lifetime: 11215 hours (467 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 b0 90 c7 a0 e0  Error: ICRC, ABRT 176 sectors at LBA = 0x00a0c790 = 10536848

 

Thanks for your help. I'll make a trip to Microcenter today to replace drive 7. Drives are connected to SAS backplane, no sata cable. Should I put the parity drive in another slot? 

47 minutes ago, ceb0610 said:

Should I put the parity drive in another slot? 

 

Yes, and check in a few days/weeks to see if the number of CRC errors remains the same.

Edited July 8, 20178 yr by johnnie.black