meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
datarecovery [2016/08/17 07:56] – niziakdatarecovery [2025/01/31 10:08] (current) – niziak
Line 1: Line 1:
 +====== Data recovery ======
 +
 +<code bash>
 +hdparm -c0 /dev/sdi
 +hdparm -X1 /dev/sdi
 +hdparm -d0 /dev/sdi
 +echo 1 > /sys/block/sdi/device/queue_depth
 +</code>
 +
 +===== fast erase whole disc =====
 +
 +search tags: "secure erase"
 +
 +<code bash>
 +sudo hdparm --user-master u --security-set-pass ABC /dev/sdX
 +sudo hdparm --user-master u --security-erase ABC /dev/sdX
 +
 +# check if device security is "not enabled"
 +hdparm -I /dev/sdX
 +</code>
 +
 +
 ====== sata hotplug  ====== ====== sata hotplug  ======
 +
 ===== Plug ===== ===== Plug =====
  
Line 15: Line 38:
  
  
- 
-====== safecopy ====== 
-There are some predefined settings: 
-  * stage1: Preset to rescue most of the data fast,  using  no  retries  and avoiding bad areas. 
-  * stage2: Preset to rescue more data, using no retries but  searching  for exact ends of bad areas. 
-  * stage3: Preset to rescue everything that can be  rescued  using  maximum retries, head realignment tricks and low level access. 
- 
-In current working directory, safecopy will create files with badblocks map: stage#.badblocks, which are used in next stages. 
-Typical usage is: 
-<code bash> 
-safecopy --stage1 /dev/source output.img 
-safecopy --stage2 /dev/source output.img 
-safecopy --stage3 /dev/source output.img 
-</code> 
- 
-===== on usb drives ===== 
-Not all USB adapters can handle SATA low level operations. 
-<code bash> 
-safecopy --forceopen -L 0 --stage1 /dev/source /dev/destination 
-</code>