Disk SMART Failure

Basic question I'm sure, but want to get it right the first time. I've done my searching and still not clear on the procedure to replace a failed adm in our Xserve RAID. I have a RAID5 setup (upper controller) with (4) 250GB adm's (approx. 20,000 hours each) and (1) 250GB adm as a hot spare. The drives are in position 1 through 4, with the hot spare in position 7. Drive 2 is throwing a SMART failure and making an annoying high pitched whine, so I'd like to proactively replace it prior to failure. I have an extra 250GB adm ready to install, have backed up the data, so how to proceed? Is it as easy as pulling drive 2 and inserting the new adm? Thanks in advance for any advise / experience / reassurances
BPR
RAID admin 1.5 / Firmware 1.5 /1.50f

Yes - just pull the failed/failing drive. Since you
have a hot spare in the chassis, the XServe RAID will
imediately begin rebuilding the array using this
spare.
Hi,
I've a similar issue with a RAID 5 array: the Xserve RAID notified me by email of a disk SMART failure.
In the RAID Admin, the status for that disk is "Warning" (orange).
I also have a spare disk in the array, its status is "OK" (green).
Will the Xserve RAID automatically "replace" the failed drive to the spare one?
If so, how can I check if it's already rebuilding the array in the background?
Thanks.

Similar Messages

Multiple SMART Failures on Drive Slot #11

(Using firmware 1.5.1/1.5.1c.)
I've attempted to build a RAID 5 on the lower controller twice. Each time the drive in slot # 11 returned SMART failure. Each attempt had a different drive. Set it to RAID Now when I built it. There is a hot spare spare, but attempting to copy/delete files from RAID with OK status has failed also. The build must have failed because it stopped building the array 4 hours later. Typical build times are at least 10 hours long.
Something is up with slot # 11.
RAID Admin reported -
Disk 11 Reported and Error: COMMAND 0X35 ERROR:0x10STATUS:0x51 LBA:0x2F3EF80
Suggestions appreciated.

Are these Apple Drive Modules you're replacing or are you just swapping a new drive into the carrier itself?
It's pretty common to have 3rd party drives fail to work properly. The Xserve RAID uses drives with a firmware specifically tuned and optimized for the Xserve RAID, so few 3rd party drives have the necessary settings.

Toshiba satalite p300. SMART failure hard disc 2 .

SMART failure predicted on hard disk 2 : Toshibamk2546sx-(s1) warning: immedialely back up data and replace hard disk drive;a failure may be immiunet. perss F1 to continue........... i press F1 but nothing happens, what should i do?

Do what it says to do because if you have anything on the computer you don't want to lose you will if your system crashes as mine has done going on the third time in 7 months. I want them to replace it this time because I have had it back for a week now and gout the same message.

Trouble with two hard drives including SMART failure

About a week ago my mac mini g4 that I've had for less than 3 years, crashed while I was using itunes and playing music off an external usb drive.
As a result there has been trouble with both drives:
*Internal hard drive failure:*
The internal drive would not boot and reported a fatal hardware error, with a SMART failure. Interestingly, when I start up the computer as a firewire target and run the same Disk Utility program, it does not report the fatal error. I was able to reformat this drive and it seems to now be booting and running fine.
*External hard drive failure*
The external hard drive worked intermittently and then died completely a few days later, where it is now unable to mount it at all.
Does this mean I have two failed hard drives? The internal one seems to work fine and has for over a week, even though it still says there was a S.M.A.R.T. failure. When Disk Utility says there was a hardware failure, it prevents me from running the verify/repair functions. Is it possible that the external drive failure was somehow attributed to the internal drive?
I think it is also strange that when I run the Disk Utility using firewire target, the internal hard drive tests fine.
The message I get is:
"This drive reported a fatal hardware error to disk utility. If the drive has not failed completely, back up as much data as you can and then replace it with a working drive."
and at the bottom it says:
"S.M.A.R.T. status: failing"
Meanwhile it works just fine and my other external drive has failed altogether.
I normally wouldn't question this error message, but the fact that the other drive failed more completely at around the same time, and that the error message doesn't show up when I run the disk utility on the internal drive via firewire makes me wonder if there are other factors. It's also just frustrating that I may need to replace both.
Other things I have done is run the Apple Hardware Test, and everything passed. I also tried a PMU reset, and that didn't help.
Should I just replace the internal hard drive or should I look for other problems?
I appreciate any advice on this.
Message was edited by: biz123

I'm not aware of any firmware update for the PPC minis - I've not had any with either of my own that I recall.
Of course future reliability is something you can never really check or fully assess, but the fact the system passes the hardware test tells us that the components which could have been responsible and which are not fairly easy to replace (the logic board, disk controller, PMU are all healthy. RAM could be a problem because the hardware test is not all that capable at revealing RAM issues, but it is also not likely to be the cause of this kind of problem. The PSU is obviously suspect to some degree, but is also replaceable.
While it's not common to suffer multiple drive failures, the fact one was active and the other could easily have been paging would account for the result if either failed in that situation. Bad luck and not easy to reproduce if you tried, but not inconceivable.
The fact that the internal rendered up your files while in FW target disk mode tends to indicate that the reason it wouldn't boot from that drive was not that the drive itself was trashed, but that the drive crashed during use - a circumstance which often creates catalog and file problems, and can certainly cause the system to fail in locating the MacOS install to boot from. In that situation, unless there is physical damage to the drive, it typically can be re-used with a reformat and reinstall, since of course that corrects the kind of catalog/file issues that this sort of crash typically causes. It would be expected to report 'verified' for SMART status though.
There are a few reasons why a damaged external might not appear in Disk Utility, or refuse to mount, some of which are broad;ly similar - a crash causing file or catalog issues. The fact it was FAT32 would complicate the matter to a small degree since if the allocation tables weren't visible to the Mac due to corruption, the system wouldn't have any way to mount the drive. That said, while it would likely be visible to a PC, and may even render up files in data recovery, it wouldn't be reusable itself without a reformat, and could well produce I/O errors in the process. It would usually be amenable to reformatting though it might also need repartitioning depending on the damage done. The overheating you mention may be an indicator of a fault, or it may be that the drive is being pushed to all 3 read attempts with each data block - that would cause it to work very hard! If you have rescue the data you think you can get off it, I'd suggest you try a reformat. If that fails, use a utility such as FDISK to delete all the partitions and recreate them, then try formatting again.
In terms of iTunes, any version will work, including 7.6. If music is stored on the external and that is USB connected, that would count for some speed impediment since iTunes is fairly cpu intensive, and the USB bus is also highly variable in performance, depending on CPU activity. But no, there is nothing in the latest version of iTunes that would cause a PPC to suffer such performance problems in itself, so you can use that quite safely. All are very cautious about this aspect of software design, since updates are often released to deal with stability or security issues, and must be usable for everyone.

Disk Boot Failure, Insert System Disk and Press Enter

I have been experiencing an intermittent disk boot failure for the last few months on my HP Pavilion Slimline PC. At first, it would occur once every week or two, typically when the computer would boot up after being in hibernation. After turning off the computer and turning it back on, everything worked normally. Within the last month, the failure began occurring with more regularity.
This week, I started receiving the error every time the computer would boot from hibernation. I went into the BIOS and saw that the system was not recognizing the hard drive. I tried changing the boot priority to boot from the HDD first, but to no avail. Today, the system worked as usual until I performed a restart, and it has yet to work again. Additionally, the performance has taken a nose dive over the last week (slow processing, programs not responding, etc.).
System Specs:
HP Pavilion Slimline s3710t PC
250 GB SATA Western Digital HDD (Caviar Blue)
Intel Pentium Dual-Core Processor
Windows Vista Home Premium (32-bit)
3GB DR2-800 MHz SDRAM
I have read through many technical forums, including HP’s, and followed all of the advice. I have again changed the boot priority to HDD first, restored the default settings, etc. The only drive I can find listed is the DVD drive on the unit, which is listed as the second drive. There is no first drive listed in the main tab of the BIOS CMOS Setup Utility.
I attempted to run a system recovery, but it is not even possible. Upon running the diagnostics, it of course mentions that there is no hard drive connected. Upon entering the boot menu, it also only lists the DVD drive.
My next course of action was to remove the side panel and reseat the connections on the hard drive, as well as the connection to the motherboard. This was also unsuccessful, and I have not been able to boot up the computer again today.
The computer itself is 1.5 years old and this is the original hard drive that shipped with it. I have never opened the computer, prior to today. The symptoms started a few months ago, just outside of the warranty period.
Based on the forums I have read, it all signs are pointing to a bad hard drive. This is hard for me to believe, as the computer is relatively new and does not get much use. The use it does get revolves around email and Internet access, as well as use of Microsoft Office.
As you can imagine, I am not happy about the prospect of having to buy a new hard drive, as well as pay for the data recovery on the original drive. I hope that someone at HP can come up with a better solution, as a 1-year life on a hard drive is pretty pathetic.
Thanks,
JR

HI JR,
You situation does not sound good if the PC doesn't recognize your hard drive.
Boot into the bios and run some bios hardware diagnostics.
Try clearing the CMOS.
Try this procedure:
Unplug the PC and open it up. Clean out all the dust. Carefully remove and replace all the cables going to the motherboard one at a time. Do the same for the memory dimms and the video and sound cards if you have any. You might want to buy a can of compressed air to blow the dust out of the CPU heat sink. Plug your PC back in and give it a go.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

HP Pc 3010 Microtower VN 969EA - Hard Disk Reporting failure

The folloing hard disks reporting failure - Disk nameT3320418AS ATA Device volume C:\ D:\ E:\

Meshmesh -
Is this hard drive a Seagate ST3320418AS ??
320 Gbytes, Barracuda 7200.12 Serial ATA
http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%207200.12/100529369c.pdf
IF YES, then assure that the Data on this drive is backed up.
That should be your immediate step, backup/retrieve important files, photos or data,
IF the drive is still accessible.
This Seagate drive was released in 2008-2009 time period (5 to 6 years ago).
Seagate Desktop HDD (Barracuda Hard Drive) Product Page
http://www.seagate.com/support/internal-hard-drives/desktop-hard-drives/desktop-hdd/

SMART failure on internal SATA drive - Can I recover data or disable SMART?

Hi
One of my internal SAT drives (a Western Digital RE2 500gb drive) appears to be giving up the ghost and is reporting a SMART failure. The drive is mounting and shows that it has 100gb available but I can't access the data held in the missing 400gb.
I've run a TechTool report on it which has come back stating a failure on the following 2 points out of 15 tests:
• Reallocated Sector Counts
• Seek error rate
Appreciate that the drive is on its way out but is there anything i can do do retrieve the 400gb of data on it now before is completely dies? Can SMART be disabled on that drive to allow me to access it?
Any help would be appreciated.
Mark

It's not that SMART is preventing you from accessing it, the drive has had a physical failure. It may be possible to recover some data with a data recovery tool, like [Data Rescue|http://www.prosofteng.com> or [File Salvage|http://subrosasoft.com/OSXSoftware/index.php?mainpage=product_info&productsid=1], or you could send it off to a data recovery service, but there are no guarantees. If the data on that drive is not backed up, I'd guess you're about to learn a painful lesson about backups.

Directory cannot be rebuilt due to Disk hardware failure (-36, 2286 )

Hello everybody,
my macbook was running slower and slower until it became unusable.
I have restarted the macbook with system DVD and run harddisk utilities from the DVD :
- First diagnostic : directory damaged, error on knot, cannot be repaired by this program.
I tried to put the disk in target mode but it was impossible to mount it on the desk.
-Then I tried with DiskWarrior utilities and got the message : Directory cannot be rebuilt due to Disk hardware failure (-36, 2286 )
Does anybody knows what it means ?
If disk has to be changed what brand would be the best suited.
Any advice on this issue will be more than welcome
Best regards from France
Jean Claude

*Many thanks* Templeton Peck for your help.
I am going to replace the disk but all the work of the last four days will be lost, kinf of hard to swallow on a machine bought a little more than a year ago !
Sweet home Chicago ! 41 years ago I heard Menphis Slim sing that tune in "Les trois maillets" a famous St. Germain des prés jazz club in Paris. Souvenirs, souvenirs…
Message was edited by: HotDna

Disk Boot Failure [solved]

I'm installing arch on a rebuilt system, but I cannot get it to boot. I have pared the system down to a a SCSI card, a video card, a single hard drive, an IDE CD, a SCSI tape drive, and a floppy. I have tried my standard installation partitioning scheme, and the automatic version.
No matter what I do, while the system seems to install correctly, when I reboot I get a Disk Boot Failure.
I've zeroed the drive, I've tried an fdisk /mbr, I've run a Maxtor burn-in test which came back fine. I'm convinced it isn't the drive. The standard menu.lst uses root (0,0) and the kernel in /dev/discs/disc0/part3 after an automatic installation. I mounted the /boot partition set up by the auto install, and the grub directory and files are there.
What am I missing?
Last edited by timm (2009-05-04 22:11:42)

I think it's solved.
Everybody who was mentioning the BIOS got me looking in there, but I found nothing out of the ordinary. I decided to try to install Windows 2K to see if that would boot, which it did flawlessly. I reinstalled arch, and go the disk failure. Back to the BIOS.
This is an IDE hard drive; the only thing SCSI is the tape drive.
What I found was that the access on the hard drive was set to Auto, which I had seen before but didn't think to be a problem. I tried changing that to LBA (which is what I thought Auto would do on a drive like this), and suddenly arch comes up just fine.
I have a couple of RocketRaid cards that I'm installing, and will be playing around with the SCSI as well. I'm going to play with things a bit more, but unless I can make it fail with some other tweaking, that BIOS setting appears to have been the problem.
Thanks to everyone for their help!

Problems with 1st Boot (media test failure, disk boot failure)

I have the K7N2G motherboard.
I hooked up everything in my system and on my first boot I get this error:
PXE-E61: Media Test Failure, check cable
PXE-M0F: Exiting NVIDIA Boot Agent
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
So, I figure I'll start from scratch and just start with the floppy drive, cpu, and ram hooked up and I get the same error. Here are my specs:
MSI K7N2G
Athlon 2400
Kingston PC3500 RAM
Volcano 7 Fan/Heatsink
Seagate Barracuda V SATA 80 GB
Verbatim CDRW 52/24/52
Any help or suggestions would be greatly appreciated.

This happens if:
- The hard drive is not installed
- An Operating System is not installed
- The BIOS cant detect the hard drive, maybe:
= The wrong jumpers are set on the hard-drive
= The cable is not polarised and pin 1 is on the wrong pin
- The hard-drive has not been set-up in the BIOS
Try something like the above

DISK BOOT FAILURE: PLEASE INSERT SYSTEM DISK....

Hi
I have exhausted two full days on the following problem so I would greatly appreciate some help. The problem I am experiencing is that the disk will not boot on its own. I receive the "DISK BOOT FAILURE: PLEASE INSERT SYSTEM DISK...." error when starting up. I have run chkdsk, i have run Western Digital Diagnostics for Dos (quick test) and no problems come up with the drive. I have also jumpered pins 5 and 6 to force the drive to run at SATA-I speeds. Now here's the curious part: The disk boots up and functions absolutely perfectly IF and ONLY IF, the bios is set to boot from my IDE drive. Now on the IDE drive I have a boot.ini file set up to allow me to boot the SATA drive instead. Using this work around (i.e. boot from IDE, select SATA drive from boot menu) the drive seems to work just fine. However if i change the bios back to boot from the SATA drive (and therefore use its own boot.ini) I receive the error again and the boot will not continue.
Here is my set up:
MSI K8T Neo2-F v2.0 motherboard (with latest BIOS).
Athlon 64 X2 4200+ dual core CPU
1024GB DDR 400 RAM
1 Western Digital 120GB IDE HD running on primary master.
1 Pioneer DVD-108 DVD-RW running on secondary master.
1 Western Digital 250GB (WD2500KS) running on SATA1.
Nividia GeForce 6800 running on AGP.
M-Audio Audiophile 2496 PCI
Sound Blaster Audigy 2 ZS PCI
Originally the system was as above without the new WD2500KS drive. I then bought the new SATA drive and installed windows to it with the intention of clearing windows from the original IDE and making it a storage drive. The above workaround is how I completed installation of Windows XP and installed my other programs, otherwise when rebooting during installation the disk would fail again.
Another issue is that Windows will NOT designate the SATA as drive C. When disconnecting the IDE, the SATA will become "c:" but as soon as the IDE is plugged back in, it immediately claims "c:" again and the SATA becomes "d:". This is ascertained from running the Recovery Console and using 'map' for example. It is important that I get this to "c:" as I have programs which appear to look for files by an absolute path and will not find them on "d:".
I have also tried to 'fixmbr' and this is the only time I have seen any curious message. Using the workaround the disk works fine. But when I tried to 'fixmbr', the system warned that the disk had a non-standard boot record (or something to that effect). But in any case, boot seems fine so long as we're not booting it directly.
Finally, I should confirm that the BIOS is set to run the SATA in IDE mode and not SATA (although as a sanity check I have run it in RAID and the result is the same).
I have no idea at this stage whether the problem lies with the SATA drive or the motherboard. I have sent a copy of this to WD "for further troubleshooting", and am posting a copy here for any advice on the mobo side of things.
Many thanks

Thank you for your reply. You are right, I've just resolved the problem today and discovered that this was the case.
To close the topic and leave advice for anyone else facing similar difficulties I will sum up the progress since the initial post.
Having tried absolutely everything else, I thought "what happens if i make this sata c:?" so I decided to edit the registry and force a drive letter change to ensure that my SATA was "c:". After having done this the SATA for the first time successfully booted to the boot menu! However when loading up into Windows it kept hanging. So next I thought all I need to do is a repair install now, I disconnected the IDE to leave the SATA only and attempted this. Unfortunatley the repair install also kept hanging. The Microsoft support page detailing how to force the drive letter change does warn that doing so can mess everything up unless the problem occurred in some specific circumstances.
So a new install was in order. I hooked up the IDE again and booted from it, backed up all my files to the IDE, and then disconnected it again. Then booted from a Western Digital diagnostics disk and zero filled the SATA - this was more for my own sanity so as not to worry about dodgy MBR's and what not. Then booted from WINXP CD and formatted and reinstalled fresh.
Install was successful.
Hooked up IDE externally to dump back my backed up files. Then deleted the IDE's partition and formatted it. Powered down, connected the IDE internally again - booted from SATA successfully (now on c:)... the IDE was no longer recognised as a "system" disk in Disk Manager, so I gave it a drive letter and hey presto we're business again!! One SATA system disk on drive c: and one IDE storage drive!
SHORT VERSION: If you are adding an SATA drive to an IDE set up, and want the SATA to be your OS disk, unhook all the IDE's first... if the target drive is not in isolation when installing Windows, all kinds of problems can ensue which are very difficult to correct after the install.

MSI 975x disk boot failure

I have been having a problem lately with a 975x having disk boot failure once in a while. The system has 2 drives and a dvd writer. It's about 2.5 years old also. When this happens it doesn't see any drives. I've cleaned the filters, fans etc and sometimes during this it'll start working. Once it finds the drive it boots just fine and works fine. I don't think it's a drive as it can't find any of them.
This happens intermittently, and there is no pattern to what gets it working again. The case is well ventilated. I have 4 gig DDR2, the drives are SATA, core 2 duo 2.13 ghz.
I'm thinking the mother board is starting to go bad on me.
Does anyone have any other ideas?
Also if I change the board what is a good one in the newer models so I won't have to change a lot of other hardware?
I've not kept current on the advances in mother boards the last few years

Well I spoke too soon.
It did it again today. It started with a not responding message and on reboot it did not detect any drives the first time. In the bios it said none in all positions also. After Another reboot it identified the WD drive but not the Seagate drive. After sitting about 2 hours I rebooted with the Seagate drive unplugged and it came up just fine. I then put in 2 more drives and plugged in the Seagate drive and it worked just fine.
Any other ideas?
Do you think my suspecting a flaky MB is wrong?
Also whats a good MB for the hardware I have?

Smart failure on imac

My hard drive has a SMART FAILURE, I understand that I will need a new hard drive, but does anyone know the cost?
I've contacted An Apple store but they said I needed to bring it in, so rather then carrying a 21.5 imac to a store,
Can anyone give me a rough price?
I would be really greatful

$200-400 USD, depending on HD replacement size. BTW, the store personnel will come to your car and transport the machine to the store. The reverse after the repair is finished.
27" i7 iMac (Mid 2011) refurb, OS X Yo (10.10), Mavs, ML & SL, G4 450 MP w/10.5 & 9.2.2

When login, i see a error message saying " there is a eminent problem with hard disk " smart check

G72-250US Notebook , Win 7 64 Home Premium,
Error :
When i login " There is a eminent problem with Hard disk, SMART check faled" ,Prmary hard disk self test failed .
Please help me with ths problem

Hi,
If this message is coming up in a black screen.
Then the harddrive in the system is about to go bad or already bad.
If you are able to boot to windows, FIRST BACKUP DATA.
Also run a startup test by tapping F2 as soon as you power on the system.
The smart test is a BIOS feature in most of the computer which is designed to keep cust informed if the HDD is about to go bad. But their are instances where the SMART will only let you know that the HDD is bad only when the HDD has bad.
More Info: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01443317&cc=us&dlc=en&lc=en&jumpid=reg_R1002_US...
Although I am an HP employee, I am speaking for myself and not for HP.

Disk write failure

when i go to update the song on my ipod it does 2 or 3 then says disk write failure disk could not be read or written to
does anyone know whats going on

http://docs.info.apple.com/article.html?artnum=301267
When you sync your iPod with iTunes, iTunes may display an error message that reads:
"Attempting to copy to the disk <iPod name> failed. The disk could not be read from or written to."
When you update or restore your iPod, you may see this error:
"Firmware update failure. Disk write error."
These errors can happen with any iPod.
These errors can occur anytime iTunes can't read information from or write information to the iPod. Here are some things that can cause this.
Outdated operating system software
Make sure you have the latest updates for your operating system, which may include improvements for device connections. For example, many USB and FireWire improvements have been included in Windows Service Packs.
Computer needs updates
Make sure you have the latest updates available for your specific computer model (or components for home-built PCs). These are usually available for download on the support website for the maker of the PC (or component). Many USB updates are listed as "Intel chipset" or just "chipset" updates on PC manufacturer's support and download websites.
Software interference
Some software can interfere with iTunes, making it unable to write files to your iPod. For example, antivirus software that scans all files on connected disks can cause one of these errors. Think about what software you have installed, and try disabling any add-ons that might be interfering with iTunes. Check your suspected software's documentation or contact the software maker if you need assistance with disabling the application.
Damaged files
If one of your music files or photos is damaged, iTunes may display one of these errors when transferring that file to the iPod. If you identify a file that is causing the error, try deleting that file and reimporting it from a backup file or from the original source. You may be able to repair files by repairing the disk (see the solutions in the next section).
Damaged disk structure
These errors can also appear if the format of your computer's hard drive or your iPod disk is damaged.
Windows users, search the Help system in Windows for chkdsk to get more information on checking and repairing the disk structure.
To repair an iPod disk—Restore the iPod or iPod shuffle using the latest version of iPod Updater. Warning: Be sure to back up your data before restoring an iPod. The restore process cannot be undone. All of your songs and files will be deleted.
Corrupt iPod photo Cache
If you're getting the error when transferring photos to an iPod photo, try deleting the iPod photo Cache and then starting the photo sync again.
Lost connection
Make sure that the connections from your computer to the iPod are snug and do not wiggle or come loose during transfers. For example, if you use the wrong size dock for your iPod, it can put strain on the connectors and cause a bad connection.
Hardware failure or non-compliant hardware can cause these errors. This could be an issue with iPod hardware or with the cable or dock you're using, but more often it's an issue with the USB or FireWire card or interface in your computer. Some USB and FireWire interfaces just don't work very well. If you isolate the issue to the USB or FireWire interface in your computer, you may want to try a different port, get the computer serviced, or replace the card or interface with a better one.

Disk SMART Failure

Similar Messages

Maybe you are looking for