Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 2004 21:59:43 +1000
From:      "Tim McCullagh" <timbo@halenet.com.au>
To:        "Putinas Piliponis" <putinas.piliponis@icnspot.net>
Cc:        freebsd-isp@FreeBSD.ORG
Subject:   Re: fsck 
Message-ID:  <535501c3df4c$e49144e0$6500a8c0@halenet.com.au>
References:  <534601c3df4a$0e8ef650$6500a8c0@halenet.com.au> <004401c3df4b$abe1f780$1e64a8c0@spotripoli.local>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Putinas


----- Original Message -----
From: "Putinas Piliponis" <putinas.piliponis@icnspot.net>
To: "Tim McCullagh" <timbo@halenet.com.au>
Sent: Tuesday, January 20, 2004 9:50 PM
Subject: Re: fsck


> if it's mounted - unmount

It is unmounted

> and you just do fsck /dev/da1s1f

That is what I thought and am doing.  The only problem is that when I do
that it comes up with the following errors and then seems to freeze. Or
perhaps I am not waiting long enough

cathy# fsck /dev/da1s1f
** /dev/da1s1f
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes
CANNOT READ: BLK 29163616
UNEXPECTED SOFT UPDATE INCONSISTENCY

CONTINUE? [yn] y

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 29163616,
** Phase 2 - Check Pathnames
MISSING '.'  I=1759514  OWNER=1002 MODE=40700
SIZE=512 MTIME=Jan 20 09:58 2004
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

MISSING '..'  I=1759514  OWNER=1002 MODE=40700
SIZE=512 MTIME=Jan 20 09:58 2004
DIR=/spool/postfix/deferred/C

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

Message from syslogd@cathy at Tue Jan 20 22:05:56 2004 ...
cathy /kernel: <<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>>

Then It freezes or continues to give
cathy /kernel: <<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>>
errors

Should I just leave it and wait?

Regards

Tim


> ----- Original Message -----
> From: "Tim McCullagh" <timbo@halenet.com.au>
> To: <freebsd-isp@FreeBSD.ORG>
> Sent: Tuesday, January 20, 2004 1:39 PM
> Subject: fsck
>
>
> > Hi Fellows
> >
> > Can someone shed some light on whether it is possible to do a fsck check
> > on
> > a dirty file system if it is installed (and not mounted) as a second HDD
> > on
> > a new system install.  I have a mail server that crashed this morning
and
> > now fails to boot even into single user mode.
> >
> > So I installed a clean install of FreeBSD 4.9 on a spare HDD and have
> > tried
> > to mount the old drive, but it complains about a  "Filesystem is not
> > clean -
> > run fsck".   When I do this it seems to want to "WARNING: R/W mount of
> > /var
> > denied."      /var is already mounted on da0s1f.   Is there any way to
run
> > fsck to clean up the filesystem on /dev/da1s1f so that it can be mounted
> > as
> > a second  HDD in this type of setup?
> >
> > Are there any other suggestions as to how to clean it up?
> >
> > Regards
> >
> > Tim
> >
> > _______________________________________________
> > freebsd-isp@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
> >
> >
>
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?535501c3df4c$e49144e0$6500a8c0>