Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #70231
| From | John McWilliams <jpmcw@comcast.net> |
|---|---|
| Newsgroups | comp.sys.mac.system |
| Subject | Re: MacBook Pro is bolshy |
| Date | 2015-02-25 21:49 -0800 |
| Organization | Sept. all the time |
| Message-ID | <mcmc4c$9g6$1@dont-email.me> (permalink) |
| References | <mcjcmm$skr$1@dont-email.me> <mcmurtrie-2A4DD1.19351925022015@news.sonic.net> |
On 2/25/15 PDT 7:35 PM, Kevin McMurtrie wrote: > In article <mcjcmm$skr$1@dont-email.me>, > John McWilliams <jpmcw@comcast.net> wrote: > >> My son's MBP doesn't boot up. >> >> I have run Disk Utility many times, fsck -fy several times, tried Target >> Mode but it doesn't show up on any of three different Macs, and all >> messages seem to say the HD is bad, recover all the files you can, and >> get a new HDD. OK, but I don't see how I can access said files. It will >> boot into recovery mode, but still no visibility of files on the HDD. >> He's overloaded it, with only 10 Gigs free out of 500. Several years ago >> I put in a combo drive (part SS, part HD), and I cannot say what exact >> model it is, but it has the big battery door on the bottom. FW800 port, >> optical drive (which is also Bolshevik). >> >> I am out of ideas short of taking it to the Apple geniuses. Oh, it does >> boot into verbose mode, but a minute or two later it shuts down by itself. >> >> Prayers, guidance, smart remarks, mostly appreciative will I be. > > The disk is probably scrambled by the MBP suffering from hardware > failure. Move the disk to a new computer, repair it, and recover files. The disk spins up in situ, but is unreadable in Target Mode or via the Recovery Partition. I can't quite see how stripping it out and trying to mount it elsewhere would help. Could you please elaborate?
Back to comp.sys.mac.system | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-24 18:41 -0800
Re: MacBook Pro is bolshy Your Name <YourName@YourISP.com> - 2015-02-25 16:11 +1300
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-25 16:39 -0800
Re: MacBook Pro is bolshy Jolly Roger <jollyroger@pobox.com> - 2015-02-26 00:59 +0000
Re: MacBook Pro is bolshy Davoud <star@sky.net> - 2015-02-24 23:17 -0500
Re: MacBook Pro is bolshy JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-02-25 00:12 -0500
Re: MacBook Pro is bolshy Alan Browne <alan.browne@FreelunchVideotron.ca> - 2015-02-25 07:33 -0500
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-25 16:33 -0800
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-25 16:42 -0800
Re: MacBook Pro is bolshy Jolly Roger <jollyroger@pobox.com> - 2015-02-26 01:01 +0000
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-25 17:05 -0800
Re: MacBook Pro is bolshy Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2015-02-25 19:35 -0800
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-25 21:49 -0800
Re: MacBook Pro is bolshy Your Name <YourName@YourISP.com> - 2015-02-26 18:56 +1300
Re: MacBook Pro is bolshy Warren Oates <warren.oates@gmail.com> - 2015-02-26 08:07 -0500
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-26 07:26 -0800
Re: MacBook Pro is bolshy Warren Oates <warren.oates@gmail.com> - 2015-02-26 11:59 -0500
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-27 11:12 -0800
Re: MacBook Pro is bolshy nospam <nospam@nospam.invalid> - 2015-02-27 14:13 -0500
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-27 11:30 -0800
Re: MacBook Pro is bolshy Jolly Roger <jollyroger@pobox.com> - 2015-02-27 20:13 +0000
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-27 14:02 -0800
Re: MacBook Pro is bolshy Jolly Roger <jollyroger@pobox.com> - 2015-02-28 02:23 +0000
Re: MacBook Pro is bolshy Jolly Roger <jollyroger@pobox.com> - 2015-02-27 20:13 +0000
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-27 14:01 -0800
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-26 07:41 -0800
Re: MacBook Pro is bolshy Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2015-02-26 19:03 -0800
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-27 11:14 -0800
Re: MacBook Pro is bolshy Warren Oates <warren.oates@gmail.com> - 2015-02-27 16:13 -0500
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-02-27 14:13 -0800
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-03-03 16:29 -0800
Re: MacBook Pro is bolshy Warren Oates <warren.oates@gmail.com> - 2015-03-03 19:40 -0500
Re: MacBook Pro is bolshy Your Name <YourName@YourISP.com> - 2015-03-04 16:15 +1300
Re: MacBook Pro is bolshy Warren Oates <warren.oates@gmail.com> - 2015-03-04 05:55 -0500
Re: MacBook Pro is bolshy Jolly Roger <jollyroger@pobox.com> - 2015-03-04 16:02 +0000
Re: MacBook Pro is bolshy Warren Oates <warren.oates@gmail.com> - 2015-03-04 13:06 -0500
Re: MacBook Pro is bolshy Jolly Roger <jollyroger@pobox.com> - 2015-03-04 19:06 +0000
Re: MacBook Pro is bolshy Warren Oates <warren.oates@gmail.com> - 2015-03-04 14:28 -0500
Re: MacBook Pro is bolshy Alan Browne <alan.browne@FreelunchVideotron.ca> - 2015-03-03 19:56 -0500
Re: MacBook Pro is bolshy Your Name <YourName@YourISP.com> - 2015-03-04 16:49 +1300
Re: MacBook Pro is bolshy John McWilliams <jpmcw@comcast.net> - 2015-03-03 21:54 -0800
csiph-web