Bonjour,
Je retrouve ce matin un serveur (Debian fraichement passé en Stretch il y a une semaine) avec la partition root passée en read-only. Un reboot hard a résolu le problème et les services WEB semblent répondre correctement mais ma question est :
Qu'est-ce qui peut faire passer une partition système en read-only ?
J'ai fait un check disk en mode rescue avant de rebooter qui n'a remonté aucune erreur.
Lors de l'upgrade debian 8 vers 9 j'avais noté ces messages d'erreur concernent le kernel:
update-initramfs: Generating /boot/initrd.img-4.9.148-xxxx-std-ipv6-64
WARNING: missing /lib/modules/4.9.148-xxxx-std-ipv6-64
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.9.148-xxxx-std-ipv6-64: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
depmod: WARNING: could not open /var/tmp/mkinitramfs_I6Juxi/lib/modules/4.9.148-xxxx-std-ipv6-64/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_I6Juxi/lib/modules/4.9.148-xxxx-std-ipv6-64/modules.builtin: No such file or directory
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Mais les services WEB semblant fonctionner correctement j'avais seulement signalé ces messages d'erreur au support technique OVH qui m'a répondu une semaine plus tard, je cite:
> Votre serveur est démarré sur disque.
> Le souci est-il toujours d'actualité?
Je passe donc sur le forum dans l'espoir d'avoir des indications tangibles. Merci pour votre aide.
/dev/sda1 passé en read only
Sujets apparentés
- Port 25 bloqué pour spam à répétition
10335
28.02.2018 13:39
- Spam et IP bloquée
8389
12.12.2016 11:53
- Rkhunter : parametre web_CMD invalide
8143
23.07.2017 15:43
- Mise à jour PHP sur Release 3 ovh
8067
11.03.2017 17:43
- Mise en place de VM avec IP publique sur Proxmox 6 [RESOLU]
8034
30.04.2020 17:12
- Connection smtp qui ne marche plus : connect error 10060
7983
12.04.2019 10:10
- Partition sur le disque de l'OS ESXI
7923
09.05.2017 14:33
- Envoi demail bloqué chez Gmail (550-5.7.26 DMARC)
7688
23.12.2019 08:40
- Meilleure solution pour disposer de plusieurs IP ?
7400
29.07.2018 09:40
- Comment me connecter par SSH en tant que root à mon serveur ?
6880
09.09.2019 14:34
Les partitions passent en read-only quand une opération d'écriture s'est mal passée.
Généralement, ça indique un problème physique.
smartctl devrait permettre d'y voir plus clair.
Les check disk en rescue ne sont pas déjà sensés remonter les dysfonctionnements ?
Voici le rapport de smartctl
> # smartctl -a /dev/sda1
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.148-xxxx-std-ipv6-64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
> === START OF INFORMATION SECTION ===
> Model Family: Seagate Barracuda 7200.12
> Device Model: ST31000524AS
> Serial Number: 6VPBM7JE
> LU WWN Device Id: 5 000c50 032cc4958
> Firmware Version: JC45
> User Capacity: 1,000,204,886,016 bytes [1.00 TB]
> Sector Size: 512 bytes logical/physical
> Rotation Rate: 7200 rpm
> Device is: In smartctl database [for details use: -P show]
> ATA Version is: ATA8-ACS T13/1699-D revision 4
> SATA Version is: SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
> Local Time is: Wed Jan 16 11:26:05 2019 UTC
> 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: ( 600) 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: ( 1) minutes.
> Extended self-test routine
> recommended polling time: ( 172) minutes.
> Conveyance self-test routine
> recommended polling time: ( 2) 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: 10
> 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 096 071 006 Pre-fail Always - 115338875
> 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0
> 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 166
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
> 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 150432482
> 9 Power_On_Hours 0x0032 024 024 000 Old_age Always - 67229
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
> 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 166
> 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
> 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
> 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 65535
> 188 Command_Timeout 0x0032 100 098 000 Old_age Always - 115966017574
> 189 High_Fly_Writes 0x003a 095 095 000 Old_age Always - 5
> 190 Airflow_Temperature_Cel 0x0022 070 051 045 Old_age Always - 30 (Min/Max 30/30)
> 194 Temperature_Celsius 0x0022 030 049 000 Old_age Always - 30 (0 12 0 0 0)
> 195 Hardware_ECC_Recovered 0x001a 032 022 000 Old_age Always - 115338875
> 197 Current_Pending_Sector 0x0012 099 096 000 Old_age Always - 50
> 198 Offline_Uncorrectable 0x0010 099 096 000 Old_age Offline - 50
> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
> 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 67661 (43 124 0)
> 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3341729429
> 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 457667540
> SMART Error Log Version: 1
> ATA Error Count: 52150 (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 52150 occurred at disk power-on lifetime: 1692 hours (70 days + 12 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 00 61 15 00 02 Error: UNC at LBA = 0x02001561 = 33559905
> 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 60 15 00 e2 00 00:05:38.225 READ DMA
> 27 00 00 00 00 00 e0 00 00:05:38.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> ec 00 00 00 00 00 a0 00 00:05:38.222 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 00:05:38.220 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 00:05:38.197 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> Error 52149 occurred at disk power-on lifetime: 1692 hours (70 days + 12 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 00 61 15 00 02 Error: UNC at LBA = 0x02001561 = 33559905
> 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 60 15 00 e2 00 00:05:35.353 READ DMA
> 27 00 00 00 00 00 e0 00 00:05:35.352 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> ec 00 00 00 00 00 a0 00 00:05:35.350 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 00:05:35.347 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 00:05:35.328 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> Error 52148 occurred at disk power-on lifetime: 1692 hours (70 days + 12 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 00 61 15 00 02 Error: UNC at LBA = 0x02001561 = 33559905
> 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 60 15 00 e2 00 00:05:32.509 READ DMA
> 27 00 00 00 00 00 e0 00 00:05:32.508 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> ec 00 00 00 00 00 a0 00 00:05:32.486 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 00:05:32.483 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 00:05:32.444 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> Error 52147 occurred at disk power-on lifetime: 1692 hours (70 days + 12 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 00 61 15 00 02 Error: UNC at LBA = 0x02001561 = 33559905
> 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 60 15 00 e2 00 00:05:29.567 READ DMA
> c8 00 08 58 15 00 e2 00 00:05:29.566 READ DMA
> c8 00 08 50 15 00 e2 00 00:05:29.565 READ DMA
> c8 00 08 48 15 00 e2 00 00:05:29.565 READ DMA
> c8 00 08 40 15 00 e2 00 00:05:29.558 READ DMA
> Error 52146 occurred at disk power-on lifetime: 1692 hours (70 days + 12 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 00 61 15 00 02 Error: UNC at LBA = 0x02001561 = 33559905
> 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 00 40 15 00 e2 00 00:05:26.607 READ DMA
> c8 00 08 f8 29 01 e2 00 00:05:26.597 READ DMA
> c8 00 08 18 13 01 e2 00 00:05:26.595 READ DMA
> c8 00 00 40 14 00 e2 00 00:05:26.594 READ DMA
> c8 00 00 40 13 00 e2 00 00:05:26.591 READ DMA
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed without error 00% 31241 -
> # 2 Short offline Completed without error 00% 5527 -
> # 3 Short offline Completed without error 00% 5519 -
> # 4 Short offline Completed without error 00% 5519 -
> # 5 Short offline Completed without error 00% 5517 -
> # 6 Short offline Completed without error 00% 5497 -
> # 7 Short offline Completed without error 00% 5496 -
> # 8 Short offline Completed without error 00% 8 -
> # 9 Short offline Completed without error 00% 8 -
> #10 Short offline Completed without error 00% 2 -
> 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.
Disque HS ! A faire remplacer par OVH.
J'espère que t'as toutes les sauvegardes nécessaires.
Je n'utilise pas les outils de diagnostic du mode rescue, donc je ne pourrai pas t'en dire beaucoup plus.
Celui-ci aussi, c'est un indicateur sérieux de crash total possible endéans les quelques heures ou jours.