dcro | j'ai un e2fsck qui c'est tout seul au (après n montage) sur un soft RAID qui me sert de système.
Depuis plus moyen de booter ! 
En faisant e2fsck /dev/md0, j'obtiens :
Code :
- root@1800xp didier # e2fsck -n /dev/md0
- e2fsck 1.33 (21-Apr-2003)
- /dev/md0 contains a file system with errors, check forced.
- Pass 1: Checking inodes, blocks, and sizes
- Pass 2: Checking directory structure
- Pass 3: Checking directory connectivity
- Unconnected directory inode 325412 (/var/lib/init.d/???)
- Connect to /lost+found? no
- '..' in ... (325412) is /var/lib/init.d (325411), should be <The NULL inode> (0).
- Fix? no
- Unconnected directory inode 328210 (/var/lib/init.d/???)
- Connect to /lost+found? no
- '..' in ... (328210) is /var/lib/init.d (325411), should be <The NULL inode> (0).
- Fix? no
- Pass 4: Checking reference counts
- Inode 325412 ref count is 2, should be 1. Fix? no
- Inode 328210 ref count is 2, should be 1. Fix? no
- Pass 5: Checking group summary information
- /dev/md0: ********** WARNING: Filesystem still has errors **********
- /dev/md0: 237295/1251712 files (0.7% non-contiguous), 861986/2500048 blocks
|
Une ideé ?
Message édité par dcro le 28-07-2003 à 21:55:51
|
