[Discuss] Discuss Digest, Vol 32, Issue 36
Stuart Conner
genuineaudio at gmail.com
Fri Jan 31 12:26:47 EST 2014
Re: WDC HDD data recovery redcommendations
The click of death is often the read heads getting bent/smashed and
therefore can't read the surface of the disks.
If you're handy, You could try to recover by transplanting the platters
into a similar HDD chassis and reading an image with a tool like dd.
This is what the pros do usually.
I've never done it personally since the last time I came across this I
didn't have a donor drive and the data was only a friend's DVR tv shows..
Trying to straighten the read heads is futile.
I happen to have an old 250GB sata I drive at work if you want to try (I
forget if it's WD or segate).
But if the data is too important to risk on your own experimentation, take
it to the pros.
Stu Conner genuineaudio at gmail.com
On Fri, Jan 31, 2014 at 12:00 PM, <discuss-request at blu.org> wrote:
> Send Discuss mailing list submissions to
> discuss at blu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.blu.org/mailman/listinfo/discuss
> or, via email, send a message with subject or body 'help' to
> discuss-request at blu.org
>
> You can reach the person managing the list at
> discuss-owner at blu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss digest..."
>
>
> Today's Topics:
>
> 1. Re: first time build of GIT server (Nuno Sucena Almeida)
> 2. Re: first time build of GIT server (Edward Ned Harvey (blu))
> 3. WDC HDD data recovery redcommendations? (Jim Gasek)
> 4. Re: WDC HDD data recovery redcommendations?
> (Edward Ned Harvey (blu))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 30 Jan 2014 13:19:57 -0500
> From: Nuno Sucena Almeida <nuno at aeminium.org>
> To: discuss at blu.org
> Subject: Re: [Discuss] first time build of GIT server
> Message-ID: <52EA97CD.303 at aeminium.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/30/2014 11:23 AM, John Malloy wrote:
> > What site should I use for the git clone <URL> ?
>
> I think that if you are asking these kind of questions, a
> more thorough reading about git is in need, unless you want to have
> frustrated developers/users down the line.
>
> I recommend the Pro Git book , available online , ebook
> and print at:
>
> http://git-scm.com/book
>
> For hosting, I also recommend gitlab, already mentioned
> by someone else in this thread:
>
> http://gitlab.org/
>
> For my personal projects/docs/etc I've been using
> gitolite + gitweb for a few years, having migrated from
> svn and before that cvs. It's fairly straightforward to
> setup, but even the gitlab guys moved away from it.
> I'll eventually move to gitlab when I have the time.
>
> cheers,
> Nuno
>
> - --
> http://aeminium.org/nuno/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iQIcBAEBAgAGBQJS6pfBAAoJEPIY6fuKMkz5zVwQAJlmnCic9AAeS7W5Ay+sYUlw
> vnamCACAwz4paV0mp7+wZf4U3mRcjswcU6GEzsgmWCimiI2ADe092QwOtv0YPTiR
> 81mX6CNW9S7HWtzOv7fxZEaoENfJp70kDqczzSXBIjRfHKMjl6VZDQgJE9So4J+X
> X27K+fQqa8VDgbaSfEWW9WBhACgsDTXTvKh1oSuVp9+VnDAS7y8pKE66h0foJOMc
> dmIymlyT/uqXNTs9s8y0GbdxZ2F15EGxkALtSGsAQFXIE/RpHTaEP90T+Tdu90e9
> C6tmQu+zpo7jxWObiQVV8PUr647+Nkb8n7FIabN0XJcQHsBk3ArhRnmriDM+0+6a
> h/uixhi4XARKNuxOcsQiWUoPXgcJ73G5GCh77BB0Jzkizh2ktigm6wm7CBfKmHr3
> WrTfiG6/uB/nioW84xJBbRK+MVnG2sWKCiU7Eg7IQLvr3x0are+X8qZ+SKdWCN8Y
> Ihmkc45WsLtD4m5pbegmJXEspVZRlH6Qc77Hb9J81FOCeR5/D6mE4R7gbfYQN2YY
> yc42iXaEqT/V5wR0p+bjpgBc0URHnzGwZWKUvgZszUWMJ7gGfy4iXsUdc5ax7pC4
> wr82LWTz1LVkX9nrBSa3vW/nAC5a1g3UI06XeVlS3Yr5O2BUJT7zNokxSpt5UPJ2
> /LBXcPfPzTPnNQNlwlDl
> =ebRe
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 30 Jan 2014 23:09:04 +0000
> From: "Edward Ned Harvey (blu)" <blu at nedharvey.com>
> To: Chris Johnson <effigies at riseup.net>, John Malloy
> <jomalloy at gmail.com>, "discuss at blu.org" <discuss at blu.org>
> Subject: Re: [Discuss] first time build of GIT server
> Message-ID:
> <
> 07b939bd9ef445c7b2a61d64e609efe5 at DM2PR04MB687.namprd04.prod.outlook.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> > From: Chris Johnson [mailto:effigies at riseup.net]
> >
> > True, and good point. Personally, I like SSH keys, but do you know of
> > any reasons to prefer HTTPS to SSH, apart from key management?
>
> Why build one when you can have two at twice the price?
> ;-)
>
> Honestly, they both work well. I think ssh is slightly more convenient,
> as more clients know how to use ssh keys for auto authentication, while by
> contrast, the ability to store the password in a https git client seems to
> be a hacked-on afterthought, if available at all.
>
> But yes, there is one specific situation where I cared about https instead
> of ssh. A company where I didn't control the firewall, they granted me
> inbound port 443, and refused to grant me inbound port 22.
>
> Similarly, I've worked at companies where they permit us to make
> *outbound* port 443 and not 22. So if I happened to want to connect to a
> public server that only gave me access on 22... Well... That sucks.
>
> So if your server is to be publicly facing, it's beneficial to enable
> every secure port, in order to reach the broadest range of users. If it's
> going to be internal and you have control over all the access barriers,
> then no worries. Do whatever you like best.
>
> Specifically for gitlab, I recommend, to always enable https, for the
> aforementioned security concern. In my most recent deployment, we got
> https working, and then I logged in and uploaded my ssh public key. So
> it's all irrelevant, everything's awesome. :-)
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 30 Jan 2014 16:25:34 -0800
> From: "Jim Gasek" <jim at gasek.net>
> To: <discuss at blu.org>
> Subject: [Discuss] WDC HDD data recovery redcommendations?
> Message-ID: <20140130162534.DC2BD2FB at m0005312.ppops.net>
> Content-Type: text/plain; charset="UTF-8"
>
> I have a WDC 160GG HAWK SATA drive, it clicks on startup,
> but the motor either fails, or doesn't stay spinning.
>
> 250GB SATA 7200rpm, 8G cache.
>
> When I connect it to a variety of laptops with a USB adapter,
> it recognizes the make/model, and tries to load up the driver
> and mount it, but never finishes.
>
> It cannot see any partition.
>
> If I had to guess I would say a bad motor(?)
>
> Any HDD repair shops, data recovery shops that can extract
> data on what seems to be a not-so-damaged but non-functional
> HDD? Not worth more than a grand for sure.
>
> Thanks,
> Jim Gasek
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 31 Jan 2014 14:27:26 +0000
> From: "Edward Ned Harvey (blu)" <blu at nedharvey.com>
> To: "jim at gasek.net" <jim at gasek.net>, "discuss at blu.org"
> <discuss at blu.org>
> Subject: Re: [Discuss] WDC HDD data recovery redcommendations?
> Message-ID:
> <
> e8e5c51170b54431b13a5abdd134d2d5 at CO2PR04MB684.namprd04.prod.outlook.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> > From: discuss-bounces+blu=nedharvey.com at blu.org [mailto:discuss-
> > bounces+blu=nedharvey.com at blu.org] On Behalf Of Jim Gasek
> >
> > Any HDD repair shops, data recovery shops that can extract
> > data on what seems to be a not-so-damaged but non-functional
> > HDD? Not worth more than a grand for sure.
>
> There are lots of those. I've liked disk doctors in the past, but haven't
> needed this type of service in several years. You get bit by this once,
> and you will never again neglect your backups. It was $700 at the time. I
> guess a grand now.
>
>
> ------------------------------
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>
>
> End of Discuss Digest, Vol 32, Issue 36
> ***************************************
>
--
Thanks,
Stu
617-462-0552
genuineaudio at gmail.com
blue23 at netzero.net
stuart.conner at state.ma.us
Stuart Conner
62 Rhodes Cir
Hingham, MA 02043
More information about the Discuss
mailing list