Prev: xdm autologin important for tiny devices
Next: Connecting the droid to a Debian workstation
From: Merciadri Luca on 1 Jun 2010 03:40
Hi,

When booting my computer this morning, fsck was not happy. Here is what
it said:

==
# cat /var/log/fsck/checkfs
Log of fsck -C -R -A -a
Tue Jun 1 09:00:07 2010

fsck 1.41.3 (12-Oct-2008)
/dev/sdc5 has been mounted 50 times without being checked, check forced.
/dev/sdc5: Inode 18554881 is in use, but has dtime set. FIXED.
/dev/sdc5: Inode 18554881 has imagic flag set.

/dev/sdc5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4
==

What could I do when running fsck manually? Do I need to unmount the
related filesystem (i.e. /dev/sdc5) to check it, or not? And what do I
need to specify?
Thanks.

--
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
I use PGP. If there is an incompatibility problem with your mail
client, please contact me.


If it's worth doing, it's worth over-doing.

From: Andrew M.A. Cater on 1 Jun 2010 03:50
On Tue, Jun 01, 2010 at 09:29:27AM +0200, Merciadri Luca wrote:
> Hi,
>
> When booting my computer this morning, fsck was not happy. Here is what
> it said:
>
> ==
> # cat /var/log/fsck/checkfs
> Log of fsck -C -R -A -a
> Tue Jun 1 09:00:07 2010
>
> fsck 1.41.3 (12-Oct-2008)
> /dev/sdc5 has been mounted 50 times without being checked, check forced.
> /dev/sdc5: Inode 18554881 is in use, but has dtime set. FIXED.
> /dev/sdc5: Inode 18554881 has imagic flag set.
>
> /dev/sdc5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> (i.e., without -a or -p options)
> fsck died with exit status 4
> ==
>

e2fsck [-y] /dev/sdc5

[The optional -y answers "yes" to the prompts saying "Fix.[y/n]

e2fsck -a attempts an automatic fix of the commonest errors but is conservative and makes minimal
changes. If it fails / there's more than one thing wrong, it will bail out and ask for a manual fix, in
my experience anyway.

> What could I do when running fsck manually? Do I need to unmount the
> related filesystem (i.e. /dev/sdc5) to check it, or not? And what do I
> need to specify?

If you don't unmount it, e2fsck will complain. If need be, boot from a rescue disk to do so
- but I'm assuming that it's not the root (/) filesystem, or you wouldn't have got this far.

> Thanks.
>

Hope this helps,

All the best,

AndyC
> --
> Merciadri Luca
> See http://www.student.montefiore.ulg.ac.be/~merciadri/
> I use PGP. If there is an incompatibility problem with your mail
> client, please contact me.
>
>
> If it's worth doing, it's worth over-doing.
>




--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100601074439.GA22123(a)galactic.demon.co.uk
From: Merciadri Luca on 1 Jun 2010 05:50
Andrew M.A. Cater wrote:
> On Tue, Jun 01, 2010 at 09:29:27AM +0200, Merciadri Luca wrote:
>
>
> e2fsck [-y] /dev/sdc5
>
> [The optional -y answers "yes" to the prompts saying "Fix.[y/n]
>
> e2fsck -a attempts an automatic fix of the commonest errors but is conservative and makes minimal
> changes. If it fails / there's more than one thing wrong, it will bail out and ask for a manual fix, in
> my experience anyway.
>
Thanks.
> If you don't unmount it, e2fsck will complain. If need be, boot from a rescue disk to do so
> - but I'm assuming that it's not the root (/) filesystem, or you wouldn't have got this far.
>
It will complain, but will it impede its `functioning'? I will probably
try with a rescue disk, effectively. What could have caused such errors
if I did not mistreat my computer these days?

--
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
I use PGP. If there is an incompatibility problem with your mail
client, please contact me.




From: Merciadri Luca on 1 Jun 2010 09:50
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Andrew M.A. Cater" <amacater(a)galactic.demon.co.uk> writes:

> On Tue, Jun 01, 2010 at 09:29:27AM +0200, Merciadri Luca wrote:
>> Hi,
>>
>> When booting my computer this morning, fsck was not happy. Here is what
>> it said:
>>
>> ==
>> # cat /var/log/fsck/checkfs
>> Log of fsck -C -R -A -a
>> Tue Jun 1 09:00:07 2010
>>
>> fsck 1.41.3 (12-Oct-2008)
>> /dev/sdc5 has been mounted 50 times without being checked, check forced.
>> /dev/sdc5: Inode 18554881 is in use, but has dtime set. FIXED.
>> /dev/sdc5: Inode 18554881 has imagic flag set.
>>
>> /dev/sdc5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>> (i.e., without -a or -p options)
>> fsck died with exit status 4
>> ==
>>
>
> e2fsck [-y] /dev/sdc5
>
> [The optional -y answers "yes" to the prompts saying "Fix.[y/n]
>
> e2fsck -a attempts an automatic fix of the commonest errors but is conservative and makes minimal
> changes. If it fails / there's more than one thing wrong, it will bail out and ask for a manual fix, in
> my experience anyway.
Ok. I had to use e2fsck -y, and everything worked. This was clearly a
mess on my HDD, apparently. It must be dying. But I am still unable to
explain this. Thanks, though.

- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
- --

What doesn't kill you will make you stronger. (Friedrich Nietzsche)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAkwFDOwACgkQM0LLzLt8Mhy59wCeJf1eK1gfHFiIXxTQU+46xLoK
z3UAoKCd3FQ4IXWjQzfYtMMVagMZ4HsG
=QGl6
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/87bpbuswlu.fsf(a)merciadriluca-station.MERCIADRILUCA
From: Ron Johnson on 1 Jun 2010 09:50
On 06/01/2010 04:38 AM, Merciadri Luca wrote:
[snip]
> It will complain, but will it impede its `functioning'? I will probably
> try with a rescue disk, effectively. What could have caused such errors
> if I did not mistreat my computer these days?
>

Bug(s) in the OS or HDD firmware?

--
Dissent is patriotic, remember?


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C050E1B.2000702(a)cox.net
 |  Next  |  Last
Pages: 1 2
Prev: xdm autologin important for tiny devices
Next: Connecting the droid to a Debian workstation