From: nospam <nospam@nospam.invalid>
Subject: Re: Adobe Stock Images pays photo $0.18 for using his photo
Full headers:
From: nospam <nospam@nospam.invalid>
Subject: Re: Adobe Stock Images pays photo $0.18 for using his photo
Date: Wed, 20 Dec 2017 22:17:55 -0500
Organization: A noiseless patient Spider
Lines: 37
Message-ID: <201220172217559014%nospam@nospam.invalid>
References: <p19qv4$1f8c$> <181220172047100279%nospam@nospam.invalid> <p19rs6$1gce$> <181220172123331269%nospam@nospam.invalid> <p1b4qj$17kh$> <191220171145292036%nospam@nospam.invalid> <> <p1dsh3$1837$> <> <p1empl$m2o$> <> <201220171900279941%nospam@nospam.invalid> <>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Injection-Info:; posting-host="1d903acc33b39f05810aa70b138c6a05";
logging-data="17263"; mail-complaints-to="";posting-account="U2FsdGVkX1/I8dJConnoDN5/cYPB5ZA5"
User-Agent: Thoth/1.9.0 (Mac OS X)
Cancel-Lock: sha1:fl1BWrUFtS5OuizhjS6DaIEp5NQ=
Print Article
Forward Article
In article<>, Bill W<> wrote:

> >>  A simple hard drive clone that keeps reporting
> >> source disk errors has me stumped. 
> >
> >what kind of errors? maybe the drive is failing.
> That's what it looks like. Running chkdsk takes so long I had to
> cancel it, and running the disk check from Windows also takes forever.

a quick smart test might show some relevant info, but a full smart test
(which can take many hours) would be more telling. on the other hand,
if the drive is failing, the more you use it and run tests, the closer
to total failure you get.

> I already have the new drive, so all I need to do is get the data onto
> that drive, but cloning won't work with the software I've tried. I'm
> thinking to try a system backup, and then restore to the new drive,
> but I don't know if that will work either. 

don't you have a backup of this drive?

> Just doing a fresh Windows install on the new drive isn't such a big
> deal on the laptop - there's very little software to reinstall. I just
> have no idea where the Windows software key might be. 

if it's win10, you don't need a key. otherwise, it can be extracted.

> The reason I didn't consider a failing drive, and kept fighting this
> is that there are no other signs of it. No crashes, no errors in
> normal use, nothing at all. 

drives can fail in mysterious and sometimes sudden ways. 

one of mine randomly decides it's read-only. an unmount/mount fixes it,
at least for a while. needless to say, it's queued for replacement.