Messages in this thread | | | Date | Sun, 26 Jan 2003 17:36:19 -0800 (PST) | From | Arindam Dey <> | Subject | Re: Hard Disk Failure |
| |
--- Mark Hahn <hahn@physics.mcmaster.ca> wrote: > > Now this Distribution is bundled along with its > own > > Hardware and about 45% of these PC's Harddisk are > > failing after a period of 2-3 weeks. On > reinstallation > > not IBM DTLA's, I hope. > > > they become ok but again after 2-3 weeks they fail > > again and finally after 2 months of this the Hard > Disk > > fails COMPLETELY and cannot be used again for any > > you need to get some actual data here, not this > "completely" > nonsense. do you mean it doesn't spin up? if so, > there's > nothing that the software (including the OS) could > have done > to cause it. > > > All I want to know is what is the probability that > the > > above oversight of e2fsprogs version is > responsible > > for the HDD failure thats all. Since we are > totally > > no. e2fsprogs might cause data loss, but not > physical damage. >
I am using Kernel -2.4.19. The ouput of /proc/ide/sis is as follows ############# /proc/ide/sis ###################################### SiS 5513 Ultra 66 chipset --------------- Primary Channel ---------------- Secondary Channel -------------Channel Status: On Off Operation Mode: Compatible Compatible Cable Type: 80 pins 80 pins Prefetch Count: 512 512 Drive 0: Postwrite Enabled Postwrite Disabled Prefetch Enabled Prefetch Disabled UDMA Enabled UDMA Disabled UDMA Cycle Time 2 CLK UDMA Cycle Time Reserved Data Active Time 3 PCICLK Data Active Time 8 PCICLK Data Recovery Time 1 PCICLK Data Recovery Time 12 PCICLK Drive 1: Postwrite Disabled Postwrite Disabled Prefetch Disabled Prefetch Disabled UDMA Enabled UDMA Disabled UDMA Cycle Time 4 CLK UDMA Cycle Time Reserved Data Active Time 3 PCICLK Data Active Time 8 PCICLK Data Recovery Time 1 PCICLK Data Recovery Time 12 PCICLK
#############the output of hdparm -i /dev/hda is as follows############ Model=ExcelStor Technology ES3230, FwRev=ES7CA25A, SerialNo=MA15HAX Config={ Fixed } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=58615258 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 AdvancedPM=no Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4 ATA-5
The problem is random in nature it occurs on its own giving dma error at boot time when it is checks the hard disk.
hda: dma_intr: bad DMA status (dma_stat=35) ; hda: dma_intr: status=0x50 { DriveReady SeekComplete } hda: dma_intr: bad DMA status (dma_stat=35) hda: dma_intr: status=0x50 { DriveReady SeekComplete } hda: dma_intr: bad DMA status (dma_stat=75) The hexadecimal values of the status are different.
I have attched the dmesg and the lspci output also.
__________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com[unhandled content-type:application/octet-stream][unhandled content-type:application/octet-stream] | |