 |
 |
fsck
|
 |
|
 |
|
Mac Elite
Join Date: Jul 2002
Location: Youngsville, NC
Status:
Offline
|
|
I was following the advice given by people from this forum, in various threads by running it until it 'clears'. I've been running fsck -y on my iMac pretty much all morning, still getting the ***** FILE SYSTEM WAS MODIFIED ***** statement when it's done. Just for kicks, I restarted this iBook, and it checked out fine the first go-around. I'm probably up to about 30 fsck's, should I keep going, or ?
10.2.6 iMac 700MHz G3 1GB, 10.2.6 iBook 500MHz G3 384MB
|
|
|
| |
|
|
|
 |
|
 |
|
Forum Regular
Join Date: Mar 1999
Location: Union,MO,USA
Status:
Offline
|
|
Have you repaired permissions also? If you've already done that you could try using Disk Warrior from Alsoft to rebuild the directory. You also mentioned rebooting and everything was fine the first go around. I'm presuming when you rebooted into single user mode again and ran fsck -y again you got the multiple system modified messages again. Is this the case? If so I'd definitely recommed getting Disk Warrior. Once you get Disk Warrior always follow this procedure: repair permissions first with Apple's Disk Utility, then run fsck -y, and finally run Disk Warrior. You can also run any other third party disk repair utility you have as a final step if needed.
|
|
It is better to light one candle than to curse the darkness
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Jul 2002
Location: Youngsville, NC
Status:
Offline
|
|
Hi,
Maybe I'm going about this wrong. I'm running fsck by holding down CMD-s at startup. I did this about 6 times last night, then ran repair permissions and put the machine to sleep. When I woke up, I rebooted, CMD-S, and have been fscking all day. Should I reboot, repair permissions and run it from terminal?
|
|
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Jul 2002
Location: Youngsville, NC
Status:
Offline
|
|
I was just told on IRC that I cannot run it from terminal. A fscking I will go 
|
|
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Nov 2001
Status:
Offline
|
|
yeh, i had this problem a while back. whilst there were no evident problems i did reformat and reinstall anyway, since it has been ok.
Unfortunately fsck isnt the greatest disk repair tool, norton or diskwarrior can fix things that fsck cant.
|
|
|
| |
|
|
|
 |
|
 |
|
Senior User
Join Date: Jun 2002
Status:
Offline
|
|
I encountered the same problem on my Cube. I ran fsck multiple times but continued to get the ** File System Was Modified ** statement. I purchased Disk Warrior, ran it once and whatever the problem was, it was repaired.
|
|
17" MacBook Pro 2.66 GHz Intel Core 2 Duo | 320G HD | 4 GB RAM | 10.7
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Jan 2001
Location: Kansas City, Mo
Status:
Offline
|
|
I got this awhile back on my iMac. I reinstalled the latest OS X version and everything was fine.
I did it like an upgrade. Just downloaded it from Apple and ran it. Everything was all better after that.
|
|
|
| |
|
|
|
 |
 |
|
 |
|
|
|
|
|

|
|
 |
Forum Rules
|
 |
 |
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
 |
 |
 |
 |
|
 |
|