Should my hard drive sound like this?

atomic_cat

Commendable
Oct 30, 2016
6
0
1,510
Recording here.

I ask because I've been having issues with my laptop freezing up, sometimes to the point that I have to hold the power button to shut it off. Now this happened again today only this time accompanied by the sound I posted above. I've had this computer for 3 years and the disk activity never sounded like that before...
 
Solution
Yeah it's failing to write to your HDD by the looks of it. Is 100% a clue that the drive is failing. If you're lucky it may just be a bad sector but you can;'t even run a chkdsk. Which is kind of another sign lol.

atomic_cat

Commendable
Oct 30, 2016
6
0
1,510


Well my drive doesn't show up in that program. The user guide said that "Please note: WinDFT is not designed to run on your primary operating drive" which sucks because that's exactly what I need it to do :/

Also I ran chkdsk. After an hour I got a blue screen that was stuck a 0% until I restarted
 
Did you try the legacy downloads for older versions? What OS/system are you using?

Tbh though it really sounds like your HDD has internal operation errors and you should make plans on the basis that it will fail sooner rather than later.
 

atomic_cat

Commendable
Oct 30, 2016
6
0
1,510


I'm running Windows 10. The legacy versions require that I make a bootable CD and I don't have any blank CDs (although, I suppose I could put the image on a usb, but at that point I may as well try using my ubuntu usb instead)

I'm going to cross my fingers that it can hold out until those black friday/cyber monday sales so I can go buy an SSD
 

atomic_cat

Commendable
Oct 30, 2016
6
0
1,510


Well I guess I might switch from monthly to weekly backups then :)

One last question. I found some unusual messages in the event log. There were only two in September but there were a few in the last couple of weeks:

Log Name: Application
Source: ESENT
Date: 10/27/2016 11:12:16 AM
Event ID: 508
Task Category: Performance
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
svchost (1512) SRUJet: A request to write to the file "C:\WINDOWS\system32\SRU\SRUDB.dat" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

It's not always the same file and the offset number changes too but the number of bytes is always the same. Could this be related? It's the closest thing to an IO error that I could find
 

atomic_cat

Commendable
Oct 30, 2016
6
0
1,510


Yep, that's kind of what I thought :/ On the bright side I can now justify spending a hundred or so on a good SSD. I'll keep an eye on things and backup more often until then.

Thanks for the help and advice :)