This discussion is archived
1426 Views 15 Replies Latest reply: Dec 26, 2007 11:56 PM by Odysseus1479
Currently Being ModeratedDec 20, 2007 7:23 PM (in response to mampula)Boot from the Install CD/DVD, look in the Menu Bar for Disk Utility, Repair Disk, Repair Permissions, if that doesn't work there are files to delete in Single User mode, but I'm just leaving work late now, so I'll have to check in later... lest somebody else has the info handy.
Hmmm, I guess you haven't heard of Womens's Rights & Men's Responsibilities yet, eh?
Currently Being ModeratedDec 21, 2007 5:57 AM (in response to BDAqua)Noob Mac question. How does one do the following:
Eject the CD tray from a command line? There's no button on the front of the tray . . .
Set boot priority? Or is this like a SUN, where the presence of a CD will trigger it's use?Mac OS X (10.4.11)
Currently Being ModeratedDec 21, 2007 8:15 AM (in response to mampula)OK got it. Well, part of it.
I found that I should be able to boot from CD by holding down the 'C' key as I power on. I should also be able to use the command 'drutil tray open'. But this gives me a bus error.
Umm . . . now what?
And I'm afraid this isn't my first trip through the park, so I know all about the M/F division of labor.
Message was edited by: mampulaMac OS X (10.4.11)
Currently Being ModeratedDec 21, 2007 11:37 AM (in response to BDAqua)I McGyvered the cd tray open and got the machine to boot from CD, repaired the disk and the permissions, but I still have a no-boot condition.
Anyone have any other ideas?
Given that I don't seem to be the only person with the problem, is there a posibility that Apple will address this?Mac OS X (10.4.11)
Currently Being ModeratedDec 21, 2007 11:52 AM (in response to mampula)I agree this is something Apple needs to fix, but on our end, these problems can almost always be avoided by Repairing Permissions before & After every Update.
Single User method might work...
Otherwise this might help... or not...
After that, assuming you have enough HD space, looks like an Archive & Install is in order.
Currently Being ModeratedDec 21, 2007 6:08 PM (in response to John Pietrzak)An update on my condition -- it looks like the HD in my mini has, in fact, gone seriously bad. (I've tried doing a disk repair (and failed), and tried erasing the whole disk and reinstalling the OS (and failed).) I figure that this is therefore unrelated to the security update, other than that it caused me to reboot the machine, which revealed the problem...
--JohnMac Mini, Mac OS X (10.4.11)
Currently Being ModeratedDec 23, 2007 8:48 PM (in response to mampula)I had 2 hard drives die this week after installing the update. One a Seagate 25OGB Sata II, one an external FW800. It seems curious. Admittedly one was 3 years old, the second, an external Firewire was not quite a year old. My dad also had a drive fail this past week. What are the chances of these all happening coincidentally? How many others had drives that died after installing the update? I have not yet installed 1.1. I am afraid that my remaining drive may bite the dust.
Is there a possibility that the security update is killing drives?Mac Pro, Mac OS X (10.5.1), 2x2.66 Ghz Dual-Core Xeon; 6GB RAM
Currently Being ModeratedDec 23, 2007 9:07 PM (in response to tpb)I doubt it, but contrary to what every experienced/intelligent person says... the only drives /i've had die, (and be unrecoverable to boot) was I figure due to Journalling, I no longer use it and hae no problems as long as I fsck -fy or use AppleJack after any untoward bomb/freeze.KP.
Currently Being ModeratedDec 24, 2007 4:11 AM (in response to tpb)
Is there a possibility that the security update is killing drives?
It's probably just coincidence. In my experience, hard drives are the twitchiest part of a PC. The engineering on them has come a long way over the years, but they're just about the only moving mechanical part left inside a PC (other than the CD/DVD drive). You've got bearings that can wear out, motors for both the platters and the arm that can fail or have subtle problems, and a stationary read/write head sitting extremely close to that fast-moving platter -- if the two actually touch the drive is probably scarred for life. There are lots of ways for a drive to die.
In my case, I hadn't rebooted my machine for some time before the update (I tend to keep my computers running 24/7), and the reboot is probably what revealed that my drive had gone bad, not the update itself. It's true that this particular machine was only a year old, and most of my hard drives have lasted far longer than a year, but I've had several drives die untimely deaths before...
Just another reason to keep good backups!!!
--JohnMac Mini, Mac OS X (10.4.11)
Currently Being ModeratedDec 24, 2007 8:49 PM (in response to mampula)Hello there, had this same error, I could boot up the mac pro by holding alt in the keyboard after turned on, and selecting the mac hard drive, booted up fine just hope doesnt do it after restart again, ill repair permissions just in case. Hope this can help any of you.Mac Pro 2.6, Mac OS X (10.5.1), 7300gt
Currently Being ModeratedDec 25, 2007 3:46 PM (in response to Lutechi)shut down, turned on and guess what, same problem, had to hold alt again while turning on for select drive to boot up. This was after permissions repaired, so I guess repairing permissions is not a fix.Mac Pro 2.6, Mac OS X (10.5.1), 7300gt