From: "Frédéric L. W. Meunier" <0@pervalidus.tk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: What may be causing this ? ext3, hard drive, motherboard ?
Date: Sat, 24 May 2003 22:59:48 -0300 (E. South America Standard Time) [thread overview]
Message-ID: <Pine.WNT.4.55.0305242226390.1388@pervalidus> (raw)
3 days ago I noticed the following:
May 22 00:29:25 pervalidus kernel: eth0: Too much work at interrupt, IntrStatus=0x0001.
May 22 00:30:00 pervalidus last message repeated 17 times
May 22 00:30:13 pervalidus last message repeated 5 times
May 22 00:30:24 pervalidus kernel: eth0: Too much work at interrupt, IntrStatus=0x0001.
May 22 00:30:33 pervalidus last message repeated 2 times
May 22 00:30:34 pervalidus last message repeated 2 times
May 22 00:35:21 pervalidus kernel: EXT3-fs error (device ide0(3,7)): ext3_new_b lock: Allocating block in system zone - block = 1573066
May 22 00:38:51 pervalidus kernel: EXT3-fs error (device ide0(3,7)): ext3_new_inode: reserved inode or inode > inodes count - block_group = 0,inode=1
May 22 00:38:51 pervalidus kernel: EXT3-fs error (device ide0(3,7)) in ext3_new_inode: IO failure
I was disconnected from the Internet and most commands stopped
working with "Cannot execute binary file.".
>From /var/log/syslog:
May 22 00:30:39 pervalidus modprobe: modprobe: Can't locate module binfmt-0804
May 22 00:31:14 pervalidus last message repeated 26 times
May 22 00:32:19 pervalidus last message repeated 52 times
May 22 00:33:24 pervalidus last message repeated 52 times
May 22 00:34:25 pervalidus last message repeated 52 times
May 22 00:35:30 pervalidus last message repeated 52 times
May 22 00:36:35 pervalidus last message repeated 52 times
May 22 00:37:40 pervalidus last message repeated 52 times
May 22 00:38:41 pervalidus last message repeated 54 times
May 22 00:39:46 pervalidus last message repeated 54 times
May 22 00:40:51 pervalidus last message repeated 54 times
May 22 00:42:24 pervalidus last message repeated 8 times
On reboot:
May 22 01:01:52 pervalidus kernel: EXT3-fs error (device ide0(3,7)): ext3_new_inode: reserved inode or inode > inodes count - block_group = 0,inode=2
May 22 01:01:52 pervalidus kernel: EXT3-fs error (device ide0(3,7)) in ext3_new_inode: IO failure
I manually ran fsck and it "fixed" (there were some messages
about duplicate/bad blocks) everything, leaving 3 files I
recovered in /lost+found, but this undeletable:
br-s--xr-x 1 28260 28532 0, 0 Sep 22 2014 #1570049
#1570049: setuid block special (0/0)
smartmontools doesn't report any errors besides the high
Hardware_ECC_Recovered, which increased after I ran all
read-only Maxtor's Powermax tests (from 3 to almost 5 million),
but the latter didn't find anything wrong either.
Should I replace it ? There was also a crash today on Windows,
and after using reset the hard drive restarted
(Start_Stop_Count increased by 1), what it only does when you
power on or use sleep / wake up.
--
0@pervalidus.{tk, dyndns.org}
reply other threads:[~2003-05-25 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.WNT.4.55.0305242226390.1388@pervalidus \
--to=0@pervalidus.tk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®