I built a desktop several weeks ago, which has been running quite stably until today. I came in this afternoon to see a black screen alerting me that I needed to select new boot media. Checked in BIOS and saw that my HDD was no longer being recognized. Swapped the SATA cable to another connection on the mobo just to see if it was a physical connection error, no change. Used a powered SATA-USB adapter and did some analysis with GSmartControl on a Linux machine (original desktop was running Win7 Pro 64).
Issues:
- No partition table found
- Was claiming the device to have a 2 TB (2199 GB) capacity, when the drive is only 1.5 TB.
- "Logical block address out of range"
Attempts to write a new partition table using the utility failed due to I/O errors. In fact, it's impossible to do anything to the drive besides using the utility to observe the above errors--everything fails due to I/O errors. I'm guessing this is why it's assigning 2 TB to the capacity (just a random value associated with it getting no data back from the drive). The only thing the software seems to recognize is that there *is* something plugged into the mount.
Specifications:
HDD - Western Digital Caviar Black 1.5 TB, 7200 RPM, 3.5" (WD1502FAEX)
Mobo - ASRock Extreme3 Gen3, was utilizing one of its SATA 6Gb/s headers
Other - i5 2500K at stock frequencies, 8 GB DDR3-1600 (Corsair Vengeance), Antec HCG-750W PSU, (2x) Zotac GTX-560, LG Blu-Ray burner using one of the other SATA headers (the 3 Gb/s oness).
Since the motherboard is a fairly new product, released just over a month ago, should I be suspicious of it, or is this almost certainly a typical hard drive failure? I've had one other drive failure, which was with a WD 2.5" Caviar Black drive, but that was a mechanical issue and it was in a laptop. This drive isn't making any odd noises, and has spent its entire powered life in a desktop that has never been moved. I took ESD precautions when building the computer, and as I said before, the it did work perfectly for about 3 weeks up until today.
I am not too concerned with data recovery (I didn't have anything valuable onboard yet, and once I do I'll be doing regular backups), and I was planning to migrate my OS to an SSD soon (this is motivation to finally get that done), but I am concerned about what caused the issue in the first place, which was seemingly out of the blue. I don't want a similar failure to happen again if the root of the problem lies in the motherboard, especially when I have multiple drives attached in the near future. If you think this is just a typical drive failure, though, I'll just RMA it back to WD and re-install my system.
Thoughts/opinions? Thanks.
Issues:
- No partition table found
- Was claiming the device to have a 2 TB (2199 GB) capacity, when the drive is only 1.5 TB.
- "Logical block address out of range"
Attempts to write a new partition table using the utility failed due to I/O errors. In fact, it's impossible to do anything to the drive besides using the utility to observe the above errors--everything fails due to I/O errors. I'm guessing this is why it's assigning 2 TB to the capacity (just a random value associated with it getting no data back from the drive). The only thing the software seems to recognize is that there *is* something plugged into the mount.
Specifications:
HDD - Western Digital Caviar Black 1.5 TB, 7200 RPM, 3.5" (WD1502FAEX)
Mobo - ASRock Extreme3 Gen3, was utilizing one of its SATA 6Gb/s headers
Other - i5 2500K at stock frequencies, 8 GB DDR3-1600 (Corsair Vengeance), Antec HCG-750W PSU, (2x) Zotac GTX-560, LG Blu-Ray burner using one of the other SATA headers (the 3 Gb/s oness).
Since the motherboard is a fairly new product, released just over a month ago, should I be suspicious of it, or is this almost certainly a typical hard drive failure? I've had one other drive failure, which was with a WD 2.5" Caviar Black drive, but that was a mechanical issue and it was in a laptop. This drive isn't making any odd noises, and has spent its entire powered life in a desktop that has never been moved. I took ESD precautions when building the computer, and as I said before, the it did work perfectly for about 3 weeks up until today.
I am not too concerned with data recovery (I didn't have anything valuable onboard yet, and once I do I'll be doing regular backups), and I was planning to migrate my OS to an SSD soon (this is motivation to finally get that done), but I am concerned about what caused the issue in the first place, which was seemingly out of the blue. I don't want a similar failure to happen again if the root of the problem lies in the motherboard, especially when I have multiple drives attached in the near future. If you think this is just a typical drive failure, though, I'll just RMA it back to WD and re-install my system.
Thoughts/opinions? Thanks.
