Hi all,
I have successfully installed system imager on scientific linux 44 (a clone
of RHEL) and get it working. But I found a strange bug when deploying an
image on another hard drive.
The golden client was using hdb hard disk (there was no \dev\hda at all - I
forgot to set jumpers correctly - it was a slave). If I deploy image on
another client which is also has slave hard disk, then evrth works fine. But
if I set it as master (as /dev/hda) and change autoinstallscript.conf,
remake autoinstall script, change grub loader config to use hda - then
system boots with kernel reporting errors about out of boundary of disk
access. This seems to be caused by bklid program (a tool from e2fsprogs)
which marks devices with UID and label and allows use of LABEL=/home style
entries in /etc/fstab. If I edit fstab to use old style entries like
/dev/hda1 and stop haldaemon from running then evrth is fine.
I can't figure out the difference in installing it to hda or hdb, may be
some config file left from /dev/hdb setup or smth else.
I tried to remove /etc/blkid.tab file which contained old labels for
/dev/hdb and it was restored to correct devices by blkid, but it doesn't
help.
There was one more problem when installing it to /dev/hda - the image file
system was missing entries in /dev for hda, thus preventing grub from
installing, but I fixed it with MAKEDEV. I think presence of entries in
image file system should be done by autoinstall script itself.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
