Eek! Mini problem

It would be the short name that you usually set up in Mac OS X or in this case, I believe BatMaste.

 

That's single user mode, otherwise known as the console or terminal. Things have indeed gone wrong. Try rebooting (login, then type "reboot"). If it still comes up to the console, reboot and insert the hardware test DVD that (should have) came with your mini. Let it run and see if it reports any errors. If it doesn't, then your OS X installation may be borked. Dig out your OS X installation DVD, and do a erase/install. If THAT doesn't work, then it's time to call Crucial or Apple up.

 

*kisses apple certified RAM bought from macmall and pats G5*

 

Hold down the power button.


But first stick in that CD!

 

Or try sudo reboot (you'll be prompted for your password again)

Jx

 

Yep, whenever they tell you you can't do something, tell it to stuff it with a "sudo". That stands for "super user do", which gives you temporary root privileges. Do respect it through, you can do some major, major damage with root powers.

Eh, just hitting the power button would do the trick as well, but it's easier on the machine to do it software-side instead of hardware - data corruption and stuff, ya know?

 

diskutil eject

 

Sorry.. WRONG command..

drutil eject

If that doesn't work, reboot and hold down the mouse button until it ejects the CD/DVD.

 

Well, did you try holding down the mouse button as you boot? That would take the DVD out, and you can then boot into hardware test.

 

Restart and hold the T button down for FireWire Target Disk mode.

Mac becomes hard drive... plug into other Mac for HD access.

 

That != single-user mode, for the record. The whole point of single-user mode is that you don't have to log in. For some reason, WindowServer doesn't seem to be starting.

Boot into single user mode, fsck the hard drive, mount it, and type <b>cat /var/log/crashreporter.log</b> and post that (at least the last few lines or lines that seem wrong/errorific. That'll give us an idea of what happened. Then cat /var/log/windowserver.log and anything else in /var/log.

 

Can you start it up in FireWire Target Disk mode? If so connect it to another Mac or bring it to an Apple Store to back up there. The geniuses tend to be nice about that, especially if you're getting AppleCare work done.

The actual command was cat /var/log/crashreporter.log because someone didn't know about vB code and tried to just get by with standard HTML tags....

 

Actually, the whole point of single user mode is maintenance of a machine, without any daemons running. But I'm being anal, I know.

 

archive and install os x.

 

Try re sitting your RAM

Did you try to re sit your replacement RAM?

 

I could be out in left field here, but when I've had something similure to this happen I rebooted to the cd (I forget which one) and ran a repair permissions. Then shut down and restarted without booting to the cd and everything came up okay.

If they are having problems reading the volumn during an archive/install, it sounds like his partition or rights on the partition are goofed up.

My 2 cents, worth everthing you paid for it.

Good luck