LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
To: "zine el abidine Hamid" <zine46@yahoo.fr>
Cc: <gene.heskett@verizon.net>,
"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Detecting I/O error and Halting System : come back
Date: Thu, 7 Dec 2006 07:27:58 -0500 [thread overview]
Message-ID: <Pine.LNX.4.61.0612070713380.16015@chaos.analogic.com> (raw)
In-Reply-To: <20061207110104.74408.qmail@web27706.mail.ukl.yahoo.com>
On Thu, 7 Dec 2006, zine el abidine Hamid wrote:
> Hi evrybody,
>
> I come back with my problem of "I/O error" (refer to
> the following link to reffresh your mind :
> http://groups.google.fr/group/linux.kernel/browse_thread/thread/386b69ca8389cda0/a58d753bf87c4f06?lnk=st&q=hamid+ZINE+EL+ABIDINE&rnum=2&hl=fr#a58d753bf87c4f06
> )
Please don't copy everybody in the universe when you have a problem. That said,
it is likely that you have a bad spot on your hard disk. You can verify this
bu copying the RAW device to the null device and checking for errors. Assume
that your hard disk device was /dev/hda (not /dev/hda1 or other partitions).
You would simply execute from the root account, cp `/dev/hda /dev/null`.
That will read every block on your hard disk. If that does not produce any
errors, then the problem that you have is caused by file-system errors,
not device errors.
To fix file-system errors, you need to restart in single-user mode:
`init 1` should bring you to that mode, then you need to unmount the
file-systems and execute fsck on each of them. If you are unable to unmount
the file systems, then you need to cold boot in single-user mode to do so.
If you have bad blocks then you need to execute `badblocks` with its output
to `fsck -l`. That will map the bad blocks away from the file-system.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.68 BogoMips).
New book: http://www.AbominableFirebug.com/
_
\x1a\x04
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
prev parent reply other threads:[~2006-12-07 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 11:01 zine el abidine Hamid
2006-12-07 12:27 ` linux-os (Dick Johnson) [this message]
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.LNX.4.61.0612070713380.16015@chaos.analogic.com \
--to=linux-os@analogic.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zine46@yahoo.fr \
--subject='Re: Detecting I/O error and Halting System : come back' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).