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

pagetuneup

macrumors newbie
Original poster
Jun 25, 2011
16
0
I want to test my backup system and was wondering what is the best way to
purposely corrupt the Snow Leopard OS?

I mean REALLY corrupt it - kernal panic, hosed, no return...

Any suggestions?
 
I couldn't tell you an easy way to do that, but why don't you just try a reformat. Also, if you're just testing your backup system, completely screwing your system would suck if your backup didn't work.
 
Any way to do it is what I'm aiming for, all unix systems have a good security system i was wondering if anyone might know a way around it
 
I'm with Alust, why not format the drive, will have the same effect.

Unless maybe its not your system your trying to corrupt?
 
I've accomplished this using a short script on my PC, but I've had no luck on my mac:/
 
Any way to do it is what I'm aiming for, all unix systems have a good security system i was wondering if anyone might know a way around it
We're not going to help you hack or corrupt any Mac, whether it be your own or someone else's. If that's your goal, you're asking in the wrong forum.
 
My intentions are good, I'm trying to develop my own back-up system.

My system is Windows-ready (sort-of) but I'm hoping i can dev something similar for mac
 
Would that produce the same results as kernal panic? That's what I'm aiming for
 
trying to dev a backup system that will restore any computer on my network. Detect its OS I have several macs and pc'sand automatically restore it without any user help

have a software in mind for that?
 
Last edited by a moderator:
trying to dev a backup system that will restore any computer on my network. Detect its OS I have several macs and pc'sand automatically restore it without any user help
Just because a kernel panic occurs, it doesn't necessarily indicate that a system restore is called for. This shouldn't be an automatic process. The user should determine if the system needs to be restored from a backup. That decision shouldn't be handled by software or any automated process.

Resolution
Restart your Mac with a Safe Boot and see if the kernel panic happens again

In most cases, kernel panics are not caused by an issue with your Mac. They are most likely caused by an issue external to your Mac. If the kernel panic doesn't happen again within a few weeks, you don't need to troubleshoot further.
 
Logic here: Most kernal panics call for a system restore? anyone disagree?

The software attempts to boot computer in single user mode first and run command fsck first as initial diagnosis. Depending on the results from that then decides how to proceed. Most kernal panics don't even allow the user to key in anything in single user mode anyways
 
I will have to take this into account this is much harder than it was for windows. (I can sense the hair pulling already). Hmm, what do you guys suggest will WITHOUT A DOUBT call for a system restore? I think I'm going to adapt my system to diagnosis first rather then execute system restores off the bat. Its like shoot first ask questions later.
 
Logic here: Most kernal panics call for a system restore? anyone disagree?

I disagree completely as you can resolve a kernal panic without restoring the entire os. If you back up, you could very well be backing up the issue that caused the kernal panic on the first place


I will have to take this into account this is much harder than it was for windows. (I can sense the hair pulling already). Hmm, what do you guys suggest will WITHOUT A DOUBT call for a system restore? I think I'm going to adapt my system to diagnosis first rather then execute system restores off the bat. Its like shoot first ask questions later.

I can't think of anything that would call for it to be honest as if the kernal panic is sw related, you can pin point it and resolve it. If it's hw, then a restore won't do anything
 
I will have to take this into account this is much harder than it was for windows. (I can sense the hair pulling already). Hmm, what do you guys suggest will WITHOUT A DOUBT call for a system restore? I think I'm going to adapt my system to diagnosis first rather then execute system restores off the bat. Its like shoot first ask questions later.

Pretty much nothing. I have never re-installed Mac OSX to resolve issues and I've been using it since the first public beta.
 
I had to re-install it like last week for this girl running leopard. Apparently she took out the battery while her comp was running a system update
 
well apple did take action after those kind of issues occurred. They stopped allowing users the option to take out their comps battery without taking apart the whole thing.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.