I have a MacPro with a RAID1 disk (2x750GB Seagate).
Lately it had difficulty starting up, later announced it would rebuild
one slice of the RAID1. Then it did not start up.
I did a repair permissions, worked ok.
After that started up with installation disk and fired up Disk Utility.
First run: extent allocation wrong, etc.
Currently it does return this when run:
---
Invalid extent entry
Incorrect block count for file dup-i.yami
(It should be 1 instead of 4194305)
Overlapped node allocation
Volume check failed
Error: The underlying task reported failure on exit.
1 HFS volume checked
1 volume could not be repaired because of an error
First Aid failied
---
(Seagate ST3750540NS media, SMART status verified
Mirrored RAID Set, RAID Status Online, 2 slices)
What can I do?
TIA
Marc
(Desperately hoping for ZFS in Leopard ...)

Signature
Switzerland/Europe
<http://www.heusser.com>
remove CHEERS and from MERCIAL to get valid e-mail
In article <marc.heusser-D7508E.00533119062007@news.unizh.ch>,
Marc Heusser <marc.heusser@cheersheusser.commercialspammers.invalid>
wrote:
> I have a MacPro with a RAID1 disk (2x750GB Seagate).
> Lately it had difficulty starting up, later announced it would rebuild
[quoted text clipped - 10 lines]
> (It should be 1 instead of 4194305)
> Overlapped node allocation
Ouch. "Overlapped node allocation" is not a good problem; one part of
the directory has been mapped to more than one file.
> Volume check failed
>
[quoted text clipped - 9 lines]
>
> What can I do?
Try DiskWarrior. If that doesn't work, erase the volume and re-install
your data from your backups.

Signature
Photography, kink, polyamory, shareware, and more: all at
http://www.xeromag.com/franklin.html
Marc Heusser - 21 Jun 2007 22:19 GMT
> Try DiskWarrior. If that doesn't work, erase the volume and re-install
> your data from your backups.
Thanks for the tip.
I have DiskWarrior running - it has been running for 15 hours actually,
comparing directories now (about 300 GB of data, "7 million
comparisons"). Is it possible that it takes so long? Or do you suspect
an infinite loop?
TIA
Marc

Signature
Switzerland/Europe
<http://www.heusser.com>
remove CHEERS and from MERCIAL to get valid e-mail
Jolly Roger - 21 Jun 2007 23:55 GMT
>> Try DiskWarrior. If that doesn't work, erase the volume and re-install
>> your data from your backups.
[quoted text clipped - 5 lines]
> comparisons"). Is it possible that it takes so long? Or do you suspect
> an infinite loop?
It takes that long - depending on how much data and fragmentation, it
can take, literally, days. Don't touch it - let it do its thing.

Signature
JR
Marc Heusser - 22 Jun 2007 05:53 GMT
> > I have DiskWarrior running - it has been running for 15 hours actually,
> > comparing directories now (about 300 GB of data, "7 million
[quoted text clipped - 3 lines]
> It takes that long - depending on how much data and fragmentation, it
> can take, literally, days. Don't touch it - let it do its thing.
Thanks for the help.
I have the latest DW4.
Marc

Signature
Switzerland/Europe
<http://www.heusser.com>
remove CHEERS and from MERCIAL to get valid e-mail
Marc Heusser - 29 Jun 2007 19:29 GMT
> >> Try DiskWarrior. If that doesn't work, erase the volume and re-install
> >> your data from your backups.
[quoted text clipped - 8 lines]
> It takes that long - depending on how much data and fragmentation, it
> can take, literally, days. Don't touch it - let it do its thing.
It has been running now for a full week - 180 hours CPU, mostly
"comparing directories". In activity monitor it does appear normal
(not hung), and system CPU load on the 4 cores shifts from time to
time, which looks pretty normal. Still - is it possible that it runs
for so long, or is it in an infinite loop? When would you expect it
to finish?
Or what would you recommend to do? Restart the hard way? ...
TIA
Marc

Signature
Switzerland/Europe
<http://www.heusser.com>
remove CHEERS and from MERCIAL to get valid e-mail
Jolly Roger - 29 Jun 2007 21:28 GMT
>>>> Try DiskWarrior. If that doesn't work, erase the volume and re-install
>>>> your data from your backups.
[quoted text clipped - 16 lines]
> to finish?
> Or what would you recommend to do? Restart the hard way? ...
Well, 300 GB is huge...
I don't own DiskWarrior. So I can't tell you how long 300 GB should
take. And I'm sure other factors can influence the speed (like
fragmentation, etc.).
If you are really concerned, give Alsoft a call and see what they think
about it.

Signature
JR
Little Sir Echo - 29 Jun 2007 21:37 GMT
> >>>> Try DiskWarrior. If that doesn't work, erase the volume and
> >>>> re-install
[quoted text clipped - 27 lines]
> If you are really concerned, give Alsoft a call and see what they think
> about it.
I don't have a 300GB HD but I do have DiskWarrior.
Another factor to consider is the amount of free space on the disk.
The less that is available, the longer it takes DW to do its job.
Try JR's suggestion and call or email Alsoft; I have found them to be very
helpful.
Tom Stiller - 29 Jun 2007 22:49 GMT
> >>>> Try DiskWarrior. If that doesn't work, erase the volume and re-install
> >>>> your data from your backups.
[quoted text clipped - 22 lines]
> take. And I'm sure other factors can influence the speed (like
> fragmentation, etc.).
The only time I encountered comparable DiskWarrior run times was when
there were a large number of cross-linked files on the drive. It takes
a long time to run down the extent lists and safely allocate new extents
for the files. I shouldn't have to say it, but if cross-linked files
are recovered, their contents must be verified.
> If you are really concerned, give Alsoft a call and see what they think
> about it.
J.J. O'Shea - 22 Jun 2007 00:06 GMT
>> Try DiskWarrior. If that doesn't work, erase the volume and re-install
>> your data from your backups.
>
> Thanks for the tip.
>
> I have DiskWarrior running
DW 3 or 4?
> - it has been running for 15 hours actually,
Sounds like 3. 4 is much faster.
> comparing directories now (about 300 GB of data, "7 million
> comparisons"). Is it possible that it takes so long? Or do you suspect
> an infinite loop?
DW 3 can take a _long_ time.

Signature
email to oshea dot j dot j at gmail dot com.