Welcome to Techsurvivors => Tech => Topic started by: daryl66 on August 10, 2011, 01:18:01 PM
Title: More Lion Stuff
Post by: daryl66 on August 10, 2011, 01:18:01 PM
Motoring along this morning with Safari when the house took a quick power hit (probably the power co doing some work). It immediately shut down the mini. I won't go into everything that transpired subsequently, however a new "Power up" brought up some really strange things. and it no workey. Ultimately rebooted 10.6.8 from the back-up, Ran "first aid" which told me it could not repair the disc, ran Tech tool Pro,( 3 times) it told me the volume structure was bad and could not be completed, attempted restart using the "Restore HD" Kernal panic etc . Almost to the point of erasing the hd and starting over, I held down the option key for another restart and got an Icon of a HD, named "EFI HD", thinking "What the heck you have tried everything else WHY NOT. That restored everything.(took almost 10 minutes) I had one more Kernal Panic about 10 minutes into Safari. Power off and back on and it seems to be ok now.
Lots of "log" reports, on attempted restore efforts, which are greek to me,
What does EFI mean??
I had upgraded the RAM to 2.5 (added a 2 gb and removed one of the 512"s) Before upgrading to Lion, thinking that might be the problem, apparently not.
Once again DONT throw away your USB mouses, Absolutely necessary. I am guessing, but suspect that wireless mice would be as hard to find as the trackpad.
Daryl
Title: More Lion Stuff
Post by: gunug on August 10, 2011, 01:28:45 PM
EFI is short for Extensible Firmware Interface and it's the Intel version of the old Open Firmware concept that the G3-G5 type computers had! Essentially, and hopefully, you just got scrambled information in your open firmware which hashed up the startup on your Mac Mini!
Title: More Lion Stuff
Post by: Xairbusdriver on August 10, 2011, 01:30:28 PM
How old is your UPS? Disks don't like to be de-powered while writing!
Well if one can believe everything one reads, it looks like "no worries". Ran First Aid 2 more times, first time it fixed a few things and the 2nd time it says the disc "appears to be ok"
FWIW, Holding the option key down on restart now shows the "internal" hd as "EFI HD", on the desktop and in system prefs it is "Macmini"
ABD: UPS, UPS, UPS what is UPS ?????, aren't they they guys in the brown truck that chases the FedEx truck up my hill a couple of times a day??? (No got, surge protectors are the sum total of my "protection") Power hits are pretty rare. Thats my story and I am sticking to it.
GN: Thanks. My education is now "enhanced"
Daryl
Title: More Lion Stuff
Post by: Xairbusdriver on August 10, 2011, 03:44:52 PM
It might be useful to add a "Debug" menu to Disk Utility, also. Just open Terminal and copy & paste the following:
It will show exactly what hidden volumes/partitions you have (the Recovery volume is not normally shown). Open DU, if the "Recovery HD" is not shown, try the "List All Disks" item in the new Debug menu. When I look at my listing (see below) the EFI disk shows up labeled as "disk0s1" on the internal and "disk1s1" on the external drive.
[attachment=2293:Disk_Uti...eenSnapz.jpg]
I highly recommend a good quality UPS rather than a "surge protector." Many inexpensive "surge protectors" are of the 'sacrificial' type. They will usually work...once. Whether they are still useful may not be evident until the next surge when your equipment is fried... And good quality UPS will not only have longer lasting surge protection but will protect against low voyages and provide you with time to make an orderly shutdown of the rather expensive hardware and the irreplaceable data. I've had great performance from APS brand but there are a few other good ones.
Title: More Lion Stuff
Post by: Paddy on August 10, 2011, 04:27:31 PM
FWIW, Holding the option key down on restart now shows the "internal" hd as "EFI HD", on the desktop and in system prefs it is "Macmini"
Yep - sounds like that Disk Warrior renaming the disk as EFI-HD bug isn't confined to Disk Warrior. I believe the fix is also noted in the link I posted earlier, if you care to fix it (in the Terminal). If not, I see no harm in leaving it as is.