Estou tentando configurar um novo computador com um software raid0. Estou executando o Ubuntu 12.04 de 32 bits. Eu tenho o meu sistema operacional instalado em um disco rígido PATA, e 4 SATA 2TB Hitachi Drives para ser invadido. A Motherboard é uma ASUS M2N-L, que usa o nForce 570 SLI / NVIDIA MCP55 (rev a3) para seu controlador SATA integrado. Im ciente software raid pode não ser o melhor, mas eu tenho várias outras máquinas com esta configuração que funcionam excelentes para os meus propósitos.
Consegui construir e iniciar o ataque com êxito através do Utilitário de Disco da GUI do Ubuntu, mas ele me deu um erro, que a partição foi deslocada seria muito lenta e sugeriu que eu partisse novamente. Eu fiz a partição novamente, mas isso simplesmente resultou em mais erros ... não é possível localizar dispositivos, ou problemas de deslocamento, eventualmente voltei para a etapa de particionamento e consegui montar a unidade apesar da mensagem de erro, mas foi de fato lento. E continuamente não conseguiu capturar vídeo DV. (Os outros ataques como este no meu escritório capturam 8 fluxos de cada vez)
Eu já troquei todos os 4 cabos SATA, troquei as portas usadas e troquei a placa-mãe (eu tenho 2 desta ASUS M2N-L). Eu também troquei 1 dos 4 discos rígidos de 2Tb. (Eu tenho 6, eventualmente terá 8 em dois Raid0 de 4 unidades nesta caixa) Eu tenho o BIOS atualizado para o mais recente. Eu tentei usar manualmente o mdadm para asseble e criar uma matriz de raid, mas eles sempre não conseguem formatar um sistema de arquivos. A GUI às vezes me deixa tentar e montar, mas sempre volta com erros como, procure em "dmesg | tail". Bad superblock ... Eu olhei isso e tentei "reparar" de um superbloco alternativo, mas isso também falhou.
Além disso, durante todo esse processo, verifiquei a GUI do Utilitário de Disco e descobri que, ocasionalmente, uma das quatro unidades desaparecerá ou uma delas perderá o status do SMART DATA. Se eu reiniciar, todas as unidades e todos os dados do SMART retornarão. (Boot mostra todas as unidades, todas com o SMART)
Na minha opinião, todas as observações apontam para um conflito de driver com o Ubuntu, mas não encontrei mais ninguém reclamando de problemas com minha combinação de hardware? ASUS tem "Linux Drivers" mas nenhum para qualquer liunx baseado no Debian, eu tentei converter rpms e instalar, mas isso não funcionou ou não teve efeito (é o mesmo driver já incluído no Ubuntu?)
Alguma idéia de quem é a culpa ou como corrigi-lo? Ficarei feliz em postar quaisquer dados específicos, apenas pergunte, não tenho certeza do que é relevante neste momento ... obrigado antecipadamente. -Mark
1ª edição: OK, tentando recriar a mensagem de erro original que criou uma invasão de trabalho, mas estava muito lenta. Para fazer isso, estou tentando excluir as partições em cada unidade e recebo este erro:
Error erasing: helper exited with exit code 1: In part_del_partition:
device_file=/dev/sde, offset=17408
Entering MS-DOS parser (offset=0, size=2000398934016)
MSDOS_MAGIC found
found partition type 0xee => protective MBR for GPT
Exiting MS-DOS parser
Entering EFI GPT parser
GPT magic found
partition_entry_lba=2
num_entries=128
size_of_entry=128
Leaving EFI GPT parser
EFI GPT partition table detected
got it
got disk
got partition - part->type=0
committed to disk
Error calling fsync(2) on /dev/sde: Input/output error
Cannot scrub filesystem signatures at offset=17408 and size=2000398899712
Tentativa de excluir outra partição:
Error erasing: helper exited with exit code 1: In part_del_partition:
device_file=/dev/sdb, offset=17408
Entering MS-DOS parser (offset=0, size=2000398934016)
MSDOS_MAGIC found
found partition type 0xee => protective MBR for GPT
Exiting MS-DOS parser
Entering EFI GPT parser
GPT magic found
partition_entry_lba=2
num_entries=128
size_of_entry=128
read failed (Input/output error)
Leaving EFI GPT parser
EFI GPT partition table detected
got it
Error: /dev/sdb: unrecognised disk label
ped_disk_new() failed
Logo após esse erro, tentei:
$ sudo smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-32-generic-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: /3:0:0:0
Product:
User Capacity: 600,332,565,813,390,450 bytes [600 PB]
Logical block size: 774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T
permissive' options.
1 das 4 unidades desapareceu da minha lista na GUI do Utilitário de Disco e 2 das 3 restantes não mostram mais o status SMART, eis o único relatório SMART "disponível" no momento:
$ sudo smartctl -a /dev/sdd
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-32-generic-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Deskstar 7K3000
Device Model: Hitachi HDS723020BLA642
Serial Number: <removed>
LU WWN Device Id: 5 000cca 36ac60074
Firmware Version: MN6OA800
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Tue Nov 13 09:18:40 2012 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (19381) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 135 135 054 Pre-fail Offline - 84
3 Spin_Up_Time 0x0007 182 182 024 Pre-fail Always - 276 (Average 353)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 27
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 135 135 020 Pre-fail Offline - 26
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 197
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 23
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 31
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 31
194 Temperature_Celsius 0x0002 150 150 000 Old_age Always - 40 (Min/Max 23/51)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 168 168 000 Old_age Always - 2323
SMART Error Log Version: 1
ATA Error Count: 2323 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 2323 occurred at disk power-on lifetime: 197 hours (8 days + 5 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 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
27 00 00 00 00 00 e0 08 18:47:11.304 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 18:47:11.296 IDENTIFY DEVICE
f5 00 00 01 00 00 e0 04 18:47:11.141 SECURITY FREEZE LOCK
f5 00 00 01 00 00 e0 00 18:47:00.653 SECURITY FREEZE LOCK
e3 00 00 01 00 00 a0 00 18:47:00.007 IDLE
Error 2322 occurred at disk power-on lifetime: 197 hours (8 days + 5 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 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
27 00 00 00 00 00 e0 08 18:42:41.701 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 18:42:41.693 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 18:42:41.685 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 18:42:41.685 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 18:42:41.677 IDENTIFY DEVICE
Error 2321 occurred at disk power-on lifetime: 182 hours (7 days + 14 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 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ec 00 00 00 00 00 a0 08 03:48:06.464 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 03:48:06.464 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 03:48:06.464 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 03:48:06.456 IDENTIFY DEVICE
f5 00 00 01 00 00 e0 04 03:48:06.301 SECURITY FREEZE LOCK
Error 2320 occurred at disk power-on lifetime: 182 hours (7 days + 14 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 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
27 00 00 00 00 00 e0 08 03:48:06.464 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 03:48:06.456 IDENTIFY DEVICE
f5 00 00 01 00 00 e0 04 03:48:06.301 SECURITY FREEZE LOCK
f5 00 00 01 00 00 e0 00 03:47:53.105 SECURITY FREEZE LOCK
e3 00 00 01 00 00 a0 00 03:47:52.448 IDLE
Error 2319 occurred at disk power-on lifetime: 182 hours (7 days + 14 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 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
27 00 00 00 00 00 e0 08 03:46:21.429 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 03:46:21.421 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 03:46:21.413 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 03:46:21.413 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 03:46:21.405 IDENTIFY DEVICE
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Vou tentar recriar esse erro original novamente ... mas, como você pode ver, vi muitos erros neste empreendimento! Obrigado novamente!
2a edição: parece que não consigo voltar a todos os discos rígidos vazios para reproduzir o erro original! 1 das 4 unidades se recusa a excluir ...
Na GUI do Utilitário de Disco
Error erasing: helper exited with exit code 1: In part_del_partition:
device_file=/dev/sdd, offset=17408
Entering MS-DOS parser (offset=0, size=2000398934016)
MSDOS_MAGIC found
found partition type 0xee => protective MBR for GPT
Exiting MS-DOS parser
Entering EFI GPT parser
GPT magic found
partition_entry_lba=2
num_entries=128
size_of_entry=128
Leaving EFI GPT parser
EFI GPT partition table detected
got it
got disk
got partition - part->type=0
committed to disk
Error calling fsync(2) on /dev/sdd: Input/output error
Cannot scrub filesystem signatures at offset=17408 and size=2000398899712
Eu também tentei limpar a unidade com o dd
$ sudo dd if=/dev/zero of=/dev/sdd bs=1M
dd: writing '/dev/sdd': No space left on device
2009+0 records in
2008+0 records out
2106302464 bytes (2.1 GB) copied, 1.73234 s, 1.2 GB/s
Parece estranho que uma unidade de 2 TB esteja cheia depois de gravar 1,2 GB? Desde que eu não consigo apagar esta unidade não posso recriar minha mensagem de erro original ... mas algo me diz que todos esses erros apontam para a mesma razão pela qual eu tenho um erro em primeiro lugar .. se eles Apontar para qualquer coisa.
3ª edição:
A saída do dmesg foi cortada devido ao limite do caractere askUbuntu, texto completo disponível no Google Drive
[ 480.956838] ata5.00: status: { DRDY ERR }
[ 480.956840] ata5.00: error: { ICRC ABRT }
[ 480.956842] ata5.00: failed command: WRITE FPDMA QUEUED
[ 480.956847] ata5.00: cmd 61/28:08:88:88:e0/00:00:e8:00:00/40 tag 1 ncq 20480 out
[ 480.956848] res 51/84:08:00:08:00/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 480.956850] ata5.00: status: { DRDY ERR }
[ 480.956852] ata5.00: error: { ICRC ABRT }
[ 480.956856] ata5.00: failed command: READ FPDMA QUEUED
[ 480.956861] ata5.00: cmd 60/08:10:00:08:00/00:00:00:00:00/40 tag 2 ncq 4096 in
[ 480.956862] res 51/84:08:00:08:00/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 480.956864] ata5.00: status: { DRDY ERR }
[ 480.956866] ata5.00: error: { ICRC ABRT }
[ 480.956870] ata5: hard resetting link
[ 480.956872] ata5: nv: skipping hardreset on occupied port
[ 481.424020] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 481.448420] ata5.00: configured for UDMA/133
[ 481.448427] ata5: EH complete
[ 481.470607] ata5: EH in SWNCQ mode,QC:qc_active 0x7 sactive 0x7
[ 481.470610] ata5: SWNCQ:qc_active 0x6 defer_bits 0x1 last_issue_tag 0x2
[ 481.470611] dhfis 0x6 dmafis 0x2 sdbfis 0x1
[ 481.470613] ata5: ATA_REG 0x51 ERR_REG 0x84
[ 481.470615] ata5: tag : dhfis dmafis sdbfis sactive
[ 481.470617] ata5: tag 0x1: 1 1 0 1
[ 481.470619] ata5: tag 0x2: 1 0 0 1
[ 481.470625] ata5.00: exception Emask 0x1 SAct 0x7 SErr 0x400000 action 0x6 frozen
[ 481.470627] ata5.00: Ata error. fis:0x21
[ 481.470629] ata5: SError: { Handshk }
[ 481.470632] ata5.00: failed command: READ FPDMA QUEUED
[ 481.470636] ata5.00: cmd 60/08:00:00:01:00/00:00:00:00:00/40 tag 0 ncq 4096 in
[ 481.470638] res 51/84:28:00:00:00/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 481.470642] ata5.00: status: { DRDY ERR }
[ 481.470644] ata5.00: error: { ICRC ABRT }
[ 481.470646] ata5.00: failed command: WRITE FPDMA QUEUED
[ 481.470650] ata5.00: cmd 61/28:08:88:88:e0/00:00:e8:00:00/40 tag 1 ncq 20480 out
[ 481.470651] res 51/84:28:00:00:00/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 481.470654] ata5.00: status: { DRDY ERR }
[ 481.470656] ata5.00: error: { ICRC ABRT }
[ 481.470658] ata5.00: failed command: WRITE FPDMA QUEUED
[ 481.470662] ata5.00: cmd 61/28:10:00:00:00/00:00:00:00:00/40 tag 2 ncq 20480 out
[ 481.470663] res 51/84:28:00:00:00/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
[ 481.470665] ata5.00: status: { DRDY ERR }
[ 481.470667] ata5.00: error: { ICRC ABRT }
[ 481.470671] ata5: hard resetting link
[ 481.470672] ata5: nv: skipping hardreset on occupied port
[ 481.936094] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 481.960135] ata5.00: model number mismatch 'Hitachi HDS723020BLA642' != 'tachi HDS723020BLA642 \xffffff80\x10'
[ 481.960139] ata5.00: revalidation failed (errno=-19)
[ 481.960144] ata5.00: limiting speed to UDMA/133:PIO2
[ 486.936020] ata5: hard resetting link
[ 486.936024] ata5: nv: skipping hardreset on occupied port
[ 487.404034] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 487.412144] ata5.00: n_sectors mismatch 3907029168 != 268435455
[ 487.412148] ata5.00: old n_sectors matches native, probably late HPA lock, will try to unlock HPA
[ 487.412151] ata5.00: revalidation failed (errno=-5)
[ 487.412154] ata5.00: disabled
[ 492.404029] ata5: hard resetting link
[ 493.288057] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 493.296139] ata5.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 498.288135] ata5: hard resetting link
[ 499.168100] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 499.176442] ata5.00: ATA-8: Hitachi HDS723020BLA642, MN6OA800, max UDMA/133
[ 499.176445] ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 499.192263] ata5.00: configured for UDMA/133
[ 499.192275] sd 4:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 499.192279] sd 4:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 499.192283] Descriptor sense data with sense descriptors (in hex):
[ 499.192284] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 499.192292] 00 00 00 00
[ 499.192301] sd 4:0:0:0: [sdc] Add. Sense: Scsi parity error
[ 499.192305] sd 4:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 01 00 00 00 08 00
[ 499.192313] end_request: I/O error, dev sdc, sector 256
[ 499.192316] quiet_error: 57 callbacks suppressed
[ 499.192318] Buffer I/O error on device sdc, logical block 32
[ 499.192327] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192330] sd 4:0:0:0: killing request
[ 499.192337] sd 4:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 499.192340] sd 4:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 499.192343] Descriptor sense data with sense descriptors (in hex):
[ 499.192346] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192350]
[ 499.192351] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 499.192358] 00 00 00 00
[ 499.192361] sd 4:0:0:0: [sdc] Add. Sense: Scsi parity error
[ 499.192364] sd 4:0:0:0: [sdc] CDB: Write(10): 2a 00 e8 e0 88 88 00 00 28 00
[ 499.192370] end_request: I/O error, dev sdc, sector 3907029128
[ 499.192372] Buffer I/O error on device sdc, logical block 488378641
[ 499.192374] lost page write due to I/O error on sdc
[ 499.192378] Buffer I/O error on device sdc, logical block 488378642
[ 499.192380] lost page write due to I/O error on sdc
[ 499.192382] Buffer I/O error on device sdc, logical block 488378643
[ 499.192384] lost page write due to I/O error on sdc
[ 499.192386] Buffer I/O error on device sdc, logical block 488378644
[ 499.192388] lost page write due to I/O error on sdc
[ 499.192391] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192394] Buffer I/O error on device sdc, logical block 488378645
[ 499.192396] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192399] lost page write due to I/O error on sdc
[ 499.192405] sd 4:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 499.192408] sd 4:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
[ 499.192411] Descriptor sense data with sense descriptors (in hex):
[ 499.192412] 72 0b 47 00 00 00 00 0c 00 0a 80 00
[ 499.192419] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192421] 00 00 00 00
[ 499.192424] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192427] 00 00 00 00
[ 499.192430] sd 4:0:0:0: [sdc] Add. Sense: Scsi parity error
[ 499.192433] sd 4:0:0:0: [sdc] CDB: Write(10): 2a 00 00 00 00 00 00 00 28 00
[ 499.192439] end_request: I/O error, dev sdc, sector 0
[ 499.192441] Buffer I/O error on device sdc, logical block 0
[ 499.192442] lost page write due to I/O error on sdc
[ 499.192447] Buffer I/O error on device sdc, logical block 1
[ 499.192449] lost page write due to I/O error on sdc
[ 499.192451] Buffer I/O error on device sdc, logical block 2
[ 499.192453] lost page write due to I/O error on sdc
[ 499.192466] Buffer I/O error on device sdc, logical block 3
[ 499.192467] lost page write due to I/O error on sdc
[ 499.192479] ata5: EH complete
[ 499.192498] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192503] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192507] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192510] sd 4:0:0:0: [sdc] READ CAPACITY(16) failed
[ 499.192512] sd 4:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 499.192514] sd 4:0:0:0: [sdc] Sense not available.
[ 499.192517] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192520] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192524] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192527] sd 4:0:0:0: [sdc] READ CAPACITY failed
[ 499.192528] sd 4:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 499.192531] sd 4:0:0:0: [sdc] Sense not available.
[ 499.192536] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192542] end_request: I/O error, dev sdc, sector 0
[ 499.192548] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192553] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192557] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192561] sd 4:0:0:0: rejecting I/O to offline device
[ 499.192564] sd 4:0:0:0: [sdc] Asking for cache data failed
[ 499.192566] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 499.192571] sdc: detected capacity change from 2000398934016 to 0
[ 499.196063] ata5.00: detaching (SCSI 4:0:0:0)
[ 499.196142] sd 4:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 499.196352] sd 4:0:0:0: [sdc] Stopping disk
[ 499.196989] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 499.196993] sdc: detected capacity change from 0 to 2000398934016
[ 499.197053] ldm_validate_partition_table(): Disk read failed.
[ 499.197080] Dev sdc: unable to read RDB block 0
[ 499.197122] sdc: unable to read partition table
[ 499.871722] scsi 4:0:0:0: Direct-Access ATA Hitachi HDS72302 MN6O PQ: 0 ANSI: 5
[ 499.871907] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 499.871943] sd 4:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 499.871985] sd 4:0:0:0: [sdc] Write Protect is off
[ 499.871988] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 499.872013] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 501.738525] sdc:
[ 501.738749] sd 4:0:0:0: [sdc] Attached SCSI disk
Parece que você tem um cabo sata incorreto, um controlador sata ruim ou uma unidade defeituosa. Tente trocar os cabos primeiro. Você não tem um antigo sistema de ponte aérea com o chipset P68? Eles tinham controladores de sata defeituosos e tiveram que recuperá-los.