Welcome to the MacNN Forums.

KidRed · Jul 10, 2003, 11:09 PM

X froze on me, or it hung, forcing a hard reboot. So I went into single user to run fsck -y and under Jag its' not the sh-0.5 thing. So after running fsck -0y it shows some errors, bad block counts etc, but doesn't repair anything. Up top says the drive is read only. I thought fsck -y was suppose to repair issues? It won't. I keep typing fsck -y and it keeps repeating the same errors with no hint that it's attempting a repair. Why wont fsck -y repair it?

KidRed · Jul 10, 2003, 11:30 PM

Damn. I booted into um, a newer biuld of X and ran disk utility and it wouldn't complete verification because

Error: The underlying task reported failure on exit (-9972)

So I can't even verify the problem. So does this mean I'm screwed and need to start clean? If so, what, Copy Cloner is the best way to go? What about Tri-Backup 3 or I'mSafe? I want to copy EVERYTHING. I have 85% of my files root level.

-I forgot to mention, it runs fine, a little slow perhaps, but I botted into after the fsck -y wouldn't do anything. So it's not like I can't boot it an work in it.

Phoenix1701 · Jul 11, 2003, 01:27 AM

You have to manually mount the disk into read-write mode when you go into single user mode; otherwise you'll get that very problem. To do so, I believe the command is:

Code:
mount -uw /

That should allow you to do what you need to do, unless the volume in question is journaled. This might happen if you formatted it with that particular "um newer build" you mentioned... if that's the case, well, you're sort of out of luck as far as fsck goes.

Good luck!

silverghost · Jul 11, 2003, 06:13 AM

hi, if your volume has journal enabled then try /sbin/fsck -f , then /sbin/mount -uw /.

if that dont work maybe diskwarrior can help.

aloha

suthercd · Jul 11, 2003, 09:24 AM

In addition the the advice given, run /sbin/fsck -y again until you get a no errors found response. The -y turns on the option to repair without a user prompt, mounting the disk negates what fdisk does. To have it unmounted is why you boot into single user mode- some repairs cannot be made while the disk is mounted. The instructions that are there after booting into single user mode are correct- that's why they are there and in the order that is proper.

Fsck has not repaired bad blocks on my machines. You can try booting from the Install Disk 1 of OS X and running the Disk Utility, but that has not always been a complete fix. Third party utilities like Diskwarrior do the best job and do not require a system and backup re-install.

Carbon Copy Cloner has been an excellent resource- allowing mirror backups w/permissions intact.

HTH
Craig

KidRed · Jul 11, 2003, 09:52 AM

Originally posted by Phoenix1701:
You have to manually mount the disk into read-write mode when you go into single user mode; otherwise you'll get that very problem. To do so, I believe the command is:

Code:
mount -uw /

That should allow you to do what you need to do, unless the volume in question is journaled. This might happen if you formatted it with that particular "um newer build" you mentioned... if that's the case, well, you're sort of out of luck as far as fsck goes.

Good luck!

Yea, I have journeling enabled, is that why i cant run fsck -y? So, I assume that if I disable journaling that I should be able to run fsck -y? I'm not holding my breathe as running Disk Utility would not verify the drive due to an error. So, I'm not sure fsck -y can either.