aprodigy Posted September 19, 2007 Share Posted September 19, 2007 Maybe some of you does have some answers for me... The purpose of all of this: One HD, two partitions of equal size. The HD needs to be repartitioned to only one partition (namely /dev/disk2s1) and the formerly installed osX86 has to become restored into that single but bigger partition in whatever way. What I tried so far... 1.) Backup with Acronis 9.1, repartitioned with Apple's Install DVD to only one partition and tried to restore that former created image with Acronis back to that partition. No go - no matter what option I select, Acronis does not feel like restoring the contents of that image into a larger partition. It only works when I choose the restore the whole partition or the whole HD. 2.) Tried iPartition and VolumeWorks. Both of them don't work either and brag about some invalid kind of partition table (the partition table was created with Apple's Install DVD though and the whole HD does NOT contain any other partitions). Okay, don't care, I still got another idea... 3.) Created an basic diskimage with Apple's Install DVD from that system partition, repartitioned and when it came to restore I could select the disk image by clicking on the 'Image' button in the restore window but I could not move the device I wanted to restore this image to into the appropriate field?! In fact, I couldn't even enter '/dev/disk2s1' or anything like that or move anything else at all there. It just didn't work... Why, I could not figure out. I guess that the type of HD is not what the Apple-Installer expects to restore a .dmg to even though I can install a brand new osX to that drive without any hassle. Well, whatever... Coming from 12 years of working with Linux I'm at least a little creative... So, here comes number 4... 4.) With Apple's Install mounted the image and the target partition and launched the terminal. 'cp -RPv * ../osX' and after an hour and a half everything seemed to be copied back. I marked the partition active with fdisk and restarted. It was starting fine at first but when 'launchd' tried starting services (syslogd, nibindd, et cetera), every one of those were failing with some error like 'launchd - ... - bad system command - ... throtteling too fast ... - respawning x times in 10 seconds'. It was doing this with four system related daemons ten times and then the system halted completely. Well, I still could type on the screen but didn't get a working console. So at least the kernel was still alive then... I started the system with '-v -s' and when it reached the single-user-mode I tried starting the services by hand and well, they started fine... # /usr/sbin/syslogd & # /usr/sbin/nibindd & No problem here... By the way... The system.log does not say anything else but what's written to the console. So I can't get anything else out of them (of course, works only by starting the syslogd by hand anyway). GNU/Linux-Systems can always be copied (e.g. by using Knoppix) back and forth to any partition one wants. Modifying the fstab and the bootloader is always enough for the system to become revitalized. So why can't I just copy the contents of an bds/darwin/apple disk-image (.dmg) while keeping the permissions back to the drive without killing the system (or at least launchd completely). The target disk is the same as before and I haven't touched the MBR at all. So basically, no fstab or lilo/grub/darwin-bootloader modifications should have become necessary. The volume's got even the same name! I reinstalled the base-system for fun afterwards to see if the system starts again then and well, it does but it does seem to have trouble with something else since the system is lagging somewhat (and yes, I was waiting till Spotlight finished its job) while moving the mouse or selecting windows, the finder or whatever. Anyway, this was just for testing. I can always restore the whole HD with Acronis but the system partition will be at 34GB again and that's just not what I was trying here. Anyone? It just has to be possible to copy/image an installed osX to somewhere else without destroying it or at least, with a chance of fixing it afterwards. Oh, I don't want/need a long solution. I'd be satisfied with some hints into the proper direction. I'd do the rest... And yes, I'm totally bash/perl/solaris/linux/win-aware... not much bsd or osx/darwin knowledge so far though Thanks a lot and bye... PS: Oh, no, it's probably not possible to reinstall that 'system'. Worked about 3 weeks on it (customizing, installing, whatever) and I just don't wanna do that again Link to comment https://www.insanelymac.com/forum/topic/63738-a-couple-of-questions-to-the-underlying-architecture-of-osx/ Share on other sites More sharing options...
aprodigy Posted September 20, 2007 Author Share Posted September 20, 2007 May some moderator close this thread please?! I finally found a workable solution for resizing 'fstab_partition_scheme'-volumes without destroying the installed base. The partition-scheme actually seems to be the problem for all the trouble I had but oh well, there's always a way uh?! http://forum.insanelymac.com/index.php?sho...c=32890&hl= Link to comment https://www.insanelymac.com/forum/topic/63738-a-couple-of-questions-to-the-underlying-architecture-of-osx/#findComment-452043 Share on other sites More sharing options...
jharleman Posted September 27, 2007 Share Posted September 27, 2007 wow, long post! i have a santa rosa platform intel laptop--lenovo t61p. got uphuck installed with ahci compatibility mode in the bios. tried to upgrade to 10.4.10, that went ok. tried to upgrade my kernel and kaboom, the same errors. what platform are you on? cheers - jl Link to comment https://www.insanelymac.com/forum/topic/63738-a-couple-of-questions-to-the-underlying-architecture-of-osx/#findComment-457404 Share on other sites More sharing options...
aprodigy Posted September 27, 2007 Author Share Posted September 27, 2007 wow, long post! i have a santa rosa platform intel laptop--lenovo t61p. got uphuck installed with ahci compatibility mode in the bios. tried to upgrade to 10.4.10, that went ok. tried to upgrade my kernel and kaboom, the same errors. what platform are you on? cheers - jl weird. anyway, i guess the cause of your trouble is something else... maybe you should start a topic as well and ask the crowd! Link to comment https://www.insanelymac.com/forum/topic/63738-a-couple-of-questions-to-the-underlying-architecture-of-osx/#findComment-457865 Share on other sites More sharing options...
Recommended Posts