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


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

A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests...

Started byANTant@zimage.com (Ant)
First post2015-09-23 18:16 -0500
Last post2015-09-28 05:03 +0000
Articles 20 on this page of 91 — 11 participants

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


Contents

  A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 18:16 -0500
    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 18:18 -0500
      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-23 22:41 -0500
        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-09-24 00:38 -0400
          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-09-24 00:42 -0400
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:09 +0000
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:39 +0000
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 11:24 -0500
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Ant <ant@zimage.comANT> - 2015-09-26 04:57 -0700
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-26 16:30 +0000
                    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-27 19:48 -0500
                      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-28 03:44 +0000
                        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-27 23:13 -0500
                Re: MacBook Pro (MBP) gets stuck during its boot ups and tests, disk's I/O error in verbose bootup, & unable to repair! ANTant@zimage.com (Ant) - 2015-09-27 19:27 -0500
                  Re: MacBook Pro (MBP) gets stuck during its boot ups and tests, disk's I/O error in verbose bootup, & unable to repair! Jolly Roger <jollyroger@pobox.com> - 2015-09-28 03:43 +0000
                    Re: MacBook Pro (MBP) gets stuck during its boot ups and tests, disk's I/O error in verbose bootup, & unable to repair! ANTant@zimage.com (Ant) - 2015-09-27 22:48 -0500
          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 00:53 -0500
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 01:31 -0500
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-24 12:35 +0000
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 10:53 -0500
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:55 +0000
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 11:24 -0500
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:15 +0000
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 10:54 -0500
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Fred Moore <fmoore@gcfn.org> - 2015-09-25 11:14 -0400
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-25 15:34 +0000
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-25 16:39 -0500
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-25 16:32 -0500
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Michael Vilain <vilain@NOspamcop.net> - 2015-09-25 17:52 -0700
                    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-25 20:14 -0500
                      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Michael Vilain <vilain@NOspamcop.net> - 2015-09-25 23:45 -0700
                        Re: SMART utilities... ANTant@zimage.com (Ant) - 2015-09-26 05:58 -0500
        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:03 +0000
          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 10:55 -0500
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:58 +0000
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 11:27 -0500
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 16:56 +0000
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 13:34 -0500
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-24 16:58 +0000
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! ANTant@zimage.com (Ant) - 2015-09-24 13:35 -0500
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-09-25 00:56 -0400
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-25 05:23 +0000
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Ant <ant@zimage.comANT> - 2015-09-26 05:00 -0700
                    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-26 16:41 +0000
                      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Andreas Rutishauser <andreas@macandreas.ch> - 2015-09-27 07:24 +0200
                        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Jolly Roger <jollyroger@pobox.com> - 2015-09-27 16:44 +0000
                    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-09-26 13:59 -0400
    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... nospam <nospam@nospam.invalid> - 2015-09-23 19:23 -0400
      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 19:38 -0500
        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 01:20 +0000
          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 20:24 -0500
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 01:27 +0000
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 22:17 -0500
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 14:57 +0000
        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-24 12:32 +0000
          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:14 +0000
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-24 10:57 -0500
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 16:00 +0000
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-24 11:27 -0500
    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 00:28 +0000
      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 19:44 -0500
        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 01:22 +0000
          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 20:25 -0500
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 22:58 -0500
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 14:59 +0000
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-24 11:00 -0500
    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Your Name <YourName@YourISP.com> - 2015-09-24 13:25 +1200
      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-23 20:28 -0500
    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-24 12:29 +0000
      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-24 15:11 +0000
      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-24 11:21 -0500
        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-25 06:07 +0000
          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Ant <ant@zimage.comANT> - 2015-09-26 05:02 -0700
            Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-26 16:27 +0000
              Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-27 19:22 -0500
                Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-28 03:37 +0000
                  Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-27 22:45 -0500
                    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... David Ritz <dritz@mindspring.com> - 2015-09-27 23:17 -0500
                      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... ANTant@zimage.com (Ant) - 2015-09-27 23:22 -0500
                        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... David Ritz <dritz@mindspring.com> - 2015-09-27 23:50 -0500
                        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... nospam <nospam@nospam.invalid> - 2015-09-28 01:49 -0400
                    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Michael Vilain <vilain@NOspamcop.net> - 2015-09-27 21:26 -0700
                      Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... nospam <nospam@nospam.invalid> - 2015-09-28 01:49 -0400
                        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-28 06:05 +0000
                          Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... nospam <nospam@nospam.invalid> - 2015-09-28 02:09 -0400
                        Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-28 07:28 +0000
                          Re: Apple Store's appointments (was A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests...) ANTant@zimage.com (Ant) - 2015-09-28 02:41 -0500
                            Re: Apple Store's appointments (was A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests...) Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-28 09:27 +0000
                              Re: Apple Store's appointments (was A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests...) ANTant@zimage.com (Ant) - 2015-09-28 07:25 -0500
                                Re: Apple Store's appointments (was A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests...) nospam <nospam@nospam.invalid> - 2015-09-28 12:18 -0400
                    Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... Jolly Roger <jollyroger@pobox.com> - 2015-09-28 05:03 +0000

Page 3 of 5 — ← Prev page 1 2 [3] 4 5  Next page →


#80565 — Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!

FromJF Mezei <jfmezei.spamnot@vaxination.ca>
Date2015-09-25 00:56 -0400
SubjectRe: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!
Message-ID<5604d3f0$0$4059$c3e8da3$12bcf670@news.astraweb.com>
In reply to#80482
On 15-09-24 11:58, Jolly Roger wrote:

> Repair will cause Disk Utility to attempt to *modify* the disk before
> you have had a chance to read the output to determine what is wrong.

If Disk Utility is unable to read a disk block, it won't attempt to fix
it since it can't write to it.

The "repair" only applies to the file system (some lost files not in any
directories, some catalog bits not set properly etc).  I suspect that
Disk Utility will not detect a few corrupt blocks inside a file.

Yes, you can run "Verify" first. However, it will take twice as long.
The problem is that if you run Verify and then Repair, you double the
number of disk operations that get done and if the disk is on its last
legs, you may not want to do this.

In fact, if you have a spare disk, I would do a disk backup on the
device (dismount the disk and do the disk image on the drive, using Disk
Utility).

Once you have the backup done, you can play with the new drive to do
Verify/repair etc.

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


#80571 — Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-25 05:23 +0000
SubjectRe: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!
Message-ID<d6k421Fc5eoU12@mid.individual.net>
In reply to#80565
On 2015-09-25, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 15-09-24 11:58, Jolly Roger wrote:
>
>> Repair will cause Disk Utility to attempt to *modify* the disk before
>> you have had a chance to read the output to determine what is wrong.
>
> If Disk Utility is unable to read a disk block, it won't attempt to fix
> it since it can't write to it.

Irrelevant to my point above.

> The "repair" only applies to the file system (some lost files not in any
> directories, some catalog bits not set properly etc).  I suspect that
> Disk Utility will not detect a few corrupt blocks inside a file.

Again, irrelevant. Your assumption that this volume must have bad blocks
is premature and based on ignorance. We do not know what is wrong with
the volume, which is why it is best not to attempt modification which
may result in data loss.

> Yes, you can run "Verify" first. However, it will take twice as long.

Wrong. Verify operations actually take less time than Repair operations
because repairs naturally take time to make. Without the repairs, there
is less to do, which means the operation finishes faster.

> The problem is that if you run Verify and then Repair, you double the
> number of disk operations that get done and if the disk is on its last
> legs, you may not want to do this.

If you want to determine what is wrong with the volume you have to
verify it, silly. Otherwise you might as well just throw the drive away,
which is just plain silly.

> In fact, if you have a spare disk, I would do a disk backup on the
> device (dismount the disk and do the disk image on the drive, using Disk
> Utility).

He already has a backup. Please pay better attention.

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


#80682 — Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!

FromAnt <ant@zimage.comANT>
Date2015-09-26 05:00 -0700
SubjectRe: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!
Message-ID<V66dnXcOCvNKFZvLnZ2dnUU7-WednZ2d@earthlink.com>
In reply to#80571
>> Yes, you can run "Verify" first. However, it will take twice as long.
>
> Wrong. Verify operations actually take less time than Repair operations
> because repairs naturally take time to make. Without the repairs, there
> is less to do, which means the operation finishes faster.

How long does verifications usually take? I tried it on my work's MBP 
(Retina; 2013)'s 250 GB SSD and it took a couple minutes. I hope it is a 
few minutes for an old HDD (forgot how big it was -- under a TB?) from 2012.


>> The problem is that if you run Verify and then Repair, you double the
>> number of disk operations that get done and if the disk is on its last
>> legs, you may not want to do this.
>
> If you want to determine what is wrong with the volume you have to
> verify it, silly. Otherwise you might as well just throw the drive away,
> which is just plain silly.
>
>> In fact, if you have a spare disk, I would do a disk backup on the
>> device (dismount the disk and do the disk image on the drive, using Disk
>> Utility).
>
> He already has a backup. Please pay better attention.

Yep, Time Machine. I hope it is a good backup to restore from! I have 
never restored fully from a TM before though. :/
-- 
"The sun's just a big glass, we're all ants, I LOVE YOU." --"Magnified" 
song by the Failure band
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.
    /\___/\         Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
   / /\ /\ \                Ant's Quality Foraged Links: http://aqfl.net
  | |o   o| |
     \ _ /        If crediting, then use Ant nickname and AQFL URL/link.
      ( )              Chop ANT from its address if e-mailing privately.
Ant is currently not listening to any songs on this computer.

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


#80695 — Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-26 16:41 +0000
SubjectRe: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!
Message-ID<d6o05vFcfoiU7@mid.individual.net>
In reply to#80682
On 2015-09-26, Ant <ant@zimage.comANT> wrote:
>
> How long does verifications usually take? I tried it on my work's MBP 
> (Retina; 2013)'s 250 GB SSD and it took a couple minutes. I hope it is a 
> few minutes for an old HDD (forgot how big it was -- under a TB?) from 2012.

It will definitely take longer than your SSD. Hard drives will *always*
be much slower than SSDs.  The older the hard drive, the slower it is.
Also, if the hard drive is a 5400 RPM drive, it will be much slower than
a 7200 RPM drive. And the size of the drive naturally effects how long
surface scans will take (a 250GB drive will scan much faster than a 4TB
drive). With that said, you're probably right that it's smaller than 1TB
(probably more like 250 or 500, or possibly 750 GB). So you are probably
looking at 20 minutes to an hour or so, depending.

> Yep, Time Machine. I hope it is a good backup to restore from! I have 
> never restored fully from a TM before though. :/

It's not hard. The basic steps are install the new hard drive in the
computer, connect the Time Machine backup drive to the computer, reboot
while holding down the Command-R keys to boot on the recovery partition,
and then follow the prompts to restore from the backup.

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


#80761 — Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!

FromAndreas Rutishauser <andreas@macandreas.ch>
Date2015-09-27 07:24 +0200
SubjectRe: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!
Message-ID<andreas-2E3448.07240927092015@news.individual.de>
In reply to#80695
Salut Jolly

In article <d6o05vFcfoiU7@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2015-09-26, Ant <ant@zimage.comANT> wrote:

> > Yep, Time Machine. I hope it is a good backup to restore from! I have 
> > never restored fully from a TM before though. :/
> 
> It's not hard. The basic steps are install the new hard drive in the
> computer, connect the Time Machine backup drive to the computer, reboot
> while holding down the Command-R keys to boot on the recovery partition,
> and then follow the prompts to restore from the backup.

will this work as you decribe it? From what recovery partition do you 
want to boot? The new drive does not have one, Time Macine drives don't 
have one as far as I know...
Good news though: since about 10.7.2 you can boot from a Time Machine 
backup (keep the option key pressed at boot and select the time Machine 
drive).
Use Disk Utility to "format" the new drive 
Quit Disk Utility
Restore from Time Machine Backup (a recovery partition will be installed 
on the new drive in the process)

Cheers
Andreas

-- 
MacAndreas Rutishauser, <http://www.MacAndreas.ch> 
EDV-Dienstleistungen, Hard- und Software, Internet und Netzwerk
Beratung, Unterstuetzung und Schulung
<mailto:andreas@MacAndreas.ch>, Fon: 044 / 721 36 47

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


#80789 — Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-27 16:44 +0000
SubjectRe: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!
Message-ID<d6qknhF2b10U3@mid.individual.net>
In reply to#80761
On 2015-09-27, Andreas Rutishauser <andreas@macandreas.ch> wrote:
> Salut Jolly
>
> In article <d6o05vFcfoiU7@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
>
>> On 2015-09-26, Ant <ant@zimage.comANT> wrote:
>
>> > Yep, Time Machine. I hope it is a good backup to restore from! I have 
>> > never restored fully from a TM before though. :/
>> 
>> It's not hard. The basic steps are install the new hard drive in the
>> computer, connect the Time Machine backup drive to the computer, reboot
>> while holding down the Command-R keys to boot on the recovery partition,
>> and then follow the prompts to restore from the backup.
>
> will this work as you decribe it? From what recovery partition do you 
> want to boot? The new drive does not have one, Time Macine drives don't 
> have one as far as I know...

If you don't have a recovery partition, assuming you have a recent Mac
(mid-2011 or later) connected to the internet, you can use Internet
Recovery instead by holding down the Command-Option-R keys at startup.

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


#80699 — Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!

FromJF Mezei <jfmezei.spamnot@vaxination.ca>
Date2015-09-26 13:59 -0400
SubjectRe: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup!
Message-ID<5606dcf5$0$1725$c3e8da3$f017e9df@news.astraweb.com>
In reply to#80682
On 15-09-26 08:00, Ant wrote:

> How long does verifications usually take?


Disk Utility is just an application. It issues IOs and waits for IO to
complete.

Normally, the disk responds very quickly.

But when there is a hardware problem, the disk will attempt to reread
the requested sector(s) and number of times before reporting back on a
failed IO (which you see in your verbose boot). In such cases, the
application (Disk Utility) will slow down considerably.

The disk driver (and the disk drive) doesn't know about files. it knows
about disk blocks.  Obviously, if the file system has a bug and asks to
read beyond the highest disk block available, that too would generate an
IO error.

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


#80318

Fromnospam <nospam@nospam.invalid>
Date2015-09-23 19:23 -0400
Message-ID<230920151923114515%nospam@nospam.invalid>
In reply to#80316
In article <JOednbDWmv12r57LnZ2dnUU7-Yv46u6z@earthlink.com>, Ant
<ANTant@zimage.com> wrote:

> As of a few hours ago after travelling far away (somewhere in Europe) 
> and using it briefly in his hotel room, my client's 13.3" MBP no longer 
> boots up fully to its updated Mac OS X v10.8.5. It gets stuck at the 
> gray Apple logo with its spinning indicator as shown in his blurry 
> iPhone photo(graph): http://i.imgur.com/uOP2XkC.jpg ... It never gets to 
> the login screen.
> 
> Over the phone and e-mails, we briefly tried safe mode but it showed the 
> same results but at slower speeds which is expected. I told him to boot 
> it up with D key held down for its hardware test. He ran the tests, but 
> he said it got stuck too as shown in http://i.imgur.com/VQ6Yy8s.jpg 
> since the status bar and time werne't changing. I told him to let it run 
> longer just in case it is slow like when he is asleep (night time now). 
> If it is indeed stuck, then it seems like his RAM went bad based on that 
> screen?

if aht failed, it have serious problems.

> My next idea is to have him do a Command and V keys. I basically want to 
> see its boot up screen show all of its technical texts on his screen and 
> where it gets stuck at if any. If it does show them and getting stuck 
> after a while, then to get a picture and send it to me so others and I 
> can read and plan what to try next. What else to try remotely for him? 
> He's not a technical computer user so it needs to be simple and share 
> with his iPhone's camera for us.

worth a shot but it looks like a hardware issue.

> Ironically, his AppleCare just ended after getting it over three years 
> ago (late summer of 2012) so it will probably be expensive to repair or 
> buy a new MBP if I can't fix it next week. :(

if applecare just ended then they might fix it anyway for no cost.

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


#80391

FromANTant@zimage.com (Ant)
Date2015-09-23 19:38 -0500
Message-ID<iZWdnWOZwplt2J7LnZ2dnUU7-dOdnZ2d@earthlink.com>
In reply to#80318
In comp.sys.mac.portables nospam <nospam@nospam.invalid> wrote:
> In article <JOednbDWmv12r57LnZ2dnUU7-Yv46u6z@earthlink.com>, Ant
> <ANTant@zimage.com> wrote:

> > As of a few hours ago after travelling far away (somewhere in Europe) 
> > and using it briefly in his hotel room, my client's 13.3" MBP no longer 
> > boots up fully to its updated Mac OS X v10.8.5. It gets stuck at the 
> > gray Apple logo with its spinning indicator as shown in his blurry 
> > iPhone photo(graph): http://i.imgur.com/uOP2XkC.jpg ... It never gets to 
> > the login screen.
> > 
> > Over the phone and e-mails, we briefly tried safe mode but it showed the 
> > same results but at slower speeds which is expected. I told him to boot 
> > it up with D key held down for its hardware test. He ran the tests, but 
> > he said it got stuck too as shown in http://i.imgur.com/VQ6Yy8s.jpg 
> > since the status bar and time werne't changing. I told him to let it run 
> > longer just in case it is slow like when he is asleep (night time now). 
> > If it is indeed stuck, then it seems like his RAM went bad based on that 
> > screen?

> if aht failed, it have serious problems.

Great. I wonder what it is. I told it sounded bad if it got stuck on the 
tests. :( Maybe something broke while travelling or overheated due to 
the recent heat waves (100+F degrees weather). I'm waiting for his 
results from his test.


> > My next idea is to have him do a Command and V keys. I basically want to 
> > see its boot up screen show all of its technical texts on his screen and 
> > where it gets stuck at if any. If it does show them and getting stuck 
> > after a while, then to get a picture and send it to me so others and I 
> > can read and plan what to try next. What else to try remotely for him? 
> > He's not a technical computer user so it needs to be simple and share 
> > with his iPhone's camera for us.

> worth a shot but it looks like a hardware issue.

:(


> > Ironically, his AppleCare just ended after getting it over three years 
> > ago (late summer of 2012) so it will probably be expensive to repair or 
> > buy a new MBP if I can't fix it next week. :(

> if applecare just ended then they might fix it anyway for no cost.

OK, we'll try it if it is not fixed by next week. I told him to go to an 
Apple store in Europe, he said no. Bah.
-- 
Quote of the Week: "When I am at my lowest, that is when I see things 
the clearest. It's hard to care about ants when you're soaring with 
eagles." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
  /\___/\   Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
 / /\ /\ \                 Ant's Quality Foraged Links: http://aqfl.net
| |o   o| |
   \ _ /    Please nuke ANT if replying by e-mail privately. If credit-
    ( )     ing, then please kindly use Ant nickname and AQFL URL/link.

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


#80409

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-24 01:20 +0000
Message-ID<d6h1f5Fk9a4U8@mid.individual.net>
In reply to#80391
On 2015-09-24, Ant <ANTant@zimage.com> wrote:
> In comp.sys.mac.portables nospam <nospam@nospam.invalid> wrote:
>> In article <JOednbDWmv12r57LnZ2dnUU7-Yv46u6z@earthlink.com>, Ant
>> <ANTant@zimage.com> wrote:
>
>>> I told him to boot it up with D key held down for its hardware test.
>>> He ran the tests, but he said it got stuck too as shown in
>>> http://i.imgur.com/VQ6Yy8s.jpg since the status bar and time werne't
>>> changing. I told him to let it run longer just in case it is slow
>>> like when he is asleep (night time now).  If it is indeed stuck,
>>> then it seems like his RAM went bad based on that screen?
>
>> if aht failed, it have serious problems.
>
> Great. I wonder what it is. I told it sounded bad if it got stuck on the 
> tests. :(

Who says it was stuck? You only let it run for one minute and 44 seconds
before you made that assumption and canceled the tests. The user
interface, as you should realize by the appearance, is very minimal,
meaning often during hardware tests it may *appear* nothing is happening
because nothing is changing on the screen. That doesn't mean nothing is
happening.

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


#80413

FromANTant@zimage.com (Ant)
Date2015-09-23 20:24 -0500
Message-ID<GfWdnUVJ0qtKzZ7LnZ2dnUU7-cWdnZ2d@earthlink.com>
In reply to#80409
> >>> I told him to boot it up with D key held down for its hardware test.
> >>> He ran the tests, but he said it got stuck too as shown in
> >>> http://i.imgur.com/VQ6Yy8s.jpg since the status bar and time werne't
> >>> changing. I told him to let it run longer just in case it is slow
> >>> like when he is asleep (night time now).  If it is indeed stuck,
> >>> then it seems like his RAM went bad based on that screen?
> >
> >> if aht failed, it have serious problems.
> >
> > Great. I wonder what it is. I told it sounded bad if it got stuck on the 
> > tests. :(

> Who says it was stuck? You only let it run for one minute and 44 seconds
> before you made that assumption and canceled the tests. The user
> interface, as you should realize by the appearance, is very minimal,
> meaning often during hardware tests it may *appear* nothing is happening
> because nothing is changing on the screen. That doesn't mean nothing is
> happening.

No, he said it was frozen at 1 minute and 44 seconds for a long time. I 
told him to let it run for hours in case it is still working like 
overnight when he sleeps.
-- 
Quote of the Week: "When I am at my lowest, that is when I see things 
the clearest. It's hard to care about ants when you're soaring with 
eagles." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
  /\___/\   Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
 / /\ /\ \                 Ant's Quality Foraged Links: http://aqfl.net
| |o   o| |
   \ _ /    Please nuke ANT if replying by e-mail privately. If credit-
    ( )     ing, then please kindly use Ant nickname and AQFL URL/link.

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


#80416

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-24 01:27 +0000
Message-ID<d6h1rqFk9a4U11@mid.individual.net>
In reply to#80413
On 2015-09-24, Ant <ANTant@zimage.com> wrote:
>> >>> I told him to boot it up with D key held down for its hardware test.
>> >>> He ran the tests, but he said it got stuck too as shown in
>> >>> http://i.imgur.com/VQ6Yy8s.jpg since the status bar and time werne't
>> >>> changing. I told him to let it run longer just in case it is slow
>> >>> like when he is asleep (night time now).  If it is indeed stuck,
>> >>> then it seems like his RAM went bad based on that screen?
>> >
>> >> if aht failed, it have serious problems.
>> >
>> > Great. I wonder what it is. I told it sounded bad if it got stuck on the 
>> > tests. :(
>
>> Who says it was stuck? You only let it run for one minute and 44 seconds
>> before you made that assumption and canceled the tests. The user
>> interface, as you should realize by the appearance, is very minimal,
>> meaning often during hardware tests it may *appear* nothing is happening
>> because nothing is changing on the screen. That doesn't mean nothing is
>> happening.
>
> No, he said it was frozen at 1 minute and 44 seconds for a long time.

Again, that doesn't necessarily mean nothing was happening.

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


#80436

FromANTant@zimage.com (Ant)
Date2015-09-23 22:17 -0500
Message-ID<F_ydnRjkM8vI9p7LnZ2dnUU7-WmdnZ2d@earthlink.com>
In reply to#80416
> >> >>> I told him to boot it up with D key held down for its hardware test.
> >> >>> He ran the tests, but he said it got stuck too as shown in
> >> >>> http://i.imgur.com/VQ6Yy8s.jpg since the status bar and time werne't
> >> >>> changing. I told him to let it run longer just in case it is slow
> >> >>> like when he is asleep (night time now).  If it is indeed stuck,
> >> >>> then it seems like his RAM went bad based on that screen?
> >> >
> >> >> if aht failed, it have serious problems.
> >> >
> >> > Great. I wonder what it is. I told it sounded bad if it got stuck on the 
> >> > tests. :(
> >
> >> Who says it was stuck? You only let it run for one minute and 44 seconds
> >> before you made that assumption and canceled the tests. The user
> >> interface, as you should realize by the appearance, is very minimal,
> >> meaning often during hardware tests it may *appear* nothing is happening
> >> because nothing is changing on the screen. That doesn't mean nothing is
> >> happening.
> >
> > No, he said it was frozen at 1 minute and 44 seconds for a long time.

> Again, that doesn't necessarily mean nothing was happening.

Bad news after about five/5 hours of the test running with his e-mailed 
"Same result, frozen, the screen shot is the same as before..." comment. 
:(

I'm waiting for his command+v verbose picture to see what the last 
several lines show for more clues.
-- 
Quote of the Week: "When I am at my lowest, that is when I see things 
the clearest. It's hard to care about ants when you're soaring with 
eagles." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
  /\___/\   Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
 / /\ /\ \                 Ant's Quality Foraged Links: http://aqfl.net
| |o   o| |
   \ _ /    Please nuke ANT if replying by e-mail privately. If credit-
    ( )     ing, then please kindly use Ant nickname and AQFL URL/link.

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


#80467

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-24 14:57 +0000
Message-ID<d6ihauF1tc3U1@mid.individual.net>
In reply to#80436
On 2015-09-24, Ant <ANTant@zimage.com> wrote:
>
> Bad news after about five/5 hours of the test running with his e-mailed 
> "Same result, frozen, the screen shot is the same as before..." comment. 
>:(

That is bad news.  : (

> I'm waiting for his command+v verbose picture to see what the last 
> several lines show for more clues.

Yeah, that would be useful.

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


#80456

FromLewis <g.kreme@gmail.com.dontsendmecopies>
Date2015-09-24 12:32 +0000
Message-ID<slrnn07rf2.b8g.g.kreme@amelia.local>
In reply to#80391
In message <iZWdnWOZwplt2J7LnZ2dnUU7-dOdnZ2d@earthlink.com> 
  Ant <ANTant@zimage.com> wrote:
> OK, we'll try it if it is not fixed by next week. I told him to go to an 
> Apple store in Europe, he said no. Bah.

Ah, so he is a fool.

He can try the "It failed while I was in Europe" tack when he gets back
and that might work, but every day out of AppleCare reduces the odds
that Apple will extend AppleCare for him.


-- 
On 20-12-2013 Wes Groleau wrote:
>On 12-20-2013, 10:04, George Kerby wrote:
>> 'Tis the Season to bitch and moan.
 
> That doesn't fit the tune you @#$%#$&%$*#$@%T#^% !

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


#80473

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-24 15:14 +0000
Message-ID<d6iialF1tc3U7@mid.individual.net>
In reply to#80456
On 2015-09-24, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
> In message <iZWdnWOZwplt2J7LnZ2dnUU7-dOdnZ2d@earthlink.com> 
>   Ant <ANTant@zimage.com> wrote:
>> OK, we'll try it if it is not fixed by next week. I told him to go to an 
>> Apple store in Europe, he said no. Bah.
>
> Ah, so he is a fool.

I don't think name calling is very productive or called for here. He may
have legitimate reasons for not bringing it to an Apple retail store -
perhaps due to travelling distance or convenience. Or maybe he's just
not in that big if a hurry and wants to ensure that he doesn't have to
hang around for a week waiting for Apple to release his machine. : )

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


#80481

FromANTant@zimage.com (Ant)
Date2015-09-24 10:57 -0500
Message-ID<2LadnX_oYewfgJnLnZ2dnUU7-Y_46u6z@earthlink.com>
In reply to#80473
> >> OK, we'll try it if it is not fixed by next week. I told him to go to an 
> >> Apple store in Europe, he said no. Bah.
> >
> > Ah, so he is a fool.

> I don't think name calling is very productive or called for here. He may
> have legitimate reasons for not bringing it to an Apple retail store -
> perhaps due to travelling distance or convenience. Or maybe he's just
> not in that big if a hurry and wants to ensure that he doesn't have to
> hang around for a week waiting for Apple to release his machine. : )

Another problem is that there are no Apple retail stores where he is. I 
didn't find any. Just third party authorized places. Also, he doesn't 
speak their local languages. At least, his iPhone with old iOS v8.4.1  
works. :P
-- 
Quote of the Week: "When I am at my lowest, that is when I see things 
the clearest. It's hard to care about ants when you're soaring with 
eagles." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
  /\___/\   Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
 / /\ /\ \                 Ant's Quality Foraged Links: http://aqfl.net
| |o   o| |
   \ _ /    Please nuke ANT if replying by e-mail privately. If credit-
    ( )     ing, then please kindly use Ant nickname and AQFL URL/link.

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


#80483

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-24 16:00 +0000
Message-ID<d6il00F1tc3U16@mid.individual.net>
In reply to#80481
On 2015-09-24, Ant <ANTant@zimage.com> wrote:
>> >> OK, we'll try it if it is not fixed by next week. I told him to go to an 
>> >> Apple store in Europe, he said no. Bah.
>> >
>> > Ah, so he is a fool.
>
>> I don't think name calling is very productive or called for here. He may
>> have legitimate reasons for not bringing it to an Apple retail store -
>> perhaps due to travelling distance or convenience. Or maybe he's just
>> not in that big if a hurry and wants to ensure that he doesn't have to
>> hang around for a week waiting for Apple to release his machine. : )
>
> Another problem is that there are no Apple retail stores where he is. I 
> didn't find any. Just third party authorized places. Also, he doesn't 
> speak their local languages. At least, his iPhone with old iOS v8.4.1  
> works. :P

Personally, I wouldn't bring it to anything but an actual Apple retail
store. Other places will likely want to charge for anything they do, and
sometimes can end up gouging the customer. Better to bring it into a
legitimate Apple retail store where there's a chance Apple will repair
it for free - even if it's no longer covered by warranty.

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


#80490

FromANTant@zimage.com (Ant)
Date2015-09-24 11:27 -0500
Message-ID<bYCdnR3MiKUSuZnLnZ2dnUU7-X-dnZ2d@earthlink.com>
In reply to#80483
> >> >> OK, we'll try it if it is not fixed by next week. I told him to go to an 
> >> >> Apple store in Europe, he said no. Bah.
> >> >
> >> > Ah, so he is a fool.
> >
> >> I don't think name calling is very productive or called for here. He may
> >> have legitimate reasons for not bringing it to an Apple retail store -
> >> perhaps due to travelling distance or convenience. Or maybe he's just
> >> not in that big if a hurry and wants to ensure that he doesn't have to
> >> hang around for a week waiting for Apple to release his machine. : )
> >
> > Another problem is that there are no Apple retail stores where he is. I 
> > didn't find any. Just third party authorized places. Also, he doesn't 
> > speak their local languages. At least, his iPhone with old iOS v8.4.1  
> > works. :P

> Personally, I wouldn't bring it to anything but an actual Apple retail
> store. Other places will likely want to charge for anything they do, and
> sometimes can end up gouging the customer. Better to bring it into a
> legitimate Apple retail store where there's a chance Apple will repair
> it for free - even if it's no longer covered by warranty.

I agree. Plus, they probably won't speak English!
-- 
Quote of the Week: "When I am at my lowest, that is when I see things 
the clearest. It's hard to care about ants when you're soaring with 
eagles." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
  /\___/\   Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
 / /\ /\ \                 Ant's Quality Foraged Links: http://aqfl.net
| |o   o| |
   \ _ /    Please nuke ANT if replying by e-mail privately. If credit-
    ( )     ing, then please kindly use Ant nickname and AQFL URL/link.

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


#80375

FromJolly Roger <jollyroger@pobox.com>
Date2015-09-24 00:28 +0000
Message-ID<d6gud9Fk9a4U2@mid.individual.net>
In reply to#80316
On 2015-09-23, Ant <ANTant@zimage.com> wrote:
>
> I told him to boot it up with D key held down for its hardware test.
> He ran the tests, but he said it got stuck too as shown in
> http://i.imgur.com/VQ6Yy8s.jpg since the status bar and time werne't
> changing.

From the photo, it appears the test had only been running for 1 minute
and 44 seconds. That's nowhere near enough time to give up on the test.
They can run quite a lot longer than that. 

> I told him to let it run longer just in case it is slow like when he
> is asleep (night time now). 

He should let it run at *least* 30 minutes before he thinks about
cancelling it. Hardware tests often take a long time. For instance, with
a computer with a lot of RAM installed, RAM tests can take a long time
to complete.

> If it is indeed stuck, then it seems like his RAM went bad based on
> that screen?

Nothing in the photo indicates RAM is an issue. He needs to let the test
run its course and see what it says when it is finished.

> My next idea is to have him do a Command and V keys. I basically want
> to see its boot up screen show all of its technical texts on his
> screen and where it gets stuck at if any. If it does show them and
> getting stuck after a while, then to get a picture and send it to me
> so others and I can read and plan what to try next. What else to try
> remotely for him?  He's not a technical computer user so it needs to
> be simple and share with his iPhone's camera for us.

I would be good to know if he can boot from the Apple recovery
partition, assuming he has one:

<https://support.apple.com/en-us/HT201314>

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


Page 3 of 5 — ← Prev page 1 2 [3] 4 5  Next page →

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


csiph-web