With the kernel provided by Bernard Li, I have been able to get the DHCP working correctly on the Dell PowerEdge 1750 servers. I'm running the EduOSCAR92 distribution with the initrd.img and kernel files in /tftpboot replacing the ones packaged with EduOSCAR92.
However, I now have a new point of failure during the installation.
The autoinstaller client gets the DHCP information, and gets a response from the cluster head, which gives the node its IP address. It then begins to try and install the node. I have captured as much of the error message as was displayed on the scroll-up buffer of the target node.
[EMAIL PROTECTED] oscarconfig]# more installerrors.dec10
insmod: unresolved symbol ..... (lots of these--more than 3 screens worth)
mkswap -v1 /dev/sda5 || shellout
Setting up swapspace version 1, size = 2146758656 bytes
swapon /dev/sda5 || shellout
Adding Swap: 2096440k swapspace (priority -1)
mke2fs -j /dev/sda1 || shellout
mke2fs 1.33 (21-Apr-2003)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
262144 inodes, 524112 blocks
26205 blocks (5.00%) reserved for the super user
First data block=0
16 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or 180
days, whichever comes first. Use tune2fs -c or -i to override.
mkdir -p /a/ || shellout
mount /dev/sda1 /a/a -t ext3 -o defaults || shellout
mount: Mounting /dev/sda1 on /a failed: No such device
write_variables
<<<<<<<<<<<<<<<<<<<< System imager auto install system error message follows.
A df of my head node reveals:
[EMAIL PROTECTED] oscarconfig]# df
Filesystem Size Used Avail Use% Mounted on
/dev/scsi/host0/bus0/target0/lun0/part1
4.0G 2.7G 1.2G 70% /
/dev/scsi/host0/bus0/target0/lun0/part8
54G 2.0G 52G 4% /home
/dev/scsi/host0/bus0/target0/lun0/part7
4.0G 954M 2.9G 25% /usr
/dev/scsi/host0/bus0/target0/lun0/part6
4.0G 343M 3.5G 9% /var
horus:/u1/Mandrake/9.2
267G 83G 172G 33% /mnt2
i.e., they're not using /dev/sda1 and the like, but rather /dev/scsi/host0/bus0/target0/lun0/part1. However, this is a freshly created filesystem, so I don't know what's going on.
I have made my partition file as follows:
[EMAIL PROTECTED] oscarconfig]# more oscarimage.partitions
/dev/scsi/host0/bus0/target0/lun0/part1 2048 ext3 / defaults
/dev/scsi/host0/bus0/target0/lun0/part5 2048 swap
/dev/scsi/host0/bus0/target0/lun0/part6 2048 ext3 /usr defaults
/dev/scsi/host0/bus0/target0/lun0/part7 * ext3 /biobits defaults
nfs_oscar:/home - nfs /home rw
I had the same errors when the above partitions said /dev/sda1 and the like. (i.e. if you were to run
s#/dev/scsi/host0/bus0/target0/lun0/part#/dev/sd# on the above file with #'s as substitution delimiters.)
Anyone have any ideas?
--------------
Jason Hlady, B. Sc., M. Sc. (Chem), Adv. Cert. (Comp. Sci.)
Programmer/Analyst (Bioinformatics Specialist)
U of Saskatchewan, Bioinformatics Research Laboratory (BIRL)
[EMAIL PROTECTED] (306) 966-2075
- Re: [Oscar-users] further SystemInstaller problems Jason Hlady
- Re: [Oscar-users] further SystemInstaller problems Bernard Li
- Re: [Oscar-users] further SystemInstaller problems Frank Crawford