Project

General

Profile

Anomalie #1262

Freeze de l'ordinateur d'Aurelia

Added by Quentin CHERGUI over 9 years ago. Updated about 3 years ago.

Status:
Fermé
Priority:
Immédiate
Category:
-
Target version:
-
Start date:
04/22/2013
Due date:
% Done:

100%

Estimated time:
Spent time:
Difficulté:
2 Facile

Description

L'ordinateur d'Aurelia a des freezes réguliers.
Au reboot, le fsck indique des erreurs, mais sans possibilités de les réparer.

History

#1

Updated by Quentin CHERGUI over 9 years ago

  • Start date changed from 04/23/2013 to 04/22/2013

fsck exécuté depuis un Live-USB de Debian Wheezy, des erreurs corrigées :

root@debian:/media# fsck -f /dev/sda1 
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
Pass 1: Checking inodes, blocks, and sizes
Inode 287314 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287316 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287317 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287319 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287321 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287322 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287324 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287325 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287330 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287332 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287333 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287342 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287343 has a bad extended attribute block 4.  Clear<y>? yes
Inode 287344 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451346 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451348 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451349 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451351 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451353 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451354 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451356 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451357 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451362 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451364 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451365 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451374 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451375 has a bad extended attribute block 4.  Clear<y>? yes
Inode 1451376 has a bad extended attribute block 4.  Clear<y>? yes
Pass 2: Checking directory structure
i_faddr for inode 287314 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/overlayfs) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287318 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/jffs2) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287322 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/jfs) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287324 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/qnx4) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287330 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287313 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/squashfs/squashfs.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287315 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/overlayfs/overlayfs.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287317 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/udf/udf.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287332 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_cp737.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287333 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_iso8859-5.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287335 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_ascii.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287337 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_iso8859-4.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287338 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_iso8859-9.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287340 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_koi8-u.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287343 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_koi8-ru.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287344 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_cp936.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 287331 (/lib/modules/3.2.0-36-generic-pae/kernel/fs/nls/nls_cp874.ko) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451354 (/usr/share/icons/hicolor/64x64/emblems) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451356 (/usr/share/icons/hicolor/64x64/filesystems) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451361 (/usr/share/icons/hicolor/64x64/stock) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451375 (/usr/share/icons/hicolor/72x72/animations) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451376 (/usr/share/icons/hicolor/72x72/apps) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451362 (/usr/share/icons/hicolor/16x16/actions/package-reinstall.png) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451345 (/usr/share/icons/hicolor/48x48/stock/media) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451346 (/usr/share/icons/hicolor/48x48/stock/navigation) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451347 (/usr/share/icons/hicolor/48x48/stock/net) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451349 (/usr/share/icons/hicolor/48x48/stock/table) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451350 (/usr/share/icons/hicolor/48x48/stock/text) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451363 (/usr/share/icons/hicolor/64x64/stock/chart) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451364 (/usr/share/icons/hicolor/64x64/stock/code) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451365 (/usr/share/icons/hicolor/64x64/stock/data) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451367 (/usr/share/icons/hicolor/64x64/stock/image) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451369 (/usr/share/icons/hicolor/64x64/stock/media) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451370 (/usr/share/icons/hicolor/64x64/stock/navigation) is 4, should be zero.
Clear<y>? yes
i_faddr for inode 1451372 (/usr/share/icons/hicolor/64x64/stock/object) is 4, should be zero.
Clear<y>? yes
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 799177/2445984 files (0.1% non-contiguous), 4815988/9764864 blocks

Rien de visible dans les logs sinon. L'état smart du disque est OK.

#2

Updated by Quentin CHERGUI over 9 years ago

En voulant instiguer les logs du freeze de ce midi, j'ai constaté que le système de fichier racine de l'ordinateur d'Aurelia ets passé en lecture seule :

root@aurelia:~# mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/sda3 on /home type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
/home/aurelia/.Private on /home/aurelia type ecryptfs (ecryptfs_check_dev_ruid,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs,ecryptfs_sig=9d5e6d841a33d279,ecryptfs_fnek_sig=70338692b847b2d7)
gvfs-fuse-daemon on /home/aurelia/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=aurelia)

mount : attention : impossible d'écrire sur /etc/mtab (le système de fichiers
        est peut-être en lecture seule). Les informations renvoyées par
        mount(8) ne sont pas forcément à jour. Pour de véritables informations
        sur les points de montage du système, regardez le fichier /proc/mounts.

root@aurelia:~# cat /proc/mounts 
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=2006952k,nr_inodes=205999,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=806868k,mode=755 0 0
/dev/disk/by-uuid/98db9fb8-c02d-4b2b-8d58-0f252a20f289 / ext4 ro,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
/dev/sda3 /home ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
/home/aurelia/.Private /home/aurelia ecryptfs rw,relatime,ecryptfs_fnek_sig=70338692b847b2d7,ecryptfs_sig=9d5e6d841a33d279,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs 0 0
gvfs-fuse-daemon /home/aurelia/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0

#3

Updated by Quentin CHERGUI over 9 years ago

  • Priority changed from Élevée to Immédiate

Après un memtest, il s'avère que la RAM de la machine est défectueuse. Il faut la remplacer le plus rapidement possible.

#4

Updated by Quentin CHERGUI over 9 years ago

  • % Done changed from 0 to 100

La barrette défectueuse a été remplacée. Memtest OK.
fsck effectué sur les deux disques.

Les fichiers de configuration de Gnome étaient endommagés, empêchant le bureau de s'afficher correctement : ils ont étés supprimés.

#5

Updated by Quentin CHERGUI over 9 years ago

  • Status changed from Confirmé to Résolu
#6

Updated by Quentin Gibeaux about 3 years ago

  • Status changed from Résolu to Fermé

Also available in: Atom PDF