Share via

New Hard Disk “Seagate ST2000DM001 “ not detecting under my computer, Windows 7

Anonymous
2012-02-17T23:42:49+00:00

Original title :  HDD Missing

I added a Seagate ST2000DM001 2TB drive to my computer.  It appears in Device Manager and BIOS.  It appears as "Disk 1" in Computer Mgnt, but the volume does not appear.  The drive does not appear in My Computer.

I cannot format or assign a letter to the secondary drive.

I updated the HDD Firmware w/ Barracuda-ALL-GRCC4CD.exe.

What do I need to do to access the 2TB drive?

System Specs:

Windows 7 Ultimate (64-bit)

MSI x58 Platinum SLI w/ BIOS v. 3.9 (2011-01-28)

Intel Core i7 920 @ 2.67GHz

6 GB RAM

Disk 0 - Seagate 150 GB ST3160023A-RK (Ultra ATA/100 w/ SATA adapter)

Disk 1 - Seagate 2TB ST2000DM001

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2012-02-18T17:01:12+00:00

    Hi,

    Have you made any changes to the computer prior to this issue?

    I would suggest you to follow the below methods and check if it helps.

    Method 1:

    Try running Hardware and Devices troubleshooter and check.

    Refer: http://windows.microsoft.com/en-us/windows7/Open-the-Hardware-and-Devices-troubleshooter

    Method 2:

    Check your hard disk for errors:

    http://windows.microsoft.com/en-US/windows7/Check-a-drive-for-errors

    Note: While performing chkdsk on the hard drive if any bad sectors are found on the hard drive when chkdsk tries to repair that sector if any data available on that might be lost.

    Method 3:

    Initialize the disk in Disk Management.

    Create and format a hard disk partition : http://windows.microsoft.com/en-US/windows7/Create-and-format-a-hard-disk-partition

    Note :Converting a hard disk partition or volume from NTFS to FAT32 requires that you reformat the partition, which deletes any data on it. Be sure to back up any data you want to keep before you begin.

    Method 4:

    Try connecting with different computer and check if it helps.

    If the issue is still persist, then it would be better to contact the Seagate for further assistance.

    Seagate Support: http://www.seagate.com/www/en-us/support/

    Hope the information is helpful.

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-12-06T07:37:15+00:00

    The drivel from the Microsoft engaged Support Engineer "expert" must be the answer since another Microsoft engaged Support Engineer "expert" marked it as the "Answer".  These are the Microsoft "experts".

    Oh wait -  we know how things work here...  if one Microsoft engaged Support Engineer "expert" replies to a topic and the topic goes idle for 5-10 days, another Microsoft engaged "expert" will mark that reply as the "Answer" even if the reply makes no sense, is untested or impossible to work. 

    In this case it only took 6 days of idleness.  Right on time.

    Folks could save a lot of time by not paying much/any attention to replies that begin with the words Hi or Hello, contain Methods and Steps, have suggestions that begin with the word "try" and end with "check if it helps".

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2015-12-06T06:35:20+00:00

    OK  so how, having read the above drivel, does one obtain the magic wand with which to carry out the instructions?

    Method 1 will never work because it involves a windows troubleshooter and we all know how useless they are - like a politician - look good but a waste of space.

    Methods 2 to 4 require the ability to READ the drive. I thought THAT was the problem.  Hence to read a drive which is obviously inaccessible, one must have a magic wand because all of the suggestions postulate the premise that one HAS ACCESS.

    It seems nothing has changed in the last four years because I am having the same problem and MS have not come up with a workable/sensible solution.  What's new?

    Of course one could suspect that it is a Windows issue and not a drive problem.

    5 people found this answer helpful.
    0 comments No comments