Fedora-Fr

Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Problème de démarrage F16

Elfist

Bonjour tout le monde, je me rapproche de vous car j'ai un serieux problème de démarrage suite à des coupures intempestives sur mon ordi portable.
Quand je démarrage j'ai le message d'erreur suivant:

    Booting 'Fedora (3.2.3-2.fc16.i686)'

Loading Fedora (3.2.3-2.fc16.i686)
Loading initial ramdisk ...

_Fedora-16-i686-: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
               (i.e., without -a or -p options)
dracut Warning: e2fsck returned with 4
dracut Warning: _Fedora-16-i686- contains a file system with errors, check forced.
dracut Warning: _Fedora-16-i686-: Inodes that were part of a corrupted orphan linked list found.
dracut Warning: *** An error occured during the file system check.
dracut Warning: *** Dropping you to a shell; the system will try
dracut Warning: *** to mount the filesystem(s), when you leave the shell.


dracut Warning:

Dropping to debug shell.

sh: can't access tty; job control turned off
(Repair filesystem):/#

J'ai vu dans d'autres postes qu'il fallait faire fsck -y /dev/sda, ce que j'ai fait mais voila le résultat:

(Repair filesystem):/# fsck -y /dev/sda
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Device or resource busy while trying to open /dev/sda
Filesystem mounted or opened exclusively by another program?
(Repair filesystem):/#

Alors j'ai essayé en faisant fsck -y /dev/sda1 et voici le résultat:

(Repair filesystem):/# fsck -y /dev/sda1
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
     e2fsck -b 8193 <device>

Repair filesystem):/#

Pour être franc, je commence un peu à sécher. Serait-il possible de me venir en aide svp?
Je vous remercie d'avance.

titijhajha

Bonjour Elfist,

Je suis pas un expert loin de là, mais as-tu vu ce post ?

Elfist

Bonjour titijhajha,

Oui j'ai regardé ce matin ce post mais le problème est que étant en console de réparation si j'exécute la commande fdisk -l pour voir quel sda réparer, il m'indique qu'il ne trouve pas la commande

(Repair filesystem):/# fdisk -l
sh: fdisk: not found

et si je fais la commande fsck.ext4 -y -f /dev/sda1, il me renvoie la même erreur que la commande fsck -y /dev/sda1

(Repair filesystem):/# fsck.ext4 -y -f /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
     e2fsck -b 8193 <device>

Repair filesystem):/#

nouvo09

4 ans que tu es sous linux et tu ne sais pas démarrer depuis un cd/dvd d'install en mode rescue ?

Elfist

Et juste 3 ans que j'ai pas remis les mains dessus donc bon

Elfist

Sinon une idée d'où cela pourrait venir et ce que je pourrais faire?

nouvo09

La première chose à faire serait un

fdisk -l /dev/sda

suivi d'un (au cas où) blkid /dev/sda*

Elfist

Salut Nouvo09,

Voici le résultat de fdisk -l /dev/sda

[root@localhost ~]# fdisk -l /dev/sda

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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 identifier: 0x00000000

Device Boot   Start        End     Blocks     Id    System
/dev/sda1       1     488397167  244198583+   ee    GPT

Elfist

et voici le résultat de blkid /dev/sda*:

[root@localhost ~]# blkid /dev/sda*
/dev/sda2: UUID="99aef7a0-b2a5-4a52-b9cf-4e1aef3b322f" TYPE="ext4"
/dev/sda3: UUID="GzilSZ-Fwz9-0zZz-S27C-QBRe-5TSO-CqnpiG" TYPE="LVM2_member"

Que dois-je faire maintenant, une idée?

nouvo09

Ton disque est au format GTP donc il n'est pas pris en charge par fdisk mais par gdisk.

En plus de toute évidence tu n'as pas de partition réelle sda1 donc tu peux tenter autant de fsck que tu veux, ça n'aboutira à rien.

essaie donc un fsck.ext4 -y -f /dev/sda2 pour commencer.

Elfist

voici le résultat,

[root@localhost ~]# fsck.ext4 -y -f /dev/sda2
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks,  and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: 233/128016 files (0.4% non-contiguous), 98216/512000 blocks
[root@localhost ~]#

et le problème reste inchangé malheureusement

nouvo09

Ok alors que donne un

lvdisplay -a

pour voir ce qu'il y a dans la partition lvm sda3

Elfist

[root@localhost ~]# lvdisplay -a
  --- Logical volume ---
  LV Name                /dev/VolGroup/lv_swap
  VG Name                VolGroup
  LV UUID                PUR1Ug-ktZT-c2FR-vQKt-jhzG-hTxp-mBzw3k
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                4.97 GiB
  Current LE             159
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2
   
  --- Logical volume ---
  LV Name                /dev/VolGroup/lv_home
  VG Name                VolGroup
  LV UUID                mAWcgC-wi01-yeMH-cRnB-2NFP-1yHP-AacOwW
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                177.41 GiB
  Current LE             5677
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3
   
  --- Logical volume ---
  LV Name                /dev/VolGroup/lv_root
  VG Name                VolGroup
  LV UUID                sIK6b3-Iq91-DIf8-1MeS-dvdb-J0I3-a0Ygm4
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                50.00 GiB
  Current LE             1600
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4
   
[root@localhost ~]#

Tu en pense quoi?

nouvo09

Alors lance aussi la commande :

fsck.ext4 -y -f /dev/VolGroup/lv_root

Elfist

Ok déja ca tourne je laisse tourner et je te poste le résultat.

Elfist

Alors voila le résultat

[root@localhost ~]# fsck.ext4 -y -f /dev/VolGroup/lv_root
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 1274 was part of the orphaned inode list.  FIXED.
Deleted inode 1341 has zero dtime.  Fix? yes

Inode 1388 was part of the orphaned inode list.  FIXED.
Inode 3198 was part of the orphaned inode list.  FIXED.
Inode 3339 was part of the orphaned inode list.  FIXED.
Deleted inode 3341 has zero dtime.  Fix? yes

Inode 3764 was part of the orphaned inode list.  FIXED.
Inode 4840 was part of the orphaned inode list.  FIXED.
Error reading block 319599 (Attempt to read block from filesystem resulted in short read).  Ignore error? yes

Force rewrite? yes

Inode 52843 has an invalid extent node (blk 319599, lblk 0)
Clear? yes

Inode 52843, i_blocks is 336, should be 0.  Fix? yes

Inode 140429 was part of the orphaned inode list.  FIXED.
Inode 144353 was part of the orphaned inode list.  FIXED.
Inode 145293 was part of the orphaned inode list.  FIXED.
Inode 145907 was part of the orphaned inode list.  FIXED.
Inode 145908 was part of the orphaned inode list.  FIXED.
Inode 145909 was part of the orphaned inode list.  FIXED.
Inode 145928 was part of the orphaned inode list.  FIXED.
Inode 145929 was part of the orphaned inode list.  FIXED.
Inode 145943 was part of the orphaned inode list.  FIXED.
Inode 145944 was part of the orphaned inode list.  FIXED.
Inode 145945 was part of the orphaned inode list.  FIXED.
Inode 145946 was part of the orphaned inode list.  FIXED.
Inode 145984 was part of the orphaned inode list.  FIXED.
Inode 145985 was part of the orphaned inode list.  FIXED.
Inode 145997 was part of the orphaned inode list.  FIXED.
Inode 145998 was part of the orphaned inode list.  FIXED.
Inode 145999 was part of the orphaned inode list.  FIXED.
Inode 146015 was part of the orphaned inode list.  FIXED.
Inode 146033 was part of the orphaned inode list.  FIXED.
Inode 146201 was part of the orphaned inode list.  FIXED.
Inode 147541 was part of the orphaned inode list.  FIXED.
Inode 157504 was part of the orphaned inode list.  FIXED.
Error reading block 1048621 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan.  Ignore error? yes

Force rewrite? yes

Error reading block 2621713 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan.  Ignore error? yes

Force rewrite? yes

Pass 2: Checking directory structure
Entry '20' in /var/lib/yum/history/2011-11-03 (35) has deleted/unused inode 659229.  Clear? yes

Entry '31f8398e5af80f41685c75e4e83e54ae99b12283-rpmfusion-free-release-16-1.2-noarch' in /var/lib/yum/yumdb/r (26403) has deleted/unused inode 659227.  Clear? yes

Entry '1cbadbb907b77c13ae3ab96ec2317a2f52e33b76-PackageKit-glib-0.6.21-2.fc16-i686' in /var/lib/yum/yumdb/P (26426) has deleted/unused inode 262365.  Clear? yes

Entry '4351ed76df8ddb33c7a8438de63d31469b36aefc-yum-langpacks-0.2.4-2.fc16-noarch' in /var/lib/yum/yumdb/y (26738) has deleted/unused inode 262357.  Clear? yes

Entry 'metalink.xml' in /var/cache/yum/i386/16/fedora (262205) has deleted/unused inode 262360.  Clear? yes

Entry '9f370e2ba7f6afaad4cfe809c7066e20bad1279a6d7b2565f8dfccbdfbffc54d-filelists.sqlite' in /var/cache/yum/i386/16/rpmfusion-free (657847) has deleted/unused inode 659220.  Clear? yes

Entry 'da16234b86169d5ef823d1fa759160cf587a113e60a59d62fdd7473cddec59d1-other.sqlite' in /var/cache/yum/i386/16/rpmfusion-free (657847) has deleted/unused inode 659219.  Clear? yes

Entry '263279232ec929e646faeefbc03570da75d36899d193164d6e1a3e1c5b6b364c-filelists.sqlite' in /var/cache/yum/i386/16/rpmfusion-nonfree (657878) has deleted/unused inode 659222.  Clear? yes

Entry '0b1553a671b9a7ceebe0e6721a3eb541d9369e1e57bc3f7379decc665bcd4abd-other.sqlite' in /var/cache/yum/i386/16/rpmfusion-nonfree (657878) has deleted/unused inode 659218.  Clear? yes

Entry 'gen' in /var/cache/yum/i386/16/rpmfusion-nonfree-updates (657884) has deleted/unused inode 659225.  Clear? yes

Entry '0772da725e099e1774c6253ed7baa6755dd2f7f0a232306398b0101d56c90f7d-filelists.sqlite' in /var/cache/yum/i386/16/rpmfusion-nonfree-updates (657884) has deleted/unused inode 659223.  Clear? yes

Entry 'vlc-cache-gen' in /usr/lib/vlc (658501) has deleted/unused inode 659217.  Clear? yes

Entry 'groups.xml' in /var/cache/yum/i386/16/rpmfusion-free-updates/gen (658869) has deleted/unused inode 659224.  Clear? yes

Entry 'a32754a8534537b83b78816b4933e724d970d62e-libhangul-0.1.0-1.fc16-i686' in /var/lib/yum/yumdb/l (26360) has deleted/unused inode 262363.  Clear? yes

Entry '80bc8829ef40e8ec0db14c1e9ac34046b42f4409-gjs-1.30.1-1.fc16-i686' in /var/lib/yum/yumdb/g (26378) has deleted/unused inode 262361.  Clear? yes

Entry '552b48a7f2977cc7d7fdd57c1238b944bbccce7a-libsepol-2.1.3-2.fc16-i686' in /var/lib/yum/yumdb/l (26360) has deleted/unused inode 262367.  Clear? yes

Entry 'bbd1823de93aec3e0eb337d11f4251a77634ec85-python-cups-1.9.60-1.fc16-i686' in /var/lib/yum/yumdb/p (26340) has deleted/unused inode 262355.  Clear? yes

Entry 'dd0e6f7cfd8bb5aceda70639e31c11ec7624691b-clutter-1.8.4-1.fc16-i686' in /var/lib/yum/yumdb/c (26375) has deleted/unused inode 262353.  Clear? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 35 ref count is 22, should be 21.  Fix? yes

Inode 26333 ref count is 340, should be 339.  Fix? yes

Inode 26335 ref count is 783, should be 782.  Fix? yes

Inode 26339 ref count is 1126, should be 1119.  Fix? yes

Inode 26340 ref count is 144, should be 143.  Fix? yes

Inode 26342 ref count is 807, should be 801.  Fix? yes

Inode 26360 ref count is 285, should be 283.  Fix? yes

Inode 26375 ref count is 59, should be 58.  Fix? yes

Inode 26378 ref count is 131, should be 130.  Fix? yes

Inode 26403 ref count is 28, should be 27.  Fix? yes

Inode 26426 ref count is 11, should be 10.  Fix? yes

Inode 26738 ref count is 11, should be 10.  Fix? yes

Inode 262295 ref count is 362, should be 355.  Fix? yes

Inode 262296 ref count is 366, should be 359.  Fix? yes

Inode 262297 ref count is 330, should be 324.  Fix? yes

Inode 262298 ref count is 330, should be 324.  Fix? yes

Inode 262300 ref count is 326, should be 320.  Fix? yes

Inode 262301 ref count is 326, should be 320.  Fix? yes

Inode 262302 ref count is 362, should be 355.  Fix? yes

Inode 531479 ref count is 28, should be 27.  Fix? yes

Inode 531480 ref count is 28, should be 27.  Fix? yes

Inode 531482 ref count is 28, should be 27.  Fix? yes

Inode 531483 ref count is 28, should be 27.  Fix? yes

Inode 657839 ref count is 2, should be 1.  Fix? yes

Inode 657840 ref count is 17, should be 16.  Fix? yes

Inode 657846 ref count is 2, should be 1.  Fix? yes

Inode 657884 ref count is 4, should be 3.  Fix? yes

Unattached inode 659233
Connect to /lost+found? yes

Inode 659233 ref count is 2, should be 1.  Fix? yes

Unattached inode 659234
Connect to /lost+found? yes

Inode 659234 ref count is 2, should be 1.  Fix? yes

Unattached inode 659235
Connect to /lost+found? yes

Inode 659235 ref count is 2, should be 1.  Fix? yes

Inode 659236 ref count is 2, should be 1.  Fix? yes

Pass 5: Checking group summary information
Block bitmap differences:  -(34104--34108) -35335 -35352 -(36000--36013) -48680 -(69535--69544) -(69554--69567) -(71179--71188) -(107521--107522) -107829 -107851 -107890 -107898 -181248 -181254 -(181440--181456) -(233590--233834) -319599 -322048 -322055 -322106 -322157 -322288 -(563920--563927) -(578636--578640) -(640256--640306) -(643012--643069) -(644966--645037) -(645182--645267) -(647286--647650) -(649088--649166) -(650533--650616) -(650654--650738) -(654046--654060) -(654819--654835) -(654853--655078) -(665519--665555) -(667648--667874) -(674422--674441) -(675600--675615) -(787140--787271) -(918048--918056) -(918144--918262) -(918464--918510) -(1057624--1057625) -(1057627--1057630) -1078353 -(1083208--1083215) -1083853 -1092169 -(1116096--1116129) -(1146503--1146504) -(1146506--1146509) -(2630292--2630294) -2667554 -(2667557--2667559) -2668273 -(2671150--2671151) -(2673892--2674173) -(2674525--2674791)
Fix? yes

Free blocks count wrong for group #1 (5192, counted=5214).
Fix? yes

Free blocks count wrong for group #2 (14886, counted=14920).
Fix? yes

Free blocks count wrong for group #3 (9452, counted=9458).
Fix? yes

Free blocks count wrong for group #5 (12416, counted=12435).
Fix? yes

Free blocks count wrong for group #7 (14763, counted=15008).
Fix? yes

Free blocks count wrong for group #9 (20162, counted=20168).
Fix? yes

Free blocks count wrong for group #17 (58, counted=71).
Fix? yes

Free blocks count wrong for group #19 (2166, counted=3304).
Fix? yes

Free blocks count wrong for group #20 (7224, counted=7524).
Fix? yes

Free blocks count wrong for group #24 (9439, counted=9571).
Fix? yes

Free blocks count wrong for group #28 (16675, counted=16850).
Fix? yes

Free blocks count wrong for group #32 (14, counted=21).
Fix? yes

Free blocks count wrong for group #33 (15240, counted=15250).
Fix? yes

Free blocks count wrong for group #34 (9903, counted=9943).
Fix? yes

Free blocks count wrong for group #80 (23915, counted=23918).
Fix? yes

Free blocks count wrong for group #81 (12375, counted=12931).
Fix? yes

Free blocks count wrong (11991821, counted=11994527).
Fix? yes

Inode bitmap differences:  -1274 -1341 -1388 -3198 -3339 -3341 -3764 -4840 -140429 -144353 -145293 -(145907--145909) -(145928--145929) -(145943--145946) -(145984--145985) -(145997--145999) -146015 -146033 -146201 -147541 -157504 -(262353--262368) -(659217--659220) -(659222--659232)
Fix? yes

Free inodes count wrong for group #0 (12, counted=20).
Fix? yes

Free inodes count wrong for group #17 (35, counted=55).
Fix? yes

Free inodes count wrong for group #18 (1, counted=2).
Fix? yes

Free inodes count wrong for group #19 (4, counted=5).
Fix? yes

Free inodes count wrong for group #32 (1444, counted=1460).
Fix? yes

Directories count wrong for group #32 (993, counted=986).
Fix? yes

Free inodes count wrong for group #80 (4354, counted=4369).
Fix? yes

Directories count wrong for group #80 (623, counted=620).
Fix? yes

Free inodes count wrong (3157043, counted=3157104).
Fix? yes


_Fedora-16-i686-: ***** FILE SYSTEM WAS MODIFIED *****
_Fedora-16-i686-: 119696/3276800 files (0.2% non-contiguous), 1112673/13107200 blocks
[root@localhost ~]#

Je tente de redémarrer?

nouvo09

Le système de fichiers est propre et utilisable. Si quelques données ont été perdues, elles seront rangées dans le répertoire lost+found.

Tu peux redémarrer oui.

Elfist

J'ai un message d'erreur:

Could not update ICEauthority file /var/lib/gdm/.ICEauthority

Avec comme choix Log Out

hechmi50

Un problème de droits sur les fichiers du à la réparation du système de fichiers, pour réparer cela:

chown gdm:gdm -R /var/lib/gdm
chmod 600 /var/lib/gdm/.ICEauthority
mv /home/ton_utilsateur/.ICEauthority /home/ton_utilisateur/.ICEauthority-old

Elfist

Voila ce qu'il me dit quand je lance le chmod:

[root@localhost ~]# chown gdm:gdm -R /var/lib/gdm
[root@localhost ~]# chmod 600 /var/lib/gdm/.ICEauthority
chmod: cannot access `/var/lib/gdm/.ICEauthority': No such file or directory
[root@localhost ~]#

Page suivante »