Question New HDD problems - - - am I screwed ?

[Muchacho45]

Hello
I bought a new Seagate 4tb hdd, since the first moment it made the sound in the video. The pc indentified it at first and hdd sentinel said its a 100%, i went through the whole formatting process and it gave me an error in the end “a device which does not exist was specified”, I closed the pc, checked connections and everything was fine. Turned it back on, did the same noise again and now the pc wont recognize it and giving me
" the the request could not be performed because of an i/o device error"
Is it faulty?

View: https://www.youtube.com/shorts/qI9J9KE2ARs

 

[Lutfij]

You will need to include the video you speak of.

Try and use another SATA cable, does the device get flagged on Device Manager(assuming you're on Windows OS)? What is the make and model of your PSU and it's age?

 

[Muchacho45]

You will need to include the video you speak of.

Try and use another SATA cable, does the device get flagged on Device Manager(assuming you're on Windows OS)? What is the make and model of your PSU and it's age?

It does get flagged when I go to format it but with a red X over the side no showing the properites, in the first time it showed.

The PSU is 5 and it's Antec GOLD 550W, But I doubt that is the culrpit is the rest of the computer works fine and recognized it the first time, I added the video, it is now quiet though but is not recognizeable.

 

[Muchacho45]

@Lutfij I tried a new sata cable and nothing, still giving me that same error. HD sentiel recognizes it but not as it should, just giving question marks on his status and health. The first time it was fine, I don't know what happened. And it makes this noise for the first 2 minutes then stops.

 

[Muchacho45]

This is how it looks

 

[Moonstick2]

If it's new and the computer has stopped recognising it, just return it and ask for a replacement.

Only if a second one does the same thing should you start investigating your system.

 

[Muchacho45]

If it's new and the computer has stopped recognising it, just return it and ask for a replacement.

Only if a second one does the same thing should you start investigating your system.

I returend it to the store today, they said they need to check it and will give me an answer. I am afraid they will tell me that I ruined it somehow and tell me to [censored] off. I don't know...

Some guy through reddit who knows his stuff about it told me there's no way I could have done something wrong from my end that caused it to flop, and it's most likley a faulty drive.

 

[Satan-IR]

That sounds like the head/actuator is clicking. That HDD is toast I guess.

If you didn't drop it the drive must have been DOA. Hope you get a replacement soon.

EDIT: You said "the rest of the computer works fine and recognized it the first time". It worked first and Windows recognized it? Then it started doing the sound and not being recognized? Did you do anything in between? Was it dropped or any other hit or something?

 

[Muchacho45]

That sounds like the head/actuator is clicking. That HDD is toast I guess.

If you didn't drop it the drive must have been DOA. Hope you get a replacement soon.

EDIT: You said "the rest of the computer works fine and recognized it the first time". It worked first and Windows recognized it? Then it started doing the sound and not being recognized? Did you do anything in between? Was it dropped or any other hit or something?

Since the first moment I fired the computer up it made those sounds. My computer usually goes up in about 10 seconds. It has been over a minute and I thought that maybe it froze, due to the sound and such. I restarted it, the second time it also did not go up straight away so I waited. After 2 minutes windows is up, HDS recognized it and wrote all 100%. I went on to foramt the drive, windows recognized it and it was showing it's properties in black. I went through the whole formatting process, choosing NTFS, and when launching it to format and end process it gave me "a device which does not exist was specified".

I tried again, same result. I closed the PC and checked that everything is fine, turn it up again, now HDS does recognize it but with question marks (??) as in the picture I posted, it was no longer indicating 100% like it did. I went on the to windows formatting tab and like in the second picture I posted, it is no longer showing it's properties with a black tab, but all empty and a red X and gave me "the the request could not be performed because of an i/o device" error when just wanting to start the formatting process.

All of this time still doing the same sound for the first 2 minutes after startup, then it went quiet. i think that in the first time it was doing it constantly. Afterwards it was giving it only the first 2 minutes after startup.

never dropped nor hit anything.

 

[Satan-IR]

Since the first moment I fired the computer up it made those sounds. My computer usually goes up in about 10 seconds. It has been over a minute and I thought that maybe it froze, due to the sound and such. I restarted it, the second time it also did not go up straight away so I waited. After 2 minutes windows is up, HDS recognized it and wrote all 100%. I went on to foramt the drive, windows recognized it and it was showing it's properties in black. I went through the whole formatting process, choosing NTFS, and when launching it to format and end process it gave me "a device which does not exist was specified".

I tried again, same result. I closed the PC and checked that everything is fine, turn it up again, now HDS does recognize it but with question marks (??) as in the picture I posted, it was no longer indicating 100% like it did. I went on the to windows formatting tab and like in the second picture I posted, it is no longer showing it's properties with a black tab, but all empty and a red X and gave me "the the request could not be performed because of an i/o device" error when just wanting to start the formatting process.

All of this time still doing the same sound for the first 2 minutes after startup, then it went quiet. i think that in the first time it was doing it constantly. Afterwards it was giving it only the first 2 minutes after startup.

never dropped nor hit anything.

Bad luck then you got a faulty/failing drive. It must be under warranty and I hope you get a free replacement soon.

 

[Muchacho45]

Bad luck then you got a faulty/failing drive. It must be under warranty and I hope you get a free replacement soon.

I hope they will not give me some BS excuse why it's my fault. I am so tired of this *** [Mod edit]. 'Bad Luck' seems to be my middle name...I am very tired of this life honestly...fml

 

[Cellie]

I returend it to the store today, they said they need to check it and will give me an answer. I am afraid they will tell me that I ruined it somehow and tell me to [censored] off. I don't know...

Some guy through reddit who knows his stuff about it told me there's no way I could have done something wrong from my end that caused it to flop, and it's most likley a faulty drive.

There's probably a lot going on in your system logs. Hold onto them for proof until the RMA is complete.

Edit: Also, it's a Seagate. Worst case scenario get in contact with them instead. I had to RMA an HDD to them recently and the support was pretty good.

 

[Muchacho45]

There's probably a lot going on in your system logs. Hold onto them for proof until the RMA is complete.

Edit: Also, it's a Seagate. Worst case scenario get in contact with them instead. I had to RMA an HDD to them recently and the support was pretty good.

What do you mean by System Logs? I don't know what is that or how to access it.

 

[Cellie]

Control Panel > Event Viewer >Windows Logs > System. From your description you'll have plenty warnings and errors with "disk" as source. Likely from the moment you plugged it, thus unless they argue you dropped it on the way home from the store there's your proof the drive wasn't fine already since the moment you first connected it.

 

[SkyNetRising]

I hope they will not give me some BS excuse why it's my fault.

Avoid Seagate Barracuda drives. Those all are SMR drives with inconsistent write performance.
They are so cheap because they are inferior products.
For your next HDD make sure it is CMR drive (not SMR).

 

[Muchacho45]

Control Panel > Event Viewer >Windows Logs > System. From your description you'll have plenty warnings and errors with "disk" as source. Likely from the moment you plugged it, thus unless they argue you dropped it on the way home from the store there's your proof the drive wasn't fine already since the moment you first connected it.

I am going through it, all I could find for now is one event id 98 that says a drive (which gives a link without a specified letter, probably thats it) is healthy.

Then another one later (219) that says: The driver \Driver\WudfRd failed to load for the device {C5A047D8-CB5B-40E9-B9E3-316AB06B5A18}\WirelessKeyboardFilter\9&33dd0964&0&01.

And then another one - The IO operation at logical block address 0x0 for Disk 0 (PDO name: \Device\0000003a) was retried. (153)

it gives that 153 error a few times ^ and then:

VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008

Error code 10^

And then a dozen more times: The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Error 10010 ^

Goes between those last 2 like 30 times over....

 

[Satan-IR]

I hope they will not give me some BS excuse why it's my fault. I am so tired of this shit. 'Bad Luck' seems to be my middle name...I am very tired of this life honestly...fml

Hope things change for the better. Things like this happen. I guess we shouldn't let it bother us that much.

I had a 2TB Seagate I used to archive from data fail shortly after the warranty expired. It's annoying but it happens. I had backup of the files I needed and despite the fact that on paper an HDD shouldn't fail in 26 months knowing that *all drives/components fail* I just went on.

I think that video of the sound the drive makes is proof enough it's faulty.

Keeping the logs and Event Viewer might help if they contain data that point to the system not being able to recognize and mount/load the disk/drive.

 

[Muchacho45]

Hope things change for the better. Things like this happen. I guess we shouldn't let it bother us that much.

I had a 2TB Seagate I used to archive from data fail shortly after the warranty expired. It's annoying but it happens. I had backup of the files I needed and despite the fact that on paper an HDD shouldn't fail in 26 months knowing that *all drives/components fail* I just went on.

I think that video of the sound the drive makes is proof enough it's faulty.

Keeping the logs and Event Viewer might help if they contain data that point to the system not being able to recognize and mount/load the disk/drive.

From the events I posted, does it make any evidence? And how to keep it, simply write it or screenshot it?

 

[Satan-IR]

From the events I posted, does it make any evidence? And how to keep it, simply write it or screenshot it?

You can search inside the Event Viewer and search for Ntfs or Disk and see if Windows event viewer has logged anything relating to the time you tried to format the dirve and it failed.

There might not be that much in there as the Windows didn't really have time to log anything about that drive since you couldn't even formatted and used. It wouldn't hurt to check anyway. Search for disk, Disk, Ntfs, NTFS and see if there's anything regarding the system not being able to format the drive.

Generally speaking, you can also save events in the Event Viewer as files.

I would keep that video you recorded of the drive making that sound.

Although if the drive is under warranty (which it should be) and if the vendor/supplier/seller is a decent one I don't think there would be much problem for an RMA and drive replecement. I hope not.