Difference between revisions of "Talk:Disk cloning"

From ArchWiki
Jump to: navigation, search
(Data recovery using `safecopy`: new section)
(remove conv sync noerror)
 
Line 1: Line 1:
== remove conv sync noerror ==
+
== <s> remove conv sync noerror </s> ==
  
 
Particularly in conjunction with larger blocksizes it seems to produce corrupt data ( steps to reproduce http://superuser.com/a/1075837/195171 ) in case of errors that are not aligned to the block size. If that isn't a bug in dd, the conv sync noerror should no longer be recommended. [[User:Frostschutz|Frostschutz]] ([[User talk:Frostschutz|talk]]) 13:41, 13 May 2016 (UTC)
 
Particularly in conjunction with larger blocksizes it seems to produce corrupt data ( steps to reproduce http://superuser.com/a/1075837/195171 ) in case of errors that are not aligned to the block size. If that isn't a bug in dd, the conv sync noerror should no longer be recommended. [[User:Frostschutz|Frostschutz]] ([[User talk:Frostschutz|talk]]) 13:41, 13 May 2016 (UTC)
 +
: Close. This issue is already clearly explained in page. --[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 08:34, 31 August 2018 (UTC)
  
 
== Data recovery using `safecopy` ==
 
== Data recovery using `safecopy` ==

Latest revision as of 08:34, 31 August 2018

remove conv sync noerror

Particularly in conjunction with larger blocksizes it seems to produce corrupt data ( steps to reproduce http://superuser.com/a/1075837/195171 ) in case of errors that are not aligned to the block size. If that isn't a bug in dd, the conv sync noerror should no longer be recommended. Frostschutz (talk) 13:41, 13 May 2016 (UTC)

Close. This issue is already clearly explained in page. --Fengchao (talk) 08:34, 31 August 2018 (UTC)

Data recovery using `safecopy`

safecopy could be a useful addition to the article: it can rescue data from a damaged medium through a multi-stage process similar to ddrescue, but comes with presets for a pretty well thought out three-step process (e.g. safecopy --stage1 /dev/source target.img && safecopy --stage2 /dev/source target.img && safecopy --stage3 /dev/source target.img), so it should be much more intuitive to use for an inexperienced user.
I currently don't have enough time to flesh this out for inclusion in the article, but I figured I'd leave this here for future reference. -- n-st (talk) 11:45, 26 November 2017 (UTC)