[Question] Harddisk Error!!!
Hello List :
i have some problem as following :
fileserver:/# e2fsck -v -y /dev/hda
bash: /sbin/e2fsck: Input/output error
then,i check /var/log/mesagg
fileserver:/# tail -10 /var/log/messages
Apr 15 03:09:37 fileserver kernel: ide0: reset: success
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: status=0x61 {
DriveReady DeviceFault Error }
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: error=0x04 {
DriveStatusError }
Apr 15 03:09:37 fileserver kernel: end_request: I/O error, dev 03:03 (hda),
sector 37492776
Apr 15 03:09:37 fileserver kernel: hda: recal_intr: status=0x61 { DriveReady
DeviceFault Error }
Apr 15 03:09:37 fileserver kernel: hda: recal_intr: error=0x04 {
DriveStatusError }
Apr 15 03:09:37 fileserver kernel: ide0: reset: success
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: status=0x61 {
DriveReady DeviceFault Error }
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: error=0x04 {
DriveStatusError }
Apr 15 03:09:37 fileserver kernel: ide0: reset: success
it seems, my harddisk crash?or my kernel problem?
anybody knows how to solve this problem?? @_@
--
Trust Unique ...
axacheng [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!!
On Monday 15 April 2002 12:02 am, axacheng wrote:
Hello List :
i have some problem as following :
fileserver:/# e2fsck -v -y /dev/hda
bash: /sbin/e2fsck: Input/output error
then,i check /var/log/mesagg
fileserver:/# tail -10 /var/log/messages
Apr 15 03:09:37 fileserver kernel: ide0: reset: success
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: status=0x61 {
DriveReady DeviceFault Error } Apr 15 03:09:37 fileserver kernel: hda:
set_geometry_intr: error=0x04 { DriveStatusError } Apr 15 03:09:37
fileserver kernel: end_request: I/O error, dev 03:03 (hda), sector 37492776
Apr 15 03:09:37 fileserver kernel: hda: recal_intr: status=0x61 {
DriveReady DeviceFault Error } Apr 15 03:09:37 fileserver kernel: hda:
recal_intr: error=0x04 { DriveStatusError } Apr 15 03:09:37 fileserver
kernel: ide0: reset: success
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: status=0x61 {
DriveReady DeviceFault Error } Apr 15 03:09:37 fileserver kernel: hda:
set_geometry_intr: error=0x04 { DriveStatusError } Apr 15 03:09:37
fileserver kernel: ide0: reset: success
it seems, my harddisk crash?or my kernel problem?
anybody knows how to solve this problem?? @_@
I am by no means an expert about HD's, but I just had an IBM TravelStar 48GB
laptop HD bite the dust with errors identical to these. Bad blocks growing
rapidly. In fact I am just now getting everything back up on the replacement
from Dell, but because of many many errors in /usr when tranferring from the
bad HD to the replacement, I am going to wipe it and reinstall.
I don't know what you're hardware is, and I don't know about generic utils,
but I used Dell's 32bit Diagnostic util in order to get them to
replace the drive under warrenty.
Good luck,
--
J. Patrick Lanigan
Debian Linux - 2.4.18 on vagabond
00:17:46 up 7:58, 1 users, load average: 1.13, 1.16, 1.10
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!!
hi ya axacheng
fileserver:/# e2fsck -v -y /dev/hda
bash: /sbin/e2fsck: Input/output error
you cannot run e2fsck on a disk... you need to run e2fsck on
ext2 partitions
e2fsck /dev/hda1
e2fsck /dev/hda2 ...
NOTE... do NOT run e2sck on your mounted root partition
( read the warnings you would be getting especially root
partition...
( ie... dont do -v -y in your example or you'd
( be creating major problems on your machines
the error messages may be real or self-induced mis-leading errors...
if you do NOT have any of those seek errors in your logs, than
i'd not worry about your disk yet ...
am assuming that there are no such warnings other than
on Mar 15 03:09 which is exactly the same time you rand the
erroneous e2fsck command
if yu do have tons of these error at all times of the day and nights
than you have a dying disks...
- copy off all your data to a new backup disks
- start replacing the ide cables and wiggle it and see
if there is good connections or shorts or other whacky stuff
c ya
alvin
then,i check /var/log/mesagg
fileserver:/# tail -10 /var/log/messages
Apr 15 03:09:37 fileserver kernel: ide0: reset: success
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: status=0x61 {
DriveReady DeviceFault Error }
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: error=0x04 {
DriveStatusError }
Apr 15 03:09:37 fileserver kernel: end_request: I/O error, dev 03:03 (hda),
sector 37492776
Apr 15 03:09:37 fileserver kernel: hda: recal_intr: status=0x61 { DriveReady
DeviceFault Error }
Apr 15 03:09:37 fileserver kernel: hda: recal_intr: error=0x04 {
DriveStatusError }
Apr 15 03:09:37 fileserver kernel: ide0: reset: success
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: status=0x61 {
DriveReady DeviceFault Error }
Apr 15 03:09:37 fileserver kernel: hda: set_geometry_intr: error=0x04 {
DriveStatusError }
Apr 15 03:09:37 fileserver kernel: ide0: reset: success
it seems, my harddisk crash?or my kernel problem?
anybody knows how to solve this problem?? @_@
--
Trust Unique ...
axacheng [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!!
On Sunday 14 April 2002 10:40 pm, Alvin Oga wrote: hi ya axacheng fileserver:/# e2fsck -v -y /dev/hda bash: /sbin/e2fsck: Input/output error you cannot run e2fsck on a disk... you need to run e2fsck on ext2 partitions e2fsck /dev/hda1 e2fsck /dev/hda2 ... NOTE... do NOT run e2sck on your mounted root partition ( read the warnings you would be getting especially root partition... ( ie... dont do -v -y in your example or you'd ( be creating major problems on your machines the error messages may be real or self-induced mis-leading errors... if you do NOT have any of those seek errors in your logs, than i'd not worry about your disk yet ... am assuming that there are no such warnings other than on Mar 15 03:09 which is exactly the same time you rand the erroneous e2fsck command if yu do have tons of these error at all times of the day and nights than you have a dying disks... - copy off all your data to a new backup disks - start replacing the ide cables and wiggle it and see if there is good connections or shorts or other whacky stuff can you indicate some point of reference to justify that claim? my system runs e2fsck by default after every 20 bootups, and i've yet to notice any damage due to that. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!! - damage
hi ya can you indicate some point of reference to justify that claim? my system runs e2fsck by default after every 20 bootups, and i've yet to notice any damage due to that. sorry for the confusing comment... on your box... try to run e2fsck /dev/hda1 if your / is on /dev/hda1 normal bootups is configured to do the right thing in the right sequence so is NOT an problem like a user running e2fsck on a mounted root partition .,,, a very bad idea... but if you umount it first.. than its cool mount -n -o ro /dev/hda1 - take / offline first e2fsck /dev/hda1 mount /dev/hda1 -- put it back online and always a good idea to look at any warnings/error messages spewed out by the system... c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 14 April 2002 10:44 pm, ben wrote: On Sunday 14 April 2002 10:40 pm, Alvin Oga wrote: hi ya axacheng fileserver:/# e2fsck -v -y /dev/hda bash: /sbin/e2fsck: Input/output error you cannot run e2fsck on a disk... you need to run e2fsck on ext2 partitions e2fsck /dev/hda1 e2fsck /dev/hda2 ... NOTE... do NOT run e2sck on your mounted root partition ( read the warnings you would be getting especially root partition... ( ie... dont do -v -y in your example or you'd ( be creating major problems on your machines the error messages may be real or self-induced mis-leading errors... if you do NOT have any of those seek errors in your logs, than i'd not worry about your disk yet ... am assuming that there are no such warnings other than on Mar 15 03:09 which is exactly the same time you rand the erroneous e2fsck command if yu do have tons of these error at all times of the day and nights than you have a dying disks... - copy off all your data to a new backup disks - start replacing the ide cables and wiggle it and see if there is good connections or shorts or other whacky stuff can you indicate some point of reference to justify that claim? my system runs e2fsck by default after every 20 bootups, and i've yet to notice any damage due to that. ben Greetings Ben: I think 'boot' is the keyword, where the root file system has yet to be mounted. - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8umyrZHBxKsta6kMRAhMaAKCkjU45cvLDUqlgtAx0QjqrNTxp/wCdGWO4 7C4wxmS1q53965ZZUQsdWYo= =SV6b -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!! - damage
On Sunday 14 April 2002 11:00 pm, Alvin Oga wrote: hi ya can you indicate some point of reference to justify that claim? my system runs e2fsck by default after every 20 bootups, and i've yet to notice any damage due to that. sorry for the confusing comment... on your box... try to run e2fsck /dev/hda1 if your / is on /dev/hda1 normal bootups is configured to do the right thing in the right sequence so is NOT an problem like a user running e2fsck on a mounted root partition .,,, a very bad idea... but if you umount it first.. than its cool mount -n -o ro /dev/hda1 - take / offline first e2fsck /dev/hda1 mount /dev/hda1 -- put it back online and always a good idea to look at any warnings/error messages spewed out by the system... so that e2fsck on an unmounted partition is okay? but to check a mounted partition it should be efsck? or what? sorry, i haven't been following the thread. i'm not sure if it matters but since using the 2.4.17 kernel on my machine , crashes nessecitating the check haven't happened, at all. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!!
On Sunday 14 April 2002 11:01 pm, Jaye Inabnit ke6sls wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 14 April 2002 10:44 pm, ben wrote: On Sunday 14 April 2002 10:40 pm, Alvin Oga wrote: hi ya axacheng fileserver:/# e2fsck -v -y /dev/hda bash: /sbin/e2fsck: Input/output error you cannot run e2fsck on a disk... you need to run e2fsck on ext2 partitions e2fsck /dev/hda1 e2fsck /dev/hda2 ... NOTE... do NOT run e2sck on your mounted root partition ( read the warnings you would be getting especially root partition... ( ie... dont do -v -y in your example or you'd ( be creating major problems on your machines the error messages may be real or self-induced mis-leading errors... if you do NOT have any of those seek errors in your logs, than i'd not worry about your disk yet ... am assuming that there are no such warnings other than on Mar 15 03:09 which is exactly the same time you rand the erroneous e2fsck command if yu do have tons of these error at all times of the day and nights than you have a dying disks... - copy off all your data to a new backup disks - start replacing the ide cables and wiggle it and see if there is good connections or shorts or other whacky stuff can you indicate some point of reference to justify that claim? my system runs e2fsck by default after every 20 bootups, and i've yet to notice any damage due to that. ben Greetings Ben: I think 'boot' is the keyword, where the root file system has yet to be mounted. yeah, alvin offered some info on that. the question that remains is what is the command to run a check on a mounted system? sorry, i haven't been following the thread. somone may have answered this already. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!! - damage
ben wrote: so that e2fsck on an unmounted partition is okay? but to check a mounted partition it should be efsck? or what? sorry, i haven't been following the thread. i'm not sure if it matters but since using the 2.4.17 kernel on my machine , crashes nessecitating the check haven't happened, at all. Umm no... First off, fsck just calls the appropriate filesystem-specific program, which happens to be e2fsck for most of us. I've never heard of efsck... possible typo? Second, You always want to fsck unmounted partitions only. If nothing else, trying to fsck a mounted partition produces the following message: WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Mr. Ts'o (the guy who wrote a large portion of the ext2 stuff in Linux) knows much more about filesystems in general, and ext2 in particular, than I do, so I listen to that error message. Finally, It's not just crashes that will cause the system to run an fsck at boot time. There's a mount counter that will automatically fsck after so many reboots (or was it mounts?). I recall the number being set to 20. You can also force checking upon reboot by supplying the -F option to the shutdown command. --Rich _ Rich Puhek ETN Systems Inc. _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Question] Harddisk Error!!! - damage
On Sunday 14 April 2002 11:35 pm, Rich Puhek wrote: ben wrote: so that e2fsck on an unmounted partition is okay? but to check a mounted partition it should be efsck? or what? sorry, i haven't been following the thread. i'm not sure if it matters but since using the 2.4.17 kernel on my machine , crashes nessecitating the check haven't happened, at all. Umm no... First off, fsck just calls the appropriate filesystem-specific program, which happens to be e2fsck for most of us. I've never heard of efsck... possible typo? Second, You always want to fsck unmounted partitions only. If nothing else, trying to fsck a mounted partition produces the following message: WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Mr. Ts'o (the guy who wrote a large portion of the ext2 stuff in Linux) knows much more about filesystems in general, and ext2 in particular, than I do, so I listen to that error message. Finally, It's not just crashes that will cause the system to run an fsck at boot time. There's a mount counter that will automatically fsck after so many reboots (or was it mounts?). I recall the number being set to 20. You can also force checking upon reboot by supplying the -F option to the shutdown command. no probs. that's exactly my understanding of the situation; although pre-2.4.17 kernels crashed so often, i really thought my disk was fscked. since then, it's all been good--so much so that i've been reticent about moving up from there. thanks for the response. ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
