On Tue, 21 Jun 2005 13:00, Steve Holdoway wrote: > man tune2fs There is a bit more to it than that. You cannot do a repairing file check on a mounted filesystem. Doing so will kill off the data set with a fair degree of certainty, so the only safe way to do so is to boot the machine using different root and boot partitions.
Toms root and boot. ( Floppy ) http://www.toms.net/rb/ 0r BG-Rescue ( Two floppies, but imho better than Tom's because chroot works ) http://www.giannone.de But apparently NZ is not the only country in the world where back-hoe diggers occasionally have intimate, earthy, and catastrophic relationships with fibre cables :-) so I've put the diskette images here:- http://shell.clug.net.nz:8080/~chris/ Not the latest, but good enough. Or Knoppix ( CDROM ) Download per BitTorrent: http://torrent.unix-ag.uni-kl.de/ 3.9 is out! > On Tue, June 21, 2005 12:47 pm, Maurice Butler said: > > Hi all, > > running e2fsck -n -f on my ipcop box I hav problems on the root drive. > > how > > do i force it to fix the disk on the next reboot. > > > > Maurice > > > > [EMAIL PROTECTED]:~ # df -h > > Filesystem Size Used Avail Use% Mounted on > > rootfs 1.1G 194M 846M 19% / > > /dev/root 1.1G 194M 846M 19% / > > /dev/harddisk1 16M 3.8M 12M 25% /boot > > /dev/harddisk2 3.0G 158M 2.7G 6% /var/log > > [EMAIL PROTECTED]:~ # e2fsck -n -f /dev/root > > e2fsck 1.35 (28-Feb-2004) > > Warning! /dev/root is mounted. > > Warning: skipping journal recovery because doing a read-only filesystem > > check. > > 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 > > Block bitmap differences: +136190 -136193 > > Fix? no > > > > > > /dev/root: ********** WARNING: Filesystem still has errors ********** > > > > /dev/root: 5578/136800 files (0.3% non-contiguous), 53863/273105 blocks > > [EMAIL PROTECTED]:~ #
