# Le fichier de cache des paquets est corrompu **URL:** \ **Category:** Support Debian\ **Created:** [Décembre 14, 2022, 7:43 UTC](https://www.debian-fr.org/t/le-fichier-de-cache-des-paquets-est-corrompu/87561 "2022-12-14T19:43:17Z")\ **Posts on this page:** 5\ **Page:** 2
**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\ **Post date:** [Décembre 17, 2022, 2:30 UTC](https://www.debian-fr.org/t/le-fichier-de-cache-des-paquets-est-corrompu/87561/22 "2022-12-17T02:30:59Z")
salut quand je lis dossier de cache je pense plutot à /var/lib/dpkg/info/ quand je lis `E: Erreur de lecture - read (5: Erreur d'entrée/sortie)` je pense à `fsck -f -y -v /dev/sdb` et à smart `smartctl -t long /dev/sdb` ---
**Author:** ![choops](https://www.debian-fr.org/user_avatar/www.debian-fr.org/choops/32/8109_2.png) [@choops](https://www.debian-fr.org/u/choops)\ **Post date:** [Décembre 17, 2022, 6:09 UTC](https://www.debian-fr.org/t/le-fichier-de-cache-des-paquets-est-corrompu/87561/23 "2022-12-17T06:09:50Z")
> [@Plug](#): > > `-t vxfs` Tiens ! Une nouvelle surprise (ça va faire plaisir à @Verner)… un filesystem « exotique »… des fois, il ne faut pas chercher plus loin (j’ai eu un souci avec un volume RAID 0 réalisé en btrfs au passage au kernel 6.0…) Du coup, ça raconte quoi quand tu fais: ```auto df -hT ``` (Je réalise seulement maintenant que pour une question à priori d’espace indisponible, tu n’as pas encore présenté un état de cette indisponibilité d’espace par rapport à ton partitionnement avec un `df`, ce qui permettrait d’y voir un peu plus clair) ---
**Author:** ![Plug](https://www.debian-fr.org/user_avatar/www.debian-fr.org/plug/32/12496_2.png) [@Plug](https://www.debian-fr.org/u/Plug)\ **Post date:** [Décembre 17, 2022, 1:08 UTC](https://www.debian-fr.org/t/le-fichier-de-cache-des-paquets-est-corrompu/87561/24 "2022-12-17T13:08:50Z")
> [@choops](#): > > tu n’as pas encore présenté un état de cette indisponibilité d’espace Si, je l’ai dit dans le premier post > [@Plug](#): > > J’ai un taux d’occupation du disque de 15%. > [@choops](#): > > un filesystem « exotique » Que veux-tu dire par là ? C’est du Ext4. Bon, sauf à discuter de la fiabilité de l’outil utilisé (badblocks) il semblerait que le problème soit matériel. J’ai arrêté le contrôle au bout de 9h 🤒 ``` 49188820done, 9:32:59 elapsed. (143/0/61 errors) 49188821done, 9:33:01 elapsed. (144/0/61 errors) 49188822done, 9:33:03 elapsed. (145/0/61 errors) 49188823done, 9:33:05 elapsed. (146/0/61 errors) 20.15% done, 9:33:07 elapsed. (147/0/61 errors) ``` Avec déjà pas mal d’erreurs. Je vais passer sur un forum dédié matériel et vous tiendrai informés de mes avancées. ---
**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\ **Post date:** [Décembre 17, 2022, 1:48 UTC](https://www.debian-fr.org/t/le-fichier-de-cache-des-paquets-est-corrompu/87561/25 "2022-12-17T13:48:12Z")
tu as essayé smart? en gui : gsmartcontrol ---
**Author:** ![Plug](https://www.debian-fr.org/user_avatar/www.debian-fr.org/plug/32/12496_2.png) [@Plug](https://www.debian-fr.org/u/Plug)\ **Post date:** [Décembre 17, 2022, 2:43 UTC](https://www.debian-fr.org/t/le-fichier-de-cache-des-paquets-est-corrompu/87561/26 "2022-12-17T14:43:58Z")
Oui. En revanche le gui n’est pas le plus adapté, vu que je suis en console de récupération 😕 Voilà le premier résultat que j’avais obtenu : ``` root@Debian:~# smartctl -a /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-18-amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar SE Serial ATA Device Model: WDC WD2500JS-60NCB1 Serial Number: WD-WCANK7476328 Firmware Version: 10.02E02 User Capacity: 250 059 350 016 bytes [250 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7 (minor revision not indicated) Local Time is: Wed Dec 14 01:44:27 2022 CET 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 8280) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 96) minutes. Conveyance self-test routine recommended polling time: ( 6) minutes. SCT capabilities: (0x103f) 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 0x000f 200 200 051 Pre-fail Always - 73 3 Spin_Up_Time 0x0003 218 188 021 Pre-fail Always - 4058 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2681 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 13144 10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2575 190 Airflow_Temperature_Cel 0x0022 052 042 045 Old_age Always In_the_past 48 194 Temperature_Celsius 0x0022 102 092 000 Old_age Always - 48 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 199 199 000 Old_age Always - 50 198 Offline_Uncorrectable 0x0010 199 199 000 Old_age Offline - 50 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline - 13 SMART Error Log Version: 1 ATA Error Count: 252 (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 252 occurred at disk power-on lifetime: 13143 hours (547 days + 15 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 -- -- -- -- -- -- -- 40 51 10 4f 2c 3f 40 Error: UNC at LBA = 0x003f2c4f = 4140111 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 88 48 2c 3f 07 08 00:27:17.679 READ FPDMA QUEUED ef 10 02 00 00 00 00 00 00:27:17.675 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 00 00 00:27:17.675 IDENTIFY DEVICE ef 03 45 00 00 00 00 00 00:27:17.675 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 00 00 00:27:17.675 SET FEATURES [Enable SATA feature] Error 251 occurred at disk power-on lifetime: 13143 hours (547 days + 15 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 -- -- -- -- -- -- -- 40 51 80 4f 2c 3f 40 Error: UNC at LBA = 0x003f2c4f = 4140111 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 08 48 2c 3f 07 08 00:27:15.710 READ FPDMA QUEUED 60 08 00 40 2c 3f 07 08 00:27:15.710 READ FPDMA QUEUED 60 08 f0 38 2c 3f 07 08 00:27:15.710 READ FPDMA QUEUED 60 08 e8 30 2c 3f 07 08 00:27:15.710 READ FPDMA QUEUED 60 08 e0 28 2c 3f 07 08 00:27:15.710 READ FPDMA QUEUED Error 250 occurred at disk power-on lifetime: 13143 hours (547 days + 15 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 -- -- -- -- -- -- -- 40 51 01 4f 2c 3f 40 Error: UNC at LBA = 0x003f2c4f = 4140111 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 78 60 2b 3f 07 08 00:27:13.677 READ FPDMA QUEUED 60 00 70 60 2a 3f 07 08 00:27:13.675 READ FPDMA QUEUED 60 00 68 60 29 3f 07 08 00:27:13.673 READ FPDMA QUEUED 60 00 60 60 28 3f 07 08 00:27:13.671 READ FPDMA QUEUED 60 00 58 60 27 3f 07 08 00:27:13.668 READ FPDMA QUEUED Error 249 occurred at disk power-on lifetime: 13143 hours (547 days + 15 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 af 87 94 45 Error: UNC at LBA = 0x059487af = 93620143 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 12 ae 87 94 05 00 00:10:36.582 READ DMA c8 00 2e 80 87 94 05 00 00:10:36.582 READ DMA c8 00 11 6f 87 94 05 00 00:10:36.581 READ DMA c8 00 2f 40 87 94 05 00 00:10:36.581 READ DMA c8 00 10 30 87 94 05 00 00:10:36.581 READ DMA Error 248 occurred at disk power-on lifetime: 13142 hours (547 days + 14 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 af 87 94 45 Error: UNC at LBA = 0x059487af = 93620143 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 12 ae 87 94 05 00 00:00:44.465 READ DMA c8 00 2e 80 87 94 05 00 00:00:44.465 READ DMA c8 00 11 6f 87 94 05 00 00:00:44.464 READ DMA c8 00 2f 40 87 94 05 00 00:00:44.464 READ DMA c8 00 10 30 87 94 05 00 00:00:44.463 READ DMA 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. ``` [Page précédente](https://www.debian-fr.org/t/le-fichier-de-cache-des-paquets-est-corrompu/87561.md?page=1)