Saturday, November 30, 2019

How to Check Compatible Heads WD

How to Check Compatible Heads WD


Also to that , i use this old procedure :

DCM: 123456789

1- Motor
2- Base
3- Latch
4- Bottom VCM
5- Media
6- Headstack
7- Actuator-Preamp
8- Top VCM
9- Separator

Works well to me .
WD USB to SATA Conversion Compatible PCB Guide
Cross Compatible WD Families

Cross Compatible WD Families

So I'm starting this sticky to keep track of families which can be used as cross-compatible heads donors if matched correctly.

Here's what I've confirmed so far:
Dolphin & Mercury
Mariner & Marn5 4K
Tahoe 2D & Vulcan RE
Sabre 53 and Sabre 58

Confirmed by Luke:
Shrek and Shrek LT

Confirmed by Amarbir:
Firebird and FBLite

Confirmed by AJ2008 (on Ace forum)
Diablo 3D & Diablo 3S

Confirmed by Blizzard:
Hubble & Hubble LT
Tornado & Pinclite
Helios & Shasta-3D
Venus & McKinley

Confirmed by FreekinGeeks:
Tahoe LT & Tahoe PL

Confirmed by Boerge
Aries & Lynx

Confirmed by abedalkareem
Espirt & Europa

Please add any you know below, and I'll update the list.
SA SPT (aerial density) of WD Families

SA SPT (aerial density) of WD Families






Hey guys, I'm starting this thread to keep track of the aerial density of different families of WD Marvel drives. I think this might turn out to be useful for determining families that might be cross-compatible for heads. Feel free to post below any additional families or if you know of other aerial densities common to any of these families.

2.5" Drives
Aquarius - 666
Orion - 666
Mckinley - 686
Aries - 690
Lynx - 690
Bobcat - 693
Denali - 693
Saturn - 693
Venus - 693
Viking - 768
Everest - 846
Shasta - 867
Mariner5 (not 4K) - 877 (this is specific to the drives with -xxA1Cx code)
Europa - 881 (4 heads) (WD Black)
Jamaica - 885
Pluto - 885
Everest5 - 886
Everest V - 1064
Jamaica 4K - 1074 / 1091
Esprit - 1085 (4 heads) (WD Black)
Mariner 5 4K - 1091
Mariner - 1095 (note some are actually Mariner5 family which are 877 - Same PC3K Util)
Zephyr - 1098
Shasta 3D - 1108
Shasta 2D - 1116
Dolphin - 1178
Mercury - 1178
Inca - 1200
Jamaica 4KV - 1364
Helios - 1364 / 1372 (6 heads)
Firebird - 1420 / 1437 (4 heads)
Hubble - 1420 / 1437 (2 heads)
Shrek - 1437 (8 heads)
Hubble LT - 1437 / 1480 (2 heads)
FBLite - 1437 / 1480 (4 heads)
Shrek LT - 1480 (8 heads)
Big Bear - 1564 (4 heads)
PebbleB - 1782 (10 heads)
Makalu - 1836
Charger - 1860
Palmer - 1944
Spyglass - 2140 (10 heads)


3.5" Drives
Sabre53 - 533
Sabre58 - 533
Hawk - 720
Hawk 2 - 720
Starling - 720
Mammoth - 820
Aztec PL - 825
Sequoia - 840
Tornado - 853
Tornado PATA - 853
Sequoia PMR - 857
Tornado 2D - 857
Tornado 2 PMR - 857
Tornado 2R - 857
Zeus - 864
Buccaneer - 900
Raider - 925
Sumt RE - 1264
Mars - 1275
Hulk - 1280
Spider - 1280
DragonFly4 - 1289 / 1974
Tahoe - 1290
Tahoe LT - 1290
Tahoe XL - 1290
Tahoe 2D - 1296
Vulcan RE - 1296
STG Twin Lakes - 1301
Jupiter - 1302
Atlantis - 1311
Cypress - 1311
Pinclite - 1311
Pinnacle - 1311
Gekko - 1325
Kermit - 1325
TrailXLB - 1575
TresselB - 1578
TresXLB2 - 1578
Trails - 1682
Tressels - 1689
Malibu - 1706
TrailXLS - 1706
TresXLS - 1706
Diablo 3D - 1714
Diablo 3S - 1740
Vivaldi - 1920
Manpl RE - 1945
Manti RE - 1962
DF4PL RE - 1974 (8 heads) (Enterprise)
DragonFly2 - 1974 (4 heads) (WD Green)
DragonFly4 - 1974 (8 heads) (WD Green)
DragonFly1 - 1980 (2 heads) (WD Green)
DragonFly3 - 1980 (6 heads / numbering starts at 2) (WD Green)
Sadle G6 - 1980 (6 heads / heads 2&3 missing in numbering)
Draco - 1988 (8 heads) (WD Green)
Dragon - 1988 (8 heads) (WD Green)
Sadle 2D - 2005 (3 heads - usually missing one from 4 head assembly) (WD Green)
Giant - 2116 (8 heads) (WD Green/Red)
Rembrndt - 2480 (10 heads) (WD Green/Red)
Apollo - 2800 (6 heads) (WD Blue)
Kojin - 2976 (WD Black)
Kojin RE - 3072 (Enterprise)

Tuesday, November 26, 2019

 Case study 15 WD10SDZW-11UMGS0 Data Recovery

















Model : WDC WD10SDZW-11UMGS0
  Serial : WD-WX91A9878FLJ
 Firmware : 01.01A01
 Capacity : 1 000 GB (1 953 459 632)

Symptoms: Customer describes that drive was taking a long time to appear when connected it.  They tried to copy data off, but it disconnected before they were able to finish copying the data.  When they tried subsequent times to connect the drive it would spin up normally, make no clicking sounds, but never mount to the system.








Hard Drive Evaluation

 HEAD BAD 0,1  > 0 IS BAD HEAD 

HEAD SWAP AFTER RECOVERY GOING ON

 

 

Data Recovery 100% RECOVERY

 

 

 

 

 

RamInfotech Data Recovery

 

No 24/13, Ground Floor, Pillayar Koil St,

near R8Police Station,

Vadapalani

Chennai, Tamil Nadu 600026 

Phone: 070921 14422

 

http://www.datarecoverychennai.co.in/  

 

Thursday, October 24, 2019

SIM ERROR 1009 RW ERROR 00000080 (17a sys. file)




SIM ERROR 1009 RW ERROR 00000080 (17a sys. file)

Monday, October 21, 2019

   Case study 14-  ST1000LX015-1U7172-SSHD   Serial : WDEGGS2K Firmware : SHM2 Capacity : 1 000 GB (1 953 525 168)
 






Model : ST1000LX015-1U7172-SSHD
  Serial : WDEGGS2K
Firmware : SHM2

Capacity : 1 000 GB (1 953 525 168)











 Case study 13  -Model : ST2000LM007-1R8174

  





 Model : ST2000LM007-1R8174
Serial : WDZM0RRK
Firmware : EB01
Capacity : 2 TB (3 907 029 168)







THIS ROM UNLOCK DATA RECOVERY JOB DONE 








Tuesday, October 15, 2019

Case study 12 -HDD. Seagate F3. How to fix SIM Error 1009 RW Error 00000080 on Sentosa family



HDD. Seagate F3. How to fix SIM Error 1009 RW Error 00000080 on Sentosa family

 

Hello Friends,
Some family of Seagate F3 drives has specific issue which you wil not see on other families. One of these issues we would like to show today.


Sentosa family is common disk in our technical support department. Drives of this family can have standard problems of Seagate F3 architecture, such as background processes, translator, overfilled G-list.
But there is unique problem of Sentosa family.
When you open the drive in utility you can see following picture:

Drive shows correct ID, capacity, ready state, but doesn’t allow to read sectors.
We would like you to pay attention to messages in terminal:
SIM Error 1009
RW Error 00000080
It means that drive has problem with S.M.A.R.T partially with system file 0x017A
Let check it terminal

This terminal output means that system file 17A is damaged.
Try to read it

We get error when try to read system file

Write 17A sys file (you can take it from the link provided at the bottom of the article)

File is written and now check the terminal output after power off/on
Drive comes to ready state and doesn’t send error messages in terminal.

Try to read first and last sectors of user data.

All data is available and we can save it.
And link for a good 17A system file





Police Station, No 24/13, Ground Floor, Pillayar Koil St, 
Near R8, Vadapalani, Chennai, Tamil Nadu 600026


http://www.datarecoverychennai.co.in/ 

Thursday, October 10, 2019

Automatic Windows Device Encryption / BitLocker on Dell Systems



Automatic Windows Device Encryption / BitLocker on Dell Systems


Windows Device Encryption / Bitlocker

Windows device encryption is a security feature in Microsoft Windows that helps protect your data by encrypting the system drive. If device encryption is enabled, only authorized individuals will be able to access your device and data.

System Requirements

Devices that support encryption meet multiple hardware and software requirements External Link:
You can check Windows System Information to see if the system supports device encryption: Type System Information into the search box on the taskbar. In the results list, right-click on System Information and select Run as administrator. Scroll down to Device Encryption Support. If the system supports device encryption it will show Meets prerequisites.
Windows 10 Device Encryption Table

Automatic Device Encryption

Automatic device encryption allows Windows to encrypt the system drive automatically after you completed the setup of your system. This occurs very similar to smartphones and is completely seamless for the user. Automatic device encryption however is only enabled on systems that meet above system requirements and support Connected Standby or Modern Standby specifications External Link, which require solid-state storage (SSD or eMMC) and non-removable (soldered) RAM.
Automatic device encryption only starts after the Out-Of-Box Experience (OOBE) is completed and a Microsoft Account (MSA) is used on the system (e.g. use MSA for Windows logon, add MSA as email, app and work/school account, log into the Microsoft Store app with MSA, redeem/activate Microsoft Office or other Microsoft applications with MSA).
Note: Dell devices are not encrypted when shipped from the factory.

Manual Device Encryption

Windows Device Encryption/BitLocker can also be enabled manually:
Click on the Start button, select Settings > Update & Security > Device Encryption. If device encryption is turned off, click select Turn on.
You will be prompted to back-up your recovery key. Dell recommends saving the recovery key to USB drive and not to the system drive.
If Device Encryption is not shown the system may not meet device encryption requirements. Verify the System Requirements are met.

Preparing a Device for Service

Device encryption should be suspended before the system is serviced either onsite or returned to a service center. The device encryption must also be suspended prior to flashing the system BIOS and when a motherboard or system drive replacement is expected.

Suspending / Pausing Device Encryption

Windows 10 HomeWindows 10 Pro
Right-click the Start button, and select Windows
PowerShell (Admin)
Select Control Panel > System and Security > BitLocker Drive Encryption
Type manage-bde -protectors -disable C:Select Suspend Protection on drive C
Windows Command PromptWindows BitLocker

Difference Between Suspending and Disabling Encryption

Suspension provides a quick option to temporarily disable the protection on the system drive for servicing. The process only takes a few seconds to complete and ensures that the drive content is still protected from unauthorized access yet allows system repair/maintenance to take place.
Decryption permanently removes the protection and makes the content accessible to anybody who can access the drive. Additionally, decrypting a drive is time consuming: Microsoft estimates that it takes approximately 1 minute per 500 MB of drive space. The device decryption should only be used prior to restoring a Windows image.

Recovery Key

Some servicing scenarios will require a recovery key to regain access to Windows after the repair was finished.
The recovery key is automatically saved to your Microsoft Account (MSA) when the device is encrypted and can be retrieved from https://account.microsoft.com/devices/recoverykey External Link. It is good practice to verify the recovery key is listed in your account before servicing the system.
Bitlocker Recovery Key Screen
If you don’t see your device listed, check if Device Encryption is enabled on the device, and refer to: Find my BitLocker recovery key External Link
Additional information:

Identifying Device Encryption Status

There are several options to verify the device encryption status in Microsoft Windows:
  • Select the Start button, then select Settings > Update & Security > Device encryption
  • Open a Windows PowerShell or Command prompt: Right-click the Start button select Windows PowerShell (Admin) or Command Prompt (Admin). Type manage-bde -status C:
  • Event viewer: Expand Windows Logs and select System. Look for Event ID 24660 Source: BitLocker Driver
Additional information are available on Microsoft’s support portal External Link

How to Decrypt a Drive Before Restoring Factory Image

There is no hardware fault with the system and this error is the normal result of attempting an image restore on an encrypted drive.
The error can be easily resolved by disabling Microsoft BitLocker before attempting to restore the factory image.
  1. Type "BitLocker" in the search panel next to the Start menu icon. Then click on "Manage BitLocker". (See Figure 1.)
    Windows 10 Start Menu
    Figure 1. - Access BitLocker
  2. You will see the following screen. Click on "Turn off BitLocker". (See Figure 2.)
    BitLocker Screen
    Figure 2. - BitLocker Drive Encryption Turn Off Button.
  3. You will be prompted again at the following screen. Click on "Turn off BitLocker". (See Figure 3.)
    BitLocker Turn Off Prompt
    Figure 3. - Turn off BitLocker.
  4. You will see the following screen. (See Figure 4.)
    Windows 10 BitLocker Screen
    Figure 4. - BitLocker decryption is in progress.
  5. You must wait for the decryption process to finish. You can check the progress by clicking on the notification. (See Figure 5.)
    BitLocker Drive Decrypting Status
    Figure 5. - BitLocker decrypting
  6. When the decryption process is complete, you will see the following message. (See Figure 6.)
    BitLocker Drive Decryption Complete
    Figure 6. - Decryption of the drive is now complete
  7. You may now re-boot to the Windows Recovery Environment and proceed with restoring the Dell Factory Image.
    Note: To re-boot to the Windows Recovery Environment, press and hold down the "Shift" key while clicking on "Restart".
  8. If you wish to re-enable Microsoft BitLocker after restoring the Factory Image, simply follow steps 1 and 2 above and click on "Turn on BitLocker" in the following screen. (See Figure 7.)
    Windows 10 BitLocker Manager Screen
    Figure 7. - Re-enable BitLocker
If you are not able to enter Windows to deycrypt the drive, a Windows Reinstall will need to take place.