Greg Freemyer wrote:
Linda Walsh <suse@tlinx.org> wrote:
Somehow this topic seems to have migrated from how to do disk to disk copy w/o using command line (and so many of us try to tell him the command line is by far the best for something this simple), to dealing with bad sector in a source disk... which fortunately for me, is a rare situation.
Linda,
I do this procedure as part of my day job.
--- My condolences! ;-)
(That's why I packaged ewfacquire, I use it routinely.)
I am sure it is better for treating bad disks than 'dd'
The "subject drives" which I read from are a random collection of customer drives. They can be a almost new drive in a new machine, all the way to a 10 year old drive in a computer sitting out in a shed that was almost forgotten about. Most are from desktop/laptop PCs a few years old and routinely in use.
I don't keep stats, but I would guess between 5 and 10% of them have at least one bad sector. Having a significant number of bad sectors I agree is rare, but having one or two I would say is almost routine.
---- Um, are you saying a typical user should expect to see 1-2 disk errors on a disk->disk copy? Isn't it fair to say that many consumer level drives not only have 1-2 disk errors, but already have such sectors remapped to per-track spares when new? For that matter, if it isn't a drive nearing it's "end of useful life", would you expect users to actually see or notice such an error -- or wouldn't it be handled by the drives internal firmware -- w/recovery via internal ECC and remapping all handled on the fly? Isn't, by 'SMART' standards, a drive at the end of its useful lifespan when it can no longer automatically relocate such data automatically? Isn't it *normally* the case that a user will only see disk errors on a drive that can no longer remap sectors?
In fact, I think the spec for new drives is no more than one bad sector in 10e10. 500gb drives have a billion sectors, so even with brand new drives having 1 in 10 have a bad sector would be in spec.
---- But you are talking raw sectors -- not formatted capacity, no? Wouldn't the MTBF say, a new, 5-year warranty Hitachi 4TB drive rated at 1-2 million hours (for DeskStar V. Ultrastar models) sort of imply that most users will never see a disk error during the useful life of that disk?
Greg
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org