Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #70187 > unrolled thread

MacBook Pro is bolshy

Back to article view | Back to comp.sys.mac.system

Contents

  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

Page 1 of 3  [1] 2 3  Next page →

#70187 — MacBook Pro is bolshy

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.

-- 
John McWilliams

[toc] | [next] | [standalone]

#70188

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.

It has nothing to do with "overloading" the drive - by the sound of it
the drive has simply died. There's a good chance those files are lost.
You could try a specific disk repair utility or a file rescue service,
but the price probably isn't worth paying and the chance of retrieving
anything is probably nil.

Looks like time for a new hard drive and re-installing the OS and
applications.

[toc] | [prev] | [next] | [standalone]

#70221

On 2/24/15   PDT 7:11 PM, Your Name 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.
>
> It has nothing to do with "overloading" the drive - by the sound of it
> the drive has simply died. There's a good chance those files are lost.
> You could try a specific disk repair utility or a file rescue service,
> but the price probably isn't worth paying and the chance of retrieving
> anything is probably nil.
>
> Looks like time for a new hard drive and re-installing the OS and
> applications.

Could be!

Overloading didn't cause HD failure, but it makes installing or 
defragging more difficult. (not that I can do either for other reasons)

[toc] | [prev] | [next] | [standalone]

#70223

On 2015-02-26, John McWilliams <jpmcw@comcast.net> wrote:
>
> Overloading didn't cause HD failure, but it makes installing or 
> defragging more difficult. (not that I can do either for other reasons)

Mac OS X 10.3 and later automatically optimizes and defragments files
smaller than 20 MB in size on the fly when they are opened - see
"Optimizations" section here:

<http://www.osxbook.com/book/bonus/ancient/whatismacosx/arch_fs.html>

And Apple says there is little benefit to defragmenting HFS+ drives:

<http://support.apple.com/en-us/HT1375>

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#70189

John McWilliams:

> 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.

Same as my wife's 27" iMac. Gray screen, then it shuts down. And
restarts. And repeats. Once in a while it will boot OK after being off
for a couple of days. I'm taking it to a well regarded Mac specialist
because they're 20 minutes closer than the Genius Bar. I suggest the
Genius Bar for your son's MBP. You can tinker 'til the cows come home
and go nowhere. Ask me how I know.

-- 
I agree with almost everything that you have said and almost everything that
you will say in your entire life.

usenet *at* davidillig dawt cawm

[toc] | [prev] | [next] | [standalone]

#70190

On 15-02-24 21:41, John McWilliams wrote:

> I have run Disk Utility many times, fsck -fy several times,

How do you run Disk Utility  or fsck ?  (how do you boot machine to get
to a point where you can do fsxk or run Disk Utility ?)

> 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. 

If it boots into recovery mode, it is likely that the hadrware disk is
fine since it can read data from it (the recovery partition).


> 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.

This is most likely the problem. when you have 2 hardware disks that
create a single disk to the OS, There is magic that happens in terms of
the file system, since some files are placed on one drive and others on
the other drive.  Corrupt the index and all hell breaks loose because
there is only one catalog for both disks and without it, you lose files
on both drives.

If the combo drive was pruchased from some 3rd party, you need to
contact them to see if they have recovery tools. (or suggest recovery
tools).

How much time and money you spend on this depends on value of data on
your son's machine.

The other option is to reformat the drive and install OS-X from scratch
on it.

I am pressure some here will recommend some disk recovery tools.
Depending on what your son did, you may be able to recover a large or
small number of files.


> 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.

In verbose mode, copy down the screen just before it shuts down. AKA;
the last lines before it fails. You can video the screen with your
iphone and play it back to freeze frame just before it shuts down.

[toc] | [prev] | [next] | [standalone]

#70195

On 2015.02.25 00:12 , JF Mezei wrote:
> On 15-02-24 21:41, John McWilliams wrote:
>
>> I have run Disk Utility many times, fsck -fy several times,
>
> How do you run Disk Utility  or fsck ?  (how do you boot machine to get
> to a point where you can do fsxk or run Disk Utility ?)

SU mode.

-- 
"Your net worth to the world is usually
  determined by what remains after your
  bad habits are subtracted from your good ones."
                                   Benjamin Franklin

[toc] | [prev] | [next] | [standalone]

#70220

On 2/25/15   PDT 4:33 AM, Alan Browne wrote:
> On 2015.02.25 00:12 , JF Mezei wrote:
>> On 15-02-24 21:41, John McWilliams wrote:
>>
>>> I have run Disk Utility many times, fsck -fy several times,
>>
>> How do you run Disk Utility  or fsck ?  (how do you boot machine to get
>> to a point where you can do fsxk or run Disk Utility ?)
>
> SU mode.
>

I can actually hold down the Option key to get a choice of the Recovery 
Partition or the HD we've been running on. Recovery Disk allows DU, 
console, online help and restore OS.  Restore doesn't, online help I can 
get with other computers, and both DU and console leave me holding the bag.

[toc] | [prev] | [next] | [standalone]

#70222

On 2/24/15   PDT 9:12 PM, JF Mezei wrote:
> On 15-02-24 21:41, John McWilliams wrote:
>
>> I have run Disk Utility many times, fsck -fy several times,
>
> How do you run Disk Utility  or fsck ?  (how do you boot machine to get
> to a point where you can do fsxk or run Disk Utility ?)
>
>> 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.
>
> If it boots into recovery mode, it is likely that the hadrware disk is
> fine since it can read data from it (the recovery partition).

It does give hope, but so far, not possible.
>
>> 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.
>
> This is most likely the problem. when you have 2 hardware disks that
> create a single disk to the OS, There is magic that happens in terms of
> the file system, since some files are placed on one drive and others on
> the other drive.  Corrupt the index and all hell breaks loose because
> there is only one catalog for both disks and without it, you lose files
> on both drives.
>
> If the combo drive was pruchased from some 3rd party, you need to
> contact them to see if they have recovery tools. (or suggest recovery
> tools).
>
> How much time and money you spend on this depends on value of data on
> your son's machine.
>
> The other option is to reformat the drive and install OS-X from scratch
> on it.
>
> I am pressure some here will recommend some disk recovery tools.
> Depending on what your son did, you may be able to recover a large or
> small number of files.

Yes, it may not be worth hundreds to restore what's on there.
>
>
>> 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.
>
> In verbose mode, copy down the screen just before it shuts down. AKA;
> the last lines before it fails. You can video the screen with your
> iphone and play it back to freeze frame just before it shuts down.

Thanks. I will do that. Seems that it was the same message as the failed 
DU to the effect that I should back up as many files as I can and get a 
new HDD. But I need to be sure.

[toc] | [prev] | [next] | [standalone]

#70224

On 2015-02-26, John McWilliams <jpmcw@comcast.net> wrote:
> Thanks. I will do that. Seems that it was the same message as the failed 
> DU to the effect that I should back up as many files as I can and get a 
> new HDD. But I need to be sure.

The time to backup is *before* disaster strikes. Hopefully you already
have another drive ready to use for backups once you've got this machine
back up and running?

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#70225

On 2/25/15   PDT 5:01 PM, Jolly Roger wrote:
> On 2015-02-26, John McWilliams <jpmcw@comcast.net> wrote:
>> Thanks. I will do that. Seems that it was the same message as the failed
>> DU to the effect that I should back up as many files as I can and get a
>> new HDD. But I need to be sure.
>
> The time to backup is *before* disaster strikes.

Really??

:)

  > Hopefully you already have another drive ready to use for backups 
once you've got this machine
> back up and running?

Yes, and yes. Except this machine was a backup machine for him, but he 
needs to get religious about backups in general.

[toc] | [prev] | [next] | [standalone]

#70228

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.

-- 
I will not see posts from astraweb, theremailer, dizum, or google
because they host Usenet flooders.

[toc] | [prev] | [next] | [standalone]

#70231

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?

[toc] | [prev] | [next] | [standalone]

#70232

In article <mcmc4c$9g6$1@dont-email.me>, John McWilliams
<jpmcw@comcast.net> wrote:
> 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?

Potentially if the problem is with the MacBook Pro's hardware itself
(e.g. I/O, motherboard, etc.), then taking the drive out and putting it
into a USB enclosure may mean it works when plugged into another Mac.
It's unlikely, but could be worth a try if you have an enclosure or
hard drive dock (or a Mac Pro tower model), or can get one cheaply.

[toc] | [prev] | [next] | [standalone]

#70237

In article <260220151856370941%YourName@YourISP.com>,
 Your Name <YourName@YourISP.com> wrote:

> Potentially if the problem is with the MacBook Pro's hardware itself
> (e.g. I/O, motherboard, etc.), then taking the drive out and putting it
> into a USB enclosure may mean it works when plugged into another Mac.
> It's unlikely, but could be worth a try if you have an enclosure or
> hard drive dock (or a Mac Pro tower model), or can get one cheaply.

If you have a dock or an external drive with a bootable system on it (or 
even a bootable stick) you could test out the laptop's hardware. The 
fact that the recovery partition is able to boot leads me to think that 
there's nothing wrong with the Mac itself. I've got the same problem 
here: MacBook Pro won't boot from the internal drive, but runs very 
nicely from an attached firewire 800 system. Fortunately the data on the 
internal drive isn't important in our case. 

We've been quoted CDN $200 for a new drive installed (I'm not willing to 
open up the case; I've looked at the tutorials, and while I have nice 
slim fingers, I don't think I have the dexterity. I don't mind messing 
around inside the Mac Pro "have you seen my vice-grips dear?")
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#70246

On 2/26/15   PDT 5:07 AM, Warren Oates wrote:
> In article <260220151856370941%YourName@YourISP.com>,
> Your Name <YourName@YourISP.com> wrote:
>
>> Potentially if the problem is with the MacBook Pro's hardware itself
>> (e.g. I/O, motherboard, etc.), then taking the drive out and putting it
>> into a USB enclosure may mean it works when plugged into another Mac.
>> It's unlikely, but could be worth a try if you have an enclosure or
>> hard drive dock (or a Mac Pro tower model), or can get one cheaply.
>
> If you have a dock or an external drive with a bootable system on it (or
> even a bootable stick) you could test out the laptop's hardware. The
> fact that the recovery partition is able to boot leads me to think that
> there's nothing wrong with the Mac itself. I've got the same problem
> here: MacBook Pro won't boot from the internal drive, but runs very
> nicely from an attached firewire 800 system. Fortunately the data on the
> internal drive isn't important in our case.
> We've been quoted CDN $200 for a new drive installed (I'm not willing to
> open up the case; I've looked at the tutorials, and while I have nice
> slim fingers, I don't think I have the dexterity. I don't mind messing
> around inside the Mac Pro "have you seen my vice-grips dear?")

Thanks.

My next move was going to be— and will still be— just that. I have a 
Yosemite installed flash drive, but do not know if this older MBP will 
boot off USB even in best of times. But I also have FW drives, could set 
them up after a bit.

Were you able to access the data on the internal? That's the only task I 
am interested in for now. Getting it to function as a working computer 
is far down the list, as it's simply and older machine where we have 
newer functioning ones.

And in addition to vise-grips, I have a ball-peen hammer, a blowtorch 
and a couple of plumber's wrenches.

[toc] | [prev] | [next] | [standalone]

#70253

In article <mcndu4$12s$1@dont-email.me>,
 John McWilliams <jpmcw@comcast.net> wrote:

> My next move was going to be— and will still be— just that. I have a 
> Yosemite installed flash drive, but do not know if this older MBP will 
> boot off USB even in best of times. But I also have FW drives, could set 
> them up after a bit.
> 

What MacBook Pro is it? Or what year, if you're not sure? If it's got a 
firewire 800 port, it's probably new enough to also boot from a USB 
stick.

> Were you able to access the data on the internal? That's the only task I 
> am interested in for now. Getting it to function as a working computer 
> is far down the list, as it's simply and older machine where we have 
> newer functioning ones.

I was able to get at the data for a while. Our problem was a bit 
different: the thing would boot up and about five minutes later would 
"lock up" in the pizza-wheel-of-death. I wasn't worried about the files 
on it -- we use it as a travel computer, and the main files are 
elsewhere (BusyCal, Mail, Stickies, Addresses). It's not a problem to 
restore them to a new drive and reinstall the other apps we use.

When you run disk utility from the recovery partition, what happens if 
you tell it to repair the main disk (you mentioned that you 'ran Disk 
Utility' but I'm not sure what you did exactly. What shows up in Disk 
Utility for disks and volumes?
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#70299

On 2/26/15   PDT 8:59 AM, Warren Oates wrote:
> In article <mcndu4$12s$1@dont-email.me>,
> John McWilliams <jpmcw@comcast.net> wrote:
>
>> My next move was going to be— and will still be— just that. I have a
>> Yosemite installed flash drive, but do not know if this older MBP will
>> boot off USB even in best of times. But I also have FW drives, could
>> set them up after a bit.
>>
>
> What MacBook Pro is it? Or what year, if you're not sure? If it's got a
> firewire 800 port, it's probably new enough to also boot from a USB stick.

Can't access the about this Mac, but it has the large square removable 
battery on the bottom.
>
>> Were you able to access the data on the internal? That's the only task
>> I am interested in for now. Getting it to function as a working
>> computer is far down the list, as it's simply and older machine where
>> we have newer functioning ones.
>
> I was able to get at the data for a while. Our problem was a bit
> different: the thing would boot up and about five minutes later would
> "lock up" in the pizza-wheel-of-death. I wasn't worried about the files
> on it -- we use it as a travel computer, and the main files are
> elsewhere (BusyCal, Mail, Stickies, Addresses). It's not a problem to
> restore them to a new drive and reinstall the other apps we use.
>
> When you run disk utility from the recovery partition, what happens if
> you tell it to repair the main disk (you mentioned that you 'ran Disk
> Utility' but I'm not sure what you did exactly. What shows up in Disk
> Utility for disks and volumes?

The top level is in red, with numerals starting with 500. 11 GB 
ST9.............. and the named (formatted) disk is the only subsection. 
Clicking on the top line allows for nothing, and  I re-ran DU about five 
times on my main (and only) partition.

  Even though it said "Volume repair complete", the next line says 
"Updating boot support partitions for the volume as required". Followed 
by "Error: Disk Utility can't repair this disk. backup as many of your 
files as possible, reformat the disk, and restore your backed up files."-
Which also shows up in a popup dialog, with the only choice being "OK".

Running fsck -fy eventually returns "The volume MBP500 could not be 
verified completely".

[toc] | [prev] | [next] | [standalone]

#70300

In article <mcqfh3$8dn$1@dont-email.me>, John McWilliams
<jpmcw@comcast.net> wrote:

>   Even though it said "Volume repair complete", the next line says 
> "Updating boot support partitions for the volume as required". Followed 
> by "Error: Disk Utility can't repair this disk. backup as many of your 
> files as possible, reformat the disk, and restore your backed up files."-
> Which also shows up in a popup dialog, with the only choice being "OK".
> 
> Running fsck -fy eventually returns "The volume MBP500 could not be 
> verified completely".

get disk warrior.

[toc] | [prev] | [next] | [standalone]

#70302

On 2/27/15   PDT 11:13 AM, nospam wrote:
> In article <mcqfh3$8dn$1@dont-email.me>, John McWilliams
> <jpmcw@comcast.net> wrote:
>
>>    Even though it said "Volume repair complete", the next line says
>> "Updating boot support partitions for the volume as required". Followed
>> by "Error: Disk Utility can't repair this disk. backup as many of your
>> files as possible, reformat the disk, and restore your backed up files."-
>> Which also shows up in a popup dialog, with the only choice being "OK".
>>
>> Running fsck -fy eventually returns "The volume MBP500 could not be
>> verified completely".
>
> get disk warrior.
>
I knew that would come up sooner or later. Don't want to spend $100 or 
so for a small possibility. Not a problem if it would work.

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | comp.sys.mac.system

csiph-web