Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

'One Volume could not be repaired'.... need help

Sundance Kid

Sundance Kid

macrumors regular
Original poster
Feb 16, 2005
194
0
Canada
I performed a 'verify disk' from Disk Utility. It said the disk had minor problems, so I booted the computer from the intall disk and repaired it. So in red letters this it says: One Voluem Could not be Repaired. What do I do? I can't find out what to do on with the help from disk utility.

I'm really annoyed with this. I doesn't tell me what to do. Further more, the Mac Help from the finder doesn't seem to work. I just entered 'repairing disk' and its been searching for 10 minutes.


Any help would be appreciated.


edit: I have the latest version software for my 15' powerbook 1.5Ghz with 1 gig ram

edit2: I verified it again, and I still have the original problem:


Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
%)
Checking Extended Attributes file.
Reserved fields in the catalog record have incorrect data
Checking volume bitmap.
Checking volume information.
eeds to be repaired.",1)
Macintosh HD
Error: The underlying task reported failure on exit


1 HFS volume checked
Volume needs repair

......This is completely ridiculous.....
 
mad jew said:
Have you tried using fsck instead of the OSX disks? If the disk is pre-10.4.2 then fsck is definitely a better option. :)
Click to expand...

I said I was running the latest software. 10.4.5. that is.


Any help?
 
Well, what I'm saying is that unless your OSX disks are post-10.4.2, their Disk Utility repair function will be quite out of date which is why I recommend running fsck. :)
 
mad jew said:
Well, what I'm saying is that unless your OSX disks are post-10.4.2, their Disk Utility repair function will be quite out of date which is why I recommend running fsck. :)
Click to expand...

Arrgg. Ok, yeah.... got it. I have 10.3.7 here.... Does my tiger install disk count too? Like can i boot from it? (Ask this because i'm not quite sure where it is at the moment)


Ok, will do the fsck thing.
 
What I'm saying is that running the Disk Utility app from the disks is essentially the same as running fsck except that the underlying code is obviously not updated (it's stuck on the disk) which is why running fsck directly from the hard drive (which has Software Updater updating it periodically) is a better idea. :)

I had the same experience with my iBook but fsck resolved it.
 
mad jew said:
What I'm saying is that running the Disk Utility app from the disks is essentially the same as running fsck except that the underlying code is obviously not updated (it's stuck on the disk) which is why running fsck directly from the hard drive (which has Software Updater updating it periodically) is a better idea. :)

I had the same experience with my iBook but fsck resolved it.
Click to expand...


OK.... I don't know what to do. I went to the apple site, and read the crap.
I opened terminal and put this in: /sbin/fsck -fy

But nothing happened! help?


edit: And why isn't my MAC HELP not working at all?
 
mad jew said:
It's done through Single User Mode which involves starting up whilst holding COMMAND-S, not Terminal. :)
Click to expand...


yeah... lol... i overlooked that part.
And it worked, thx for you help.


But the damn Help Viewer still doesn't work. What do i do about that?
 
Well, it's a bit of an OSX bug. The best solution seems to be to delete everything in a folder named com.apple.helpui which can be found in your Caches folder, within your user's Library folder.

If that doesn't work, then try dragging com.apple.help.plist and com.apple.helpviewer.plist to the Desktop. You shouldn't need this second step though. :)
 
mad jew said:
Well, it's a bit of an OSX bug. The best solution seems to be to delete everything in a folder named com.apple.helpui which can be found in your Caches folder, within your user's Library folder.

If that doesn't work, then try dragging com.apple.help.plist and com.apple.helpviewer.plist to the Desktop. You shouldn't need this second step though. :)
Click to expand...


Yay! thx
 
mad jew said:
What I'm saying is that running the Disk Utility app from the disks is essentially the same as running fsck except that the underlying code is obviously not updated (it's stuck on the disk) which is why running fsck directly from the hard drive (which has Software Updater updating it periodically) is a better idea. :)
Click to expand...


I'm curious where you get this info?

My /sbin/fsck's date is March 20th 2005 on my box.

Definitely not up to date, in fact I'd wager it's about the same as DU on the DVD.

In fact, /usr/sbin/diskutil on the local is only slightly newer by 6 days than fsck. ANd the local DU is the newest as it's been modified Nov 2nd 2005.
 
There's nothing official from Apple but this outline of 10.4.2 kind of shows that those dates are irrelevant. Disk Utility in Tiger was definitely updated in June 2005 (or later, if you held off that update).

I'll keep working on the link but it's not on Apple because for safety reasons (people booting into Single User Mode isn't always the best idea), they prefer us to still use the OSX disks. :)
 
Disk Utility's (and diskutil's) ability to repair a drive is basically a repackaged form of fsck, so there shouldn't be any differece at all.
 
Yeah, I know but that's not what I've experienced. I've had OSX CDs and DVDs fail where fsck works. I've put the fact that it's not overly publicised down to the fact that Apple really doesn't like people using Single User Mode and therefore fsck.

I still haven't got anywhere on the link. I thought it was an OSX Hints article but that doesn't quite fit and I can't find it there. :eek:
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back