So, I was able to get the cloning working (sort of), however it's not
all that clean, and I'm still not completely sure why it required
these changes.
1) Edited the $IMAGENAME.master script to remove the all options from
systemconfigurator except hardware config during image roll out.
2) Added a post-install script that executes:
echo (hd0) /dev/cciss/c0d0 > /boot/grub/device.map
grub-install --rootdirectory=/boot hd0
Upon completion the freshly imaged server grub installs properly and
no worries after reboot.
But, I've clearly created a problem if a /dev/sda device is attempting
to get cloned.
Still not sure why the device.map is getting zeroed, even if I include
it in the overrides (??).
I'm guessing that systemconfigurator 2.2.11 starts playing with
device.map as part of its --configboot option?
Again, this only appears to be a problem with SuSE, a RHEL5U1 x86_64
clone took with zero changes to the $IMAGENAME.master file.
Different edition of grub-install, or is that binary included with the
boel binaries package?
Sorry for all the questions,
Seth
>Running into some cloning issues this morning attempting a new configuration
>we're trying out.
>
>OS:
>SuSE 10 Update 1 x86_64
>
>Hardware:
>HP DL380 G5
>P400 SAS Controller
>
>System Imager is 4.0.2 running on SuSE 10.1 x86 HP DL320.
>
>The PXEbooting portion of the installation works fine until the very end
>where autoinstall script attempts a grub-install (or runs through a series
>of potential boot loaders). It throws an error claiming line 112 of
>Label.pm under /usr/lib/systemimager/Boot/ is the problem, but looking at
>line 112 just shows a reference to an if statement about not being able to
>locate grub.conf.
>
>The prepareclient server is a fresh SuSE 10.1x86_64 install that uses Grub.
>A cloned system shows the correct partitioning structure, file contents, and
>the like when viewed in SuSE rescue mode, the odd part is the
>/boot/grub/device.map file is empty in the cloned image.
>
>RHEL5.1 x86_64 imaged just fine on an identical box this morning using
>4.0.2(very happy with the release aside from the SuSE problem) so I
>don't believe
>it to be an imageserver configuration issue. My cloning experience with
>SuSE is limited, even more so with x86_64, so hopefully this is something
>simple that I'm just overlooking.
>
>Cheers,
>
>Seth
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
