传输几个小时后 dd 崩溃

传输几个小时后 dd 崩溃

我正在尝试使用 dd 将外部硬盘驱动器 ( 1.5T ) 克隆到第二个硬盘驱动器 ( 3T )。我正在 Unix 上工作,想要创建一个磁盘映像。

这是我正在使用的命令:

dd if=/dev/disk1 of=/Volumes/FreeAgent\ GoFlex\ Drive\ DENISE/SeaGate_AC.dmg conv=noerror

我使用以下命令来检查传输进度:

kill -INFO 1880

一开始它工作正常,下面是输出的示例:

8576952+0 records in
8576952+0 records out
4391399424 bytes transferred in 658.085533 secs (6672992 bytes/sec) 

但过了一段时间,当我尝试访问目标 HD 时,终端没有响应,甚至我的 Finder 也崩溃了。

我尝试过使用同步选项,但结果相同

欢迎任何建议...

谢谢西蒙

以下是 slm 建议的 dmesg 输出:

2Request - begin
com_seagate_IOPowSec00_10_5: GetBufferDescriptor with buffer=0 dataSize=0 task=0
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - SCSITaskStatus 2
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - SendCommand non-zero status,     check condition
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - senseSize 18, respCode 0x72,    senseKey 0x1, addlSenseCode 0x0, addlSenseQual 0x1d, addlLength 0xe
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - returning main line 0
com_seagate_IOPowSecUserClient00_10_5[0x12f7ed00]::externalMethod(2, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x12f7ed00]::externalMethod(9, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSec00_10_5-(NA0LVZ12)::UpdateSelfTestResults: using     IssueSmartDiagnosticStatus
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - begin
com_seagate_IOPowSec00_10_5: GetBufferDescriptor with buffer=12ee1928 dataSize=200 task=0
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - SCSITaskStatus 0
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - returning main line 1
com_seagate_IOPowSecUserClient00_10_5[0x12f7ed00]::externalMethod(2, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x12f7ed00]::externalMethod(10, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x12f7ed00]::externalMethod(1, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x9ffc000]::externalMethod(0, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x9ffc000]::externalMethod(23, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x9ffc000]::externalMethod(1, 0x1102c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x9ffc000]::externalMethod(0, 0x1152c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x9ffc000]::externalMethod(24, 0x1442c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0x9ffc000]::externalMethod(1, 0x1442c70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(0, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(2, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(12, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSec00_10_5-(NA0LVZ12)::IssueSmartRequest: using IssueSmartReturnStatus
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - begin
com_seagate_IOPowSec00_10_5: GetBufferDescriptor with buffer=0 dataSize=0 task=0
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - SCSITaskStatus 2
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - SendCommand non-zero status,  check condition
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - senseSize 18, respCode 0x72,     senseKey 0x1, addlSenseCode 0x0, addlSenseQual 0x1d, addlLength 0xe
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - returning main line 0
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(2, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(9, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSec00_10_5-(NA0LVZ12)::UpdateSelfTestResults: using IssueSmartDiagnosticStatus
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - begin
com_seagate_IOPowSec00_10_5: GetBufferDescriptor with buffer=12ee1928 dataSize=200 task=0
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - SCSITaskStatus 0
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueSAT12Request - returning main line 1
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(2, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(10, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSecUserClient00_10_5[0xa014600]::externalMethod(1, 0x112ac70, 0, 0, 0)
com_seagate_IOPowSec00_10_5-(NA0LVZ12) handling stop request
com_seagate_IOPowSec00_10_5-(NA0LVZ12) IssueModeSelectTimer: shortTime = 1
com_seagate_IOPowSec00_10_5-(NA0LVZ12)::SetModeSelectTimer: using shortime
com_seagate_IOPowSec00_10_5-(NA0LVZ12) IssueModeSelectTimer: complete
com_seagate_IOPowSec00_10_5-(NA0LVZ12): IssueStopUnderDeviceControlCommand
Warning: audit space low (< 5% free)on audit log file-system

我的镜像文件大约有17G...

更新#1

两个驱动器都格式化为NTFS.它们安装的系统是Mac OSX 10.6.8.希捷提供的软件GoFlex用于访问 3TB 硬盘。

1.5TB HDD 出现故障,并且在启动期间Disk Utility扫描驱动器时出现故障。

答案1

我认为你的问题是你想写一个主引导记录(MBR)格式化的驱动器,MBR最多只能支持2TB

你必须格式化你的3TB驾驶时使用GUID 分区表 (GPT) 布局。我建议使用以下命令对 3TB 驱动器进行分区分手了然后使用克隆齐拉复制2TB驱动器的数据到3TB驾驶。

相关内容