![]() ![]()
I suspect this is a matter of special drivers being needed for this particular device at this particular stage of it and its OS's life. But I hit a very mysterious situation in which built-in ethernet could not be found. The installations proceeded as expected and I was able to boot off the target volumes after. Thanks for the *great* hint!Įdit: Well, it almost worked. ![]() It all worked because I never had to boot into an out-of-date version of the OS in order to bootstrap up to a sufficiently recent version of the OS. (Because of an unusual situation with Apple releasing a version of the 10.6.4 updater that was specific to this generation Mac Mini and which was not a "combo" updater, I actually had to use a 10.6.3 updater instead of the latest 10.6.4 updater, but this is not likely to be a common scenario.) (And erase the original boot volume and use it for the data I always intended for my second internal drive.) Outstanding! #Osinstall.mpkg patched for mbr mac os#I could safely boot off of that second volume into standard Mac OS X. #Osinstall.mpkg patched for mbr update#Applied the update to the system on that second volume. ![]() Downloaded the latest combo updater from /support. #Osinstall.mpkg patched for mbr install#Used this technique to install 10.6 to the second volume in the machine. Inserted my Snow Leopard install disc (in an external USB CD/DVD drive). I booted the Mini off its originally installed server OS. A couple of phone calls to Apple couldn't come up with any solutions and they were even suggesting I might want to return the unit and get the non-server model (which I very much didn't). However, the Mini was too recent to use the boxed version of Snow Leopard I had, and the machine would kernel panic when I tried to boot from the installer DVD. I had a retail, boxed copy of Snow Leopard I intended to use for this purpose. I bought a new Mac Mini (mid 2010, with HDMI), but because I wanted two 7200 rpm internal drives and didn't need an optical drive I bought the server configuration, fully planning to blow away Snow Leopard Server with regular Snow Leopard. However this command-line technique works correctly and does produce a bootable volume.Ī slightly easier to read version of the command using quotes instead of escaping all the spaces, that should work but I have not tested, is: sudo "/Volumes/Mac OS X Install DVD/System/Installation/CDIS/Mac OS X Installer.app/Contents/MacOS/Mac OS X Installer" "/Volumes/Mac OS X Install DVD/System/Installation/Packages/OSInstall.mpkg" I tried that and, as you observed, it goes through the entire install, but does not produce a bootable volume. In answer to "m3kw", this is different from just finding and double-clicking the OSInstall.mpkg in the GUI. So the technique seems to work as advertised as long as you provide the path to the correct package to be installed. ![]() "Unable to create record in /Local/Target."and: mv: rename /Volumes//Recovered Items//Volumes/ to /Volumes//: No such file or directoryDespite a few pages of these warnings and errors, the resulting volume could be selected in the Startup Disk prefPane, and booting from the resulting volume worked correctly, wanting to be registered, allowing you import user data, correctly performing software updates, etc. Did not move file from: to: and: Error writing cache to /Volumes//Recovered Items/Libary/Caches/.and: Could not create entry for. They are mostly of the form: Broadcast message from at. It does produce a bunch of warning or error messages, at least in the case in which the target volume is empty, but it appears they can safely be ignored. So, assuming the installer volume is called "Mac OS X Install DVD" (even if it's on a hard drive), the command written out in full to perform the install is: sudo /Volumes/Mac\ OS\ X\ Install\ DVD/System/Installation/CDIS/Mac\ OS\ X\ Installer.app/Contents/MacOS/Mac\ OS\ X\ Installer /Volumes/Mac\ OS\ X\ Install\ DVD/System/Installation/Packages/OSInstall.mpkgThis definitely works to install Snow Leopard from a hard drive, without having to boot from the installer partition. Just add the path to the main OSInstall.mpkg to the command. (At least this is true for Snow Leopard.) The solution is simple. A package must be specified as an argument in order to install Mac OS X.As the error message fairly clearly indicates, the "Mac OS X Installer" program requires the specification of a particular package to install when invoked from the command line. #Osinstall.mpkg patched for mbr mac os x#This hint leaves out one important detail, which is what gave "frankt" a hard time and results in the error message he reported: There was a problem installing Mac OS X.No package was specified for the Mac OS X installer to install. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |