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

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

Corrupted HD

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

Contents

  Corrupted HD RonTheGuy@null.invalid (Ron) - 2013-11-11 17:00 -0800
    Re: Corrupted HD Wes Groleau <Groleau+news@FreeShell.org> - 2013-11-11 20:20 -0500
    Re: Corrupted HD nospam <nospam@nospam.invalid> - 2013-11-11 21:23 -0500
      Re: Corrupted HD RonTheGuy@null.invalid (Ron) - 2013-11-11 21:27 -0800
        Re: Corrupted HD nospam <nospam@nospam.invalid> - 2013-11-12 00:36 -0500
        Re: Corrupted HD me@home.spamsucks.ca (Király) - 2013-11-12 06:06 +0000
          Re: Corrupted HD "M. John Matlaw" <nouser@invalid.com> - 2013-11-12 15:05 -0500
    Re: Corrupted HD Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2013-11-11 20:51 -0800
      Re: Corrupted HD nospam <nospam@nospam.invalid> - 2013-11-12 00:26 -0500
      Re: Corrupted HD jamiekg@wizardling.geek.nz (Jamie Kahn Genet) - 2013-11-12 19:46 +1300
        Re: Corrupted HD Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2013-11-11 23:08 -0800
          Re: Corrupted HD nospam <nospam@nospam.invalid> - 2013-11-12 02:46 -0500
            Re: Corrupted HD George Kerby <ghost_topper@hotmail.com> - 2013-11-12 07:55 -0600
            Re: Corrupted HD Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2013-11-12 21:43 -0800
          Re: Corrupted HD George Kerby <ghost_topper@hotmail.com> - 2013-11-12 07:55 -0600
          Re: Corrupted HD "John Varela" <newlamps@verizon.net> - 2013-11-12 20:12 +0000
      Re: Corrupted HD Lewis <g.kreme@gmail.com.dontsendmecopies> - 2013-11-13 00:51 +0000
    Re: Corrupted HD Laszlo Lebrun <lazlo_lebrun@laszlomail.com> - 2013-11-12 21:22 +0100
      Re: Corrupted HD Wes Groleau <Groleau+news@FreeShell.org> - 2013-11-12 23:02 -0500
        Re: Corrupted HD Laszlo Lebrun <lazlo_lebrun@laszlomail.com> - 2013-11-13 05:26 +0100
          Re: Corrupted HD Wes Groleau <Groleau+news@FreeShell.org> - 2013-11-13 00:47 -0500
            Re: Corrupted HD Laszlo Lebrun <lazlo_lebrun@laszlomail.com> - 2013-11-13 21:00 +0100

Page 1 of 2  [1] 2  Next page →

#52147 — Corrupted HD

We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
because it was running really slow. DU sayd the disk was corrupted and
need to be repaired. What are my options? I'm pretty sure this laptop
didn't come with install disks, so I have nothing from which to boot
except the install disks that came with my MBP that have 10.6. Will that
work? 
TIA, Ron
-- 
_____________________________
Ron, the humblest guy in town

[toc] | [next] | [standalone]

#52148

On 11-11-2013, 20:00, Ron wrote:
> We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> because it was running really slow. DU sayd the disk was corrupted and
> need to be repaired. What are my options? I'm pretty sure this laptop
> didn't come with install disks, so I have nothing from which to boot
> except the install disks that came with my MBP that have 10.6. Will that
> work?

New disk.  Boot from CD.  Restore from backup.

If you don't have a backup, install 10.6 and run software update over 
and over until it stops telling you there's new stuff.


-- 
Wes Groleau

   Armchair Activism: http://www.breakthechain.org/armchair.html

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

#52149

In article <1lc6kdk.7xljiyi7d7c0N%RonTheGuy@null.invalid>, Ron
<RonTheGuy@null.invalid> wrote:

> We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> because it was running really slow. DU sayd the disk was corrupted and
> need to be repaired. What are my options?

disk warrior is your best bet:
<http://www.alsoft.com/DiskWarrior/index.html>

> I'm pretty sure this laptop
> didn't come with install disks,

it did.

> so I have nothing from which to boot
> except the install disks that came with my MBP that have 10.6. Will that
> work? 

probably not. the install disks that are bundled with a machine are
model specific. sometimes it works if the two systems are similar but a
white macbook and a macbook pro are probably different enough that it
will not.

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

#52156

nospam <nospam@nospam.invalid> wrote:

> In article <1lc6kdk.7xljiyi7d7c0N%RonTheGuy@null.invalid>, Ron
> <RonTheGuy@null.invalid> wrote:
> 
> > We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> > because it was running really slow. DU sayd the disk was corrupted and
> > need to be repaired. What are my options?
> 
> disk warrior is your best bet:
> <http://www.alsoft.com/DiskWarrior/index.html>
> 
> > I'm pretty sure this laptop
> > didn't come with install disks,
> 
> it did.
> 
> > so I have nothing from which to boot
> > except the install disks that came with my MBP that have 10.6. Will that
> > work? 
> 
> probably not. the install disks that are bundled with a machine are
> model specific. sometimes it works if the two systems are similar but a
> white macbook and a macbook pro are probably different enough that it
> will not.

I don't think this laptop came with DVDs; it was a refurb from Apple. At
least, I can't find them... 

The DU error msg said "Invalid Volume File Count"; does DiskWarrior fix
that sort of thing? 
-- 
_____________________________
Ron, the humblest guy in town

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

#52157

In article <1lc6wuq.mkg97crgpvv8N%RonTheGuy@null.invalid>, Ron
<RonTheGuy@null.invalid> wrote:

> I don't think this laptop came with DVDs; it was a refurb from Apple. At
> least, I can't find them... 

a mac that has 10.6 or earlier should have come with a dvd, regardless
whether it was a refurb or new.

macs with 10.7 and later have a recovery partition on the hard drive,
so there's no need for a dvd anymore. even new macs don't have a dvd. 

> The DU error msg said "Invalid Volume File Count"; does DiskWarrior fix
> that sort of thing?

definitely. it can fix nearly anything you can throw at it. 

sometimes it takes a while if the drive is *really* corrupted (hours,
sometimes days), but what you describe doesn't sound severe. 

apple's disk utility might be able to fix it, but diskwarrior checks a
*lot* more stuff (and fixes it), so it is really the way to go.

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

#52158

Ron <RonTheGuy@null.invalid> wrote:
> I don't think this laptop came with DVDs; it was a refurb from Apple. At
> least, I can't find them... 

Call Apple and ask for a replacement set. They will ask you for your 
Mac's serial number and send them out for a nominal S&H fee.

Diskwarrior is a good program but Disk Utility is all I've ever needed. 
If it ever doesn't do the job then I'll just reformat the disk and 
restore my data from backup. 

-- 
K.

Lang may your lum reek.

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

#52179

On 11/12/13, 1:06 AM, Király wrote:
> Ron <RonTheGuy@null.invalid> wrote:
>> I don't think this laptop came with DVDs; it was a refurb from Apple. At
>> least, I can't find them...
>
> Call Apple and ask for a replacement set. They will ask you for your
> Mac's serial number and send them out for a nominal S&H fee.
>
> Diskwarrior is a good program but Disk Utility is all I've ever needed.
> If it ever doesn't do the job then I'll just reformat the disk and
> restore my data from backup.
>
I'd echo this.  I got a 17 inch MacBook Pro from Apple refurb (the last 
one to run SL, I believe).  Came with Lion installed.  At some point I 
decided to partition it, run SL on one of the partitions and found out 
that it needed a machine specific DVD to install SL on the machine. 
Called Apple, explained the problem and they sent one free of charge and 
no shipping cost either.  Give 'em a call.  Can't hurt.

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

#52154

In article <1lc6kdk.7xljiyi7d7c0N%RonTheGuy@null.invalid>,
 RonTheGuy@null.invalid (Ron) wrote:

> We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> because it was running really slow. DU sayd the disk was corrupted and
> need to be repaired. What are my options? I'm pretty sure this laptop
> didn't come with install disks, so I have nothing from which to boot
> except the install disks that came with my MBP that have 10.6. Will that
> work? 
> TIA, Ron

I'd only use DiskWarrior as a last resort after everything is backed up.  
It's hacker-grade software that often refuses to run due to ridiculously 
bad assumptions about disk access timing.

The same software that Disk Utility runs is available on the command 
line.  Boot into "single user mode" by holding down cmd-S while booting.  
Single user mode starts with the disk mounted read-only so the OS won't 
interfere with repairs.  Type this:

fsck -fy


When it's done, press ctrl-D to resume normal booting.  If it fails you 
can try running fsck again.

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

#52155

In article
<mcmurtrie-8FBAAD.20515811112013@c-61-68-245-199.per.connect.net.au>,
Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:

> I'd only use DiskWarrior as a last resort after everything is backed up.  
> It's hacker-grade software that often refuses to run due to ridiculously 
> bad assumptions about disk access timing.

nonsense. diskwarrior is *extremely* well written and well tested
software and is almost always is able to repair directory corruption.
it has saved my butt on many occasions.

what it can't do is fix hardware failures, i.e., excessive bad blocks.
nothing can.

> The same software that Disk Utility runs is available on the command 
> line.

diskwarrior does significantly more than disk utility does.

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

#52159

Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:

> In article <1lc6kdk.7xljiyi7d7c0N%RonTheGuy@null.invalid>,
>  RonTheGuy@null.invalid (Ron) wrote:
> 
> > We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> > because it was running really slow. DU sayd the disk was corrupted and
> > need to be repaired. What are my options? I'm pretty sure this laptop
> > didn't come with install disks, so I have nothing from which to boot
> > except the install disks that came with my MBP that have 10.6. Will that
> > work? 
> > TIA, Ron
> 
> I'd only use DiskWarrior as a last resort after everything is backed up.
> It's hacker-grade software that often refuses to run due to ridiculously
> bad assumptions about disk access timing.
> 
> The same software that Disk Utility runs is available on the command 
> line.  Boot into "single user mode" by holding down cmd-S while booting.
> Single user mode starts with the disk mounted read-only so the OS won't
> interfere with repairs.  Type this:
> 
> fsck -fy
> 
> 
> When it's done, press ctrl-D to resume normal booting.  If it fails you
> can try running fsck again.

Rubbish. Diskwarrior often succeeds where Disk Utility failed, IME.
-- 
If you're not part of the solution, you're part of the precipitate.

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

#52160

In article <1lc8muq.1ell7wpz0alpaN%jamiekg@wizardling.geek.nz>,
 jamiekg@wizardling.geek.nz (Jamie Kahn Genet) wrote:

> Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> 
> > In article <1lc6kdk.7xljiyi7d7c0N%RonTheGuy@null.invalid>,
> >  RonTheGuy@null.invalid (Ron) wrote:
> > 
> > > We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> > > because it was running really slow. DU sayd the disk was corrupted and
> > > need to be repaired. What are my options? I'm pretty sure this laptop
> > > didn't come with install disks, so I have nothing from which to boot
> > > except the install disks that came with my MBP that have 10.6. Will that
> > > work? 
> > > TIA, Ron
> > 
> > I'd only use DiskWarrior as a last resort after everything is backed up.
> > It's hacker-grade software that often refuses to run due to ridiculously
> > bad assumptions about disk access timing.
> > 
> > The same software that Disk Utility runs is available on the command 
> > line.  Boot into "single user mode" by holding down cmd-S while booting.
> > Single user mode starts with the disk mounted read-only so the OS won't
> > interfere with repairs.  Type this:
> > 
> > fsck -fy
> > 
> > 
> > When it's done, press ctrl-D to resume normal booting.  If it fails you
> > can try running fsck again.
> 
> Rubbish. Diskwarrior often succeeds where Disk Utility failed, IME.

DiskWarrior incorrectly assumes that latency is caused by I/O errors, it 
incorrectly assumes that swapping will crash your computer, and it has 
to skip some steps on disk images to avoid crashing.  That means it 
can't repair large local Time Machine disks (aborts of virtual memory) 
and it can't reliably do any remote Time Machine disks (aborts on 
latency).

Early versions of 4.2 had a tendency to cause system crashes.  That 
would often corrupt the startup disk while attempting to fix an external 
disk.  Nice, eh?


Yes, DW can fix some things that fsck_hfs can't but that doesn't mean it 
isn't hacky crap.

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

#52161

In article
<mcmurtrie-BAB415.23084511112013@c-61-68-245-199.per.connect.net.au>,
Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:

> > > > We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> > > > because it was running really slow. DU sayd the disk was corrupted and
> > > > need to be repaired. What are my options? I'm pretty sure this laptop
> > > > didn't come with install disks, so I have nothing from which to boot
> > > > except the install disks that came with my MBP that have 10.6. Will that
> > > > work? 
> > > > TIA, Ron
> > > 
> > > I'd only use DiskWarrior as a last resort after everything is backed up.
> > > It's hacker-grade software that often refuses to run due to ridiculously
> > > bad assumptions about disk access timing.
> > > 
> > > The same software that Disk Utility runs is available on the command 
> > > line.  Boot into "single user mode" by holding down cmd-S while booting.
> > > Single user mode starts with the disk mounted read-only so the OS won't
> > > interfere with repairs.  Type this:
> > > 
> > > fsck -fy
> > > 
> > > When it's done, press ctrl-D to resume normal booting.  If it fails you
> > > can try running fsck again.
> > 
> > Rubbish. Diskwarrior often succeeds where Disk Utility failed, IME.
> 
> DiskWarrior incorrectly assumes that latency is caused by I/O errors, it 
> incorrectly assumes that swapping will crash your computer, and it has 
> to skip some steps on disk images to avoid crashing.  That means it 
> can't repair large local Time Machine disks (aborts of virtual memory) 
> and it can't reliably do any remote Time Machine disks (aborts on 
> latency).

nonsense. 

the only issue is that diskwarrior is still a 32 bit app, so it's
possible that some large drives with a *lot* of files can fill that
memory space. most people do not encounter this.

they've been working on a 64 bit version for a while and it takes time
to do it properly. 

> Early versions of 4.2 had a tendency to cause system crashes.  That 
> would often corrupt the startup disk while attempting to fix an external 
> disk.  Nice, eh?

nonsense. 

disk warrior does not write to the drive while reconstructing the
directory. the *only* time it modifies the hard drive is if the user
decides to write the newly rebuilt directory. that is *optional*.

the user can preview the drive using the new directory before writing
it out, or they can decide to not write it out at all. in the latter
case, the drive will be *exactly* the same as it was before the process
began. 

> Yes, DW can fix some things that fsck_hfs can't but that doesn't mean it 
> isn't hacky crap.

it definitely is not hacky crap. far from it.

it's one of the most amazing apps on the mac.

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

#52165

On 11/12/13 1:46 AM, in article 121120130246198560%nospam@nospam.invalid,
"nospam" <nospam@nospam.invalid> wrote:

> In article
> <mcmurtrie-BAB415.23084511112013@c-61-68-245-199.per.connect.net.au>,
> Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> 
>>>>> We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
>>>>> because it was running really slow. DU sayd the disk was corrupted and
>>>>> need to be repaired. What are my options? I'm pretty sure this laptop
>>>>> didn't come with install disks, so I have nothing from which to boot
>>>>> except the install disks that came with my MBP that have 10.6. Will that
>>>>> work? 
>>>>> TIA, Ron
>>>> 
>>>> I'd only use DiskWarrior as a last resort after everything is backed up.
>>>> It's hacker-grade software that often refuses to run due to ridiculously
>>>> bad assumptions about disk access timing.
>>>> 
>>>> The same software that Disk Utility runs is available on the command
>>>> line.  Boot into "single user mode" by holding down cmd-S while booting.
>>>> Single user mode starts with the disk mounted read-only so the OS won't
>>>> interfere with repairs.  Type this:
>>>> 
>>>> fsck -fy
>>>> 
>>>> When it's done, press ctrl-D to resume normal booting.  If it fails you
>>>> can try running fsck again.
>>> 
>>> Rubbish. Diskwarrior often succeeds where Disk Utility failed, IME.
>> 
>> DiskWarrior incorrectly assumes that latency is caused by I/O errors, it
>> incorrectly assumes that swapping will crash your computer, and it has
>> to skip some steps on disk images to avoid crashing.  That means it
>> can't repair large local Time Machine disks (aborts of virtual memory)
>> and it can't reliably do any remote Time Machine disks (aborts on
>> latency).
> 
> nonsense. 
> 
> the only issue is that diskwarrior is still a 32 bit app, so it's
> possible that some large drives with a *lot* of files can fill that
> memory space. most people do not encounter this.
> 
> they've been working on a 64 bit version for a while and it takes time
> to do it properly.
> 
>> Early versions of 4.2 had a tendency to cause system crashes.  That
>> would often corrupt the startup disk while attempting to fix an external
>> disk.  Nice, eh?
> 
> nonsense. 
> 
> disk warrior does not write to the drive while reconstructing the
> directory. the *only* time it modifies the hard drive is if the user
> decides to write the newly rebuilt directory. that is *optional*.
> 
> the user can preview the drive using the new directory before writing
> it out, or they can decide to not write it out at all. in the latter
> case, the drive will be *exactly* the same as it was before the process
> began. 
> 
>> Yes, DW can fix some things that fsck_hfs can't but that doesn't mean it
>> isn't hacky crap.
> 
> it definitely is not hacky crap. far from it.
> 
> it's one of the most amazing apps on the mac.

Exactly!

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

#52196

In article <121120130246198560%nospam@nospam.invalid>,
 nospam <nospam@nospam.invalid> wrote:

> In article
> <mcmurtrie-BAB415.23084511112013@c-61-68-245-199.per.connect.net.au>,
> Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> 
> > > > > We have a white MacBook running 10.6.8. I ran Disk Utility Verify 
> > > > > Disk
> > > > > because it was running really slow. DU sayd the disk was corrupted 
> > > > > and
> > > > > need to be repaired. What are my options? I'm pretty sure this laptop
> > > > > didn't come with install disks, so I have nothing from which to boot
> > > > > except the install disks that came with my MBP that have 10.6. Will 
> > > > > that
> > > > > work? 
> > > > > TIA, Ron
> > > > 
> > > > I'd only use DiskWarrior as a last resort after everything is backed 
> > > > up.
> > > > It's hacker-grade software that often refuses to run due to 
> > > > ridiculously
> > > > bad assumptions about disk access timing.
> > > > 
> > > > The same software that Disk Utility runs is available on the command 
> > > > line.  Boot into "single user mode" by holding down cmd-S while 
> > > > booting.
> > > > Single user mode starts with the disk mounted read-only so the OS won't
> > > > interfere with repairs.  Type this:
> > > > 
> > > > fsck -fy
> > > > 
> > > > When it's done, press ctrl-D to resume normal booting.  If it fails you
> > > > can try running fsck again.
> > > 
> > > Rubbish. Diskwarrior often succeeds where Disk Utility failed, IME.
> > 
> > DiskWarrior incorrectly assumes that latency is caused by I/O errors, it 
> > incorrectly assumes that swapping will crash your computer, and it has 
> > to skip some steps on disk images to avoid crashing.  That means it 
> > can't repair large local Time Machine disks (aborts of virtual memory) 
> > and it can't reliably do any remote Time Machine disks (aborts on 
> > latency).
> 
> nonsense. 
> 
> the only issue is that diskwarrior is still a 32 bit app, so it's
> possible that some large drives with a *lot* of files can fill that
> memory space. most people do not encounter this.
> 
> they've been working on a 64 bit version for a while and it takes time
> to do it properly. 

I'm a software developer and I call "bullshit".  You have completely 
screwed up if the number of address bits matters.


> > Early versions of 4.2 had a tendency to cause system crashes.  That 
> > would often corrupt the startup disk while attempting to fix an external 
> > disk.  Nice, eh?
> 
> nonsense. 
> 
Sure, all those release notes about fixing systems crashes are nonsense.


> disk warrior does not write to the drive while reconstructing the
> directory. the *only* time it modifies the hard drive is if the user
> decides to write the newly rebuilt directory. that is *optional*.
> 
> the user can preview the drive using the new directory before writing
> it out, or they can decide to not write it out at all. in the latter
> case, the drive will be *exactly* the same as it was before the process
> began. 
> 
> > Yes, DW can fix some things that fsck_hfs can't but that doesn't mean it 
> > isn't hacky crap.
> 
> it definitely is not hacky crap. far from it.
> 
> it's one of the most amazing apps on the mac.

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

#52164

On 11/12/13 1:08 AM, in article
mcmurtrie-BAB415.23084511112013@c-61-68-245-199.per.connect.net.au, "Kevin
McMurtrie" <mcmurtrie@pixelmemory.us> wrote:

> In article <1lc8muq.1ell7wpz0alpaN%jamiekg@wizardling.geek.nz>,
>  jamiekg@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> 
>> Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
>> 
>>> In article <1lc6kdk.7xljiyi7d7c0N%RonTheGuy@null.invalid>,
>>>  RonTheGuy@null.invalid (Ron) wrote:
>>> 
>>>> We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
>>>> because it was running really slow. DU sayd the disk was corrupted and
>>>> need to be repaired. What are my options? I'm pretty sure this laptop
>>>> didn't come with install disks, so I have nothing from which to boot
>>>> except the install disks that came with my MBP that have 10.6. Will that
>>>> work? 
>>>> TIA, Ron
>>> 
>>> I'd only use DiskWarrior as a last resort after everything is backed up.
>>> It's hacker-grade software that often refuses to run due to ridiculously
>>> bad assumptions about disk access timing.
>>> 
>>> The same software that Disk Utility runs is available on the command
>>> line.  Boot into "single user mode" by holding down cmd-S while booting.
>>> Single user mode starts with the disk mounted read-only so the OS won't
>>> interfere with repairs.  Type this:
>>> 
>>> fsck -fy
>>> 
>>> 
>>> When it's done, press ctrl-D to resume normal booting.  If it fails you
>>> can try running fsck again.
>> 
>> Rubbish. Diskwarrior often succeeds where Disk Utility failed, IME.
> 
> DiskWarrior incorrectly assumes that latency is caused by I/O errors, it
> incorrectly assumes that swapping will crash your computer, and it has
> to skip some steps on disk images to avoid crashing.  That means it
> can't repair large local Time Machine disks (aborts of virtual memory)
> and it can't reliably do any remote Time Machine disks (aborts on
> latency).
> 
> Early versions of 4.2 had a tendency to cause system crashes.  That
> would often corrupt the startup disk while attempting to fix an external
> disk.  Nice, eh?
> 
> 
> Yes, DW can fix some things that fsck_hfs can't but that doesn't mean it
> isn't hacky crap.

Bullshit. DW is some the best thought software available for the Mac since,
I believe, System 7.

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

#52180

On Tue, 12 Nov 2013 07:08:45 UTC, Kevin McMurtrie 
<mcmurtrie@pixelmemory.us> wrote:

> DiskWarrior incorrectly assumes that latency is caused by I/O errors, it 
> incorrectly assumes that swapping will crash your computer, and it has 
> to skip some steps on disk images to avoid crashing.  That means it 
> can't repair large local Time Machine disks (aborts of virtual memory) 
> and it can't reliably do any remote Time Machine disks (aborts on 
> latency).
 
Disk Warrior repaired a Time Machine for me after Disk Utility 
failed.

-- 
John Varela

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

#52189

In message <mcmurtrie-8FBAAD.20515811112013@c-61-68-245-199.per.connect.net.au> 
  Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> I'd only use DiskWarrior as a last resort after everything is backed up.  

Your choice, but...

> It's hacker-grade software that often refuses to run due to ridiculously 
> bad assumptions about disk access timing.

This is a flat-out lie.


-- 
"Why do you sit there looking like an envelope without any address on
it?" - Mark Twain

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

#52182

On 11/12/13 2:00 AM, Ron wrote:
> We have a white MacBook running 10.6.8. I ran Disk Utility Verify Disk
> because it was running really slow. DU sayd the disk was corrupted and
> need to be repaired. What are my options? I'm pretty sure this laptop
> didn't come with install disks, so I have nothing from which to boot
> except the install disks that came with my MBP that have 10.6. Will that
> work?
> TIA, Ron
>

Have you got another Mac at your disposal?
You could extract your drive, put it in a USB case and let it be checked 
from another MAC. Disk utility can repair external disks much better 
than the one from which it is running.

-- 
One computer and three operating systems, not the other way round.
One wife and many hotels, not the other way round ! ;-)

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

#52192

On 11-12-2013, 15:22, Laszlo Lebrun wrote:
> You could extract your drive, put it in a USB case and let it be checked
> from another MAC. Disk utility can repair external disks much better
> than the one from which it is running.

That's because it will not touch the one from which it is running.

Well, actually, it will not touch the startup disk, which is usually the 
one from which DU is running.

Select the boot disk in DU and the repair button will be disabled.

-- 
Wes Groleau

   I won't burn your Koran because I don't want you to burn my Bible;
   but if you burn my Bible, no one's going to die.
                                    — Robert Rhee

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

#52194

On 13.11.2013 05:02, Wes Groleau wrote:
> On 11-12-2013, 15:22, Laszlo Lebrun wrote:
>> You could extract your drive, put it in a USB case and let it be checked
>> from another MAC. Disk utility can repair external disks much better
>> than the one from which it is running.
>
> That's because it will not touch the one from which it is running.
>
> Well, actually, it will not touch the startup disk, which is usually the
> one from which DU is running.
>
> Select the boot disk in DU and the repair button will be disabled.
>
Yes, my words. If you can put the corrupted disk into another MAC Du 
will repair it neatly without reinstalling everything.

-- 
One computer and three operating systems, not the other way round.
One wife and many hotels, not the other way round ! ;-)

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web