While autoinstalling I had a problem with my /boot partition not getting a filesystem installed on it if the fstab on the golden-client had "noauto" as an option. I could see in the master script that the partition was made but there was no call to mke2fs. The install would of course fail. I removed the noauto and (after another 'getimage') the script had the required mke2fs call. Good.
Now however, the auto install fails right at the end with: umount /a/boot || shellout umount: /a/boot: Invalid argument /proc/mounts gives: /dev/hda1 /a/boot ext2... /dev/hda3 /a ext3... so /dev/hda1 is mounted on /a/boot but looking at the master script /dev/hda3 is mounted on /a which masks the mount of /dev/hda1 completely. All writes to /a/boot actually went onto /dev/hda3. I could successfully umount /a which 'revealed' /dev/hda1 on /a/boot, but of course it had nothing in it. If I reboot after this error the system boots OK, /dev/hda1 is mounted on /boot and /dev/hda3 is mounted on /, if fact everything seems fine except that there is nothing but lost+found in /boot! The golden client is correct with the boot things (kernel etc) in /boot where they should be. Should I worry? I'd like to able to use any installed client as a golden client in the future. I'm not sure what the repercussions of that might be. thanks Murray ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
