On Thu, Feb 15, 2001 at 09:48:49PM -0800, Nick wrote:
> it tells me running e2fsck is recommended.
>
> after I run it (e2fsck /dev/hde5),
> it still says the same message.
>
> How do you overcome the annoyance.
>
> Thanks list members
You posted about this once before. Did you try -
tune2fs
Sorry. It's a Maxtor 234MB IDE drive. I have installed Debian on other,
identical drives before and have never had a problem.
BTW, this is quite a new install (beginning of the week) and it's running
version 1.2.16.
Later,
Kevin
> hi I have a similar problem with a fijitsu 2.57gig drive. wha
hi I have a similar problem with a fijitsu 2.57gig drive. what kind of
drive do you have and any other information would be useful to help you out.
Paul
On Fri, 25 Apr 1997, Kevin Traas wrote:
> This is a first for me
>
> This has just started showing up on the console and in /var/log/m
[regarding chronic filesystem errors]
About the only additional thing I can suggest is upgrading your kernel
(we are now at 2.0.13, I think) and watching to see if the problem goes
away.
Bruce
On Fri, 23 Aug 1996, Luca Maranzano wrote:
> Bruce Perens wrote:
>
> > > I've tryed to e2fsck /dev/hdc2 (thinking that device 16:02 corresponds
> > > to /dev/hdc2) and it found a lot of errors, but it seemed that e2fsck
> > > was able to correct them all; after rebooting similar messages appeared
Bruce Perens wrote:
> > I've tryed to e2fsck /dev/hdc2 (thinking that device 16:02 corresponds
> > to /dev/hdc2) and it found a lot of errors, but it seemed that e2fsck
> > was able to correct them all; after rebooting similar messages appeared
> > again after some hours.
>
> > Any clue about thi
> The first question is this: which device are 16:02 and 16:01 ?
> I looked in /dev searching for devices whith major number 16 but
> I didn't found any. Shouldn't hda and hdc correspond to major 3 and 22 ?
The message is in hex (which is probably a mistake). It's hdc2 and hdc1.
> I've tryed to e
7 matches
Mail list logo