 what goes wrong with this centos5 iscsi pxe-boot [message #34729] |
Thu, 29 January 2009 09:45 |
psc-openvz
Messages: 1
Registered: January 2009
|
Junior Member |
|
|
I installed Centos5 on an iSCSI disk with (mostly) default options, folowing "Using open-iscsi On A System With No Firmware Boot Support for iSCSI" from the Centos5 release notes ( http://www.centos.org/docs/5/html/release-notes/as-x86/RELEA SE-NOTES-U1-x86-en.html). That went fine!
I saved the initrd (actually the whole boot-dir, Alt-F2&ftp directly after install & before reboot!) and tried to setup pxe for booting this machine. Unfortunately, the release notes are not very clear on this.
I googled for remote boot on centos4 and got a few possibilities. Out of that I setup pxelinux.cfg/default as follows:
default vmlinuz-2.6.18-xen
LABEL vmlinuz-2.6.18-xen
KERNEL vmlinuz-2.6.18-92.el5xen
APPEND initrd=initrd-2.6.18-92.el5xen.img ro root=/dev/sda1 \
iscsi_i=iqn.2005-03.com.max:01.cafb27 \
iscsi_i_ip=192.168.1.0/255.255.255.0 \
iscsi_t=iqn.1994-04.org.netbsd.iscsi-target:target0 \
iscsi_a=192.168.1.250 \
iscsi-if=eth0
Then, on pxe booting, I get "invalid or corrupt kernel image"
To find out the cause, I replaced vmlinuz-2.6.18-92.el5xen with one for remote *installation* (http://ftp.cvut.cz/centos/5.2/os/i386/images/pxeboot/). It then *does* boot & loads the initrd. But before it panics it complains about a lots of FS related problems.
If I also replace the vmlinuz from the above source I get a full working *installation* screen (& that's what I don't need) . So PXE-boot *is* working.
If I uses the non xen-vmlinuz &initrd from the saved boot directory, I get similair FS related errors before a panic.
FYI: I compared the iscsi data with the iscsistartup string in 'init' after extracting it from initrd-2.6.18-92.el5xen.img
What goes wrong or what am I doing wrong??
[Updated on: Thu, 29 January 2009 10:50] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
