#1 Le 12/06/2018, à 11:40
- frere capsule
[Résolu]demarrage imp: "le fichier de config n'est pas inscriptible"
Bonjour,
A l'ouverture de mon pc portable, j'ai un message d'erreur me disant que "des erreurs ont ete trouvées lors de la verif du disque dur /"
"Appuyer sur F pour corriger, I pour ignorer, S pour ignorer le montage, ou M pour la recup manuelle"
Avec F ou I, j'accede a une session mais j'ai plusieurs fenetre pop-up avec ecrit:
"le fichier de configuration xxxx n'est pas inscriptible".
Apres rien ne marche....
Avec S j'ai un ecran noir...
Je suis avec kde14.04.
Dernière modification par frere capsule (Le 31/08/2018, à 18:26)
Hors ligne
#2 Le 12/06/2018, à 17:42
- frere capsule
Re : [Résolu]demarrage imp: "le fichier de config n'est pas inscriptible"
voici le résultat de quelques commandes :
kubuntu@kubuntu:~$ sudo fdisk -l
Disk /dev/loop0: 1.4 GiB, 1544761344 bytes, 3017112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 13E1DB15-F013-45B8-86D1-0A6F791EE3BD
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 1452799999 1451749376 692.3G Linux filesystem
/dev/sda3 1452800000 1465147391 12347392 5.9G Linux swap
Disk /dev/sdb: 15 GiB, 16106127360 bytes, 31457280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x626b608f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3124223 3124224 1.5G 0 Empty
/dev/sdb2 3102940 3107611 4672 2.3M ef EFI (FAT-12/16/32)ici j'ai utilisé smartmontools a partir d'un livecd, on voit qu'il y a des erreurs sur mon disque dur :
kubuntu@kubuntu:~$ sudo smartctl -a /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.10.0-28-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD075
Serial Number: 24I3P7QST
LU WWN Device Id: 5 000039 552285792
Firmware Version: AX0R2J
User Capacity: 750,156,374,016 bytes [750 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Jun 12 15:33:37 2018 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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: ( 120) 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: ( 192) 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 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1530
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2893
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 24
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 058 058 000 Old_age Always - 17008
10 Spin_Retry_Count 0x0033 157 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2475
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 8100
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 177
193 Load_Cycle_Count 0x0032 092 092 000 Old_age Always - 88364
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 36 (Min/Max 10/48)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 3
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 96
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 062 062 000 Old_age Always - 15450
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 261
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 85 (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 85 occurred at disk power-on lifetime: 17002 hours (708 days + 10 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 41 70 a0 70 9d 40 Error: UNC at LBA = 0x009d70a0 = 10317984
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 70 a0 70 9d 40 00 00:03:51.138 READ FPDMA QUEUED
60 08 68 f8 f5 d4 40 00 00:03:51.118 READ FPDMA QUEUED
60 08 18 10 09 91 40 00 00:03:51.099 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:03:51.099 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:03:51.098 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 84 occurred at disk power-on lifetime: 17002 hours (708 days + 10 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 41 f0 a0 70 9d 40 Error: UNC at LBA = 0x009d70a0 = 10317984
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 00 10 09 91 40 00 00:03:47.484 READ FPDMA QUEUED
60 08 f0 a0 70 9d 40 00 00:03:46.983 READ FPDMA QUEUED
60 c0 e8 e0 fc 69 40 00 00:03:46.938 READ FPDMA QUEUED
60 28 e0 18 15 14 40 00 00:03:46.938 READ FPDMA QUEUED
60 08 d8 68 53 dd 40 00 00:03:46.914 READ FPDMA QUEUED
Error 83 occurred at disk power-on lifetime: 17002 hours (708 days + 10 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 41 f0 a0 70 9d 40 Error: UNC at LBA = 0x009d70a0 = 10317984
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 a0 70 9d 40 00 00:03:42.398 READ FPDMA QUEUED
60 08 d0 00 12 91 40 00 00:03:42.398 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:03:42.398 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:03:42.397 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 00:03:42.397 IDENTIFY DEVICE
Error 82 occurred at disk power-on lifetime: 17002 hours (708 days + 10 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 41 b8 a0 70 9d 40 Error: UNC at LBA = 0x009d70a0 = 10317984
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 b8 a0 70 9d 40 00 00:03:38.490 READ FPDMA QUEUED
61 08 70 18 d8 a7 40 00 00:03:38.475 WRITE FPDMA QUEUED
60 08 60 00 12 91 40 00 00:03:38.475 READ FPDMA QUEUED
60 20 58 00 f4 db 40 00 00:03:38.475 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:03:38.474 SET FEATURES [Enable SATA feature]
Error 81 occurred at disk power-on lifetime: 17002 hours (708 days + 10 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 41 28 a0 70 9d 40 Error: UNC at LBA = 0x009d70a0 = 10317984
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 20 40 00 f4 db 40 00 00:03:37.728 READ FPDMA QUEUED
60 38 38 88 4d dd 40 00 00:03:37.728 READ FPDMA QUEUED
60 08 30 00 12 91 40 00 00:03:37.728 READ FPDMA QUEUED
60 08 28 a0 70 9d 40 00 00:03:34.572 READ FPDMA QUEUED
60 18 20 60 40 e5 40 00 00:03:34.562 READ FPDMA QUEUED
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.Hors ligne
#3 Le 12/06/2018, à 18:32
- frere capsule
Re : [Résolu]demarrage imp: "le fichier de config n'est pas inscriptible"
Quand je demarre une session live je n'arrive pas a accéder a mes données. Et maintenant que j'ai demarré sur un live je n'arrive plus du tout a booter sur une session normale,j'ai au démarrage une ligne du type "insérez un boot device".
C'est tragique car je ne peux pas sauver mes données avant de procéder à une réinstallation d'ubuntu....
Comment faire? je peux réparer le boot ?
Hors ligne
#4 Le 13/06/2018, à 16:09
- frere capsule
Re : [Résolu]demarrage imp: "le fichier de config n'est pas inscriptible"
Vous n'avez aucune idées?
Vous pensez que mon disque dur est mort?
Hors ligne
#5 Le 31/08/2018, à 18:25
- frere capsule
Re : [Résolu]demarrage imp: "le fichier de config n'est pas inscriptible"
C'est résolu, le disque dur était en train de claquer... Maintenant il est bel et bien mort...
Hors ligne