Bonjour,
Il semblerait que ma debian n'a pas apprécié un arrêt un peu brutal.
En effet, le fsck échoue sur une de mes partitions:
"fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/mapper/debian-var. Could this be a zero-length partition?"
En fait, j'ai un volume LVM avec mes différentes partitions: var, home, tmp, etc.
J'ai essayé plusieurs commandes fsck différentes (-b xxx) mais cela a échoué.
J'ai essayé de copier via dd la partition en question mais cela a aussi échoué.
Est-ce que quelqu'un aurait une idée ?
Merci de vos réponses.
# Disque en train de crever ?
Posté par benoar . Évalué à 2.
[^] # Re: Disque en train de crever ?
Posté par sifu . Évalué à 1.
smartctl version 5.38 [i486-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint P120 series
Device Model: SAMSUNG SP2504C
Serial Number: S09QJ1ML906188
Firmware Version: VT100-41
User Capacity: 250,059,350,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Tue Jan 20 21:27:56 2009 UTC
==> WARNING: May need -F samsung3 enabled; see manual for details.
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x02) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: (4935) 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: ( 82) minutes.
SCT capabilities: (0x003f) SCT Status 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 253 253 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0007 100 100 025 Pre-fail Always - 5888
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 976
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1923
10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always - 0
11 Calibration_Retry_Count 0x0012 253 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 640
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 66772
190 Airflow_Temperature_Cel 0x0022 154 154 000 Old_age Always - 28
194 Temperature_Celsius 0x0022 154 154 000 Old_age Always - 28
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 84781
196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 253 253 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0
202 TA_Increase_Count 0x0032 253 253 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 1218 (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 1218 occurred at disk power-on lifetime: 1923 hours (80 days + 3 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 08 f8 6b 5c e0 Error: UNC 8 sectors at LBA = 0x005c6bf8 = 6056952
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 08 f8 6b 5c e0 00 01:45:48.438 READ DMA
ec 00 00 00 00 00 a0 00 01:45:46.750 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:45:46.750 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 01:45:46.750 IDENTIFY DEVICE
Error 1217 occurred at disk power-on lifetime: 1923 hours (80 days + 3 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 08 f8 6b 5c e0 Error: UNC 8 sectors at LBA = 0x005c6bf8 = 6056952
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 08 f8 6b 5c e0 00 01:45:46.625 READ DMA
ec 00 00 00 00 00 a0 00 01:45:44.938 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:45:44.938 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 01:45:44.938 IDENTIFY DEVICE
Error 1216 occurred at disk power-on lifetime: 1923 hours (80 days + 3 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 08 f8 6b 5c e0 Error: UNC 8 sectors at LBA = 0x005c6bf8 = 6056952
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 08 f8 6b 5c e0 00 01:45:44.875 READ DMA
ec 00 00 00 00 00 a0 00 01:45:43.125 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:45:43.125 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 01:45:43.125 IDENTIFY DEVICE
Error 1215 occurred at disk power-on lifetime: 1923 hours (80 days + 3 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 08 f8 6b 5c e0 Error: UNC 8 sectors at LBA = 0x005c6bf8 = 6056952
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 08 f8 6b 5c e0 00 01:45:43.063 READ DMA
ec 00 00 00 00 00 a0 00 01:45:41.375 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:45:41.313 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 01:45:41.313 IDENTIFY DEVICE
Error 1214 occurred at disk power-on lifetime: 1923 hours (80 days + 3 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 08 f8 6b 5c e0 Error: UNC 8 sectors at LBA = 0x005c6bf8 = 6056952
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 08 f8 6b 5c e0 00 01:45:41.250 READ DMA
ec 00 00 00 00 00 a0 00 01:45:39.563 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:45:39.563 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 01:45:39.500 IDENTIFY DEVICE
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 1922 6056952
# 2 Short offline Completed: read failure 90% 1922 6056952
SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1
SMART Selective self-test log data structure revision number 0
Warning: ATA Specification requires 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.
Il semble y avoir effectivement des erreurs mais je ne sais pas quoi faire.
[^] # Re: Disque en train de crever ?
Posté par benoar . Évalué à 2.
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 66772
[...]
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 84781
et les messages après à propos des erreurs de lecture et le message :
Error: UNC 8 sectors at LBA
La solution : faire tout de suite une sauvegarde du disque, même "brute", si tu n'arrives pas à monter correctement les partitions. Et ensuite, tu vas racheter un nouveau disque ...
[^] # Re: Disque en train de crever ?
Posté par benoar . Évalué à 2.
smartctl -t long /dev/...
pour voir s'il te renvoit beaucoup d'erreurs ou non, mais bon, ce n'est jamais très rassurant de continuer à utiliser un disque qui flanche de temps à autres.
[^] # Re: Disque en train de crever ?
Posté par niclone (site web personnel) . Évalué à 2.
dd devrait pouvoir te permettre de sauvegarder tes partitions en brut, notament avec l'option "noerror", tu pourra ensuite tenter des fsck dessus.
Si tu es courageux, et que tu veux mal grès tout garder ce disque, peut être cette méthode t'aidera :
http://smartmontools.sourceforge.net/badblockhowto.html
[^] # Re: Disque en train de crever ?
Posté par sifu . Évalué à 1.
J'ai tenté ce tuto http://smartmontools.sourceforge.net/badblockhowto.html avant hier et cela n'a pas fonctionné. J'ai eu des erreurs inédites !
Je vais essayer de faire une sauvegarde avec dd de ce qui peut encore l'être.
Ce qui est étrange c'est que le problème semble se poser uniquement sur une partition alors que tous est sur le même disque ...
Je vous tiens au courant.
A bientôt et encore merci !
# LVM
Posté par fcartegnie . Évalué à 3.
lvm pvck
[^] # Re: LVM
Posté par sifu . Évalué à 1.
Finding all volume groups
/dev/dm-0: read failed after 0 of 4096 at 0: Input/output error
Finding volume group "debian"
Fixing up missing size (230.00 GB) for PV /dev/sdb7
Et après, j'ai toujours le même problème.
Suivre le flux des commentaires
Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.