Detecting I/O error and Halting System : come back

Detecting I/O error and Halting System : come back

[zine el abidine Hamid]

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
)


I come back with a last question and I swear that I'll
stop annoying you with this problem.
Can you explain me why it seems that some part of the
hard drive are read only and others seems totaly
disepeared?
Some commands are available and works fine, others
generate an error like this : 

-bash: /bin/some_command: Input/output error

Can you explain that? 
Can I consider that the commands that are available
are in fact in the memory/cache and not read from the
hard drive?

Executing "e2fsck" turns sometimes in short : I got
"Bus error".
When I execute again "e2fsck" I optain this errors :
Error reading block XXXX ( Attempt to read block from
filesystem resulted in short read). Ignore error?
...
...
Inode XYZW (...) has bad mode (00).
Clear?
...



When I try to write to a file (that I can read and
that is not empty), I loose it ?(size = 0, and the
content seems to be gone away...)

Why, when I execute the shutdown commande, I got a bus
error?




Some Linux users pointed a journal commit problem;
what do you think about?
( see the link :
http://groups.google.fr/group/comp.os.linux.misc/browse_thread/thread/7b51af5a197d4ff3/facf167c3354a06f?lnk=st&q=bash+I%2FO+error&rnum=7&hl=fr#facf167c3354a06f
)


I googled and found that there are lot off similar
cases :
http://groups.google.fr/group/linux.redhat/browse_frm/thread/35cbedb6667755ed/64dc7232177c7dc8?lnk=st&q=bash%3A+Input%2Foutput+error&rnum=25&hl=fr#64dc7232177c7dc8
http://groups.google.fr/group/fa.linux.kernel/browse_frm/thread/87546535d17c674b/030caa62ad099af9?lnk=st&q=bash%3A+%2Fusr%2Fbin%2F%3A+Input%2Foutput+error&rnum=6&hl=fr#030caa62ad099af9
http://groups.google.fr/group/fa.linux.kernel/browse_frm/thread/60d92e4bb6a5f4db/18e69ef0d46448ac?lnk=st&q=bash%3A+%2Fusr%2Fbin%2F%3A+Input%2Foutput+error&rnum=10&hl=fr#18e69ef0d46448ac
http://groups.google.fr/group/comp.os.linux.misc/browse_frm/thread/a006864077740438/f08d570d516657c1?lnk=st&q=bash%3A+%2Fusr%2Fbin%2F%3A+Input%2Foutput+error&rnum=5&hl=fr#f08d570d516657c1
http://groups.google.fr/group/fa.linux.kernel/browse_frm/thread/60d92e4bb6a5f4db/18e69ef0d46448ac?lnk=st&q=bash%3A+%2Fusr%2Fbin%2F%3A+Input%2Foutput+error&rnum=10&hl=fr#18e69ef0d46448ac
http://groups.google.fr/group/alt.e-smith.fr/browse_frm/thread/44176232ffc3c1a6/5b35e4771b8030a7?lnk=st&q=bash%3A+%2Fusr%2Fbin%2F%3A+Input%2Foutput+error&rnum=63&hl=fr#5b35e4771b8030a7
http://groups.google.fr/group/comp.os.linux.misc/browse_frm/thread/137246f4bf738e2/b26503666b86972d?lnk=st&q=bash%3A+Input%2Foutput+error&rnum=3&hl=fr#b26503666b86972d
http://groups.google.fr/group/comp.os.linux.misc/browse_frm/thread/a006864077740438/f08d570d516657c1?lnk=st&q=bash%3A+Input%2Foutput+error&rnum=13&hl=fr#f08d570d516657c1
http://groups.google.fr/group/linux.gentoo.user/browse_frm/thread/678951cec2655493/54ed838422331550?lnk=st&q=bash%3A+Input%2Foutput+error&rnum=35&hl=fr#54ed838422331550



	

	
		
___________________________________________________________________________ 
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com

Re: Detecting I/O error and Halting System : come back

[linux-os (Dick Johnson)]

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.