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

peterj1967

macrumors regular
Original poster
Aug 30, 2002
182
0
Ran into a strange problem.

I have an iMac Running the most current OS, I forget if it is .4 or .5

I run a Time Machine Backup as well as a weekly backup I keep off site. I generate that backup using Super Duper

About a week ago the Timemachine backup gave me an error of that it couldn't back up the machine because the disk was read only. I check the disk permissions and made sure it was fine using Disk Utility everything was fine, and the issue went away. Time Machine ran fine.

Last night, I was making my second backup using Super Duper and it failed. Foolishly I didn't write down the error but I believe it was a file it couldn't copy.

I rebooted the machine this morning, and I got an error message that the main disk was full. Which it wasn't the night before I had about 166 gig free on a 600 gig drive. And it simply won't boot.

I booted from the install CD and ran disk utility, and it says the drive has 166 gig free. I repaired disk and it was fine, no errors, I did repair permissions and it had two corrections and then a Warning about an SUID file, which in looking a little doesn't seem to be a big deal

Restarted the machine, and this time didn't get the disk full error but I get the log in screen and then it just hangs there. Don't even get to see my desktop, just the image that Mac defaults to and it just sits there.

So the question is does anybody have an idea of what may have gotten corrupted along the way and how to fix it or prevent it in the future.

I am hoping the Time Machine back up is fine, it has been running with no issues, so I can always rebuild from that, but I don't understand how running a super duper backup may have caused and issue.

Thanks in advance

--Pete
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.