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

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

Re: Corrupted HD

Show all headers | View raw

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!

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

Thread

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

csiph-web