On 09/07/2015 01:23 PM, Sam Smith wrote:
Hello,
I've been getting some strange fsck errors for over a year now on my
Debian 8 workstation. See photo: http://tinyurl.com/otzxebh Ignore the
softreset errors. I can't really remember when the issue started, but it
was sometime after I u
On 09/09/2015 01:11 PM, David Wright wrote:
Quoting Sam Smith (deb...@net153.net):
Another issue is when a fsck actually does run, systemd doesn't
display the output, the screen just hangs for 20 minutes or so which
to the unknown user, they may reboot the machine and screw stuff up.
Is that ju
On 09/09/2015 08:10 AM, Linux 4 Bene wrote:
Op Mon, 07 Sep 2015 13:23:03 -0500, schreef Sam Smith:
Hello,
I've been getting some strange fsck errors for over a year now on my
Debian 8 workstation. See photo: http://tinyurl.com/otzxebh Ignore the
softreset errors. I can't really rem
Quoting Sam Smith (deb...@net153.net):
> Another issue is when a fsck actually does run, systemd doesn't
> display the output, the screen just hangs for 20 minutes or so which
> to the unknown user, they may reboot the machine and screw stuff up.
> Is that just the nature of systemd or is there a
Op Mon, 07 Sep 2015 13:23:03 -0500, schreef Sam Smith:
> Hello,
>
> I've been getting some strange fsck errors for over a year now on my
> Debian 8 workstation. See photo: http://tinyurl.com/otzxebh Ignore the
> softreset errors. I can't really remember when the is
Hello,
I've been getting some strange fsck errors for over a year now on my
Debian 8 workstation. See photo: http://tinyurl.com/otzxebh Ignore the
softreset errors. I can't really remember when the issue started, but it
was sometime after I upgraded to using systemd. I kept thinkin
I downloaded 1.38-2 e2fsprogs and e2fslib and used dpkg -i to install. LazarAndrew Sackville-West <[EMAIL PROTECTED]> wrote: Z F wrote:> > << big snip >>> > In my case, I downgraded the e2fsprogs to 1.38-2 and the errors went > away.So, even it it is not e2fsprogs, downgrading the package fixed> t
Z F wrote:
<< more snippidity doo da >>
In my case, I downgraded the e2fsprogs to 1.38-2 and the errors went
away.So, even it it is not e2fsprogs, downgrading the package fixed
the problem. Some other rudimentary errors remain though.
THese have to do with complains that some files are corr
Z F wrote:
<< big snip >>
In my case, I downgraded the e2fsprogs to 1.38-2 and the errors went
away.So, even it it is not e2fsprogs, downgrading the package fixed
the problem. Some other rudimentary errors remain though.
THese have to do with complains that some files are corrupted
in /etc/
Paulo Marcel Coelho Aragao wrote:
Andrew Sackville-West wrote on Dec, 16:
[...]
errors look like this
/dev/hda3: Superblock last mount time is in the future
/dev/hda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
<<>>
My understanding (or lack of) is:
1. When you mount a partition or
Paulo Marcel Coelho Aragao <[EMAIL PROTECTED]> wrote: Andrew Sackville-West wrote on Dec, 16:[...]> >>errors look like this> >>> >>/dev/hda3: Superblock last mount time is in the future> >>/dev/hda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY[...]> >This has just happened to me when I booted with
Andrew Sackville-West wrote on Dec, 16:
[...]
> >>errors look like this
> >>
> >>/dev/hda3: Superblock last mount time is in the future
> >>/dev/hda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
[...]
> >This has just happened to me when I booted with a Knoppix Live CD and
> >mounted /dev/hda1
Paulo Marcel Coelho Aragao wrote:
Andrew Sackville-West wrote on Dec, 16:
[...]
errors look like this
/dev/hda3: Superblock last mount time is in the future
/dev/hda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
[...]
This has just happened to me when I booted with a Knoppix Live CD a
ve been off this list for a while, so excuse me if I missed something...recently did a pretty big apt-get upgrade (probably 2 months worth) and now I get massive fsck errors on my boot, halting boot and dumping me to a shell.errors look like this/dev/hda3: Superblock last mount time is in the futu
Andrew Sackville-West wrote on Dec, 16:
[...]
> recently did a pretty big apt-get upgrade (probably 2 months worth) and
> now I get massive fsck errors on my boot, halting boot and dumping me to
> a shell.
>
> errors look like this
>
> /dev/hda3: Superblock last mount
I've been off this list for a while, so excuse me if I missed something...
recently did a pretty big apt-get upgrade (probably 2 months worth) and
now I get massive fsck errors on my boot, halting boot and dumping me to
a shell.
errors look like this
/dev/hda3: Superblock last mount ti
hi,
can anyone tell me why it is that every time my filesystems are
checked i get these errors:
(this is my /var filesystem)
/dev/hda7: Setting filetype for entry 'showq' in
/spool/postfix/public (45244) to 6.
/dev/hda7: Setting filetype for entry 'cleanup' in
/spool/postfix/private (100745
hi,
today i had a fsck run and for it looks like every socket type file
fsck reported:
set file type on entry `whatever' in /what/ever (inode) to 6
or something to that effect, I reran fsck again and it reported the
same errors again, I even tared the /var/ filesystem (most of these
files a
18 matches
Mail list logo
