interpretare output fsck

Riconoscimento, installazione e configurazione delle periferiche.
melmar20
Scoppiettante Seguace
Scoppiettante Seguace
Messaggi: 796
Iscrizione: lunedì 24 settembre 2007, 20:26

interpretare output fsck

Messaggio da melmar20 »

ciao a tutti , dunque credevo di avere qualche problema sul mio hd e allora ho eseguito un fsck .

l  output e stato questo

Codice: Seleziona tutto

fsck /dev/hda5
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
/dev/hda5 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 181968 has zero dtime.  Fix<y>? yes

Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes

Inode 181970 was part of the orphaned inode list.  FIXED.
Inode 181972 was part of the orphaned inode list.  FIXED.
Inode 181974 was part of the orphaned inode list.  FIXED.
Inode 181976 was part of the orphaned inode list.  FIXED.
Deleted inode 181978 has zero dtime.  Fix<y>? yes

Inode 181980 was part of the orphaned inode list.  FIXED.
Inode 182261 was part of the orphaned inode list.  FIXED.
Inode 182337 was part of the orphaned inode list.  FIXED.
Inode 182338 was part of the orphaned inode list.  FIXED.
Inode 182409 was part of the orphaned inode list.  FIXED.
Inode 182733 was part of the orphaned inode list.  FIXED.
Inode 182783 was part of the orphaned inode list.  FIXED.
Inode 182880 was part of the orphaned inode list.  FIXED.
Inode 182883 was part of the orphaned inode list.  FIXED.
Inode 182890 was part of the orphaned inode list.  FIXED.
Inode 201071 was part of the orphaned inode list.  FIXED.
Inode 201466 was part of the orphaned inode list.  FIXED.
Inode 202477 was part of the orphaned inode list.  FIXED.
Inode 202524 was part of the orphaned inode list.  FIXED.

Inode 3672356 was part of the orphaned inode list.  FIXED.
Inode 3737668 was part of the orphaned inode list.  FIXED.
Inode 3752990 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:  -398510 -402302 -480906 -(480920--480922) -(481148--481149) -481159 -(723201--723207) -744229 -746655 -(746666--746667) -746671 -959718 -(959725--959726) -959752 -(1991168--1991169) -1991205 -(1991250--1991251) -(1991253--1991256) -2016991 -(2017056--2017059) -2017064 -2017072 -2017081 -(2017088--2017092) -(2017097--2017099) -(2050284--2050297) -(2079788--2079793) -(2079801--2079806) -2079816 -2081314 -(2089088--2089096) -2089104 -(2131880--2131883) -(2131888--2131895) -(2131904--2131914) -(2133043--2133047) -(2133049--2133066) -(2294736--2294740) -2297887 -2300017 -(2300225--2300226) -2300228 -(7504387--7504394) -(7504396--7504403) -(7504405--7504412)
Fix<y>? yes

Free blocks count wrong for group #12 (22, counted=24).
Fix<y>? yes

Free blocks count wrong for group #14 (0, counted=7).
Fix<y>? yes

Free blocks count wrong for group #22 (9, counted=21).
Fix<y>? yes

Free blocks count wrong for group #29 (3, counted=7).
Fix<y>? yes

Free blocks count wrong for group #60 (3, counted=12).
Fix<y>? yes

Free blocks count wrong for group #61 (1, counted=17).
Fix<y>? yes

Free blocks count wrong for group #62 (13, counted=27).
Fix<y>? yes

Free blocks count wrong for group #63 (2, counted=26).
Fix<y>? yes

Free blocks count wrong for group #65 (1, counted=47).
Fix<y>? yes

Free blocks count wrong for group #70 (3, counted=13).
Fix<y>? yes

Free blocks count wrong for group #229 (23375, counted=23399).
Fix<y>? yes

Free blocks count wrong (6856142, counted=6856310).
Fix<y>? yes

Inode bitmap differences:  -181762 -181968 -181970 -181972 -181974 -181976 -181978 -181980 -182261 -(182337--182338) -182409 -182733 -182783 -182880 -182883 -182890 -201071 -201466 -202477 -202524 -3672356 -3737668 -3752990
Fix<y>? yes

Free inodes count wrong for group #11 (6039, counted=6056).
Fix<y>? yes

Free inodes count wrong for group #12 (2472, counted=2476).
Fix<y>? yes

Free inodes count wrong for group #224 (11607, counted=11608).
Fix<y>? yes

Free inodes count wrong for group #228 (11596, counted=11597).
Fix<y>? yes

Free inodes count wrong for group #229 (15196, counted=15197).
Fix<y>? yes

Free inodes count wrong (7777792, counted=7777816).
Fix<y>? yes


/dev/hda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda5: 315880/8093696 files (3.3% non-contiguous), 9303064/16159374 blocks
ho dato sempre yes quando me lo chiedeva, sapreste dirmi se c-[ qualcosa che non va
Avatar utente
badìl
Tenace Tecnocrate
Tenace Tecnocrate
Messaggi: 14806
Iscrizione: mercoledì 22 agosto 2007, 16:20

Re: interpretare output fsck

Messaggio da badìl »

Potevi continuare anche nel topic di prima.  ;D

Ti sta dicendo che il filsystem è stato modificato, è normale.
Riavvia e dovresti essere a posto.
Scrivi risposta

Ritorna a “Driver e periferiche”

Chi c’è in linea

Visualizzano questa sezione: Bing [Bot] e 13 ospiti