One real negative about SMART is that its mostly IDE only. Even though SATA drives have SMART capability the Linux kernel doesn't support it unless you are using the very newest kernel (just checked and 2.6.15 is the first version to support it).
John
On Wed, 2006-05-31 at 09:29 -0500, Sean Walberg wrote:
Since the docs don't make it really obvious how to do a spot check:
[root@sergeant root]# smartctl -t short /dev/hda smartctl version 5.21 Copyright (C) 2002-3 Bruce Allen Home page is http://smartmontools.sourceforge.net/
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Short self-test routine immediately in off-line mode". Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 1 minutes for test to complete. Test will complete after Wed May 31 09:27:42 2006
Use smartctl -X to abort test. [root@sergeant root]# smartctl -l selftest /dev/hda smartctl version 5.21 Copyright (C) 2002-3 Bruce Allen Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 30579
# 2 Extended offline Completed without error 00% 29284
# 3 Extended offline Completed without error 00% 28500
You may want to do "-t long" instead of short, it takes a while to execute but is more thorough.
Sean
On 5/31/06, John Lange john.lange@open-it.ca wrote: Those errors are more likely signs of failing drive.
You should use the smartmontools to do a status check on your drive. http://smartmontools.sourceforge.net/ Hard drives have had SMART technology for years and Linux has had these tools for just about as long yet no distro (that I'm aware of) activates smart monitoring by default. That is a real shame since they are so valuable. -- John Lange OpenIT ltd. www.Open-IT.ca (204) 885 0872 VoIP, Web services, Linux Consulting, Server Co-Location On Tue, 2006-05-30 at 15:20 -0500, schwartz wrote: > I'm getting weird DMA errors on my Fedora Core 5 computer. > The motherboard is an ASRock P4VM800 with 512MB DDR > Celeron 2533 MHz Model 4 > hard drive is a Hitachi 7K80 7200 rpm parallel-ATA 80 Gig. > Fedora is installed on /dev/hda7 9.4 Gig partition ext3 > The DMA error message shows up during big file, > or multiple file, copying from one directory to another, > and during bootup. dmesg shows this message: > cd ..hda: dma_intr: status=0x51 > { DriveReady SeekComplete Error } > hda: dma_intr: error=0x84 { DriverStatus Error BadCCR } > ide: failed opcode was: unknown > Sometimes the error message shows up at one point > in the boot process, sometimes in another. During really > big copies, the DMA error message is quite frequent. > I also have XP, 98SE, and Slackware on the machine > but so far none of them have this error, or maybe they're > not telling. > Can anyone tell me how to deal with this problem? > > > > > > _______________________________________________ > Roundtable mailing list > Roundtable@muug.mb.ca > http://www.muug.mb.ca/mailman/listinfo/roundtable > _______________________________________________ Roundtable mailing list Roundtable@muug.mb.ca http://www.muug.mb.ca/mailman/listinfo/roundtable-- Sean Walberg sean@ertw.com http://ertw.com/ _______________________________________________ Roundtable mailing list Roundtable@muug.mb.ca http://www.muug.mb.ca/mailman/listinfo/roundtable