☰

ddrescue：未对齐读取错误。扇区大小是否正确？

tag-icon • tag-icon data-recovery ddrescue gdisk
ddrescue：未对齐读取错误。扇区大小是否正确？

我正在尝试使用 GNUddrescue从故障 SSD 中恢复原始数据。系统是Debian Stretch。

到目前为止，我已经得到了以下信息：

dmesg

[Sun Sep  8 15:04:20 2019] sd 7:0:0:0: [sdd] 468862128 512-byte logical blocks: (240 GB/224 GiB)
[Sun Sep  8 15:04:20 2019] sd 7:0:0:0: [sdd] Write Protect is off
[Sun Sep  8 15:04:20 2019] sd 7:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[Sun Sep  8 15:04:20 2019] sd 7:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Sun Sep  8 15:04:51 2019] sd 7:0:0:0: [sdd] Attached SCSI disk
[Sun Sep  8 15:06:43 2019] sd 7:0:0:0: [sdd] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[Sun Sep  8 15:06:43 2019] sd 7:0:0:0: [sdd] tag#19 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[Sun Sep  8 15:06:44 2019] sd 7:0:0:0: [sdd] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[Sun Sep  8 15:06:44 2019] sd 7:0:0:0: [sdd] tag#21 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
[Sun Sep  8 15:09:49 2019] sd 7:0:0:0: [sdd] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[Sun Sep  8 15:09:49 2019] sd 7:0:0:0: [sdd] tag#2 CDB: Read(10) 28 00 00 00 00 00 00 00 20 00
[Sun Sep  8 15:09:49 2019] print_req_error: I/O error, dev sdd, sector 0
...

容量

所以，我们有容量 240057409536 个扇区

正如最初确认的那样fdisk（无法再使用它进行访问）：

468862128 512 字节逻辑块：（240 GB / 224 GiB）

我尝试过的：

  • fdisk

    我第一次运行这个工具时，它输出了一些有价值的信息，如上所示。第二次通话：

    # fdisk /dev/sdd

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sdd: No such file or directory

    几乎和我sfdisk现在遇到的错误一样testdisk。

  • ls

    brw-rw---- 1 root disk 8, 48 Sep  8 16:40 /dev/sdd

    所以，该设备仍然存在。

  • 数学

    468862128簇 *512扇区大小 =240057409536最初检测到的扇区dmesg

  • gdisk

    GPT fdisk (gdisk) version 1.0.3

Problem reading disk in BasicMBRData::ReadMBRData()!
Warning! Read error 22; strange behavior now likely!
Warning! Read error 22; strange behavior now likely!
Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present

***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***************************************************************

Command (? for help): p

Disk /dev/sdd: 0 sectors, 0 bytes
Model: SATAFIRM   S11  
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): B93E2FDE-39F0-4015-AEC9-96A76520F547
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 18446744073709551582
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)

Command (? for help): x

Expert command (? for help): o

Disk size is 0 sectors (0 bytes)
MBR disk identifier: 0x00000000
MBR partitions:

Number  Boot  Start Sector   End Sector   Status      Code
   1                     1   4294967295   primary     0xEE

  • GNUddrescue

    我的测试运行：

    ddrescue -d -f -r3 -R --sector-size=512 --size=240057409536  /dev/sdd /dev/null

    给出：

    GNU ddrescue 1.23
Press Ctrl-C to interrupt
     ipos:  240057 MB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:  240057 MB, non-scraped:        0 B,  average rate:       0 B/s
non-tried:  240057 MB,  bad-sector:        0 B,    error rate:       0 B/s
  rescued:        0 B,   bad areas:        0,        run time:          0s
pct rescued:    0.00%, read errors:        0,  remaining time:         n/a
                              time since last successful read:         n/a
Copying non-tried blocks... Pass 1 (backwards)
Unaligned read error. Is sector size correct?

在这里我只是不知道下一步该做什么。

我欢迎任何和所有的建议。

PS：有/曾经有 Windows 10 分区。 （用户不知道是否从非EFI升级。）

gdisk#2 启动后立即显示正确的尺寸:

Disk /dev/sdd: 468862128 sectors, 223.6 GiB
Model: SATAFIRM   S11  
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 476B6FD3-31DC-448B-834A-1E7F4ED18673
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 468862094
Partitions will be aligned on 2048-sector boundaries
Total free space is 468862061 sectors (223.6 GiB)

我不知道这种状态如何或为何在一分钟或几分钟后消失。

答案1

我没有注意到驱动器名称的重要性：

世达坚固S11

经过一番搜索后，发现可能有一种方法可以恢复 SSD 驱动器，但可能无法恢复数据。

该程序旨在恢复 Phison 3111 (S11) 控制器上磁盘的健康状况，例如 Smartbuy Revival2、Kingston A400，这些控制器由于某些问题而进入保护模式。

+

数据，如果成功恢复，则为被摧毁。

资料来源：汤姆的硬件。

相关内容