我們都知道，新的西數(shù)2.5硬盤在其FW上有一些差異，所以常見的解決方案對于這些硬盤不起作用。在本文中，由于特殊的SED問題，當(dāng)硬盤無法讀取自己的服務(wù)區(qū)時，我們將學(xué)習(xí)如何繞過錯誤對該類故障進(jìn)行硬盤數(shù)據(jù)恢復(fù)。
We all know that new Western Digital 2,5″ drives have some differences in their FW, so the common solutions don’t work for these drives. ?In this article we will learn how to bypass the error when the drive can’t read?it’s own Service Area due to a special SED issue.

很多客戶每天都問我們：如果驅(qū)動器被SED鎖定，如何獲得服務(wù)區(qū)訪問？通?？梢园凑毡臼謨越鉀Q這個問題。
A lot of customers asking us every day: how to get the Service Area access if the drive is SED locked? Usually such problem can be resolved by following this manual.

但是新的2,5“WD USB驅(qū)動器具有不同的FW。
But the new 2,5″ WD USB drives have the different FW.

我們的驅(qū)動器最初是USB，所以我們首先找到兼容的SATA PCB。故障盤的ROM從USB移動到SATA PCB后，驅(qū)動開始讀取ID和訪問用戶區(qū)域，但由于這個原因，緩慢響應(yīng)問題，讀取非常不穩(wěn)定。
Our drive was USB initially, so we found the compatible SATA PCB first. After the patient ROM moving from the USB to SATA PCB, the drive started with ID and User Area access, but had the Slow Responding problem and read very unstable due to this.

我們演示:
We performed:

• 隔離磁頭以獲得內(nèi)核模式下的ROM訪問，
• isolate the heads to get the ROM access in Kernel mode,
• 阻止模塊30訪問使用ROM菜單，
• block the module 30 access in Work with ROM menu,
• 關(guān)閉驅(qū)動器電源，
• power off the drive,
• 去除隔離，
• remove the isolation,
• 再次啟動驅(qū)動器，但是當(dāng)我們嘗試將Dir和加載程序從SA加載到RAM中時，我們得到了下面錯誤：
• start the drive again, but when we trying to load the Dir and loader from SA into the RAM, we have got the next error:

如果我們看到這個錯誤，那意味著驅(qū)動器不能訪問SA。
If we see this error, it means that the drive can’t see it’s SA.

我們必須使用備份的固件來進(jìn)行。尋找與同一個家庭和ROM FW版本的固件：
We must use the donor backup to proceed. Look for a donor with the same family and ?ROM FW version:

我們很幸運(yùn)，從一個地方找到：
We were lucky, found and downloaded the resources we need from one well-known web-site:

在下一步中，我們將從我們剛剛找到的固件中的?Dir和loader加載到故障驅(qū)動器上，：
In the next step we load the Dir and loader not from the patient drive, but from the folder we just downloaded:

并在正常模式下重新啟動該實用程序。
and restart the utility in Normal mode.

我們可以看到，驅(qū)動器可以訪問完整的SA，我們可以根據(jù)需要編輯服務(wù)區(qū)模塊。所以我們做SA備份，解決慢速響應(yīng)，然后去編輯硬盤ID刪除SED復(fù)選框：
As we can see, the drive starts with full SA access, and we can edit the Service Area modules as we need. So we make the SA backup, solve the Slow Responding and go to Edit HDD ID to remove the SED checkbox:

在此步驟之后，我們返回模塊30訪問ROM，重新啟動驅(qū)動器并重新啟動實用程序。驅(qū)動器以完整的ID和LBA訪問開始。但數(shù)據(jù)看起來加密
After this step we return the module 30 access in ROM, repower the drive and restart the utility. The drive starts with full ID and LBA access. But the data looks encrypted

而PC-3000找不到解密密鑰：
and the PC-3000 can not find?the decryption key:

這樣的SED驅(qū)動器是正常的，我們必須返回SED復(fù)選框并重新啟動驅(qū)動器。但是，如果我們嘗試在Data Extractor中構(gòu)建頭映射映射，那么我們會看到DE中的錯誤：
It is normal for such SED drives, we must return the SED checkbox back and restart the drive. But if we try to build the head map map in Data Extractor, we see the error in DE:

所以，在我們返回SED復(fù)選框之前，為了解密數(shù)據(jù)，我們必須在 Data Extractor中建立磁頭位圖，在HDD ID中禁用SED復(fù)選框，因為如果我們現(xiàn)在不建立位圖，則DE不會構(gòu)建它啟用S??ED。
So, before we return the SED checkbox back in order to decrypt the data, we must build the head map in Data Extractor with disabled SED checkbox in HDD ID, because if we don’t build the map now, the DE would not build it with SED enabled.

所以我們在DE中創(chuàng)建了新的任務(wù)，在DE中用禁用的SED構(gòu)建了磁頭位圖，并且去Marvell實用程序來保持任務(wù)的打開。
So we created the new task in DE, built the head map in DE with disabled SED, and go to Marvell utility keeping the task opened.

在Marvell實用程序中，再次選擇“編輯HDD ID”，并啟用SED，然后重新啟動驅(qū)動器。它在PC-3000中沒有SA訪問啟動，但數(shù)據(jù)看起來是解密的：
In Marvell utility we select the Edit HDD ID again and enable the SED back, and restart the drive. It starts without SA access in PC-3000, but the data looks decrypted:

現(xiàn)在我們?nèi)ハ惹按蜷_的DE任務(wù)，并獲得對用戶數(shù)據(jù)的完整訪問（如有必要，使用頭映射）。
Now we go to previously opened DE task, and get the full access to user data (using the head map if necessary).

轉(zhuǎn)載請注明：成都千喜數(shù)據(jù)恢復(fù)中心 » PC-3000 for HDD. 如何處理西數(shù)2.5″硬盤的”VSC ERR INV FUNC CODE REQ”錯誤