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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 7 Dec 2006 07:27:58 -0500
From:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To:	"zine el abidine Hamid" <zine46@...oo.fr>
Cc:	<gene.heskett@...izon.net>,
	"Linux kernel" <linux-kernel@...r.kernel.org>
Subject: Re: Detecting I/O error and Halting System  : come back

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/
_
..

****************************************************************
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@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/