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


Groups > comp.sys.mac.system > #70310

Re: MacBook Pro is bolshy

From John McWilliams <jpmcw@comcast.net>
Newsgroups comp.sys.mac.system
Subject Re: MacBook Pro is bolshy
Date 2015-02-27 14:02 -0800
Organization Sept. all the time
Message-ID <mcqpg7$fs4$2@dont-email.me> (permalink)
References (6 earlier) <54ef50ec$0$54710$c3e8da3$fdf4f6af@news.astraweb.com> <mcqfh3$8dn$1@dont-email.me> <270220151413137854%nospam@nospam.invalid> <mcqgji$blt$2@dont-email.me> <clc1g2FahmoU2@mid.individual.net>

Show all headers | View raw


On 2/27/15   PDT 12:13 PM, Jolly Roger wrote:
> On 2015-02-27, John McWilliams <jpmcw@comcast.net> wrote:
>> 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.
>
> Better to spend that money on a backup drive anyway so that next time
> you won't be caught off guard. ; )
>
Back up drives he has, and I have. It's getting him to use same. This 
will help.

Back to comp.sys.mac.system | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


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