Disque dur en lecture seule
... / Disque dur en lecture seule
< Question précédente   -   Question suivante >
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
question

Disque dur en lecture seule

F
Par
FredericL5
Créé le 2019-02-01 22:50:32 (edited on 2024-09-04 12:11:46) dans Serveurs Dédiés-old

Bonjour,

Je dispose d'un serveur de stockage (processeur arm) sur lequel j'ai installé la distribution Debian.

Le problème que je rencontre est qu'au bout d'un certain temps de fonctionnement, le serveur met le disque dur en lecture seul. Autrement dit, je n'ai plus les droits pour écrire de nouveaux fichiers, modifier un fichier (par exemple charger les droits du fichiers) ou supprimer le fichier.

Exemple si je veux créer un nouveau dossier (je précise que j'utilise un compte root) : mkdir: cannot create directory '/var/lib/php/test': Read-only file system

Cela a pour conséquence que phpMyAdmin ne va plus fonctionner car il a besoin d'écrire dans un dossier de sessions. De la même façon, je n'ai plus accès à ISPConfig.

Actuellement, la seule solution que j'ai trouvé quand j'ai besoin d'utiliser le serveur, c'est de faire un reboot.

Est-ce que quelqu'un aurait une idée du problème et comment le résoudre ? Merci d'avance.
Avis positifs (0)
3006 Vues
8 réponses ( Latest reply on 2019-02-10 23:22:20 Par
)

Si le disque passe en lecture seule c'est probablement qu'il y'a des erreurs...
Il faudrait probablement redémarrer en rescue pour faire les tests qui vont bien.

Et probablement prévoir de sauvegarder les données pour changer le disque par la suite...
Utile (0)


Read-only file system


Sous une console avec le user root: fais la commande suivante:
# smartctl -a /dev/sda

Les lignes les plus intéressantes sont dans ce bloc-ci:

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 136 136 054 Pre-fail Offline - 106
3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 0
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 7
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 128 128 020 Pre-fail Offline - 18
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 5446
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 7
192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 2002
193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 2002
194 Temperature_Celsius 0x0002 157 157 000 Old_age Always - 38 (Min/Max 22/46)
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 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

Frédéric
Utile (0)

Excusez moi d'avoir tardé à répondre mais je reviens de province.

Ce n'est que très récemment que j'ai fait l'acquisition de ce serveur et j'avoue que je n'ai jamais pris le temps de vérifier l'état du disque dur.





J'ai reçu le mail suivant venant de mon serveur :
[quote]Subject: SMART error (CurrentPendingSector) detected
This message was generated by the smartd daemon running on:
The following warning/error was logged by the smartd daemon:
Device: /dev/sda [SAT], 59 Currently unreadable (pending) sectors
Device info:
HGST HUS726040ALA610, S/N:K4GMNP7B, WWN:5-000cca-25dc8f0b3, FW:A5GNT920, 4.00 TB
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.[/quote]

Pour ce qui est de Smartmontools :
[quote]root@ns3123593:~# smartctl -a /dev/sda
smartctl 6.6 2016-05-31 r4324 [armv7l-linux-4.5.2-armada375] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: HGST HUS726040ALA610
Serial Number: K4GMNP7B
LU WWN Device Id: 5 000cca 25dc8f0b3
Firmware Version: A5GNT920
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Feb 4 00:28:49 2019 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

General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: ( 113) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 571) 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 099 099 016 Pre-fail Always - 65537
2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 108
3 Spin_Up_Time 0x0007 206 206 024 Pre-fail Always - 243 (Average 275)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 36
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 397
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 128 128 020 Pre-fail Offline - 18
9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 15194
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 36
192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 1766
193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 1766
194 Temperature_Celsius 0x0002 146 146 000 Old_age Always - 41 (Min/Max 15/86)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 397
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 59
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 77
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 4813 (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 4813 occurred at disk power-on lifetime: 15194 hours (633 days + 2 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 41 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0

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 e0 78 28 14 80 40 08 32d+01:47:21.901 READ FPDMA QUEUED
60 08 a8 28 17 00 40 08 32d+01:47:19.153 READ FPDMA QUEUED
60 08 a0 20 17 00 40 08 32d+01:47:19.153 READ FPDMA QUEUED
60 08 98 18 17 00 40 08 32d+01:47:19.153 READ FPDMA QUEUED
60 08 90 10 17 00 40 08 32d+01:47:19.152 READ FPDMA QUEUED

Error 4812 occurred at disk power-on lifetime: 15194 hours (633 days + 2 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 41 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0

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 68 28 14 80 40 08 32d+01:47:11.593 READ FPDMA QUEUED
60 00 60 00 ca 3f 40 08 32d+01:47:09.192 READ FPDMA QUEUED
60 00 58 d8 06 69 40 08 32d+01:47:09.158 READ FPDMA QUEUED
60 00 50 78 55 69 40 08 32d+01:47:08.639 READ FPDMA QUEUED
60 08 48 90 14 80 40 08 32d+01:47:08.499 READ FPDMA QUEUED

Error 4811 occurred at disk power-on lifetime: 15193 hours (633 days + 1 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 41 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0

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 b0 88 7f 64 40 00 32d+01:36:41.693 READ FPDMA QUEUED
60 00 a8 00 d6 c9 40 00 32d+01:36:38.927 READ FPDMA QUEUED
60 00 a0 00 d5 c9 40 00 32d+01:36:38.926 READ FPDMA QUEUED
60 00 98 00 d4 c9 40 00 32d+01:36:38.926 READ FPDMA QUEUED
60 00 90 00 d3 c9 40 00 32d+01:36:38.923 READ FPDMA QUEUED

Error 4810 occurred at disk power-on lifetime: 15193 hours (633 days + 1 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 41 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0

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 28 88 7f 64 40 00 32d+01:36:37.292 READ FPDMA QUEUED
60 08 d8 88 11 c1 40 00 32d+01:36:35.238 READ FPDMA QUEUED
60 00 88 00 fc f8 40 00 32d+01:36:34.563 READ FPDMA QUEUED
60 00 80 a0 19 76 40 00 32d+01:36:34.563 READ FPDMA QUEUED
60 08 78 38 31 76 40 00 32d+01:36:34.563 READ FPDMA QUEUED

Error 4809 occurred at disk power-on lifetime: 15193 hours (633 days + 1 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 41 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0

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 f0 88 7f 64 40 00 32d+01:36:33.600 READ FPDMA QUEUED
60 08 e8 80 7f 64 40 00 32d+01:36:30.684 READ FPDMA QUEUED
60 08 e0 78 7f 64 40 00 32d+01:36:30.684 READ FPDMA QUEUED
60 08 d8 70 7f 64 40 00 32d+01:36:30.684 READ FPDMA QUEUED
60 08 d0 68 7f 64 40 00 32d+01:36:30.684 READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed without error 00% 13127 -
2 Short offline Completed without error 00% 13107 -
3 Short offline Completed without error 00% 13107 -
4 Short offline Completed without error 00% 13098 -
5 Short offline Completed without error 00% 13083 -
6 Short offline Completed without error 00% 12 -
7 Short offline Completed without error 00% 10 -
8 Short offline Completed without error 00% 10 -
9 Short offline Completed without error 00% 8 -
10 Short offline Completed without error 00% 7 -
11 Short offline Completed without error 00% 7 -
12 Short offline Completed without error 00% 2 -
13 Short offline Completed without error 00% 0 -
14 Short offline Completed without error 00% 0 -

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.[/quote]

J'ai fait le test juste après avoir redémarré mon serveur et donc, le disque dur était opérationnel. Peut être que le résultat aurait été différent si je l'avais fait quand le disque dur est en read only.

Si vous pensez que c'est mon disque dur qui est en train de mourir, je le signalerai à OVH. J'ai déjà eu 2 disques durs OVH qui sont tombés en panne mais ils ne s'étaient pas mis en read only.

Encore merci pour l'aide que vous m'apportez.
Utile (0)


Device: /dev/sda [SAT], 59 Currently unreadable (pending) sectors


Faut faire tes backups et demander à OVH de changer le disque...
Utile (0)

Merci, c'est ce que je vais faire.
A titre informatif, je vous dirai la réponse d'OVH à ma demande.
Utile (0)

Le service client d'OVH m'a fait effectuer divers tests et il a conclu qu'il y avait bien un problème matériel avec le disque dur. J'ai donc le droit de demander son remplacement. Je le ferai une fois que j'aurai trouvé une solution de stockage pour mes 3 To de données.
Utile (0)
K

ça explique aussi les erreurs de commandes système que tu n'avais pas (apt) dernièrement?
Utile (0)

Je ne sais pas mais cela serait une bonne nouvelle si c'était le cas. Quand le disque dur aura été changé, je ferai des essais pour tout réinstaller correctement.
Utile (0)

Sujets apparentés

Rejoindre la discussion