Date: Sun, 17 Sep 2017 20:57:27 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Disk not spinning up Message-ID: <bea2ec4d-9328-4aeb-d4c5-be939ed49dc1@FreeBSD.org> In-Reply-To: <20170917214321.8fd2157b.freebsd@edvax.de> References: <20170917214321.8fd2157b.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dTH7BsxvEH9jLWUtLSBSHKuF5cAQp2XKL Content-Type: multipart/mixed; boundary="fMsbjjpvccX2ArvverftNE7lW6LL0GTHr"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <bea2ec4d-9328-4aeb-d4c5-be939ed49dc1@FreeBSD.org> Subject: Re: Disk not spinning up References: <20170917214321.8fd2157b.freebsd@edvax.de> In-Reply-To: <20170917214321.8fd2157b.freebsd@edvax.de> --fMsbjjpvccX2ArvverftNE7lW6LL0GTHr Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 17/09/2017 20:43, Polytropon wrote: > This is more a hardware question than a FreeBSD question, but > as FreeBSD is involved, I think it's worth being asked here > due to the experienced, intelligent, creative and (in an > entirely positive sense) "unusual" participants on this list. >=20 > I have a harddisk Quantum Fireball with ca. 1 GB capacity > (yes, that's GB, not TB). It's a (P)ATA / "IDE" disk with > a 40 pin connector for a flat cable, configured as master. >=20 > The disk has been in use in a system that I built around 1995 > and which I occasionaly used over the years. The last system > activation was yesterday. Today, the disk just didn't spin up > again. >=20 > After extracting the disk from the system and using my fine > "forensics adaptor" to power it, it made short cranking sounds > (ca. 1 per second) and short beeps from time to time, then went > silent. I can repeat this. >=20 > Now I probably did something stupid, but a radio amateur friend > had success with this approach on a 40 MB disk (yes, that's MB, > not GB). I _opened_ the disk (with gloves, face mask and cap, > just to minimize the dust falling from my head into the disk) > and saw the central motor "rotate" clockwise and counterclockwise > for less than 1/4 rotation. I tried to "help" the disk spin up > as you can imagine, but it would not do so. >=20 > My question: >=20 > Had anyone had success getting such a disk work again? Is it > worth searching my "museum" for a replacement controller? Or > does it look more like a motor failure than a controller failure? >=20 > I can read the disk with my "forensics adapter" like this (tested > with the other 1.2 GB disk from the same system): >=20 > $ sudo mount -t msdosfs -o ro /dev/da3s1 /mnt >=20 > That's the FreeBSD-related part in this question. But of course, > a disk not spinning up won't be recognized by the system. I'd like > to at least access the disk once to copy as much as I can. >=20 > Are there any ideas, options, chances, suggestions or experiments > other than "throw it out of the window"? :-) >=20 Considering the age of the disk, it's amazing it's still showing any signs of life at all. What you are experiencing sounds like 'sticktion' -- over time the lubricants on the drive bearings slowly become more sticky, and this tends to have the effect that the drive won't start up from cold. This is one place where percussive maintenance is justified. If you can tap the drive in just the right way as it is trying to spin up, you may be able to get it past the first few turns, after which it should be able to gather enough momentum to keep going. You want to hold the drive flat on the table, and tap the corner of the drive so that it rotates in the same plane that the platters do. You'll have to experiment to see what's most effective. Once you do get the platters moving, eventually the drive should come up to normal operating temperature and that which should soften the lubrication enough for it to run normally for a while, if you're lucky. The drive is definitely in its death throws, and your only hope is to concentrate on recovering any data that you can in whatever short time is left to it. If any. It may already be too far gone. Cheers, Matthew --fMsbjjpvccX2ArvverftNE7lW6LL0GTHr-- --dTH7BsxvEH9jLWUtLSBSHKuF5cAQp2XKL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZvtOuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATk74QAKnNCjG3p2JuMGH8GmA28FSd wo+FOBGsSS8RFKngLearmtSWZ7XJnodrqqktQiHArQMw8Dt/+AdIsI0J3xXbd4fx JkxNd0xzS6KyFR9+DbaXbauzKXx0VVjA3pwnSarwVGigayymrUBzQcXurQ/2L62V HUfntidWhqvIZbHGAr3KnXc1hdSVQq9idJpe86OUnQeRXE9zHezCDcdI85SBiPpE +heZLKlSetq5WSohdwjzGh7kw54KK+5YwjMonmf8d4rE5v7oK6i6dhEsmJkpcbsg ACZVXTJ1Vzl5bOu8t6v/coQ2G1wGw8E5V/npHfQCFrAu5zPNoRkyGgfhr2AUGfAD W31CU0700sayDbNfeCda9eUe/1tLvvtGVxNQB+pK73JOb1wOMhr+Zab6w139CQfb /XXjNGBt8I+7Wzpon5ufHBwiEthWou6gsToAJVV5YCsrGO8DTTwmX+vmFNH9Eltk qxVnS+vc/9cbWa1kAloM25wA7LluGlugpmAOsYW1SQkh0UZZXG9mxfSZ7NWVSRwX Jq/TcxpnD4TWkPo6eItvAhWkeFodF+xDtGdr+zo8hlp7foAcrCXPj5Xo9ZK1EUYy iYmbcR6nRNDZ8qYcs2Bx6ly0C5cUcr0xHjS/0kFr3zybzfyazwvEZ3KTeiReIHcb KCul4mJM4Q2H+QfJ6zS4 =btme -----END PGP SIGNATURE----- --dTH7BsxvEH9jLWUtLSBSHKuF5cAQp2XKL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bea2ec4d-9328-4aeb-d4c5-be939ed49dc1>