Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
iscsibootprepfc5 [2006/09/18 08:28] mcb30 iBFT module load will fail when not booted from iSCSI |
iscsibootprepfc5 [2006/09/18 12:03] (current) mcb30 |
||
---|---|---|---|
Line 19: | Line 19: | ||
DEVICETYPE=boot | DEVICETYPE=boot | ||
+ | |||
+ | If you want the hostname to be assigned via DHCP when booting from iSCSI, you must edit ''/etc/sysconfig/network'' and delete the line beginning ''HOSTNAME=''. | ||
Lastly, you need to rebuild the initrd to include the iSCSI kernel modules, using | Lastly, you need to rebuild the initrd to include the iSCSI kernel modules, using | ||
Line 25: | Line 27: | ||
If you use LILO as your bootloader (rather than grub), then you will need to run ''lilo'' after this step. | If you use LILO as your bootloader (rather than grub), then you will need to run ''lilo'' after this step. | ||
+ | |||
+ | Reboot and check that the system comes up without difficulties. You will see an error message saying | ||
+ | |||
+ | insmod: error inserting '/lib/ibft.ko': -1 No such device | ||
+ | |||
+ | during the boot process; this is harmless and simply indicates that the system is not actually booting from an iSCSI disk. You will also find that your boot network interface has not been configured with an IP address; again, this is expected at this stage. | ||
You can now proceed to [[iscsiboot#Transferring the operating system image to an iSCSI target]]. | You can now proceed to [[iscsiboot#Transferring the operating system image to an iSCSI target]]. | ||