|
#1
| ||||
| ||||
| Help!!!!! I'm desperate!!!!! Software update "broke" Mac OS X 10.4 server
So, I ran some Mac OS X updates last night and there were three. An iTunes update, I think a QuickTime update, and a security update (that was 207MB in size). I forget the name of the security update. After the update process finished, I was advised the security update didn't install correctly and was instructed to reboot. Upon rebooting, after the gray screen with the spinning wheel, I get a blue screen with a spinning wheel. I never get prompted to login. *sigh* So, after doing some Google searching, I learned I can possibly do one of two things to recover: 1) Do a Firewire Target disk Mode (http://support.apple.com/kb/HT1661) connection between the server and another, working, Mac, download the security update manually and apply it to the server disc using the Firewire connection. 2) Do an archive & install of OS X and then install the updates and rebuild from there. I have the OS X Server install DVD and it's for version 10.4.7. I believe the server had 10.4.11 installed when I ran the security update last night. I've booted from my OS X Server install DVD and learned the ONLY options are to upgrade to 10.4.7 from a previously installed version or to do an erase and install, wiping everything out. Of course, there is some data on the server I need access to before I can "nuke it" and start over. Are these my only two options? When I booted from the installation DVD, I was able to run the Disk Utility to verify the boot volume and it checked out ok. If I do get a Firewire cable and do the Firewire target disk mode connection, should I be able to update the server with the security update from a Mac-mini running OS X 10.4.11, non-server edition? Any other advice you can provide would be greatly appreciated! Thanks in advance! Peace... |
|
#2
| ||||
| ||||
|
Well, I bought a Firewire cable and am trying to do the Firmware target disk mode connection and I never get the Firewire icon on the target machine (the server) when I boot it while pressing the 'T' key. *sigh* Looks like I'm SOL unless someone else has any bright ideas. I've got one more thing I'm going to try before I start crying. ![]() Peace... |
|
#3
| ||||
| ||||
|
So, I've learned I can run the System Profiler from the OS X 10.4.7 installation DVD. Cool. I believe this Mac, despite being a G4, is too old to support Firewire Target Disk mode. So, since the internal hard drive is an ATA (IDE) drive, could I connect it to my Mac-mini via an external USB hard drive enclosure and apply the security update that way? Or would that work only in Firewire Target disk mode? Peace... |
|
#4
| ||||
| ||||
|
Have you tried booting in safe mode?
__________________ MacBook 2.16 Core 2 Duo, 2 gigs of ram, 120 gig hard drive Snow Leopard 10.6 PowerBook G4 15" High Res 1.67PPC, 2 gigs of ram 160 gig hard drive Leopard 10.5.8 Apple iPhone 2G 8 Gigabyte Unlocked, Jailbroken 3.1 |
|
#5
| ||||
| ||||
|
I've tried booting into safe mode by pressing the Shift key (I don't know which one or if it matters) while the system boots and it never loads. I power on the machine and press a Shift key after I hear the initial power-on sound. I hold the Shift key until I get the gray Apple screen with the spinning wheel and then I let go. After a bit, I get the blue screen and the mouse pointer DOES appear and I CAN move it but then it disappears and I get the blue screen with the spinning wheel... and then frustration... some cursing... you get the idea. ![]() EDIT: Thanks for the reply! ![]() Peace... |
|
#6
| ||||
| ||||
|
Howabout trying to boot in verbose mode, then posting the last 20 or so lines of the results? Hold command-v as the system boots. The error message(s) that get spit out may indicate what's hanging the machine.
__________________ Mac mini 2.0GHz 10.6.2 • 4GB • 320GB • Superdrive • 4 x 1TB USB 2.0 • LED Cinema Display MacBook 2.0GHz Core 2 Duo - White 10.6.2 • 4GB • 250GB • CD-RW/DVD-ROM iPhone 3G 8GB • iPod Touch 8GB • iPod Photo 60GB • iPod nano 1GB • AT&T U-Verse 18Mb/2Mb http://www.jeffhoppe.com |
|
#7
| ||||
| ||||
|
I tried booting in verbose mode as well but I might not have gotten they keys right. Since I'm using a non-Apple keyboard, I was pressing the "Alt-V" key sequence instead of "(Windows-key)-V", which I think is the correct sequence. I've found a way to get to the critical data (I have the server HDD connected to my Linux box using an external USB HDD enclosure) so some of the pressure is off. I'll try to get the system to boot in verbose mode when I have a chance. Thanks! Peace... |
|
#8
| ||||
| ||||
|
Ok, I booted the server in verbose mode using Command-v ({Windows Key}-v on my keyboard). I had no way to capture the output but at the end, I do see this loop: Code: g4server /System/Library/Coreservices/LoginWindow.app/Contents/MacOS/loginwindow: Login Window Application Started g4server /usr/sbin/AppleFileServer: Server crashed and exited with status 4.\n I've got the most critical data recovered so I'm going to rebuild the server. Thanks! Peace... |
![]() |
| Bookmarks |
| Thread Tools | |
|
|