无法在工作的外部Western硬盘上使用dd、smartmon、fdisk或任何东西
无法在工作的外部Western硬盘上使用dd、smartmon、fdisk或任何东西
提问于 2020-08-14 07:16:44
我在亚马逊上买了一台WD HD，因为我想要一个和我用的一模一样的。
我不能用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
尝试在任何一个设备(分区？)上使用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 errordd
即使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 systemwipefs和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 systemgdisk
我尝试使用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硬盘模型
这是我订购的硬盘：
WDMyBook3TB外部硬盘存储USB3.0文件备份和存储
型号: WDBACW0030HBK-NESN
Windows和Linux中的
文件结构和图形用户界面磁盘管理工具当我在磁盘管理器(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输出
EDIT：下面未过滤的DMSG
当我昨晚查看dmsg时，我认为“回调被抑制”的数字更高；在50's中，我不知道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我认为这些结果表明磁盘是存在的，但是没有日志记录吗？我需要打开智能turn吗？
我在文档中注意到了这一点：
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.只读和物理驱动器
我没有提到我所做的第一件事就是发出以下命令：
$ 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日
在听取了下面的一些建议(@pedant)之后，我选择了一条非常不令人满意的路线，使用WD的专有软件重新格式化。令人难以置信的是，这些低级别的实用程序都不能简单地格式化驱动器。
回答 3
Unix & Linux用户
发布于 2020-08-14 07:39:19
我认为它是写保护的，因为外部硬盘通常有这个功能，'SR0‘很可能是OEM分区与这个硬盘的软件。我建议在windows机器上下载/安装WDs专有软件，看看它是否能为您提供任何有用的东西。如果我正确的话，它是使用驱动器，所以以前的所有者可以锁定驱动器或类似的。
Unix & Linux用户
发布于 2020-08-14 16:04:25
对于所有的意图和目的，这是一个死气沉沉的磁盘。原来的所有者已经以某种方式锁定了它，因此它不再是一个工作或有用的设备。
推荐信？不要浪费更多的时间在它上，而是把它退还给寄件人，并要求你的付款。
Unix & Linux用户
发布于 2020-08-14 07:55:01
注意:写测试失败，错误号为30。
使吞食者的回答极有可能。作为errno 30 =只读文件系统。
但是，根据内核/ fdisk版本的不同，这还不够吗？
您的HD似乎是一个4K逻辑/ 4K物理扇区大小。
相当旧的linux & fdisk (*)不支持4K逻辑磁盘。
=>在这样的系统下，你必须得到？激活？有些固件要求该设备将这些4K扇区公开为8个连续512 B逻辑扇区。
(*)不能准确判断，但至少读-帽子/ CentOS 5，fdisk- 2.17没有。
页面原文内容由Unix & Linux提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://unix.stackexchange.com/questions/604453
复制相关文章
相似问题
腾讯云开发者
