Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'File system journaling won't prevent all disk damage' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
File system journaling won't prevent all disk damage
Authored by: gmachen on Jan 16, '04 01:51:31PM

> To check a journalled startup disk you can also restart in single
> user mode (hold down Cmd-S at startup) and then type fsck -y

This command only will work for the startup volume (which mine wasn't).
While there is an arcane variant that works on non-startup volumes, who but students
of Unix with upmteen years under their belts will remember the procedure while in single-user mode?

If you think a GUI is for wimps, there's always Linux.



[ Reply to This | # ]
File system journaling won't prevent all disk damage
Authored by: dthorburn on Jan 16, '04 09:06:16PM
>To check a journalled startup disk you can also restart in single user mode (hold down Cmd-S at startup) and then type fsck -y

This command only will work for the startup volume (which mine wasn't).

By default, fsck will look at all volumes mentioned in the system's files system table (/etc/fstab according to the manual). You can also specify exactily which file system you want to check from the command line.

While there is an arcane variant that works on non-startup volumes, who but students of Unix with upmteen years under their belts will remember the procedure while in single-user mode?

Well, I have 10 years experience with Unix and I still can't remember all the options to all of the programs I use - especially fsck[*]. However I do know how to read a the online manual and find out.

Fortunately single-user mode still allows you to read the online manual.

If you think a GUI is for wimps, there's always Linux.

I'm sorry, I missed your point there .....

Douglas

[*] fsck is one of those programs that you don't want to have to run manually ;-)



[ Reply to This | # ]
File system journaling won't prevent all disk damage
Authored by: gmachen on Jan 17, '04 12:17:07AM

No! To repeat, ...

/sbin/fsck -y
or
/sbin/fsck -f

... only will address the startup drive.

To do an fsck on other drives, see the following arcane tutorial:

"How To Run fsck To Examine A Non-boot Volume In Mac OS X"

http://www.osxfaq.com/Tutorials/fsck/



[ Reply to This | # ]
File system journaling won't prevent all disk damage
Authored by: imageworx on Jan 19, '04 11:22:57AM

sbin/fsck -fy will repair a journaled startup volume

You can mount and repair other volumes but need to know the device name.

Personally, I turned journaling off as it does affect the performance. And I would not have journaling on anything but the startup volume (if you must).

OT: I have a Deskstar (aka deathstar) that once in awhile will make a noise. (rrrt rrrt rttt.....rrt rrrtt rrttt....rrrrt rrrtt rrrttt....) then go away. What is that? I'll get that when repairing permissions...or even when I ran Disk Warrior (latest). But nothing is found wrong. Should I replace the drive? SMART indicates the hardware is fine.


---
To BeOS or Not to BeOS



[ Reply to This | # ]
File system journaling won't prevent all disk damage
Authored by: gmachen on Jan 19, '04 12:12:36PM

After twenty years, I see that TheWormyFruitâ„¢ finally wised-up and its new Xserve G5
switched to ECC memory! It's about damn time! (Now if only we lowly consumers could
gain some protection against cosmic rays!)



[ Reply to This | # ]