#26 Le 22/11/2015, à 01:28
- Bougron
Re : problemes de mise à jour etc
OK
il faudra alors répondre aux questions par oui yes Je pense que le seul caractère y suffit et peut-être simplement return
sudo umount /dev/sda2
sudo fsck -v /dev/sda2 Dernière modification par Bougron (Le 22/11/2015, à 01:39)
Hors ligne
#27 Le 22/11/2015, à 01:32
- Mimi8
Re : problemes de mise à jour etc
yes
ubuntu@ubuntu:~$ sudo umount /dev/sda2
umount: /dev/sda2: not mounted
ubuntu@ubuntu:~$ sudo fsck -v /dev/sda2
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 9967053 was part of the orphaned inode list. FIXED.
Inode 9967056 was part of the orphaned inode list. FIXED.
Deleted inode 9967628 has zero dtime. Fix<y>? yes
Inode 9967647 was part of the orphaned inode list. FIXED.
Inode 9973771 was part of the orphaned inode list. FIXED.
Inode 9973786 was part of the orphaned inode list. FIXED.
Inode 9973787 was part of the orphaned inode list. FIXED.
Inode 12191577 was part of the orphaned inode list. FIXED.
Inode 12193568 was part of the orphaned inode list. FIXED.
Inode 14811153 was part of the orphaned inode list. FIXED.
Inode 14811168 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(39890336--39890341) -(39960584--39960598) -(39960607--39960612) -(39973401--39973409) -(48829443--48829448) -48829482 -(48836190--48836197) -(48933391--48933396) -(48933415--48933420)
Fix<y>? yes
Free blocks count wrong for group #1217 (1544, counted=1550).
Fix<y>? yes
Free blocks count wrong for group #1219 (21056, counted=21086).
Fix<y>? yes
Free blocks count wrong for group #1490 (26013, counted=26028).
Fix<y>? yes
Free blocks count wrong for group #1493 (18670, counted=18682).
Fix<y>? yes
Free blocks count wrong (116544916, counted=116544979).
Fix<y>? yes
Inode bitmap differences: -9967053 -9967056 -9967628 -9967647 -9973771 -(9973786--9973787) -12191577 -12193568 -14811153 -14811168
Fix<y>? yes
Free inodes count wrong for group #1216 (0, counted=4).
Fix<y>? yes
Free inodes count wrong for group #1217 (3242, counted=3245).
Fix<y>? yes
Free inodes count wrong for group #1488 (29, counted=31).
Fix<y>? yes
Free inodes count wrong for group #1808 (8103, counted=8105).
Fix<y>? yes
Free inodes count wrong (29966903, counted=29966914).
Fix<y>? yes
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
269758 inodes used (0.89%, out of 30236672)
286 non-contiguous files (0.1%)
325 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 223565/69
4401197 blocks used (3.64%, out of 120946176)
0 bad blocks
1 large file
178673 regular files
28836 directories
57 character device files
25 block device files
1 fifo
26 links
62153 symbolic links (46029 fast symbolic links)
4 sockets
------------
269775 files
ubuntu@ubuntu:~$ Hors ligne
#28 Le 22/11/2015, à 01:35
- Bougron
Re : problemes de mise à jour etc
Il ne te reste plus qu'a booter et voir si tout remarche bien.
Hors ligne
#29 Le 22/11/2015, à 02:15
- Mimi8
Re : problemes de mise à jour etc
et bien désolée mais à part la corbeille qui se vide desormais
j ai les meme problèmes....
Hors ligne
#30 Le 22/11/2015, à 02:30
- Bougron
Re : problemes de mise à jour etc
Bonsoir
On va partir sur un grave problème disque qui a été abordé
Tu vas rebooter avec la clé USB
installer le logiciel de controle
sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc) universe"
sudo apt-get update
sudo apt-get install --no-install-recommends smartmontools
sudo smartctl -s on /dev/sda
Et fournir le résultat de cette commande que je ne regarderais que dans la journée car cela va confirmer la prévision de jplemoine.
sudo smartctl -a /dev/sdaPuis refaire
sudo umount /dev/sda2
sudo fsck -v /dev/sda2 Dernière modification par Bougron (Le 22/11/2015, à 10:29)
Hors ligne
#31 Le 22/11/2015, à 03:42
- moko138
Re : problemes de mise à jour etc
480 Current_Pending_Sector/secteurs en attente de réallocation, c'est énorme...
Donc, comme dit jplemoine, SAUVEGARDER !
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#32 Le 22/11/2015, à 10:35
- Bougron
Re : problemes de mise à jour etc
Bonjour à tous.
J'ai déjà vu ce contexe.
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 480Mais il était accompagné d'autres lignes mettant en évidence que cela ne marchait pas bien!
il n'y avait pas cette valeur à zéro.
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0Je suis tenté de demander de faire une lecture totale du disque pour voir ce qui va se passer.
sudo dd if=/dev/sda of=/dev/null bs=4096
sudo smartct -a /dev/sdaDernière modification par Bougron (Le 22/11/2015, à 10:43)
Hors ligne
#33 Le 22/11/2015, à 12:57
- Mimi8
Re : problemes de mise à jour etc
Bonjour
les 2 premieres ;
ubuntu@ubuntu:~$ sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc) universe"
ubuntu@ubuntu:~$ sudo apt-get update
Ign cdrom://Ubuntu 14.04.3 LTS _Trusty Tahr_ - Beta amd64 (20150805) trusty InRelease
Ign cdrom://Ubuntu 14.04.3 LTS _Trusty Tahr_ - Beta amd64 (20150805) trusty/main Translation-en_US
Ign cdrom://Ubuntu 14.04.3 LTS _Trusty Tahr_ - Beta amd64 (20150805) trusty/main Translation-en
Ign cdrom://Ubuntu 14.04.3 LTS _Trusty Tahr_ - Beta amd64 (20150805) trusty/restricted Translation-en_US
Ign cdrom://Ubuntu 14.04.3 LTS _Trusty Tahr_ - Beta amd64 (20150805) trusty/restricted Translation-en
Get:1 http://security.ubuntu.com trusty-security InRelease [64.4 kB]
Ign http://archive.ubuntu.com trusty InRelease
Get:2 http://archive.ubuntu.com trusty-updates InRelease [64.4 kB]
Get:3 http://security.ubuntu.com trusty-security/main amd64 Packages [370 kB]
Hit http://archive.ubuntu.com trusty Release.gpg
Get:4 http://archive.ubuntu.com trusty-updates/main amd64 Packages [653 kB]
Get:5 http://security.ubuntu.com trusty-security/restricted amd64 Packages [13.0 kB]
Get:6 http://security.ubuntu.com trusty-security/main Translation-en [201 kB]
Get:7 http://security.ubuntu.com trusty-security/restricted Translation-en [3,206 B]
Get:8 http://archive.ubuntu.com trusty-updates/restricted amd64 Packages [15.9 kB]
Get:9 http://archive.ubuntu.com trusty-updates/main Translation-en [320 kB]
Get:10 http://archive.ubuntu.com trusty-updates/restricted Translation-en [3,699 B]
Hit http://archive.ubuntu.com trusty Release
Hit http://archive.ubuntu.com trusty/main amd64 Packages
Hit http://archive.ubuntu.com trusty/restricted amd64 Packages
Get:11 http://archive.ubuntu.com trusty/universe amd64 Packages [5,859 kB]
Hit http://archive.ubuntu.com trusty/main Translation-en
Hit http://archive.ubuntu.com trusty/restricted Translation-en
Get:12 http://archive.ubuntu.com trusty/universe Translation-en [4,089 kB]
Ign http://archive.ubuntu.com trusty/main Translation-en_US
Ign http://archive.ubuntu.com trusty/restricted Translation-en_US
Ign http://archive.ubuntu.com trusty/universe Translation-en_US
Fetched 11.7 MB in 60s (193 kB/s)
Reading package lists... Done
ubuntu@ubuntu:~$ Hors ligne
#34 Le 22/11/2015, à 13:00
- Mimi8
Re : problemes de mise à jour etc
3 et 4
ubuntu@ubuntu:~$ sudo apt-get install --no-install-recommends smartmontools
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
gsmartcontrol smart-notifier
Recommended packages:
mailx mailutils
The following NEW packages will be installed:
smartmontools
0 upgraded, 1 newly installed, 0 to remove and 203 not upgraded.
Need to get 445 kB of archives.
After this operation, 1,650 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty/main smartmontools amd64 6.2+svn3841-1.2 [445 kB]
Fetched 445 kB in 2s (168 kB/s)
Selecting previously unselected package smartmontools.
(Reading database ... 166627 files and directories currently installed.)
Preparing to unpack .../smartmontools_6.2+svn3841-1.2_amd64.deb ...
Unpacking smartmontools (6.2+svn3841-1.2) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up smartmontools (6.2+svn3841-1.2) ...
Processing triggers for ureadahead (0.100.0-16) ...
ubuntu@ubuntu:~$ sudo smartctl -s on /dev/sda
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.19.0-25-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
ubuntu@ubuntu:~$ Hors ligne
#35 Le 22/11/2015, à 13:02
- Mimi8
Re : problemes de mise à jour etc
ensuite
ubuntu@ubuntu:~$ sudo smartctl -a /dev/sda
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.19.0-25-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD050
Serial Number: 827KSIX2S
LU WWN Device Id: 5 000039 435f81d5b
Firmware Version: AX002J
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
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: Sun Nov 22 11:01:39 2015 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: ( 126) 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 - 1041
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2552
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
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 082 082 000 Old_age Always - 7535
10 Spin_Retry_Count 0x0033 150 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2406
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 198
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 166
193 Load_Cycle_Count 0x0032 096 096 000 Old_age Always - 44759
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 12/51)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 464
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 083 083 000 Old_age Always - 6915
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 - 263
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 1216 (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 1216 occurred at disk power-on lifetime: 7534 hours (313 days + 22 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 50 c0 cb 6c 40 Error: WP at LBA = 0x006ccbc0 = 7130048
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 68 00 08 10 40 00 00:07:57.590 WRITE FPDMA QUEUED
61 08 60 00 08 10 40 00 00:07:57.589 WRITE FPDMA QUEUED
61 08 58 00 08 d4 40 00 00:07:57.589 WRITE FPDMA QUEUED
60 08 50 c0 cb 6c 40 00 00:07:57.589 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:07:57.589 SET FEATURES [Enable SATA feature]
Error 1215 occurred at disk power-on lifetime: 7534 hours (313 days + 22 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 40 c0 cb 6c 40 Error: WP at LBA = 0x006ccbc0 = 7130048
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 98 48 90 63 d4 40 00 00:07:57.503 WRITE FPDMA QUEUED
60 08 40 c0 cb 6c 40 00 00:07:53.757 READ FPDMA QUEUED
60 08 38 b8 cb 6c 40 00 00:07:53.757 READ FPDMA QUEUED
60 08 30 b0 cb 6c 40 00 00:07:53.756 READ FPDMA QUEUED
60 08 28 a8 cb 6c 40 00 00:07:53.756 READ FPDMA QUEUED
Error 1214 occurred at disk power-on lifetime: 7534 hours (313 days + 22 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 48 c0 cb 6c 40 Error: UNC at LBA = 0x006ccbc0 = 7130048
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 50 00 cc 6c 40 00 00:07:53.644 READ FPDMA QUEUED
60 00 48 00 cb 6c 40 00 00:07:49.931 READ FPDMA QUEUED
60 00 40 00 ca 6c 40 00 00:07:49.930 READ FPDMA QUEUED
60 00 38 00 c8 6c 40 00 00:07:49.904 READ FPDMA QUEUED
60 08 30 e8 34 18 40 00 00:07:49.815 READ FPDMA QUEUED
Error 1213 occurred at disk power-on lifetime: 7532 hours (313 days + 20 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 50 80 cb 18 40 Error: UNC at LBA = 0x0018cb80 = 1624960
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 58 30 6d 19 40 00 00:04:44.824 READ FPDMA QUEUED
60 08 50 80 cb 18 40 00 00:04:44.808 READ FPDMA QUEUED
60 08 48 50 6d 19 40 00 00:04:44.808 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:04:44.808 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:04:44.807 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 1212 occurred at disk power-on lifetime: 7532 hours (313 days + 20 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 30 80 cb 18 40 Error: UNC at LBA = 0x0018cb80 = 1624960
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 40 50 6d 19 40 00 00:04:41.021 READ FPDMA QUEUED
60 08 38 20 8c 17 40 00 00:04:41.016 READ FPDMA QUEUED
60 08 30 80 cb 18 40 00 00:04:41.000 READ FPDMA QUEUED
60 08 28 70 7f 15 40 00 00:04:41.000 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:04:41.000 SET FEATURES [Enable SATA feature]
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.
ubuntu@ubuntu:~$ Hors ligne
#36 Le 22/11/2015, à 13:05
- Mimi8
Re : problemes de mise à jour etc
puis
ubuntu@ubuntu:~$ sudo umount /dev/sda2
umount: /dev/sda2: not mounted
ubuntu@ubuntu:~$ sudo fsck -v /dev/sda2
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/sda2: clean, 269593/30236672 files, 4120805/120946176 blocks
ubuntu@ubuntu:~$ Hors ligne
#37 Le 22/11/2015, à 13:12
- Mimi8
Re : problemes de mise à jour etc
En tous cas merci a vous de votre disponibilite!
je fais des fautes car j ai le clavier qwerty
il y a peu que j ai ubuntu
ok pas de virus
mais je suis assez decue trop de plantages....
Hors ligne
#38 Le 22/11/2015, à 14:11
- Bougron
Re : problemes de mise à jour etc
Je ne comprends pas pourquoi ton disque est redevenu en READ.
le check montre qu'il n'a rien réparé. Donc que le filesystem est correct.
De plus on a une diminution du nombre de secteurs en réparation...
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 464la prochaine fois, commences à frapper
setxkb,qp frLe clavier redeviendra français.
Dernière modification par Bougron (Le 22/11/2015, à 14:13)
Hors ligne
#39 Le 22/11/2015, à 14:15
- moko138
Re : problemes de mise à jour etc
Mimi8 a écrit :
je fais des fautes car j ai le clavier qwerty
En graphique, taper au clavier :
setxkb,qp fren sorte de lire à l'écran :
setxkbmap fr- -
Mimi8 a écrit :
je suis assez decue trop de plantages...
Ben oui : sur un disque détérioré, tu ne peux pas avoir un système sain !
(Sauf le cas très particulier où la zone dégradée est limitée et où on la met délibérément en "zone non allouée").
- -
Bougron a écrit :
J'ai déjà vu ce contexte.
C'est vrai que c'est inhabituel, d'avoir un "Current_Pending_Sector" en désaccord apparent avec d'autres valeurs à zéro (valeurs d'hier) :
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
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
10 Spin_Retry_Count 0x0033 150 100 030 Pre-fail Always - 0
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0mais puisque, quelle que soit la cause de cette incohérence, Mimi8 rencontre des problème bien réels, il faut avant tout sauvegarder sur un autre disque ! (ter)
Ce qui n'empêchera pas de faire des investigations ensuite.
Et si c'était le micrologiciel du TOSHIBA MQ01ABD050 qui était défectueux, conduisant à afficher des mesures incohérentes ? En ce cas, on retrouvera sur la toile d'autres occurrences du problème.
Bougron, je vois bien que le nombre de secteurs en attente est descendu de 480 à 464 après fsck. Est-ce pour mesurer cet effet que tu as fait refaire un smartctl à Mimi8 ? Ou pour une autre raison qui m'échappe ?
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#40 Le 22/11/2015, à 14:24
- Mimi8
Re : problemes de mise à jour etc
J'avais dèjà essayé de sauvegarder mes fichiers mais ça ne marchait pas non plus ;
mais bon ça fait peu de temps que j'ai Ubuntu et je n'ai pratiquement rien dessus
je n'ai pas encore récupéré mes dossiers qui sont sur un autre disque
donc pas de panique, s'il faut je reformate tout....
Hors ligne
#41 Le 22/11/2015, à 14:29
- moko138
Re : problemes de mise à jour etc
Bougron, même en live, mieux vaut
sudo fsck -yfv /dev/sda2 que
sudo fsck -v /dev/sda2
qui peut rester passif ou, dans le cas d'un HD très dégradé, demander une quasi infinité de confirmations à l'utilisateur (ça m'est arrivé).
D'autre part, pour hier,
man fsck a écrit :
-a Cette option est identique à l'option -p, mais n'existe que pour
assurer la compatibilité ascendante ; il est donc vivement sug‐
géré d'utiliser plutôt l'option -p quand c'est possible.
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#42 Le 22/11/2015, à 16:22
- moko138
Re : problemes de mise à jour etc
Mimi8 a écrit :
ça fait peu de temps que j'ai Ubuntu et je n'ai pratiquement rien dessus
(...) mes dossiers qui sont sur un autre disque.
Bon ! 
Mimi8 a écrit :
pas de panique, s'il faut je reformate tout....
Attention 1 : vois ./viewtopic.php?pid=21035241
- -
Mimi8 a écrit :
J'avais dèjà essayé de sauvegarder mes fichiers mais ça ne marchait pas non plus ; (...) mes dossiers qui sont sur un autre disque
Attention 2 : vérifie cet autre disque, maintenant que tu sais utiliser smartctl !
Attention 3 : j'espère que tu n'emploies pas "disque" pour "autre partition du même disque". Parce que là, la récupération de tes données serait un problème !
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#43 Le 22/11/2015, à 16:30
- Mimi8
Re : problemes de mise à jour etc
nan nan c'est sur un disque externe!
"Attention 2 : vérifie cet autre disque, maintenant que tu sais utiliser smartctl !"
hum je 'ai fait que suivre Bougron...
Hors ligne
#44 Le 22/11/2015, à 17:20
- Bougron
Re : problemes de mise à jour etc
moko138 a écrit :
Bougron, même en live, mieux vaut
sudo fsck -yfv /dev/sda2que
sudo fsck -v /dev/sda2
qui peut rester passif ou, dans le cas d'un HD très dégradé, demander une quasi infinité de confirmations à l'utilisateur (ça m'est arrivé).
.
Bonjour
Au debut de la journée, il y a eu le message de jplemoine http://forum.ubuntu-fr.org/viewtopic.ph … #p21025821
écrit en caractères suffisamment gras,
J'aurais probalement du dire.
+1 Très bonne piste pour le problème....
enfin le soir, lorsque j'ai pris connaissance de l'état smart, j'ai pensé que les copies avaient pu se faire sans difficulté et que c'était réparable car au vu du smart j'ai pensé à une coupure électrique..
Il a d'abord fallu trouver le N° de la partition à inspecter.
Lorsque cela a été fait j'ai donné cette consigne.
http://forum.ubuntu-fr.org/viewtopic.ph … #p21031771
puis après celle-ci.
http://forum.ubuntu-fr.org/viewtopic.ph … #p21031841
en enfin celle-ci
http://forum.ubuntu-fr.org/viewtopic.ph … #p21032011
apres, je pensais que le probleme était réglé
Lorsque cela est revenu vite, j'ai été un peu surpris
J'ai donc demandé la totale
Je pensais avoir un smartctl dégradé et non amélioré.
et un problème semblable sur le disque , donc directement la troisième solution
Pourquoi je mets l'option tout simplement c'est qu'elle clairement expliquée et que je ne comprend si la valeur -p est codifiable (sa présentation laisse à penser que non)
FSCK(8) System Administration FSCK(8)
NAME
fsck - check and repair a Linux filesystem
SYNOPSIS
fsck [-lsAVRTMNP] [-C [fd]] [-t fstype] [filesys...] [--] [fs-spe‐
cific-options]
DESCRIPTION
fsck is used to check and optionally repair one or more Linux filesys‐
tems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a
mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier
(e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Nor‐
mally, the fsck program will try to handle filesystems on different
physical disk drives in parallel to reduce the total amount of time
needed to check all of them.
If no filesystems are specified on the command line, and the -A option
is not specified, fsck will default to checking filesystems in
/etc/fstab serially. This is equivalent to the -As options.
The exit code returned by fsck is the sum of the following conditions:
0 - No errors
1 - Filesystem errors corrected
2 - System should be rebooted
4 - Filesystem errors left uncorrected
8 - Operational error
16 - Usage or syntax error
32 - Fsck canceled by user request
128 - Shared-library error
The exit code returned when multiple filesystems are checked is the
bit-wise OR of the exit codes for each filesystem that is checked.
In actuality, fsck is simply a front-end for the various filesystem
checkers (fsck.fstype) available under Linux. The filesystem-specific
checker is searched for in /sbin first, then in /etc/fs and /etc, and
finally in the directories listed in the PATH environment variable.
Please see the filesystem-specific checker manual pages for further
details.
OPTIONS
-l Lock the whole-disk device by an exclusive flock(2). This
option can be used with one device only (this means that -A and
-l are mutually exclusive). This option is recommended when
more fsck (8) instances are executed in the same time. The
option is ignored when used for multiple devices or for non-
rotating disks. fsck does not lock underlying devices when exe‐
cuted to check stacked devices (e.g. MD or DM) -- this feature
is not implemented yet.
-s Serialize fsck operations. This is a good idea if you are
checking multiple filesystems and the checkers are in an inter‐
active mode. (Note: e2fsck(8) runs in an interactive mode by
default. To make e2fsck(8) run in a non-interactive mode, you
must either specify the -p or -a option, if you wish for errors
to be corrected automatically, or the -n option if you do not.)
-t fslist
Specifies the type(s) of filesystem to be checked. When the -A
flag is specified, only filesystems that match fslist are
checked. The fslist parameter is a comma-separated list of
filesystems and options specifiers. All of the filesystems in
this comma-separated list may be prefixed by a negation operator
'no' or '!', which requests that only those filesystems not
listed in fslist will be checked. If none of the filesystems in
fslist is prefixed by a negation operator, then only those
listed filesystems will be checked.
Options specifiers may be included in the comma-separated
fslist. They must have the format opts=fs-option. If an
options specifier is present, then only filesystems which con‐
tain fs-option in their mount options field of /etc/fstab will
be checked. If the options specifier is prefixed by a negation
operator, then only those filesystems that do not have fs-option
in their mount options field of /etc/fstab will be checked.
For example, if opts=ro appears in fslist, then only filesystems
listed in /etc/fstab with the ro option will be checked.
For compatibility with Mandrake distributions whose boot scripts
depend upon an unauthorized UI change to the fsck program, if a
filesystem type of loop is found in fslist, it is treated as if
opts=loop were specified as an argument to the -t option.
Normally, the filesystem type is deduced by searching for
filesys in the /etc/fstab file and using the corresponding
entry. If the type can not be deduced, and there is only a sin‐
gle filesystem given as an argument to the -t option, fsck will
use the specified filesystem type. If this type is not avail‐
able, then the default filesystem type (currently ext2) is used.
-A Walk through the /etc/fstab file and try to check all filesys‐
tems in one run. This option is typically used from the /etc/rc
system initialization file, instead of multiple commands for
checking a single filesystem.
The root filesystem will be checked first unless the -P option
is specified (see below). After that, filesystems will be
checked in the order specified by the fs_passno (the sixth)
field in the /etc/fstab file. Filesystems with a fs_passno
value of 0 are skipped and are not checked at all. Filesystems
with a fs_passno value of greater than zero will be checked in
order, with filesystems with the lowest fs_passno number being
checked first. If there are multiple filesystems with the same
pass number, fsck will attempt to check them in parallel,
although it will avoid running multiple filesystem checks on the
same physical disk.
fsck does not check stacked devices (RAIDs, dm-crypt, ...) in
parallel with any other device. See below for
FSCK_FORCE_ALL_PARALLEL setting. The /sys filesystem is used to
detemine dependencies between devices.
Hence, a very common configuration in /etc/fstab files is to set
the root filesystem to have a fs_passno value of 1 and to set
all other filesystems to have a fs_passno value of 2. This will
allow fsck to automatically run filesystem checkers in parallel
if it is advantageous to do so. System administrators might
choose not to use this configuration if they need to avoid mul‐
tiple filesystem checks running in parallel for some reason ---
for example, if the machine in question is short on memory so
that excessive paging is a concern.
fsck normally does not check whether the device actually exists
before calling a filesystem specific checker. Therefore non-
existing devices may cause the system to enter filesystem repair
mode during boot if the filesystem specific checker returns a
fatal error. The /etc/fstab mount option nofail may be used to
have fsck skip non-existing devices. fsck also skips non-exist‐
ing devices that have the special filesystem type auto
-C [ fd ]
Display completion/progress bars for those filesystem checkers
(currently only for ext2 and ext3) which support them. Fsck
will manage the filesystem checkers so that only one of them
will display a progress bar at a time. GUI front-ends may spec‐
ify a file descriptor fd, in which case the progress bar infor‐
mation will be sent to that file descriptor.
-M Do not check mounted filesystems and return an exit code of 0
for mounted filesystems.
-N Don't execute, just show what would be done.
-P When the -A flag is set, check the root filesystem in parallel
with the other filesystems. This is not the safest thing in the
world to do, since if the root filesystem is in doubt things
like the e2fsck(8) executable might be corrupted! This option
is mainly provided for those sysadmins who don't want to repar‐
tition the root filesystem to be small and compact (which is
really the right solution).
-R When checking all filesystems with the -A flag, skip the root
filesystem. (This is useful in case the root filesystem has
already been mounted read-write.)
-T Don't show the title on startup.
-V Produce verbose output, including all filesystem-specific com‐
mands that are executed.
fs-specific-options
Options which are not understood by fsck are passed to the
filesystem-specific checker. These arguments must not take
arguments, as there is no way for fsck to be able to properly
guess which options take arguments and which don't.
Options and arguments which follow the -- are treated as
filesystem-specific options to be passed to the filesystem-spe‐
cific checker.
Please note that fsck is not designed to pass arbitrarily com‐
plicated options to filesystem-specific checkers. If you're
doing something complicated, please just execute the filesystem-
specific checker directly. If you pass fsck some horribly com‐
plicated options and arguments, and it doesn't do what you
expect, don't bother reporting it as a bug. You're almost cer‐
tainly doing something that you shouldn't be doing with fsck.
Options to different filesystem-specific fsck's are not standardized.
If in doubt, please consult the man pages of the filesystem-specific
checker. Although not guaranteed, the following options are supported
by most filesystem checkers:
-a Automatically repair the filesystem without any questions (use
this option with caution). Note that e2fsck(8) supports -a for
backward compatibility only. This option is mapped to e2fsck's
-p option which is safe to use, unlike the -a option that some
filesystem checkers support.
-n For some filesystem-specific checkers, the -n option will cause
the fs-specific fsck to avoid attempting to repair any problems,
but simply report such problems to stdout. This is however not
true for all filesystem-specific checkers. In particular,
fsck.reiserfs(8) will not report any corruption if given this
option. fsck.minix(8) does not support the -n option at all.
-r Interactively repair the filesystem (ask for confirmations).
Note: It is generally a bad idea to use this option if multiple
fsck's are being run in parallel. Also note that this is
e2fsck's default behavior; it supports this option for backward
compatibility reasons only.
-y For some filesystem-specific checkers, the -y option will cause
the fs-specific fsck to always attempt to fix any detected
filesystem corruption automatically. Sometimes an expert may be
able to do better driving the fsck manually. Note that not all
filesystem-specific checkers implement this option. In particu‐
lar fsck.minix(8) and fsck.cramfs(8) do not support the -y
option as of this writing.
AUTHOR
Theodore Ts'o (tytso@mit.edu)
AVAILABILITY
The fsck command is part of the util-linux package and is available
from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
FILES
/etc/fstab.
ENVIRONMENT VARIABLES
The fsck program's behavior is affected by the following environment
variables:
FSCK_FORCE_ALL_PARALLEL
If this environment variable is set, fsck will attempt to check
all of the specified filesystems in parallel, regardless of
whether the filesystems appear to be on the same device. (This
is useful for RAID systems or high-end storage systems such as
those sold by companies such as IBM or EMC.) Note that the
fs_passno value is still used.
FSCK_MAX_INST
This environment variable will limit the maximum number of
filesystem checkers that can be running at one time. This
allows configurations which have a large number of disks to
avoid fsck starting too many filesystem checkers at once, which
might overload CPU and memory resources available on the system.
If this value is zero, then an unlimited number of processes can
be spawned. This is currently the default, but future versions
of fsck may attempt to automatically determine how many filesys‐
tem checks can be run based on gathering accounting data from
the operating system.
PATH The PATH environment variable is used to find filesystem check‐
ers. A set of system directories are searched first: /sbin,
/sbin/fs.d, /sbin/fs, /etc/fs, and /etc. Then the set of direc‐
tories found in the PATH environment are searched.
FSTAB_FILE
This environment variable allows the system administrator to
override the standard location of the /etc/fstab file. It is
also useful for developers who are testing fsck.
SEE ALSO
fstab(5), mkfs(8), fsck.ext2(8) or fsck.ext3(8) or e2fsck(8), cramf‐
sck(8), fsck.minix(8), fsck.msdos(8), fsck.jfs(8), fsck.nfs(8),
fsck.vfat(8), fsck.xfs(8), fsck.xiafs(8), reiserfsck(8).Vérifier régulièrement l'état de disques n'est pas un luxe même si les disque sont externes
mimi8 doit l'avoir compris.
Dernière modification par Bougron (Le 22/11/2015, à 17:34)
Hors ligne