On Thursday 05 June 2003 16:49, Rahul Kalaskar wrote: Hi Rahul,> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, > sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, > sector=1834800 end_request: I/O error, dev 16:02 (hdc), sector 1834800 > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, > sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 > > Does this mean there is a hardware problem with the disk.yes.> The machine was running for about 250days. I am using IBM Travelstar hard > disk. The machine is located in an NEMA box with maybe poor air > circulation.I still don't get it what this has to do with ext3 ML ;) ciao, Marc
* Rahul Kalaskar <rkalaskar@aethon.com>:> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 > end_request: I/O error, dev 16:02 (hdc), sector 1820440 > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800 > end_request: I/O error, dev 16:02 (hdc), sector 1834800 > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 > end_request: I/O error, dev 16:02 (hdc), sector 1820440 > > Does this mean there is a hardware problem with the disk.It's dead, Jim. -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite Campus Mitte Tel. +49 (0)30-450 570-155 Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 AIM: ralfpostfix
yeah thats bad sectors. you can possibly have linux ignore those secotrs in the future and mark them as bad by unmounting the drive (or remounting it read only) and then doing e2fsck -c -y /dev/hdc1 Adam On 5 Jun 2003, Rahul Kalaskar wrote:> Hi All, > > I had to reboot a machine as I lost the ssh connectivity to it. I could > ping to it though. On rebooting, the dmesg buffer showed the following > messsage > > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 > end_request: I/O error, dev 16:02 (hdc), sector 1820440 > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800 > end_request: I/O error, dev 16:02 (hdc), sector 1834800 > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 > end_request: I/O error, dev 16:02 (hdc), sector 1820440 > > Does this mean there is a hardware problem with the disk. > The machine was running for about 250days. I am using IBM Travelstar hard disk. > The machine is located in an NEMA box with maybe poor air circulation. > > Thanks! > Rahul > > > _______________________________________________ > Ext3-users mailing list > Ext3-users@redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users >
Hi All,
I had to reboot a machine as I lost the ssh connectivity to it. I could
ping to it though. On rebooting, the dmesg buffer showed the following
messsage
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
end_request: I/O error, dev 16:02 (hdc), sector 1820440
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800
end_request: I/O error, dev 16:02 (hdc), sector 1834800
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440
end_request: I/O error, dev 16:02 (hdc), sector 1820440
Does this mean there is a hardware problem with the disk.
The machine was running for about 250days. I am using IBM Travelstar hard disk.
The machine is located in an NEMA box with maybe poor air circulation.
Thanks!
Rahul
Thanks all. I am going to change the Hard disk. On Thu, 2003-06-05 at 12:39, Skylar Thompson wrote:> On Thu, Jun 05, 2003 at 10:49:50AM -0400, Rahul Kalaskar wrote: > > Hi All, > > > > I had to reboot a machine as I lost the ssh connectivity to it. I could > > ping to it though. On rebooting, the dmesg buffer showed the following > > messsage > > > > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 > > end_request: I/O error, dev 16:02 (hdc), sector 1820440 > > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800 > > end_request: I/O error, dev 16:02 (hdc), sector 1834800 > > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 > > end_request: I/O error, dev 16:02 (hdc), sector 1820440 > > > > Does this mean there is a hardware problem with the disk. > > The machine was running for about 250days. I am using IBM Travelstar hard disk. > > The machine is located in an NEMA box with maybe poor air circulation. > > Yes. You should get your data off the drive and replace it ASAP. > > -- > -- Skylar Thompson (skylar@cs.earlham.edu) > -- http://www.cs.earlham.edu/~skylar/
Hi. I do have a very similar problem as described in this thread. I get the same kind of errors. But I am not even able to mount the partition. When trying to do so, there is a message complaining about a missing superblock in the kernel-log. (maybe the sector where the superblock is are corrupt? BTW, what is the superblock? :) ) When I try to e2fsck the parttion I always get a message "attempt to read block from filesystem resulted in short read while trying to open /dev/ataraid/d0p2) But is there a way to force-mount the partition to at least get access to the files in not-corrupted sectors? Would be great to receive some help. Philipp