PDA

View Full Version : OSX Crash & Subsequent Backup Issues


chadders
01-22-2002, 05:35 AM
I recently experienced a Kernal Panic, partly my fault, I switched off a Firewire CD Burner, and when I switched it back on again 'POW' a Kernal panic.

My only option was to reboot using the external button on my G4, so far so good., but to my horror when it came to the Log On screen my familiar log on name and picture had been replaced with a generic picture and 'other' as my name. Non of my passwords worked, and in desperation I decided my only option was to re-install OSX 10.1 from my original CD.

Fortunately most of my Apps and Data files were on a separate Drive than my OS, so I was able to get up and working again without too much hassle, however it has made me aware of the need to backup up some other files, than my obvious data files.

For example, I lost the following;
1. All my email settings, messages, etc. because Microsoft Entourage insists on putting it's data files in the OSX User/Documents folder.
2. All my iTunes Library for the same reason as in 1.
3. All my IE bookmarks, settings etc. Where are these stored in OSX?

I guess this is partly my ignorance and partly my familiarisation with OS9. You see I have partitions set up to place all my Applications on an Applications Partition and all my Data files on a Data Partition. And I regularly backup my Data Partition. My Applications I have original disks for, so no problem there, although the preferences set for so many Applications these days means that it can be annoying resetting everything.

Is it possible for me to Backup Application setting files? If so where are these stored in OSX?
I think I have solved the issue of the Documents Folder by using Synk to syncronise my Documents folder with a duplicate Documents folder on my Data Partition. Is there an better way of doing this?

Are there any other files I need to backup in order to be able to recover more easily if this should happen to me again?

Any pointers towards Backup Strategies for OSX would be very helpful.

I love OSX, but I am still ignorant of the inner workings, and this recent incident has made me aware of just how important my data is to me! :-)

chadders
01-22-2002, 05:40 AM
Oops!

Sorry just noticed that I posted this to the wrong Forum type, it should be in the Help Questions section. Sorry about that.

If a Mod can move to a more appropriate place I would be happy...

Please accept my apology.

griffman
01-22-2002, 08:28 AM
Moved to System...

-rob.

xchanyazy
01-22-2002, 05:26 PM
All of your prefs should be stored in your user folder, in Library/Preferences. I find it best to just back up my whole user folder, then I have all of my documents and preferences stored just in case. I posted my method here (http://www.macosxhints.com/article.php?story=20011218181747247), also, make sure to read the hints afterwards. A lot of other ideas which are probably better.

mervTormel
01-22-2002, 06:39 PM
I think it was a lark that you lost your user login database, but it might have been recovered.

Whenever unix is not shutdown properly, you run the risk of corrupt disk structures.

You need to startup to single user mode, run the file system checker 'fsck' until it comes out clean, then reboot without flushing the disk cache buffers, like so.


Kernel panic...
[dead machine]

Perform a hard restart


Hold down command-s

Until you see the Darwin boot startup screen

This will leave you at the # prompt and you are logged in as root and the root / file system is mounted read only

# /sbin/fsck -p # this is 'preen' mode, check dirty disks


You may get some output here about corrupt structures and whatnot

type

# /sbin/fsck -y

Do this until it says the volume seems to be okay

Then

# reboot -q -n # do a fast reboot, and don't flush the disk buffers

And let it start up normally


Don't run fsck on any of the partitions other than root /

It just doesn't work that way. And fsck's man pages are probably wrong.

it seems there is no interactive mode at this juncture, that is, if you use no switch after fsck, you are not asked if you want to fix problems, it behaves as if you supplied the -y switch

-b