On Thu, May 16, 2002 at 02:43:17AM +0000, yan bai wrote: > >> some error messages are as the following: > >> /////////BEGIN ERROR MESSAGE > >> checking root filesystem > >> /:Duplicate blocks found... invoking duplicate block passes > >> Pass1B: Rescan for duplicate/bad blocks > >> /:Duplicate/bad blocks in inode 52:/: 1661/: > >> /:Duplicate/bad blocks in inode 53:/: 1662/: > >> /:Duplicate/bad blocks in inode 71:/: 1662/: > >> /:Duplicate/bad blocks in inode 74:/: 1661/: > >> > >> /:Pass1C: Scan directories for inodes with duplicate blocks > >> /:Pass1D: Reconciling duplicate blocks > >> /:(There are 4 inodes containing duplicate/bad blocks) > >> /:File /root/.gnome/session(inode#74.) has 1 duplicate block(s), shared > >with > >> 1 file(s) > >> /: /root/panel.d/default/Applet_4.desktop (inode#52) > >> ////////END OF ERROR MESSAGE > I tried to use fsck under the root, but I was told I should use boot > instead of directories. so I used the disk to boot into rescue mode, which > gave a shell prompt as sh-2.04, the following is what I tried and the > message I got. > > sh-2.04# fsck /dev/sda1 <ENTER> > parallelizing fsck version 1.19 (13-Jul-2000) > e2fsck 1.19 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 > /boot:clean, 27/14056 files, 5616/56190 blocks ^^^^^ You aren't checking the right partition. /dev/sda1 is the /boot partition. You need to check the '/', or root partition. I don't know what your partition layout is, /dev/sda1 clearly isn't right. Maybe /dev/sda2? You were told to use devices, not directory names, by the way. You may want to pick up an intro Linux system administration book. "Linux for Dummies" isn't a bad intro-level text, although there are many good books out there who can help up newcomers get up to speed to Linux. - Ted
