Dear Users and Wizards, This is just to report a small issue we have seen during installation of a small cluster.
We run CentOS 6.2 and the default way to install happens to be: /dev/sda1: /boot /dev/sda2: / ... This causes problems during the node installation process, as the file systems are created and mounted in order of the device numbering (barring the swap, which is made and used first). Thus, during install I have observed that /a/boot is created and mounted. And subsequently, /a/ is created and mounted. The order of this causes /a/ to mount on top of /a/boot, and thus the files in /boot actually are written to /dev/sda2 rather than /dev/sda1. As a consequence, the node will not be able to boot (as there are no files on the boot partition). We have resolved this issue by removing the /boot partition and keeping / as /dev/sda1, such that it is both the boot and root partition. I don't know if the correct "solution" is to create and mount the root partition file system before the other file systems? Or maybe just to be aware that there is an issue. I'll be happy to hear comments and other experiences. I think that the "boot before root" is (or was) a pretty common way to do things. Best, Bjarne Büchmann ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
