Ext4 file system check errors

[DrTeeth]

I have just had BIBM produce an "Error 15" on an ext4 file system. The
OS is working well. What does this error mean?

I have been searching for how to fix an unmounted file system--- 30
mins later, succeeded.

However, fsck -p /dev/sda3/ declares the drive clean and disagrees
with BIBM. Where do I go from here?
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).

[TeraByte Support]

You may have to force the check with -f

note that you should not do that on a live mounted partition or you'll have
problems.

"DrTeeth" wrote in message news:4386@public.bootitbm...

I have just had BIBM produce an "Error 15" on an ext4 file system. The
OS is working well. What does this error mean?

I have been searching for how to fix an unmounted file system--- 30
mins later, succeeded.

However, fsck -p /dev/sda3/ declares the drive clean and disagrees
with BIBM. Where do I go from here?
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).

[DrTeeth]

On Thu, 17 Jan 2013 21:21:09 PST, just as I was about to take a herb,
"TeraByte Support" disturbed my
reverie and wrote:

>You may have to force the check with -f

I did a check and it came back clean. I did not have to force
anything. I'll explain my methodology.

I booted a Linux distro after making the error partition visible. I
ran fsck -p /dev/sda and got no errors.
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).

[TeraByte Support]

try again after booting or running the fsck.

"DrTeeth" wrote in message news:4396@public.bootitbm...

On Thu, 17 Jan 2013 21:21:09 PST, just as I was about to take a herb,
"TeraByte Support"

disturbed my
reverie and wrote:

>You may have to force the check with -f

I did a check and it came back clean. I did not have to force
anything. I'll explain my methodology.

I booted a Linux distro after making the error partition visible. I
ran fsck -p /dev/sda

and got no errors.
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).

[DrTeeth]

On Fri, 18 Jan 2013 18:30:07 PST, just as I was about to take a herb,
"TeraByte Support" disturbed my
reverie and wrote:

>try again after booting or running the fsck.

All was well with both partitions after running fsck and rebooting.
Thanks.

For others, a useful command, 'lsblk' lists all block devices. Another
method I used to find the name of a partition to use in the fsck
command gave a UUID which sis not work
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).