我在亞馬遜上買了一台 WD HD，因為我想要一台和我用過的另一台一模一樣的。
我對高清無能為力。
該驅動器肯定是/dev/sdb，但它也掛載/dev/sr0
~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 698.7G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
├─sda2 8:2 0 900M 0 part
├─sda3 8:3 0 128M 0 part
├─sda4 8:4 0 343.1G 0 part
├─sda5 8:5 0 314.4G 0 part /
├─sda6 8:6 0 19.5G 0 part [SWAP]
├─sda7 8:7 0 350M 0 part
└─sda8 8:8 0 20G 0 part
sdb 8:16 0 2.7T 0 disk
sr0 11:0 1 30M 0 rom
軟碟
嘗試在任一裝置（分割區？）上使用 fdisk 都會出現相同的錯誤
$ sudo fdisk /dev/sdb
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
fdisk: cannot open /dev/sdb: Input/output error
DD
甚至dd不會向設備寫入零
$ sudo dd if=/dev/zero count=1 of=/dev/sdb
dd: writing to '/dev/sdb': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0011181 s, 0.0 kB/s
$ sudo dd if=/dev/zero count=1 of=/dev/sr0
dd: failed to open '/dev/sr0': Read-only file system
wifs 和 cfdisk
我嘗試使用wipefs和cfdisk，但沒有成功：
$ sudo cfdisk /dev/sdb
cfdisk: cannot open /dev/sdb: Input/output error
$ sudo cfdisk /dev/sr0
cfdisk: cannot open /dev/sr0: Read-only file system
$ sudo wipefs /dev/sr0
offset type
----------------------------------------------------------------
0x0 mac [partition table]
0x8001 udf [filesystem]
LABEL: WD Unlocker
UUID: 50EB4C87
$ sudo wipefs -a /dev/sr0
wipefs: error: /dev/sr0: probing initialization failed: Device or resource busy
$ sudo wipefs -a /dev/sr0
wipefs: error: /dev/sr0: probing initialization failed: Device or resource busy
$ sudo wipefs --all -f /dev/sr0
wipefs: error: /dev/sr0: probing initialization failed: Read-only file system
g磁碟
我嘗試使用 gdisk，我認為它表明磁碟正在使用 v 命令。
$ sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.1
Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): v
No problems found. 732558325 free sectors (2.7 TiB) available in 1
segments, the largest of which is 732558325 (2.7 TiB) in size.
Command (? for help): d
No partitions
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): Y
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sdb.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
我重新啟動後發現沒有什麼不同，所以我在另一台裝置上嘗試了 gdisk。
$ sudo gdisk /dev/sr0
GPT fdisk (gdisk) version 1.0.1
NOTE: Write test failed with error number 30. It will be impossible to save
changes to this disk's partition table!
Partition table scan:
MBR: not present
BSD: not present
APM: present
GPT: not present
*******************************************************************
This disk appears to contain an Apple-format (APM) partition table!
It will be destroyed if you continue!
*******************************************************************
Creating new GPT entries.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): Y
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): U
Your option? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sr0.
Unable to open device '/dev/sr0' for writing! Errno is 30! Aborting write!
Command (? for help): v
No problems found. 15341 free sectors (30.0 MiB) available in 1
segments, the largest of which is 15341 (30.0 MiB) in size.
嘗試使用 WD-Decrypte 進行長期密碼重設
我還嘗試使用我認為可以重置密碼的工具（如果有的話）。 https://github.com/SofianeHamlaoui/WD-Decrypte
我沒有克隆存儲庫，我只是複製了 python 腳本並運行以下命令：
$ vi cookpw.py ## copy paste from the github repo
$ chmod u+x cookpw.py
$ ./cookpw.py passwd >password.bin
$ sg_raw -s 40 -i password.bin /dev/sdb c1 e1 00 00 00 00 00 00 28 00
/dev/sdb: Permission denied
$ sudo sg_raw -s 40 -i password.bin /dev/sdb c1 e1 00 00 00 00 00 00 28 00
SCSI Status: Check Condition
Sense Information:
Fixed format, current; Sense key: Illegal Request
Additional sense: Authentication failed
$ stat password.bin
File: 'password.bin'
Size: 40 Blocks: 8 IO Block: 4096 regular file
Device: 805h/2053d Inode: 15205314 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1001/ xxxx) Gid: ( 1002/ gene)
Access: 2020-08-14 01:03:29.395345709 -0500
Modify: 2020-08-14 01:02:38.939618244 -0500
Change: 2020-08-14 01:02:38.939618244 -0500
Birth: -
$ sudo sg_raw -s 40 -i password.bin /dev/sdb c1 e1 00 00 00 00 00 00 28 00
SCSI Status: Check Condition
Sense Information:
Fixed format, current; Sense key: Not Ready
Additional sense: Logical unit is in process of becoming ready
$ sudo sg_raw -s 40 -i password.bin /dev/sdb c1 e1 00 00 00 00 00 00 28 00
SCSI Status: Check Condition
Sense Information:
Fixed format, current; Sense key: Illegal Request
Additional sense: Authentication failed
硬碟型號
這是我訂購的硬碟：
WD My Book 3TB 外接硬碟儲存 USB 3.0 檔案備份與存儲
型號：WDBACW0030HBK-NESN
Windows 和 Linux 中的檔案結構和 GUI 磁碟管理工具
當我將其載入到磁碟管理器（Windows 或 Ubuntu）中時，所有有用的內容都呈現灰色。我無法檢查智慧型狀態、格式、沒有磁碟機號碼。
該驅動器確實出現在Linux文件瀏覽器中，我可以看到一些預設文件，並將它們複製出來。
$ tree /media/gene/WD\ Unlocker/
/media/gene/WD Unlocker/
├── autorun.inf
├── Extras
│ └── VCDVersion.xml
├── Unlock.exe
├── WD Quick Formatter.exe
└── WD SmartWare
├── Locale
│ ├── cs_CZ.lproj
│ │ ├── CSS
│ │ │ └── WDSmartWareHelp.css
│ │ ├── EULA.html
│ │ ├── EX_UNLK0.html
│ │ ├── EX_UNLK1B.html
│ │ ├── EX_UNLK1.html
│ │ ├── EX_UNLK3.html
│ │ ├── localizable.strings
│ │ ├── UNLK2.html
│ │ └── VCDF.html
│ ├── de_DE.lproj
... (lots of languages)...
│ │ └── VCDF.html
│ └── zh_TW.lproj
│ ├── CSS
│ │ └── WDSmartWareHelp.css
│ ├── EULA.html
│ ├── EX_UNLK0.html
│ ├── EX_UNLK1B.html
│ ├── EX_UNLK1.html
│ ├── EX_UNLK3.html
│ ├── localizable.strings
│ ├── UNLK2.html
│ └── VCDF.html
└── SmartWare_CD.ico
結論
我以為這很容易格式化，但我已經無能為力了。有任何想法嗎？
2020 年 8 月 14 日編輯：
我添加了一些標題和標點符號，以使問題更易於導航，並添加以下文件：
DMSG 輸出
編輯：下面未過濾的 DMSG
當我昨晚檢查 dmsg 時，我認為「回調被抑制」的數字更高；在50年代。我不知道 dmsg 中的任何內容意味著什麼，但是回調部分看起來很奇怪，所以我用谷歌搜尋了它（仍然不知道它意味著什麼）。
$ dmesg | grep -i scsi
[ 0.304565] SCSI subsystem initialized
[ 1.212532] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 1.414640] scsi host0: ahci
[ 1.414791] scsi host1: ahci
[ 1.414941] scsi host2: ahci
[ 1.415069] scsi host3: ahci
[ 1.764038] scsi 0:0:0:0: Direct-Access ATA TOSHIBA MQ01ABD0 2J PQ: 0 ANSI: 5
[ 1.764616] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.877339] sd 0:0:0:0: [sda] Attached SCSI disk
[ 133.590618] scsi host4: usb-storage 2-2:1.0
[ 134.589496] scsi 4:0:0:0: Direct-Access WD My Book 1170 1042 PQ: 0 ANSI: 6
[ 134.590008] scsi 4:0:0:1: CD-ROM WD Virtual CD 1170 1042 PQ: 0 ANSI: 6
[ 134.591206] scsi 4:0:0:2: Enclosure WD SES Device 1042 PQ: 0 ANSI: 6
[ 134.592861] sd 4:0:0:0: Attached scsi generic sg1 type 0
[ 134.594305] sr 4:0:0:1: [sr0] scsi3-mmc drive: 51x/51x caddy
[ 134.594664] sr 4:0:0:1: Attached scsi CD-ROM sr0
[ 134.594971] sr 4:0:0:1: Attached scsi generic sg2 type 5
[ 134.595493] scsi 4:0:0:2: Attached scsi generic sg3 type 13
[ 141.554025] scsi 4:0:0:2: Wrong diagnostic page; asked for 1 got 0
[ 141.554033] scsi 4:0:0:2: Failed to get diagnostic page 0xffffffea
[ 141.554038] scsi 4:0:0:2: Failed to bind enclosure -19
[ 143.664433] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 232.696987] scsi_io_completion: 6 callbacks suppressed
[ 347.602357] scsi_io_completion: 8 callbacks suppressed
[ 363.163922] scsi_io_completion: 7 callbacks suppressed
[ 668.971338] scsi_io_completion: 8 callbacks suppressed
智慧監控
在 /dev/sdb 上使用 smartctl 不起作用，我需要新增 -d 選項。
然而，這很有趣：
$ sudo smartctl -a -T verypermissive /dev/sdb
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-184-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x1058:0x1170 (0x1042)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
我覺得我以前見過這個 USB 橋錯誤，但我確實切換了電纜，以防這是物理電纜問題（事實並非如此）。
經過一番研究後，我添加了 -d scsi 選項，得到了以下結果：
$ sudo smartctl -a -d scsi -T verypermissive /dev/sdb
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-184-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WD
Product: My Book 1170
Revision: 1042
Compliance: SPC-4
User Capacity: 3,000,558,944,256 bytes [3.00 TB]
Logical block size: 4096 bytes
Form Factor: 3.5 inches
Serial number: WCC1T0867040
Device type: disk
Local Time is: Fri Aug 14 09:19:09 2020 CDT
device Test Unit Ready [unknown error (unexpected sense key)]
SMART support is: Unavailable - device lacks SMART capability.
=== START OF READ SMART DATA SECTION ===
Error Counter logging not supported
No self-tests have been logged
/dev/sr0 上的 smartctl 指令不需要 scsi 規範，誰知道為什麼？
$ sudo smartctl -a -T verypermissive /dev/sr0
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-184-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WD
Product: Virtual CD 1170
Revision: 1042
Compliance: SPC-4
User Capacity: 31,457,280 bytes [31.4 MB]
Logical block size: 2048 bytes
Serial number: WCC1T0867040
Device type: CD/DVD
Local Time is: Fri Aug 14 09:19:36 2020 CDT
SMART support is: Unavailable - device lacks SMART capability.
=== START OF READ SMART DATA SECTION ===
Error Counter logging not supported
Device does not support Self Test logging
我認為這些結果表明磁碟存在，但沒有日誌記錄？我需要打開 smartctl 嗎？
我在文檔中註意到了這一點：
smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda
Enable SMART on drive /dev/sda, enable automatic offline testing every four hours, and enable autosaving of SMART Attributes. This is a good start-up line for your system´s init files. You can
issue this command on a running system.
只讀 - hdparm 和實體驅動器
我忘記提到我做的第一件事就是發出這些命令：
$ sudo hdparm -r0 /dev/sdb
/dev/sdb:
setting readonly to 0 (off)
readonly = 0 (off)
$ sudo hdparm -r0 /dev/sr0
/dev/sr0:
setting readonly to 0 (off)
readonly = 0 (off)
這對解決只讀狀態沒有任何作用。
此外，硬碟上的任何位置都沒有鎖定開關，自從收到驅動器以來，我在過去幾週內多次按下電源按鈕。
編輯 2020年8月14日 (2)
重新連接硬碟後，這些是我的消息：
[29847.050551] usb 2-2: USB disconnect, device number 2
[29851.566835] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
[29851.583422] usb 2-2: New USB device found, idVendor=1058, idProduct=1170
[29851.583426] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[29851.583430] usb 2-2: Product: My Book 1170
[29851.583433] usb 2-2: Manufacturer: Western Digital
[29851.583435] usb 2-2: SerialNumber: 574343315430383637303430
[29851.584159] usb-storage 2-2:1.0: USB Mass Storage device detected
[29851.584269] scsi host5: usb-storage 2-2:1.0
[29852.583294] scsi 5:0:0:0: Direct-Access WD My Book 1170 1042 PQ: 0 ANSI: 6
[29852.583557] scsi 5:0:0:1: CD-ROM WD Virtual CD 1170 1042 PQ: 0 ANSI: 6
[29852.584436] scsi 5:0:0:2: Enclosure WD SES Device 1042 PQ: 0 ANSI: 6
[29852.586165] sd 5:0:0:0: Attached scsi generic sg1 type 0
[29852.587224] sd 5:0:0:0: [sdb] Spinning up disk...
[29852.587638] sr 5:0:0:1: [sr0] scsi3-mmc drive: 51x/51x caddy
[29852.589827] sr 5:0:0:1: Attached scsi CD-ROM sr0
[29852.590297] sr 5:0:0:1: Attached scsi generic sg2 type 5
[29852.592576] ses 5:0:0:2: Attached Enclosure device
[29852.592932] ses 5:0:0:2: Attached scsi generic sg3 type 13
[29852.593612] ses 5:0:0:2: Wrong diagnostic page; asked for 1 got 0
[29852.593627] ses 5:0:0:2: Failed to get diagnostic page 0xffffffea
[29852.593638] ses 5:0:0:2: Failed to bind enclosure -19
[29853.590968] ..not responding...
[29861.407668] sd 5:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.73 TiB)
[29861.429631] sd 5:0:0:0: [sdb] Write Protect is off
[29861.429639] sd 5:0:0:0: [sdb] Mode Sense: 53 00 10 08
[29861.447321] sd 5:0:0:0: [sdb] No Caching mode page found
[29861.447326] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[29861.507569] sd 5:0:0:0: [sdb] Unit Not Ready
[29861.507576] sd 5:0:0:0: [sdb] Sense Key : Data Protect [current]
[29861.507581] sd 5:0:0:0: [sdb] Add. Sense: Logical unit access not authorized
[29861.596816] scsi_io_completion: 7 callbacks suppressed
[29861.596824] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.596828] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.596833] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.596837] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.596840] blk_update_request: 7 callbacks suppressed
[29861.596842] blk_update_request: critical target error, dev sdb, sector 0
[29861.596845] buffer_io_error: 4 callbacks suppressed
[29861.596848] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.618633] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.618639] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.618644] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.618648] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.618651] blk_update_request: critical target error, dev sdb, sector 0
[29861.618654] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.632833] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.632839] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.632844] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.632848] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.632851] blk_update_request: critical target error, dev sdb, sector 0
[29861.632854] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.632872] ldm_validate_partition_table(): Disk read failed.
[29861.651594] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.651599] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.651604] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.651608] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.651610] blk_update_request: critical target error, dev sdb, sector 0
[29861.651613] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.673907] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.673914] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.673919] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.673924] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.673927] blk_update_request: critical target error, dev sdb, sector 0
[29861.673931] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.695989] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.695995] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.696000] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.696004] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.696007] blk_update_request: critical target error, dev sdb, sector 0
[29861.696010] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.715645] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.715653] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.715658] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.715662] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.715665] blk_update_request: critical target error, dev sdb, sector 0
[29861.715668] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.715697] Dev sdb: unable to read RDB block 0
[29861.735908] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.735914] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.735919] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.735923] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.735926] blk_update_request: critical target error, dev sdb, sector 0
[29861.735929] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.736644] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.736649] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.736653] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.736657] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 03 00 00 01 00
[29861.736660] blk_update_request: critical target error, dev sdb, sector 24
[29861.736662] Buffer I/O error on dev sdb, logical block 3, async page read
[29861.737092] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[29861.737096] sd 5:0:0:0: [sdb] tag#0 Sense Key : Data Protect [current]
[29861.737100] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Logical unit access not authorized
[29861.737104] sd 5:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
[29861.737107] blk_update_request: critical target error, dev sdb, sector 0
[29861.737109] Buffer I/O error on dev sdb, logical block 0, async page read
[29861.737478] sdb: unable to read partition table
[29861.738776] sd 5:0:0:0: [sdb] Unit Not Ready
[29861.738787] sd 5:0:0:0: [sdb] Sense Key : Data Protect [current]
[29861.738793] sd 5:0:0:0: [sdb] Add. Sense: Logical unit access not authorized
[29861.739986] sd 5:0:0:0: [sdb] Attached SCSI disk
我不確定這些是什麼意思，但我看到很多錯誤訊息和一些表明我未經授權的資訊。
結論編輯：2020 年 8 月 14 日
在聽了下面的一些建議（@paul-pedant）後，我採取了使用 WD 專有軟體重新格式化的非常不滿意的路線。令人難以置信的是，這些低階實用程式都不能簡單地格式化磁碟機。
答案1
我認為它是寫入保護的，因為外部硬碟通常具有此功能，“SR0”可能是帶有該硬碟軟體的 OEM 分區。我建議在 Windows 電腦上下載/安裝 WD 專有軟體，看看它是否可以為您提供任何有用的東西。如果我猜對了，它是用過的驅動器，所以以前的所有者可能已經鎖定了驅動器或類似的驅動器。
答案2
無論如何，這都是一個死磁碟。原始所有者已以某種方式鎖定了它，因此它不再是一個工作或有用的設備。
推薦？不要再浪費時間了，而是將其退還給寄件者並索回您的付款。
答案3
注意：寫入測試失敗，錯誤編號為 30
吞噬者的答案很有可能。 as errno 30 = 只讀檔案系統。
但這可能還不夠，取決於您的核心/fdisk 版本？
您的 HD 似乎是 4K 邏輯/4K 實體磁區大小。
相當舊的 linux 和 fdisk (*) 不支援 4K 邏輯磁碟。
=> 在這樣的系統下，你必須得到？啟用 ？一些韌體可以讓該裝置將這些 4K 磁區公開為 8 個連續的 512B 邏輯磁區。
(*) 無法準確判斷，但至少 Read-hat / CentOS 5、fdisk- 2.17 沒有。