ledube

Salut, Pour moi maj hier soir de mon RS3614RPxs et ce matin plus d’accès... 2015-05-13 09:42:22 Error RProd_NAS user System SYSTEM: Failed to send email. (Failed to resolve host address.). 2015-05-13 09:42:01 Warning RProd_NAS user System SYSTEM: System booted up from an improper shutdown. 2015-05-13 09:41:57 Information RProd_NAS user System SYSTEM: Local UPS was plugged in. 2015-05-13 09:41:56 Information RProd_NAS user System SYSTEM: System started to boot up. Pas de coupure de courant... Inexplicable... je n'aime pas trop ca... séb (dsl la mise en forme du tableau a disparue) PS : https://forum.synology.com/enu/viewtopic.php?f=256&t=100466

Direction SAV. Merci à tous !

Salut, Pour badblocks, pas d'erreurs. Par contre un smartctl me donne : Toujours la ligne 183 run time badblock à 4 ainsi que #2 Extended offline Completed: / read failure / 40% / 617heures / LBA 1st error 585688042 Que penser... Merci

J'ai un disque neuf de commandé. Celui ci va partir en SAV après les tests. Je me disais qu'en prenant des disques RE je serais tranquille.... j'avais tord...

Pas de veille activée. Je vais essayer badblocks -nvs ; je vous tiens au courant.

Bonjour, J'ai dans un RS3614RPxs 6 disques WD4000FYYZ-01UL1B2 en Raid 6. Lors de la création du volume, j'ai sélectionné la version lente (celle qui à priori vérifie toute la surface du disque) en pensant qu'elle était équivalente à une préparation par dd. Malheureusement, il y a quelques jours : 2015/03/29 16:41:13 SYSTEM: Write error at internal disk [1] sector 2193448. Résultat, éjection du hd de la grappe raid, mode dégradé et tout le tralala... L'assistance syno me répond : So it is a disk failure, please replace it, thank you. Donc, je récupère le disque et le passe par l'utilitaire WD. Smart test rapide --> ok Smart test complet --> ok Write 0 --> ok Les résultats de smartctr smartctl 6.3 2014-07-26 r3976 [x86_64-w64-mingw32-win7-sp1] (sf-6.3-1) Copyright © 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === 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 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 4658 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 19 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 665 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 096 096 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 48 194 Temperature_Celsius 0x0022 122 104 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 ********************************************************************************************************************************************************************************************************************************** smartctl 6.3 2014-07-26 r3976 [x86_64-w64-mingw32-win7-sp1] (sf-6.3-1) Copyright © 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 253 253 021 - 4658 4 Start_Stop_Count -O--CK 100 100 000 - 19 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 100 100 000 - 665 10 Spin_Retry_Count -O--CK 100 253 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 4 183 Runtime_Bad_Block -O--CK 096 096 000 - 4 192 Power-Off_Retract_Count -O--CK 200 200 000 - 2 193 Load_Cycle_Count -O--CK 200 200 000 - 48 194 Temperature_Celsius -O---K 122 104 000 - 30 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning ********************************************************************************************************************************************************************************************************************* smartctl 6.3 2014-07-26 r3976 [x86_64-w64-mingw32-win7-sp1] (sf-6.3-1) Copyright © 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Error Log Version: 1 ATA Error Count: 81 (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 81 occurred at disk power-on lifetime: 617 hours (25 days + 17 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 -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 00 24d+23:06:02.971 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:02.970 IDENTIFY DEVICE ef 03 45 00 00 00 a0 00 24d+23:06:02.970 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 00 24d+23:06:02.965 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:02.964 IDENTIFY DEVICE Error occurred at disk power-on lifetime: 617 hours (25 days + 17 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 -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 00 24d+23:06:02.970 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 00 24d+23:06:02.965 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:02.964 IDENTIFY DEVICE ef 10 02 00 00 00 a0 00 24d+23:06:00.659 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:00.658 IDENTIFY DEVICE Error 79 occurred at disk power-on lifetime: 617 hours (25 days + 17 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 -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 00 24d+23:06:02.965 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:02.964 IDENTIFY DEVICE ef 10 02 00 00 00 a0 00 24d+23:06:00.659 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:00.658 IDENTIFY DEVICE ef 03 45 00 00 00 a0 00 24d+23:06:00.658 SET FEATURES [set transfer mode] Error 78 occurred at disk power-on lifetime: 617 hours (25 days + 17 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 -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 00 24d+23:06:00.659 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:00.658 IDENTIFY DEVICE ef 03 45 00 00 00 a0 00 24d+23:06:00.658 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 00 24d+23:06:00.652 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:00.651 IDENTIFY DEVICE Error 77 occurred at disk power-on lifetime: 617 hours (25 days + 17 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 -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 00 24d+23:06:00.658 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 00 24d+23:06:00.652 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:06:00.651 IDENTIFY DEVICE ef 10 02 00 00 00 a0 00 24d+23:05:58.347 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 00 24d+23:05:58.346 IDENTIFY DEVICE **************************************************************************************************************************************************************************************************************************** A votre avis, hd défectueux (donc SAV) ou pas (donc préparation par dd et remise en service) ? Un grand merci ! Sébastien

Bonjour à tous, Petite question aux utilisateurs de Raid 5 ou 6, lors des accès disques, est-ce que vos led HD s'allument et s'éteignent de manière synchro ? Chez moi (trois WD1.5 Green sur 409+), elles sont synchros, mais régulièrement la led n°3 clignotent toute seule pendant quelques secondes, comme si le HD avait pris du retard. De plus, j'ai l'impression que cela créé des ralentissements sur le NAS lors de ces accès solitaires. J'avais le même problème en raid 6 avec 4 HD (mais cette fois avec la led 4). Merci

Bonjour, Approche toi du NAS, entends tu les HD s'arreter puis redemarrer ? Séb

Nouvelle alim arrivée, tout refonctionne pour le moment...

Bonjour, Est ce que l alimentation que je cite en r

Bonjour à tous ! Voila je possède un 409+ avec 4 hd wd 1.5 To green EADS en raid 6 (plus garanti évidemment). Il y a quelques mois, gros bug. Une des led hd éteinte (HD3)... impossible de redémarrer, etc... Je récupère ms données sur un pc linux (bien que j'ai une autre sauvegarde sur un autre syno) en branchant les disques et à l'aide de mdadm, je repasse les 4 disques à la commande dd et réinstalle le tout. Il y a deux jours, rebelote... Je démonte le nas, retire les hs, en efface un et le remet... NAS accessible mais je constate des redémarrages réguliers (arrêt moteur puis relance)... Je retire le hd, le met sur mon pc, pas de prb... Je tente l'expérience avec le second hd... Idem... Donc trois possibilités d'après moi : 1- Quatre hd hs... bizarre quand même car ils fonctionnent sur PC (même si un m'a l'air fatigué, lorsque le syno fonctionnait la led HD4 était toujours entraint de clignoter quand les autres étaient syncro) 2- NAS hs... le test de la carte mère est ok. 3- alim faible... A priori un problème récurent chez syno... achat ?? http://www.webducomm...CFQELfAodqSeQvQ Ci joint une partie du fichier log après reinstall : (truffé de ligne de ce style) Jan 29 14:02:09 kernel: [ 1344.045540] ata1.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x190002 action 0xe frozen Jan 29 14:02:09 kernel: [ 1344.053730] ata1.00: edma_err_cause=020000a8 pp_flags=00000003, dev disconnect, EDMA self-disable, S Jan 29 14:02:09 kernel: [ 1344.062868] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar } Jan 29 14:02:09 kernel: [ 1344.068703] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:09 kernel: [ 1344.073937] ata1.00: cmd 61/00:00:d8:9a:90/04:00:97:00:00/40 tag 0 ncq 524288 out Jan 29 14:02:09 kernel: [ 1344.073941] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:09 kernel: [ 1344.089418] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:09 kernel: [ 1344.094035] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:09 kernel: [ 1344.099268] ata1.00: cmd 61/00:08:d8:9e:90/04:00:97:00:00/40 tag 1 ncq 524288 out Jan 29 14:02:09 kernel: [ 1344.099272] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:09 kernel: [ 1344.114750] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:09 kernel: [ 1344.119366] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:09 kernel: [ 1344.124599] ata1.00: cmd 61/00:10:d8:a2:90/04:00:97:00:00/40 tag 2 ncq 524288 out Jan 29 14:02:16 kernel: [ 1344.124603] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.140083] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.144699] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.149932] ata1.00: cmd 61/00:18:d8:a6:90/04:00:97:00:00/40 tag 3 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.149937] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.165413] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.170030] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.175263] ata1.00: cmd 61/00:20:d8:aa:90/04:00:97:00:00/40 tag 4 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.175267] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.190746] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.195360] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.200593] ata1.00: cmd 61/00:28:d8:ae:90/04:00:97:00:00/40 tag 5 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.200598] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.216077] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.220693] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.225927] ata1.00: cmd 61/00:30:d8:b2:90/04:00:97:00:00/40 tag 6 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.225931] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.241408] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.246024] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.251257] ata1.00: cmd 61/00:38:d8:b6:90/04:00:97:00:00/40 tag 7 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.251261] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.266739] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.271354] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.276587] ata1.00: cmd 61/00:40:d8:ba:90/04:00:97:00:00/40 tag 8 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.276591] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.292071] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.296688] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.301921] ata1.00: cmd 61/00:48:d8:be:90/04:00:97:00:00/40 tag 9 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.301925] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.317402] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.322018] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.327251] ata1.00: cmd 61/00:50:d8:c2:90/04:00:97:00:00/40 tag 10 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.327255] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.342821] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.347435] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.352670] ata1.00: cmd 61/00:58:d8:c6:90/04:00:97:00:00/40 tag 11 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.352674] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.368237] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.372854] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.378086] ata1.00: cmd 61/00:60:d8:ca:90/04:00:97:00:00/40 tag 12 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.378091] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.393657] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.398271] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.403504] ata1.00: cmd 61/00:68:d8:ce:90/04:00:97:00:00/40 tag 13 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.403508] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.419074] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.423690] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.428923] ata1.00: cmd 61/00:70:d8:d2:90/04:00:97:00:00/40 tag 14 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.428927] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.444492] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.449108] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.454341] ata1.00: cmd 61/00:78:d8:5a:90/04:00:97:00:00/40 tag 15 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.454345] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.469911] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.474525] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.479760] ata1.00: cmd 61/00::d8:5e:90/04:00:97:00:00/40 tag 16 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.479764] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.495328] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.499944] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.505177] ata1.00: cmd 61/00:88:d8:62:90/04:00:97:00:00/40 tag 17 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.505181] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.520747] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.525362] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.530594] ata1.00: cmd 61/00:90:d8:66:90/04:00:97:00:00/40 tag 18 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.530599] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.546164] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.550780] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.556013] ata1.00: cmd 61/00:98:d8:6a:90/04:00:97:00:00/40 tag 19 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.556017] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.571581] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.576198] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.581431] ata1.00: cmd 61/00:a0:d8:6e:90/04:00:97:00:00/40 tag 20 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.581435] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.597000] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.601617] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.606850] ata1.00: cmd 61/00:a8:d8:72:90/04:00:97:00:00/40 tag 21 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.606854] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.622417] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.627033] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.632267] ata1.00: cmd 61/00:b0:d8:76:90/04:00:97:00:00/40 tag 22 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.632272] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.647835] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.652450] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.657684] ata1.00: cmd 61/00:b8:d8:7a:90/04:00:97:00:00/40 tag 23 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.657689] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.673251] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.677867] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.683099] ata1.00: cmd 61/00:c0:d8:7e:90/04:00:97:00:00/40 tag 24 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.683104] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.698669] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.703283] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.708516] ata1.00: cmd 61/00:c8:d8:82:90/04:00:97:00:00/40 tag 25 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.708520] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.724085] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.728702] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.733934] ata1.00: cmd 61/00:d0:d8:86:90/04:00:97:00:00/40 tag 26 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.733939] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.749501] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.754117] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.759349] ata1.00: cmd 61/00:d8:d8:8a:90/04:00:97:00:00/40 tag 27 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.759354] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.774918] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.779533] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.784767] ata1.00: cmd 61/00:e0:d8:8e:90/04:00:97:00:00/40 tag 28 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.784771] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.800334] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.804953] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.810186] ata1.00: cmd 61/00:e8:d8:92:90/04:00:97:00:00/40 tag 29 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.810190] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.825755] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1344.830373] ata1.00: failed command: WRITE FPDMA QUEUED Jan 29 14:02:17 kernel: [ 1344.835606] ata1.00: cmd 61/00:f0:d8:96:90/04:00:97:00:00/40 tag 30 ncq 524288 out Jan 29 14:02:17 kernel: [ 1344.835610] res 7f/00:6c:d8:ce:90/00:00:97:00:00/40 Emask 0x12 (ATA bus error) Jan 29 14:02:17 kernel: [ 1344.851176] ata1.00: status: { DRDY DF DRQ ERR } Jan 29 14:02:17 kernel: [ 1350.782618] ata1: link is slow to respond, please be patient (ready=0) Jan 29 14:03:15 mkfs.ext4: (write_inode_tables) write cache is 1 ... Jan 29 14:03:49 synoindex: synoindex.c (486) Indexing daemon is not running Jan 29 14:03:56 synoindexd: photo_index.c (1067) Failed to read link of /var/services/photo Jan 29 14:03:57 synoindexd: photo_share.c (1015) Failed to read link of /var/services/photo Jan 29 14:03:59 kernel: [ 1454.875782] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen Jan 29 14:03:59 kernel: [ 1454.883098] ata1: edma_err_cause=000000a8 pp_flags=00000003, dev disconnect, EDMA self-disable, S Jan 29 14:03:59 kernel: [ 1454.891975] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar } Jan 29 14:04:05 kernel: [ 1460.824619] ata1: link is slow to respond, please be patient (ready=0) Jan 29 14:05:26 kernel: [ 1542.044109] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen Jan 29 14:05:26 kernel: [ 1542.051426] ata1: edma_err_cause=00000028 pp_flags=00000000, dev disconnect, SError=00190002 Jan 29 14:05:26 kernel: [ 1542.059870] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar } Jan 29 14:05:32 kernel: [ 1547.992616] ata1: link is slow to respond, please be patient (ready=0) Jan 29 14:05:58 kernel: [ 1574.589750] ata1: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen Jan 29 14:05:58 kernel: [ 1574.597068] ata1: edma_err_cause=00000028 pp_flags=00000000, dev disconnect, SError=00190002 Jan 29 14:05:58 kernel: [ 1574.605509] ata1: SError: { RecovComm PHYRdyChg 10B8B Dispar } Jan 29 14:06:04 kernel: [ 1580.537618] ata1: link is slow to respond, please be patient (ready=0) Un grand merci pour vos avis éclairés !! Séb

Bonjour

Regarde de nouveau les param

Wdidle configure les paramètres internes du hd ; un formatage n'y changera rien. Là, tu es en face d'une usure physique des disques, c'est irrattrapable. Sinon, j'ai moi meme des wd green sur mes syno ; une fois la manip effectuée; l'ensemble est très fiable. Télécharge wdidl, branche un des hd sur un pc et effectue la manip ; idem pour le second ; ca stoppera l'hémorragie. séb Edit : Décidement je me fais griller par tout le monde aujourd'hui

wdidle est un utilitaire qui marche sous dos et qui permet de d

les lcc sont trop grand = tes (les deux) hd vont planter !!!!! SAUVEGARDE TOUT DE SUITE SUR UN HD EXTERNE!!!!!!!!! EDIT : grilled par jac2904 !!

Bonjour, C'est quoi comme Raid ?? Miroir (raid 1) j'espère ! J'ai l'impression que ca sent le disque qui va bientôt rendre l'âme !! Sauvegarde immédiatement tes données puis regarde le statut smart de ce disque. Au moment où la led se rallume, entends tu le moteur du disque se relancer ? Séb

Bonjour

Ok, merci. Je viens de lancer une sauvegarde sur un disque usb branch

Bonjour, Je poss

Merci pour ta r