SMART status failing on a WD Scorpio Black WD3200BEKT 320GB 7200 RPM

I just recently purchased a Western Digital Scorpio Black WD3200BEKT 320GB 7200 RPM drive to put in my 1st Gen MacBook Pro. Ever since installing the drive, I've had random beach balls happen usually when there is a fair amount of disk I/O.
Thinking the drive was bad, I sent it back and got another one. I am still seeing the same frequent beach balls requiring a hard restart to get the system to be responsive again.
Checking the System Profiler, I see that the drive is failing SMART status. I also checked the kernel logs and am getting I/O errors on the drive at the point when the system beach balls.
I am pretty certain it isn't the drive. I'm at a loss for what to try next. Is this drive not compatible with my SATA interface. Any suggestions or comments?
Below are some of my pertinent machine information from System Profiler:
Model Name: MacBook Pro 15"
Model Identifier: MacBookPro1,1
Processor Name: Intel Core Duo
Processor Speed: 1.83 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MBP11.0055.B08
SMC Version (system): 1.2f10
Sudden Motion Sensor:
State: Enabled
Below is the Serial-ATA information from the System Profiler:
Intel ICH7-M AHCI:
Vendor: Intel
Product: ICH7-M AHCI
Speed: 1.5 Gigabit
Description: AHCI Version 1.10 Supported
WDC WD3200BEKT-60F3T1:
Capacity: 298.09 GB
Model: WDC WD3200BEKT-60F3T1
Revision: 12.01A12
Native Command Queuing: Yes
Queue Depth: 32
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Failing
Volumes:
Macintosh HD:
Capacity: 297.77 GB
Available: 153.19 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s2
Mount Point: /
I also ran this to check the current speed of the SATA interface since the drive is a SATA II drive with a 3.0gb/s burst.
$ sudo ioreg -l | grep 'Interconnect"="SATA"'
| | | | "Protocol Characteristics" = {"Physical Interconnect"="SATA","Physical Interconnect Location"="Internal/External"}
| | | | "Protocol Characteristics" = {"Physical Interconnect"="SATA","AHCI Port Number"=0,"Physical Interconnect Location"="Internal","Port Speed"="1.5 Gigabit$
| | | | "Protocol Characteristics" = {"Physical Interconnect"="SATA","Physical Interconnect Location"="Internal"}
The above shows that the interface is running at 1.5gb/s SATA I which is what I excepted on this system.
Thanks!
Dustin

Sounds like you have things well sorted out.
Despite that fact that you have had two consecutive HDDs with defects does not, necessarily, mean that all of those drive are defective. However, you are fortunate that you were able to get you money back. Seagate makes good drives, as does WD, and hopefully you have paid your dues and you will have no more incidents.
Do post back should you run into stuff and need to bounce ideas off someone else.
Good luck.
cornelius
I will certainly report back on my luck with Seagate.
You are correct that the failure of two consecutive drives does not mean the whole line is faulty. The drive I was replacing in the MacBook Pro was actually a Western Digital Scopio as well (just not a Blue or Black) and it has performed flawlessly. It's the drive I have reinstalled twice now while I waited for the replacement drive to be shipped.
Another interesting anecdote is that I searched the NewEgg customer comments for reports of SMART errors on the Western Digital Scorpio Black drive I had ordered and sure enough, there were quite a few postings where people had tried multiple times to get a good drive.
It's just one of those things that you start to question, especially with older hardware like I am using (1st Gen MacBook Pro) that maybe backwards compatible quirks between SATA 1 and SATA 2 are the real problem not the drive itself. I'm still not 100% convinced that the drives were the true culprit. Hard to say for sure.
Not to mention all the troubles I've been reading about with 3rd party drives and the recent 1.7 EFI update which has caused similar errors as to what I was seeing with these drives. The first drive I had didn't throw any SMART errors, or at least I didn't notice them.
I'm gonna order the Seagate Momentus 7200.4 ST9320423AS 320GB 7200 RPM 2.5" SATA 3.0Gb/s and see what happens. I'll report back my findings in another thread so that people who search for the Seagate drive will have a more related thread to read.
Dustin

Similar Messages

  • WD Scorpio Black 320 GB 7200 RPM Not Working

    Don't know if anyone else has experienced this, but worth a shot.
    I just purchased a WD 320 GB 7200 RPM Scorpio Black. It will not work in my brand new macbook. The original apple hard drive works fine, I have a USB->SATA adapter, hooked it up, was able to clone the old hard drive onto the WD drive. It boots up perfectly fine when I boot via USB using the adapter.
    When it is installed, however, the hard drive keeps spinning up and down and up and down...to the point where it takes 25 minutes just to boot. I disabled the sudden motion sensor via pmset, reformatted the drive, reinstalled Leopard, had the drive replaced via RMA, used the drive jumpers to limit spinnup voltage, all to no avail.
    Still the same situation. Drive works perfectly fine via USB on this computer and others, but will not work when connected to SATA on this macbook.
    My theory is that it may draw too much power, being a 7200 RPM drive and is being constantly disabled do to overcurrent then enabled again, causing the spin up/down. Maybe this is why you cannot order one of these from apple with a 7200 RPM drive? In any event, I give up. WD can't think of anything and I am stumped. If anyone has any thoughts, let me know before I return the drive, otherwise, it's going back and I am getting a 5400 RPM drive. If you are considering buying one for your macbook, beware.

    Here are some important updates:
    Got a new WD Scorpio 5400 320 gB SATA II drive! YAY! Ohhh wait....this one is having the exact same issue: won't work connected internally, will work connected externally. I did some more poking around and this is what I found:
    I also get I/O errors after booting from a linux live CD, so it must not be software related, it has to be a compatibility problem with the SATA controller and the WD hard drives. I have tried 3 WD hard drives, which all work on other computers and on this brand new macbook when connected externally. Only when connected internally. Original Mac Hitachi drive works fine.
    I called apple support and was informed, to my dismay, that "we do not guarantee non-apple hard drives will work with your macbook. The macbook may not be compatible with this drive." YAY! So the RAM incompatibility issue is happening all over again, only with hard drives now! I have not ever known another computer in all my work as a tech support provider that is only compatible with specific makes/models of SATA II drives.
    I am very disappointed, and honestly baffled. Once I make enough money to pay the restocking fee on all these WDs, I might try another brand. Someone else has to be having this issue?

  • Powerbook G4  HD SMART Status: Failing

    My powerbook G4 (1.5GHZ, 1GB RAM, OS 10.3.9)recently runs very slowly, sometimes freezed up during power off process. I checked the activity monitor to see none program hogging the cpu and memory, There are about 37GB free space on the hard drive. Checked the Disk Utility and saw the SMART status: Failing in red letters. Can anyone tell me if that is the sign the HD is going to die soon? If I used the install CDs to reinstall very thing, it will fix the problem or not? Or I just need a new HD? Luckly I was able to backup everything on my Mac to my desktop. Thx

    Welcome to the Apple discussions.
    That means that it's time to replace the hard drive, as it will fail shortly due to a hardware failure. If you want more detail on what is failing, install Smart Utility from Volitans.
    New hard drives are cheap ... good source is Newegg.com, as they have many user reviews, good prices, good service. I've bought drives from them for years, and can recommend them. You'll want a parallel ATA interface 2.5" hard drive. Can't use a serial ATA (SATA) interface hard drive.

  • SMART Status = failed

    Hi there, I have a 27" iMac from Mid 2010, been running slow the last couple of days, so done some PD.  Looks like the hard drive is on its way out, with a SMART status of failed.
    The questions are;
    best ways to replace (ie, diy, take it in to an apple fixer)
    the hard drive model is HDS722020ALA330 (2Tb Hitatchi) - looks like the model is discountinued, or very expensive to get hold of - what options should I be looking at?
    Cheers

    SSD's tend to be in the 2.5" format, generally with serial ATA interfaces. The difference between SATA II and SATA III has to do with the speeds they can support, with SATA II supporting 3 Gbit/s and SATA III supporting 6 Gbit/s.
    If you can boot up your system (OS X DVD or external hard drive backup), click the apple on the left of the menu bar, about this mac, more info, system report, and serial ATA. You'll note on the Intel chipset that it will have a value for "link speed". If it's 3 gigabit, it's SATA II and 6 gigabit would be SATA III. That's what the system can support. Or you can look up your specs on everymac.com which will also tell you what serial ATA speed your macbook supports.
    SATA III SSDs are supposed to be backward compatible to SATA II as needed. However, I recently upgraded our 2010 mac mini to an OWC SATA III SSD. Hooked it up, and the negotiated link speed was 1.5 gigabits, which is SATA I, with the mini capable of supporting SATA II. Turns out I had to install the OWC SATA II drive, which when hooked up, was running at SATA II speeds! OWC was very helpful and made the return as painless as possible.

  • Disk Disaster: SMART status "failing", can't mount - what to do?

    Hi,
    My GF's PB 12" started getting slow on disk access, so I - suspecting a hard disk failure was impending - checked SMART monitor status, and all seemed fine. Just the same, I made a full backup using SuperDuper.
    Now, two weeks later, the drive has failed. Booting from the SD backup, and using Disk Utility to investigate the internal drive shows it as "failing", and the helpful advise is to get the data off as soon as possible. Unfortunately I can't mount the drive...
    What is the best way to proceed? Should I just give up, and contact a data recovery service straight away, or is there a better way?

    Hello! If you backed up what you thought was an ailing drive didn't you backup your important data every day? Seriously though if it's really important I'd probably check out DATARESCUE. Tom

  • Drive fails SMART status-"this drive has a hardware problem"

    I recently did a major update of software and applications to my MacPro. (it's the first model of 8 core that came out). When I do a major update like this, I make a clone using Carbon Copy Cloner of the system drive to an external drive so I have a backup until I verify everything is good on the updated internal. I have 4 hard internal drives and have been having no trouble from them. However I noticed in Disk utility that one of the non-system drives is displayed in red and gives a warning that reads, "This drive has a hardware problem and can't be repaired. Backup the data and replace the drive". It also shows the SMART status as "failing". So I have everything copied to another drive.
    I'll gladly replace the drive. However here's my confusion: when booting from the system cloned to the external drive, this same drive shows as being perfectly fine in Disk Utility. Both system drives have OSX 10.6.6. the only difference is newer applications on the internal system drive that reports failure (mostly audio related applications: Pro Tools, Reason, Roxio Toast).
    So does anyone have any thoughts? I've read some other threads and they just report the failure and say to change the drive. I've not seen anyone else have one system that reports failure and another that doesn't.

    SMART status failed is usually caused by too many suspected Bad Blocks. Some of these blocks may be unjustly accused of being permanently bad.
    If you have the liberty to re-initialize the drive, doing so with security options "Zero all data, one pass" will ensure that (if the test completes without error) the drive once more has 100 percent good blocks. The process takes several hours to complete, longer if there are a lot or bona-fide errors.
    It is also possible that the drive will produce "initialization Failed", in which case it should be retired if out of warranty, returned for replacement if still in warranty.
    A drive that has ever seen a SMART status of Failed may get more Bad Blocks in the next six months. Or maybe this afternoon. If possible, it would be good to reduce your day-to-day use on this drive, such as making it a backup drive rather than using it all day every day for 'live" data.

  • New HDD S.M.A.R.T. Status failing

    Hello, Had a "S.M.A.R.T Status failing" warning last week. Bought back up disk to use with Time Machine. Brought the iMac into Apple for them to check it out and they ended up replacing the HDD and restoring everything on the disk as it was before we brought it in (apparently). When it was started up at the store, the same old beach ball appeared and the guy ensured us that was normal since it was a new install. Brought it home and looked under disk utilities and it still says "S.M.A.R.T Status failing" for that disk. There was no need to use our back-up from Time Machine as everything was still there. Is it possible that this disk was either not replaced, or it was replaced with another failing HDD? Or is there something that needs to be done to clear the SMART Status failing warning from the original back up from Apple store?The Genius at the store said it was replaced and that all we had to do was to do a restore from our backup. Anyone have any suggestions?

    There is no value in guessing what happened at the store, the fact is you have a failing HD and need to take it back to be serviced. I would recommend speaking to the store manager to let him know what happened, do so in a calm, organized and friendly fashion though...you never may know when you need him as an ally. .

  • Apple Hardware Test (AHT) Hard Drive Full Read Fail But SMART Status OK

    I have a Mac mini Server from Mid 2010 running Snow Leopard Server.
    Ocassionally, it'll freeze up with the spinning beachball wheel for a few minutes. This usually happens when opening an app or performing an app function from the menu bar. It's a pretty clean system—there are not many apps installed.
    I suspect it's a hadrware issue. I ran Disk Utility's Permission and Disk Repair. All good. SMART Status is verified. So I ran the Apple Hardware Test. Everything passes except for the Hard Drive's "Full Read"—it fails because "Reading took longer than the average time". The Hard Drive "Short .. test" and "Check SMART Status" pass.
    Does anyone have an idea of what's going on here? Is the hard drive the issue? I don't understand how there can be a read issue (or hard drive issue), when the SMART Status is verfied.

    S.M.A.R.T isn't perfect. Neither is AHT for that matter, but if it is reporting that reading is taking longer than it should then an impending failure is likely. The occasional "wait cursor" appearance supports that diagnosis.
    Consider yourself fortunate in that you still have the ability to back up anything important, and you can plan a convenient time for its replacement.

  • My smart status is failing

    In disk utility my disk is red and smart is "Failing"
    Luckily, I have time machine, so Nobody cares.
    Please help?

    If you are still under Warranty, or still under Apple Care, report to Apple immediately. There is a Contact Us link at the bottom right of this page that will get you to the right place in Apple.

  • Cannot boot from 750GB Western Digital Scorpio Black

    I just installed a new 750GB 7200rpm Western Digital Scorpio Black in my early 2008 15" MacBook Pro (last pre-unibody). I can boot the computer from the Scorpio Black when it's in an external enclosure, I can boot another computer, a MacBook, from the Scorpio Black via firewire while that's installed in my MacBook Pro, but what I cannot do is get the MacBook Pro to boot off the Scorpio Black as the internal drive. It will recognize it and show the main and recovery partititions, but it won't boot the OS (10.7.1.).
    Here's a rundown of the installation and troubleshooting steps I've taken:
    1.) Installed the drive in an external USB enclosure, formatted GUID partition table (GPT), file system HFS+ extended journaled.
    1.b) Downloaded and installed Lion (10.7.1) from the App Store, used migration assistant to transfer accounts from my (now former) internal drive, and then booted from the Scorpio Black in the external enclosure to ensure everything worked fine.
    2.) Installed the drive via iFixit instructions. Everything fit properly and I double checked the SATA connector was seated correctly.
    3.) Booted computer for the first time with the Scorpio Black. It stuck at a spinning wheel on a grey screen.
    4.) Held down option key at startup -- the computer showed the main partition and the recovery partition on the Scorpio Black as the startup drive options.
    5.) Tried the recovery partition -- spinning wheel on a grey screen.
    6.) Tried safe verbose boot (command - shift - v) -- it interleaves "still waiting for root device" with "SATA WARNING: Enable Drive PHY PM failed" and "SATA WARNING: auto-activate failed".
    7.) Reset PRAM & NVRAM -- no joy.
    8.) Connected the MacBook Pro via firewire to a Core 2 Duo white MacBook also running 10.7.1. The MacBook recognized the drive and in Disk Utility, I could see all the partitions on it.
    9.) Ran repair volume (for the drive) and repair partition (for my main partition) from disk utility on the MacBook -- it said everything's fine with both.
    10.) In system preferences, set the Scorpio Black as the startup drive for the MacBook.
    11.) Astonishingly, the MacBook booted up just fine off the Scorpio Black in the MacBook Pro. I logged in, opened a few photos and played a video. Everything worked just peachy.
    12.) Booted the MacBook Pro off my old internal hard drive, now in an external enclosure.
    13.) Disk utility sees the internal Scorpio Black, and reports everything is fine with the volume and the partition.
    14.) System profiler says everything is fine when I check under SATA. SMART status is verified.
    Which brings me to step 15: admit defeat and ask for help. Any suggestions? The exact model number of the drive is WD7500BKPT. I purchased it from Other World Computing.
    Thanks for any help.
    Cheers.

    I actually first replaced the stock hard drive with a Western Digital 500 GB Scorpio Blue (i.e., a 5400 rpm drive). Here's what I can tell you about all three.
    First, I didn't notice any difference in noise, vibration or power consumption between any of the drives. The computer felt stock with both of the Western Digital drives.
    In terms of speed, my understanding is, all other things being equal, a larger drive is always faster than a lower capacity drive (I believe that's because more of the data is on the faster rotating outer areas). That being said, the step up to the 750GB 7200 rpm Scorpio Black was a bigger one than to the 500 GB 5400 rpm Scorpio Blue -- it gave a noticeable bump in performance. Opening my Aperture library and browsing photos went from sluggish and borderline unusuable to acceptable, or even good.
    Bottom line, it's not a solid state drive, so don't expect MacBook Air levels of responsiveness, but I can wholeheartedly recommend the Scorpio Black.

  • Internal hard drive/repair: SMART status; Disk Utility, Tech Tool & More

    machine: 12" PowerBook 1.5 GHz PowerPC G4 (Aluminium) with 80GB internal HD
    internal hard drive (original): Hitachi Travelstar 5K100 series HTS541080G9AT00
    hard drive firmware: MB4AA5AJ
    ATA version: 6
    ATA standard: ATA/ATAPI-6 T13 1410D revision 3a
    I have monitored the SMART status etc. of my internal drive with smartmontools for some time. Occasionally, I would see an error or a failed self-test but later testing always succeeded and things did not seem to be problematic.
    At the beginning of this week, I started to see a lot of failed self-tests (though some still passed), a rising number of bad ("pending") sectors and reallocation attempts (though no reallocated sectors) and various other errors. The computer seemed to have trouble reading from the disk at times and Carbon Copy Cloner reported two I/O errors when cloning (a later clone succeeded). fsck showed errors although running fsck -fy repeatedly seemed to resolve them.
    The Apple hardware tests initially reported an error (2STF/8/3:ATA-100 ata-6-Master) but I hadn't realised I should disconnect peripherals before running it so I did that and repeated the test which found no issues. I ran the extended test a total of three times with no errors.
    As I continued to have problems, I booted from my clone and had Disk Utility wipe the drive by writing zeros to it. (I thought trying to get it to write everywhere would either finish the drive off or force it to reallocate the bad blocks. As I understand it, in normal use, the drive won't reallocate the blocks unless it can recover the data in the hopes of reading it at a later time.)
    I then continued monitoring the disk using smartmontools. At this point, short self-tests succeed but extended self-tests "disappear". They don't fail, they simply vanish. They begin and smartctl shows the test in progress but then no error or result is logged - it is as if the test was never run. The first time I did this, I got an error saying the SMART attributes could not be read but subsequent tests do not trigger even an error. Short self-tests continue to pass.
    There are now (according to SMART) zero bad ("pending") sectors but zero reallocated sectors, which seems odd. The raw read error rate fluctuates (zero one minute, many thousands a while later) although I am not sure it did not do this before.
    Disk Utility claims the disk does not support SMART status even though smartctl clearly shows it does. Disk Utility claims the volume is "OK".
    I ran Tech Tool Deluxe 3.04 from CD and 3.1.1 from my clone. In both cases, I ran all available tests on the drive. No problems were found.
    I am seeing some problems even while booted from my clone - yesterday, the system froze completely and I had to force a shut-down by switching off the power (fsck then found a minor error but repaired it). Just before this happened, I was unable to mount a disk image and was trying to rectify the situation when the system froze. It is possible that the errors fsck corrected were implicated in the freeze, rather than caused by it, since Disk Utility found and repaired similar errors for the other two clones I have (on different partitions of my external drive - yes, I know this is sub-optimal).
    Here is some current output from smartmontools:
    ---output: smartctl -q noserial -a disk0---
    smartctl version 5.38 [powerpc-apple-darwin8.11.0] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    === START OF INFORMATION SECTION ===
    Model Family: Hitachi Travelstar 5K100 series
    Device Model: Hitachi HTS541080G9AT00
    Firmware Version: MB4AA5AJ
    User Capacity: 80,026,361,856 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 6
    ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a
    Local Time is: Sat Jul 3 20:28:52 2010 BST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 645) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 55) minutes.
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 RawRead_ErrorRate 0x000b 100 100 062 Pre-fail Always - 0
    2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
    3 SpinUpTime 0x0007 142 142 033 Pre-fail Always - 2
    4 StartStopCount 0x0012 097 097 000 Old_age Always - 5793
    5 ReallocatedSectorCt 0x0033 100 100 005 Pre-fail Always - 0
    7 SeekErrorRate 0x000b 100 100 067 Pre-fail Always - 0
    8 SeekTimePerformance 0x0005 100 100 040 Pre-fail Offline - 0
    9 PowerOnHours 0x0012 039 039 000 Old_age Always - 26720
    10 SpinRetryCount 0x0013 100 100 060 Pre-fail Always - 0
    12 PowerCycleCount 0x0032 098 098 000 Old_age Always - 4168
    191 G-SenseErrorRate 0x000a 100 100 000 Old_age Always - 0
    192 Power-OffRetractCount 0x0032 100 100 000 Old_age Always - 201877487644
    193 LoadCycleCount 0x0012 001 001 000 Old_age Always - 2209599
    194 Temperature_Celsius 0x0002 141 141 000 Old_age Always - 39 (Lifetime Min/Max 16/46)
    196 ReallocatedEventCount 0x0032 100 100 000 Old_age Always - 194
    197 CurrentPendingSector 0x0022 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
    199 UDMACRC_ErrorCount 0x000a 200 200 000 Old_age Always - 0
    SMART Error Log Version: 1
    ATA Error Count: 2138 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    PoweredUpTime is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 2138 occurred at disk power-on lifetime: 26716 hours (1113 days + 4 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    10 51 00 09 4f c2 a0 Error: IDNF
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    b0 d6 01 09 4f c2 a0 00 08:30:04.500 SMART WRITE LOG
    b0 d5 01 09 4f c2 a0 00 08:30:04.300 SMART READ LOG
    b0 d1 00 00 4f c2 a0 00 08:30:04.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
    b0 d0 00 00 4f c2 a0 00 08:30:04.000 SMART READ DATA
    b0 da 00 00 4f c2 a0 00 08:30:04.000 SMART RETURN STATUS
    Error 2137 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:37.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    Error 2136 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 21 1f 95 98 e4 Error: UNC 33 sectors at LBA = 0x0498951f = 77108511
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
    Error 2135 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 22 1e 95 98 e4 Error: UNC 34 sectors at LBA = 0x0498951e = 77108510
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
    25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
    Error 2134 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
    25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
    25 00 80 c0 92 98 e0 00 1d+01:30:12.100 READ DMA EXT
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBAof_firsterror
    # 1 Short offline Completed without error 00% 26717 -
    # 2 Short offline Completed without error 00% 26717 -
    # 3 Short offline Completed without error 00% 26717 -
    # 4 Short offline Completed without error 00% 26717 -
    # 5 Short offline Completed without error 00% 26716 -
    # 6 Short offline Completed without error 00% 26715 -
    # 7 Short offline Completed without error 00% 26714 -
    # 8 Short offline Completed without error 00% 26697 -
    # 9 Extended offline Completed: read failure 10% 26692 75071682
    #10 Short offline Completed without error 00% 26687 -
    #11 Extended offline Completed: read failure 10% 26676 77108511
    #12 Short offline Completed: read failure 40% 26663 296917
    #13 Short offline Completed without error 00% 26657 -
    #14 Short offline Completed: read failure 10% 26646 296918
    #15 Short offline Completed: read failure 70% 26645 296905
    #16 Short offline Completed: read failure 10% 26644 296910
    #17 Short offline Completed: read failure 10% 26644 296910
    #18 Short offline Completed: read failure 40% 26643 296916
    #19 Short offline Completed: read failure 20% 26643 296909
    #20 Extended offline Completed without error 00% 26620 -
    #21 Short offline Completed without error 00% 26618 -
    Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENTTESTSTATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    ---end output---
    Self-tests 1-8 were all run after I erased the disk. The others were run before I did so. Not listed are the extended self-tests I've started since erasing which, as I say, have simply disappeared.
    The checksum error regarding the log is normal for this disk. At least, I've got that error ever since I started using smartmontools for monitoring so I assume it is normal. (I installed this version of the software in about April 2008 and have used it since.) Also, starting offline testing has never succeeded on this disk (I think I checked into this at the time but can't quite remember - this is not new, anyway).
    Questions
    how should I interpret all this? (Why does Disk Utility say SMART is not supported while smartctl clearly shows it is at the same time? Why do the extended tests simply vanish? Is the drive definitely dying?) I do not want to replace the disk unless I absolutely have to because I understand that replacing disks in 12" PBs is no small matter and cost is an issue. I do not want to replace the machine unless I have to because cost is an issue and, also, I really like this computer and have no idea what I would want in its place, even if expense were no obstacle.
    if it isn't clear whether the drive is dying or not, is there some further strategy I can use to establish this?
    if the drive is dying, is a machine of this age worth repairing and, if it is, under what circumstances is it worth doing so? For example, it might be worth doing if you can do the job yourself, but that might be quite impractical for non-expert (not to mention, inexpert) users.
    if there is a hardware problem (which I obviously think is very, very probable at this point), is it definitely a dying hard drive? (I've seen people write ominous things about disk controllers etc. which I gather are more serious - or less repairable - than a "mere" dying disk.)
    what questions should I be asking you and what are the answers to those questions?!
    Many thanks for your patience in reading this far.
    - cfr

    The 12" PB internals are a bit more complex, for PB's. If you don't want to replace the hard drive yourself or pay someone to install it, you could always get an external firewire hard drive, and use it to boot from and for general usage. Would have to be firewire, since the PB won't book from a USB device. One example of what you could get is a 160GB external hard drive: http://eshop.macsales.com/item/Other%20World%20Computing/MS4U5160GB8/ . All the choices with that case are listed here: http://eshop.macsales.com/shop/firewire/on-the-go
    Have you called any Apple Authorized Service Providers to see what they would charge to install a drive for you? Whether you bought it or they supplied it? You can find a local one in the US at http://www.apple.com/buy/locator/service/

  • SMART Status of Disk

    Hi,
    I have been having quite a few problems with the PowerMac recently - specifically the machine would regularly freeze-up and fail to wake from sleep or after the screensaver had been running. After waiting some time I would eventually give in and powerdown.
    In parallel I was constantly getting HardwareGrowler informing me that 'The SMART status of your startup disk is not supported'.
    Thought I'd be better check the disk and repaired the permissions. Also run Repair Disk from the install disk. It needed repair and finished with the message:-
    1 HFS volume repaired
    1 volume could not be repaired
    Since rebooting SmartGrowler is still telling me that the SMART status of my disk is not supported. Using Disk Utility and selecting info the SMART status is 'verified'.
    Could my disk be on the way out?
    Thanks
    Steffan
    PowerMac 2*2.5 GHz, 4GB RAM, 2*250 GB & PowerBook   Mac OS X (10.4.9)  

    Steffan:
    I'm not one of the "pro's from Dover" but had the experience of my iBook HD expiring recently. So, first thing, back-up everything you want to save now, while the HD may still be somewhat good. What advice I got from others here and the Applecare tech is to run Disk repair from start-up CD several times, not just once--trying to have it run without reporting any issues . . . that would be the easiest. And then run Repair permissions from within the OS's Disk Utility. I had SMAARTReporter iinstalled and I was having similar symptoms as you describe not reviving from sleep w/out power button, etc. and a month later SR finally announced impending doom. You could run the APPle Hardware Test CD and see if anything shows. The key would be to run Disk Repair several tiimes. The Pro's would probably say to run Disk Warrior or Tech Tool Pro to "order the Directory" but I frankly don't know what that is. Good luck--but back-up now.
    eep

  • Hard drive SMART status: do I need to replace the drive?

    Recently I checked my PowerBook's hard drive with Disk Utility, and I got "invalid node structure"--an unfixable error. I backed everything up, reformatted the disk, and copied my files back onto it, and this time Disk Utility reported no error. Disk Utility said the SMART status was "Verified" both before and after, so I wasn't worried.
    However, to make sure the hard drive was okay, I installed smartmontools (the command-line SMART data monitoring program, which I got from MacPorts) to get more detailed information. I got the following scary-looking output (sorry the columns are a mess; I can't figure out how to preserve the spacing):
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 RawRead_ErrorRate 0x000f 100 100 046 Pre-fail Always - 87253
    2 Throughput_Performance 0x0005 100 100 030 Pre-fail Offline - 26542080
    3 SpinUpTime 0x0003 100 100 025 Pre-fail Always - 1
    4 StartStopCount 0x0032 098 098 000 Old_age Always - 8090
    5 ReallocatedSectorCt 0x0033 100 100 024 Pre-fail Always - 8585639690241
    7 SeekErrorRate 0x000f 100 100 047 Pre-fail Always - 4052
    8 SeekTimePerformance 0x0005 100 100 019 Pre-fail Offline - 0
    9 PowerOnSeconds 0x0032 084 084 000 Old_age Always - 8422h25m28s
    10 SpinRetryCount 0x0013 100 100 020 Pre-fail Always - 0
    12 PowerCycleCount 0x0032 099 099 000 Old_age Always - 6781
    192 Power-OffRetractCount 0x0032 100 100 000 Old_age Always - 44
    193 LoadCycleCount 0x0032 079 079 000 Old_age Always - 215270
    194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 43 (Lifetime Min/Max 11/49)
    195 HardwareECCRecovered 0x001a 100 100 000 Old_age Always - 82
    196 ReallocatedEventCount 0x0032 100 100 000 Old_age Always - 287047681
    197 CurrentPendingSector 0x0012 100 100 000 Old_age Always - 1
    198 Offline_Uncorrectable 0x0010 099 099 000 Old_age Offline - 2
    199 UDMACRC_ErrorCount 0x003e 200 200 000 Old_age Always - 0
    200 MultiZone_ErrorRate 0x000f 100 100 060 Pre-fail Always - 23714
    203 RunOutCancel 0x0002 100 099 000 Old_age Always - 3728108027884
    The main thing I'm worried about is that some of these statistics are in the "Pre-fail" range--does that mean something really bad? I got my PowerBook in 2004, so the hard drive is old anyway; I assume there is a good chance of a problem some time soon. But how worried should I be?
    Message was edited by: k49

    k49:
    I concur with a brody on the S.M.A.R.T Status. The problem you experienced with your drive initially was a directory issue which would have been corrected by Disk Utility or TechTool Pro. However, reformatting, though the ultimate intrusive method, will certainly do the trick.
    The key, not only in your case but always, is to make sure you have an up-to-date backup of your entire HDD. The best solution would be to backup to an external firewire drive making a bootable clone using SuperDuper, Carbon Copy Cloner, or Disk Utility.
    In addition, if you are nervous about the drive I would keep an eye on it. Run Repair Disk from the installer disk at least weekly to catch any developing issues. You may also want to start researching suitable internal drives, in case you need one, although I would not buy one until you need it. Should your HDD fail, you can then use your bootable clone to format your new HDD, and clone everything back.
    Cheers
    cornelius

  • S.M.A.R.T. Status: Failing - Can't Erase

    One of my dives has a S.M.A.R.T. Status of Failing. This is backup drive, so there is already a direct copy of it. The drive is still under warranty but before I send it back, I want to try and reformat it. In disk utility, I am not able to erase the drive. Is this because of the S.M.A.R.T. Status? Is there a way around this? Can I temporarily turn off the S.M.A.R.T. readings?

    The status report tells you the drive is failing. Don't try to reformat the drive. It's under warranty so get it replaced.
    Since you've told us nothing about what you see in DU when your try to format the drive, we can't give you any input. However, the SMART status has nothing to do with formatting the drive, but if the drive is failing then that could be why. You could try the following:
    Extended Hard Drive Preparation
    1. Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Set the number of partitions from the drop down menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

  • Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

    OS 10.5.8 on a 1.8 GHz Power PC G5. Installed Western Digital WD1002FAEX as a second internal hard drive. I also installd the jumper needed to slow HD down for this computer. Initialized and formated the HD was able to back up a large iPhoto file and am still able to acceass the file from the new HD. Now Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

    Is that on your first drive or the new one???
    Only experience I had with SMART warning was that in less than 48 hrs it was dead for good.

Maybe you are looking for