Here's what I discovered after many attempts in the last few nights.

Terminal of my 2 ES.2 drives was locked (drives were in BSY state) - every 3-4 seconds I received from their terminal message LED: 000000CC....

Standard solution which is widely known for 7200.11 series (ST******AS) doesn't work for locked ES.2 series (ST******NS) !!!

But i've found a way to unlock terminal of my ES.2 drives what allows then to repair hd in a standard way (solution from Yura/Okzo).

1. Disk has to be complete (PCB+rest together), NO isolation between the PCB and the rest

2. In the terminal you will see every few seconds message LED: 000000CC ...

3. between these messages you can unlock the terminal by pushing CTRL+Z. It will show a line: "F3 T>" and it will be Unlocked for about 1 second

4. During that 1 second when you see "F3 T>" message but before you receive next "LED:000000CC..." you must short two points shown in the following image (they are known as "read-channel").

You must hold them short about 20-30 or little more seconds.

If you won't see next "LED:000000CC..." and disk will issue few unpleasant sounds then after some time you'll see in the terminal message "Input Command Eror".

Now the disk's terminal is unlocked!

Still holding those 2 pins short issue command /2 and then Z (they're cAsE sEnSiTiVe!).

When disk's engine will stop you will see message "Spin Down Complete" and now you can release the short between 2 pins.

Next do repair with standard instruction (as for 7200.11) - all below is cAsE sEnSiTiVe!:

F3 2>U

Spin Up Complete

F3 T3>/1

F3 1>N1

F3 1>/

F3 T>m0,2,2,0,0,0,0,22

and wait until you'll get message

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000

.....

User Partition Format Successful - Elapsed Time 0 mins 05 secs

Good example (also extended) gave aviko, in post number 529 in topic # 128807

It is at: http://www.msfn.org/board/index.php?showto...mp;#entry832876

I am a complete amateur (not DR professional), and of course, give no warranty for the described procedure.

It worked for me and my two ES.2 drives are alive now.

Of course, this procedure or the incorrect use might as well burn your disks and data.

I don't assume responsibility for such cases - everything you do at your own risk.

This procedure of ES.2' terminal unlocking is my own discovery, and I'd like to share this knowledge with other poor owners of bricked (in BSY state) ES.2 disks.

Calling on MSFN's hardware cognoscenti:

About two weeks ago I noticed that the HDD on my Vista system seemed to be running very slowly. Despite the drive's passing tests from several popular maintenance/health applications, I was worried that it might fail suddenly at any moment. It was taking forever to yield search results in Outlook, and Windows Explorer searches were running like molasses. Who knows, it's a seven-year-old, heavily used disk.

So, taking no chances, a week ago I imaged the drive (a Seagate ST3500620AS) and bought the closest model to it that I could find (a Seagate ST500DM002) in the hope that doing it this way would minimize problems with running the system on the new drive after transferring it.

After I got everything set up (Vista even found drivers for the new HDD), Outlook and Explorer searches are indeed running much faster. But I find that launching programs (such as Pale Moon) is quite sluggish. So I ran the program HD Tune and was shocked to see the following performance graph:

It's hard to miss the sudden and precipitous drop in performance about two-thirds of the way into the test.

What could be causing this? It's a brand-new, store-bought drive. The previous HDD (sorry, I didn't keep screenshots of it) showed a curve that started much lower but then gently dropped to about the 15 mark (left-hand scale) at the 100% point on the chart shown in the screenshot. The dot scatter pattern was also much tighter, roughly mirroring the blue graph line (that is, going up as the access time in milliseconds increased).

One other thing that might possibly have a bearing on the issue: free space in this 500GB drive was about 234GB when the system was first installed on it. After the index was rebuilt, free space went down to about 225GB. But every day since, I've noticed that the amount of free space keeps dropping for no apparent reason. Yesterday it was down to 190GB; I just checked now, and it's currently at 180GB. The list of files on the drive, sorted by size by Defraggler, shows six very large files (with names formed by long strings of letters and numbers inside curly brackets) in the folder C:\System Volume Information, ranging in size from some 5GB to 8GB.

What the heck is going on? Scans with various AV tools reveal no infection.

I look forward to hearing your wise counsel. 

--JorgeA

Has anyone bought a good external hd recently? If so what type of external hd was it? I just had the WD HD crap out on my after less than a month.

http://www.amazon.com/Blue-Black-Passport-Edition-Portable-External/dp/B00M1VICHO

Please make sure you've READ the Read-Me-First Sticky FIRST!

The Solution for Seagate 7200.11 HDDs (final and revised version):

* Spanish Version here / Versión en Español aquí.

* Italian Version here / Versione Italiana qui.

Attention: This guide might not be to everyone. Is not hard to KILL your HD if you don't follow the instructions with extreme caution. I'm NOT responsible for any damage or data loss it can happen (so far no one lost anything, but accidents can occur).

There are two common errors on Seagate 7200.11 HDDs (caused by bugs on firmware):

- 0 LBA error: it happens when your BIOS can recognize your HDD at POST moment, but as an 0MB drive.

- BSY error: it happens when your HDD enter on a halt state, or BuSY state. In this condition, your HDD will not be recognized by BIOS at POST moment.

Seagate's explanation:

Description

An issue exists that may cause some Seagate hard drives to become inoperable immediately after a power-on operation. Once this condition has occurred, the drive cannot be restored to normal operation without intervention from Seagate. Data on the drive will be unaffected and can be accessed once normal drive operation has been restored. This is caused by a firmware issue coupled with a specific manufacturing test process.

Root Cause

This condition was introduced by a firmware issue that sets the drive event log to an invalid location causing the drive to become inaccessible.

The firmware issue is that the end boundary of the event log circular buffer (320) was set incorrectly. During Event Log initialization, the boundary condition that defines the end of the Event Log is off by one. During power up, if the Event Log counter is at entry 320, or a multiple of (320 + x*256), and if a particular data pattern (dependent on the type of tester used during the drive manufacturing test process) had been present in the reserved-area system tracks when the drive's reserved-area file system was created during manufacturing, firmware will increment the Event Log pointer past the end of the event log data structure. This error is detected and results in an "Assert Failure", which causes the drive to hang as a failsafe measure. When the drive enters failsafe further update s to the counter become impossible and the condition will remain through subsequent power cycles. The problem only arises if a power cycle initialization occurs when the Event Log is at 320 or some multiple of 256 thereafter. Once a drive is in this state, there is no path to resolve/recover existing failed drives without Seagate technical intervention. For a drive to be susceptible to this issue, it must have both the firmware that contains the issue and have been tested through the specific manufacturing process.

Corrective Action

Seagate has implemented a containment action to ensure that all manufacturing test processes write the same "benign" fill pattern. This change is a permanent part of the test process. All drives with a date of manufacture January 12, 2009 and later are not affected by this issue as they have been through the corrected test process.

Recommendation

Seagate strongly recommends customers proactively update all affected drives to the latest firmware. If you have experienced a problem, or have an affected drive exhibiting this behavior, please contact your appropriate Seagate representative. If you are unable to access your data due to this issue, Seagate will provide free data recovery services. Seagate will work with you to expedite a remedy to minimize any disruption to you or your business.

You'll need:

- 1 (one) adapter ($4)

http://alldav.com/index.php?main_page=prod...;products_id=11

I used this adapter ($13.95, yep expensive):

http://www.sparkfun.com/commerce/product_i...products_id=449

- 1 (one) RS232 cable ($3.78):

http://www.cispc.com/ssproduct.asp?pf_id=10480908

or (buy a RS232 to TTL adapter, or FT232BM/BL, not need both!)

- 1 (one) FT232BM/BL adapter (check below) and USB cable ($12.47):

http://shop.ebay.com/?_from=R40&_trksi...-All-Categories

Any other similar adapter will works fine, just need to be +3.3V DC (+5V will works too, but I recommend 3.0~3.3V). Is possible to find USB to TTL adapters too, they do USB to RS232 internally and then it converts to TTL. For example, some users used a cellular data cable for PC (lots them do RS232 to TTL).

- 1 (one) USB cable ($3.99):

http://www.optimization-world.com/details/prodid/320.html

- 1 (one) kit of Ten 5" Jumpers and 20 Headers ($5):

http://www.hobbyengineering.com/H2362.html

- 1 (one) mini Torx 6 screw driver ($3.29):

https://www.acehardwareoutlet.com/(jv21u13p...spx?SKU=2167237

- Soldering stuff (optional). Use 60W max.

You can buy a complete kit for $7.99 here:

http://www.radioshack.com/product/index.js...rodsInSession=1

The rest:

- 1 (one) computer with Terminal software (like HyperTerminal or similar) and a RS232 or USB port.

- A fixed firmware from Seagate here (Released in 22/01/2009 and 24/01/2009 for all affected drives).

- A little bit of patience and practice.

TX and RX connections from a SATA Seagate 3.5":

Photo with the real drive:

Connect TX and RX ports with RS232 to TLL adapter, you'll need something like jumpers in order to do that, or soldering directly to the PCB board. Connect GND and +5V to PC power supply, or similar. Keep in mind those are direct from Seagate sides, so you'll need to connect in this way:

- From PC (TX) to >>> RX (on Seagate)

- From PC (RX) to >>> TX (on Seagate)

You can use RED wire (+5V) from PC power supply. Blacks are GNDs (yellow is +12V so don't use it).

If you don't want to mess with power supply, just use a CR2032 (3V) battery:

https://www.isaleproducts.com/p-7709-3v-lit...ll-battery.aspx

An idea of whole setup (I used an USB to RS232 too):

Run HyperTerminal (or your favourite terminal software).

Configure the RS232 port to: 38400 8 N 1 (like this one):

Fixing 0 LBA error:

Note: All commands are case sensitive !

To correct 0 LBA error, you'll need to do a quick format in order to regenerate the partition, just with m0,2,2 and the rest can be left blank by putting only commas or filling out with zeros. At the end you need to use a "ValidKey" code, or 22.

Attention: The commands must be used 100% equal as showed here, wrong cmds could lead to data loss or HD loss! Double or triple check the cmd before to press enter!

So we'll have to enter:

F3 T>m0,2,2,0,0,0,0,22 (enter)

For reference: F3 T>m does:

Level T 'm': Rev 0001.0000, Flash, FormatPartition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertifyTrkRewrites],[ValidKey]

Now wait 15~30 seconds until something like this appears (it will vary a bit):

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000

User Partition Format 5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 05 secs

User Partition Format Successful - Elapsed Time 0 mins 05 secs

ONLY after the message like above you can turn off everything.

Fixing BSY or CC errors aka BUSY (I recommend some practice before trying this):

Note: All commands are case sensitive !

First, make sure you have your hard drive accessible; on a table with open access to the drive is best.

Second, you need to remove the PCB (Printed Circuit Board) from HDA case using a Mini Torx 6 screw driver.

Third, connect RX & TX cables from your RS-232 adapter, verify that all is correct, and then connect the power supply to Hard drive circuit board.

Explanation: The problem with the drive is that the drive is stuck/halt in a BUSY state. This basically locks up the SATA port, causing the BIOS problem (cannot detect the drive at POST). In the terminal, you will see this sort of error (LED: 000000CC FAddr: 0024A051). Once you see this in the terminal, the terminal session to the drive is completely blocked and will not accept any more commands. In order to circumvent this, we'll need to disconnect the PCB (circuit board) from the hard drive case so that the LED: 000000CC FAddr: 0024A051 command cannot be sent from the firmware of the terminal session.

After you have connected the power to the circuit board, press CTRL+Z in your HyperTerminal session. You should now see a prompt like this:

F3 T>

If you do not see this prompt, check your RS-232 connections to the drive. (you may have the TX and RX flipped).

Now we'll need to access the Level 2, type:

F3 T>/2 (enter)

F3 2>

And type (to spind down the motor):

F3 2>Z (enter)

Spin Down Complete
Elapsed Time 0.147 msecs (the time will vary here)
F3 2>

Now the tricky part. Pratice a lot without any power before even trying this. You need to make sure that the screws don't touch the PCB board where they aren't suppose to or you will fry your PCB board. If you have been practicing and the power is not connected, start at STEP ONE.

With the POWER CONNECTED to the PCB board, as well as your TX/RX terminal wires, mount the board back on the HDA case. You must have the power connected when you do this.

Now type (to start the motor):

F3 2>U (enter)

You should get something like this:

Spin Up Complete

Elapsed Time 7.093 secs

F3 2>

Then go to Level 1 (by typing /1):

F3 2>/1 (enter)

Now lets do a S.M.A.R.T. erase (create S.M.A.R.T. sector):

F3 1>N1 (enter)

-------------------------------------------------------------------------------------

G-List step is optional:

Skip G-List step first, if after proceeding the whole BSY fix and the drive still remains under BSY error, then you'll need to repeat BSY process with G-List command below.

G-List Erase (Fix Defect List):

F3 1>/T (enter)

F3 T>i4,1,22 (enter)

For reference:

Level T 'i': Rev 0001.0000, Overlay, InitDefectList, i[DefectListSelect],[saveListOpt],[ValidKey]

-------------------------------------------------------------------------------------

Power OFF/ON the drive (very important!)

Wait 10 seconds and now Power ON your drive.

Press CTRL+Z on terminal and type:

Partition regeneration:

F3 T>m0,2,2,,,,,22 (enter)

For reference:

Level T 'm': Rev 0001.0000, Flash, FormatPartition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertifyTrkRewrites],[ValidKey]

You should get something like (in around 15~30 seconds):

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8

User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs

User Partition Format Successful - Elapsed Time 0 mins 05 secs

If you didn't get the msg above, then you skipped something important, and turning off your drive now will render an unreadable drive, so be careful.

ONLY after the message like above you can turn off everything.

A direct guide for BSY error (with photos):

http://www.msfn.org/board/index.php?showto...8807&st=100

Keep in mind I did my best to compile all this information and provide more and better details.

Gradius

Information Added 10 may 2010:

If you have any problem following this guide please read first the Seagate Barracuda 7200.11 READ_ME_FIRST topic!

This post has been promoted to an article

Hello folks,

My old Seagate Barracuda 1000TB ST1000DM000, PN: 9TS15E-570, FW: CC93 died suddenly, as many ill-fated Barracudas from all the world.

I connected the USB-TTL translator and accessed the HDD via Hyperterminal.

At power-up:
 

Rst 0x20M
Servo Processor Is Reset.
RW: Disc Ctlr Initialization Completed.

ExecuteSpinRequest

(P) SATA Reset

And does not react at CTRL+Z!

Removed the power, removed the PCV and mount back with a cardboard over the voice coils contacts, then power up:

Quote

Rst 0x20M
Servo Processor Is Reset.
RW: Disc Ctlr Initialization Completed.

ExecuteSpinRequest

 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
 FAIL Op=0100 Resp=0003
No HOST FIS-ReadyStatusFlags 2002B001

At Ctrl+Z the prompt comes, and I type:

Quote

ASCII Diag mode

F3 T>/2
F3 2>Z

Spin Down Complete
Elapsed Time 0.047 msecs
F3 2>

I removed the cardboard and typed:

Quote

F3 2>/1

F3 1>N1

Init SMART Fail
LED:000000BC FAddr:00004C51
LED:000000BC FAddr:00004C51
LED:000000BC FAddr:00004C51
LED:000000BC FAddr:00004C51
LED:000000BC FAddr:00004C51
LED:000000BC FAddr:00004C51

this error displays endlessly.

Please help me to revive this drive. I searched over this forum and I didn't found any solution related to my drive.

Thank you very much in advance!

Alex.

Later edit: After that endlessly error, I powered down and again up the HDD and I got:

Quote

Rst 0x20M
Servo Processor Is Reset.
RW: Disc Ctlr Initialization Completed.

ExecuteSpinRequest

No HOST FIS-ReadyStatusFlags 0002A1A5

Maybe this is relevant.

Thanks!

Once upon a time in a not-so-far away forum, here:

http://www.msfn.org/board/topic/173265-formatting-an-external-drive-using-different-interfaces/

someone found himself in a "queer" situation with an external hard disk case that provided two connections, a USB one and a e-SATA one.

This specific enclosure worked fine with the disk it originally came with as that was a "real" 512 bytes/sector disk and both interfaces exposed a 512 bytes/sector device.

But, once the disk was changed to a "new" one that is one of the so called "Advanced Format" kind, something strange happened.

The e-SATA interface exposed a 512 bytes/sector device 

The USB interface exposed a 4096 bytes/sector device.

The net result was that the disk was unreadable when connected through the "other" interface.

Provided "solutions" involved one or more of the following:

• buy a new disk
• buy a new enclosure/interface
• give up and buy a new external disk
• buy new PC's and have everything USB3
• ....

Being, besides old and grumpy, also cheap, I proposed instead a "workaround" that after quite a bit of experimenting (thanks to the OP Dave-H) seems like being "good enough" to be useful to other (I hope few) people being affected by the same issue, and that (possibly) may become useful when/if similar issues will present themselves.

Basically the disk is divided into two partitions, the first one being a small FAT12 volume that will always be accessible (both when connected through the 512 bytes/sector interface and when connected through the 4096 bytes/sector one) on which a small batch (and a few needed command line executable used by the batch) resides.

The second partition is a (large or main) NTFS one that can be accessed from the one or the other interface but that needs to be "switched" every time the connection is changed to the "other" interface.

All is needed when you connect the disk is to run the switcher.cmd from the first (FAT) small partition and it will "switch" the second (NTFS) main partition to the appropriate byte/sectors settings.

Though the scope of the thingy is quite "narrow", probably the underlying "principles" may be useful in other situations, we will see. 

The attached is version 0.99 which more or less means that all the various batches which were at various releases like 0.06 , 0.07 or 0.09 mod3, since they seemed to work, were suddenly - after very little and mostly esthetical changes - promoted to 0.99 which should give the impression of "not really final, yet almost there". 

Have fun.

jaclaz

Version0.99.zip

My Samsung Samsung 950 PRO Series - 256GB PCIe NVMe - M.2 Internal SSD (MZ-V5P256BW) drive shows up in "Device Manager" but it doesn't show up in Windows' "Device and Printer" folder, at least on my ASRock Fatal1ty Z170 Professional Gaming i7 motherboard. My secondary Sandisk 1TB SSD drive also doesn't show up there any more either after I installed the Samsung. I wonder if any other users are having this issue and how they fixed it. 

Hello and sorry for bad english language.

I bought pcie usb3 card (https://www.amazon.co.uk/PCIE-USB32-Digitalbox-USB-PCI-adapter/dp/B00BJI0FHA)

and Icy box IB-223U3 enclosure.

The idea was that i could make laptop hdd cloned images faster that through usb2.

BUT... when i put laptop hdd to the icy box and connect box to usb3 card then i only hear fast clicking sound from the hdd.

If i put box to usb2 port, then everything is ok. I have win7 32Bit updated.

It is very strange problem.

Hello to all, my first posting....

I've seen a few discussion on the forums regarding USB flash drive access problems and I have tried to follow various suggestion in them, but unfortunately have failed to reach a successful result at the moment.

Just over a week ago I was working on my computer and managed to successfully save information to my Intergral Neon 32GB USB 3.0 Flash Drive which I have been using successfully up to this point

I didn't use the computer/Flash drive the following day but when I powered up the computer and inserted the Flash drive I got the "You need to format the disk in drive H: before you can use it." " Do you wish to format?"

Obviously I declined and found that my flash drive was now reporting that it was 28.88GB RAW Healthy (Primary Partition).

I have tried several 'recovery' tools but none seem to help me get to the root of my problems.

I have getting on for 3yrs of data on this drive and unfortunately the last backup I have is well over a year out-of-date. That will teach me to back up more often!!

If someone could advise me on the best method to follow which may allow me to recover my flash drive I would be extremely grateful.

Many Thanks

Hi, everybody. 
I repair TV sets, more precisely restoration of screens (matrixes).  
Last week Ihave big problem. - all of the file a storage can died. There all work, data, clients, and backups. 
The body of Seagate Barrakuda ST1000DL002 - 9TT153-301 - CC32 . 
The disk is devided on three sections. C:\ - bootable, with system. Since morning I included a computer, I see - Windows I am loaded, turned away, after a while I look... ... Disk Boot failure. 
When loading writes the name of the connected disk, but in a setapa it doesn't detektitsya, 0 MB detektitsya more precisely.  
I checked a cables,  - 0. By other PC a disk small, but having thought to a cut I decided to try to include the second and to copy important on other disk. By other car - the disk met, and data were available. 
I copied what there was enough place for. I left, I approached after a while, all and on this PC the disk ceased Windows seems. 
I rebooted - disk  no  more activity . 
The sound of the spinning up is perfectly all right.
What was made.  

Kind of failure: Without a previous hint of problem, the drive suddenly ceases to talk to the controller (i. e., it cannot be detected by the BIOS when the machine is starting up). The sound of the spinning up is perfectly all right.

I managed to connect to the disk's serial interface, and this is the diagnostic output it gives upon power-up. Hopefully someone qualified can step up and tell me what it actually is that the ST1000DL002s are choking on.

 I just have removed a PCB and  cleaned it - oxides considerable under pads. After cleaning - the same condition. 
And still - its disk doesn't allow is loaded from other disks therefore MHDD, Victoria it is impossible to load. Or they don't see it. 
In the terminal of sreezny I changed nothing, only tests. 
Here what gives after spinup:

On command V1 gets very big log. T give start and end only...

On V10  too big

On Ctrl+X gets...

Hopefully someone qualified can step up and tell me what it actually is that the ST1000DL002s are choking on.

Wanted to see what the actual top speed of an mSATA SSD in an mSATA USB 3.0 enclosure might be, so went to a retail store with several top of the line laptops.

Tried 5 of the highest priced laptops they had and was surprised that only one was over 400 MB /s.  Even more surprised that 3 where barely over 100 MB / s.  And yes, the SSD was plugged into ports that were clearly marked with the 'SS' for USB 3.0.

Was using Crystal Disk Mark on one partition of the SSD to run tests on another partition of the SSD.

Any ideas for why these top dollar laptops had such poor USB 3.0 performance?

Guess it pays to test before you buy.

Looked thru topics in here but none seemed to contain easy-to-apply solution, so posting.

Just an hour ago one of my relatives deleted 3 rather important files from pendrive. The Device is one of the 2 GB craps they share here and there for advertising purposes, and it's like 8 years old stuff, ~600Mb of free space. Files to recover are measured in kilobytes. 'Deleter' was told to stop using pendrive just after the accident so these should be able to recover.

I looked thru different reviews of free/shardeware/trial/will-install-you-tons-of-crapware recovery programs, downloaded one that seemed to be safe and tried my best. It has shown list of deleted files properly, but recovery returned only garbage files (they were saved to HDD JFYI).

I have DMDE I have downloaded some time ago, but certainly I'm to lame to do the right thing within a reasonable time. Also, pendrive is used for sharing personal data and there is no way I will publicly share it's image.

If someone can recommend some free software that contains no crapware and will do its job, I'll be pleased. Musn't be freeware in fact, 10-minutes trial should be enough.

If this requires more work with low-level tools, I'm willing to cooperate.

Hi.

I recently bought a new mSATA SSD but I found out that the mini PCIE port in my old Acer Aspire one (ao532h) doesn't support mSATA (even though the SSD does fit in it, 'cause mSATA and miniPCIE share the same pins - different voltages, though).

My question is: does an mSATA to mini PCIE Adapter exist? And, if it does exist, is it going to work in my old, crappy, outdated Aspire One (ao532h)?

Thank you in advance.

Reading this topic, page 4 in particular: 

And this:

On 12/5/2013 at 4:46 PM, grancharov said:

NTFS tools - Repair Directory INDX-Records. There is also Recover the Object and Reconstruct File System in the context menu - what I should use? The idea is that I want to spare myself another copy of 1.8 TB in the reverse direction.

I have an old Usb stick, which possibly has already had backups of it done (onto another stick). Using Dmde I can recover a virtual filesystem (Virtual reconstruction).

I would like to write the virtual FS to the drive. The quote above is for Ntfs. The drive I am using is Fat.

Is there a way to "undelete" the files directly?

More info, the (sub)folders are ok, just the root files don't exist (in the virtual filesystem). I don't care. I just want to see the folders (I will have to rename them).

Using old version of DMDE (2.8?), will try v3.0.6.648.

Thanks. 

Hello, I just built a new computer a couple of days ago and have been having a persisting issue. The computer loads my free copy (from university) of Windows 10 Education without problems, then runs 100% fine without any issues. As soon as I shut down the computer, or it loads from sleep mode, I get either operating system not found, error 0xc00000f, or error 0xc0000225. This does not happen after a reset, but only after I shut it down and then power it back on -- and it happens EVERY time the computer is shut down. The only way I have figured out to get it working is to do a fresh install of windows. I have tried bootrec.exe /scanos, and 0 installations of windows are found. I have tried diskpart - list volume - select volume xx -active, and this is where I think you guys can help me. When I type active, it said 'the selected drive is not a fixed MBR disk. The active command can only be used on fixed MbR disks'. Then I noticed my primary volume, as well as a smaller (hidden) 450 mb volume, are listed as RAW under 'fs', instead of fat32 or ntfs. I am now reinstalling Windows once again, and am going to run testdisk (i'm not sure if this is going to help, but i saw people recommending it in this forum). I will show you the results, as well as supply any additional information necessary to fix this annoyance. Thanks in advance for any help.

Edit: I am not going to run testdisk yet, as I am not sure what it can tell you guys as I have already formatted and re-installed windows onto the drive. I can replicate this issue with ease if need be, but unless someone thinks it is helpful I will wait.

My Setup:

i7 - 6700K
Asus z170 s Sabertooth Mobo
16 GB Corsair Vengeance DDR4 Ram @ 3200MHZ (2x8gb)
Mushkin Reactor 1TB SSD
MSI GTX 1080
Corsair RM850X - 850w PSU


 

Hi,

I have a couple of FreeAgent Desk external hard drives with the following drives embedded in them:

1. ST31000528AS (Firmware: CC44)
2.  ST31000333AS (Firmware: SD35)

I saw both have firmware updates available to download from Seagate that are labeled as "important":

1. CC44 => CC49

2. SD35  => SD3B

I tried both EXE and ISO update methods (with the drives still in the FreeAgent enclosure) and both failed (big read FAILURE message in the DOS window).

Can you please verify the following?

1. In order to upgrade the firmware, I'll need to physically detach them from the external enclosures (e.g. like this) and connect them as internal HDDs (via SATA)
2. It is worthwhile to partake in this endeavor, as failing to do so might cause my hard drive to brick one day (especially the SD35 from what I gather)

Thanks!

On impulse this past summer, I bought a WinCleaner dongle at my local dollar store. It looks like a swivel thumb drive.

It claims to support XP through 8.1, so I fearlessly plugged it into my 98se machine hoping to be able to reformat it. It is recognized as an external CD-ROM drive containing a finalized read-only disc.

Discussion here with photos suggests it may be just an 8-pin ROM chip and a USB interface chip. There also appears to be a second 8-pad chip location vacant.

Any ideas for further analysis or repurposing of the hardware? I'm good with a soldering iron!

Today, in my Optiplex 780 Desktop with Win 7 Pro 64-bit and 8GB RAM, I cloned my hard drive from old drive to new drive.  To do that, I went into BIOS (which is the A14 version), went to Drives, enabled SATA2, and plugged the new empty hard drive into the SATA2 socket on the motherboard.  The original drive has always been in the SATA0 socket, and the CD-DVD has always been in the SATA1 socket.

The clone went well (using Macrium Reflect Free in a USB stick).  When I took out the old drive and connected the new cloned drive to the original SATA0 socket, the Optiplex gave me errors on the reboot.  It said it was missing a drive in SATA2 and did i want to Continue, go into System or run Diagnostics.  After a few reboots with that error, I went back into BIOS - Drives and disabled SATA2.  Then reboot went very well without errors, a few times.  All good.

However, those errors aren't right.  I should be able to enable SATA2 in BIOS and not get errors just because no actual drive is plugged into the SATA2 socket on the motherboard.  (That's how it works in a different Dell Optiplex 3010 I have).

So what's going on?  Why am I getting this error?

(By the way, the old drive was a 10-year old Maxtor 500GB, and the new drive is a Seagate Firecuda ST1000DX002.  Do you think the SATA2 socket fell so in love with the Firecuda that it just can't let go?)

Thanks.

  \

  /

Hi everyone! That is my firts time here. I´m computer fan. 
I have a big problem with my seagate hdd (ST31000520AS). It is dead. Bios can´t recognize it. I saw on Windows and no appear driver. I try in other computer and same problem. The hdd noises are normal. It does not have the typical noise when it is a physical problem. What is the problem that you think it might be? Do you have any manual to remove the electronic board of this hdd? Perharps problem is file from e2prom. I don´t know. Please help!! 

I add e2prom and photo of my hdd.

Thanks in advance

W25X40AL_HDD.rar