Re: [suse-autoinstall] PXE install fails with SCSI disks
Steve, I asked you for more information but I got no answer to the questions below. Could you provide some more information about where it hangs? Anas Anas Nashif wrote:
This is indeed strange. Where does the installation exactly stop. In YaST? In linuxrc? If in YaST, can you send me the log files from /var/log/YaST2/
There should be no difference when installaing over network, same files are used so I do not see why this is failing.
Anas
Steve Glines wrote:
suse.root is the initrd file talen from boot/loader on CD1.
SG
Anas Nashif wrote:
Steve Glines wrote:
I’m building a PXE install lab for SUSE and other flavors of Linux.
The DHCP and tftp servers are working. Note: I can fully install Red Hat from this lab but SUSE (SLES9 rc5) shows the following symptoms:
1. a cdrom install on the target system runs to completion in graphics mode. System is an HP PC with SCSI disk. 2. PXE install runs in non X-window mode (text) and fails to load scsi controllers – cannot find any disks. Fails even when modules are manually added.
Here is the content of /tftpboot/pxelinux.cfg/default:
default suse prompt 1 display boot.msg timeout 200
label redhat kernel redhat.kernel append initrd=redhat.root ramdisk_size=65536
label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536\ install=http://10.0.3.11/suse/CD1/
What is suse.root exactly?
Btw, To get graphical installer, you need to add vga=791 or something similar.
Anas
Anas, I found that installation using only CDs having the same problem of cannnot detect any disk on machines with a SCSI disk. So basically I cannot find a way to install SLES 9 on an opteron with SCSI disks. Do I need to insert some modules at boot prompt? Thanks in advance. --- Anas Nashif <nashif@suse.de> wrote:
Steve, I asked you for more information but I got no answer to the questions below. Could you provide some more information about where it hangs?
Anas
Anas Nashif wrote:
This is indeed strange. Where does the installation exactly stop. In YaST? In linuxrc? If in YaST, can you send me the log files from /var/log/YaST2/
There should be no difference when installaing over network, same files are used so I do not see why this is failing.
Anas
Steve Glines wrote:
suse.root is the initrd file talen from boot/loader on CD1.
SG
Anas Nashif wrote:
Steve Glines wrote:
I�m building a PXE install lab for SUSE and
other flavors of Linux.
The DHCP and tftp servers are working. Note: I
can fully install Red
Hat from this lab but SUSE (SLES9 rc5) shows the following symptoms:
1. a cdrom install on the target system runs to completion in graphics mode. System is an HP PC with SCSI disk. 2. PXE install runs in non X-window mode (text) and fails to load scsi controllers ?cannot find any disks. Fails even when modules are manually added.
Here is the content of /tftpboot/pxelinux.cfg/default:
default suse prompt 1 display boot.msg timeout 200
label redhat kernel redhat.kernel append initrd=redhat.root ramdisk_size=65536
label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536\ install=http://10.0.3.11/suse/CD1/
What is suse.root exactly?
Btw, To get graphical installer, you need to add vga=791 or something similar.
Anas
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
Anas, I found that installation using only CDs having the same problem of cannnot detect any disk on machines with a SCSI disk. So basically I cannot find a way to install SLES 9 on an opteron with SCSI disks. Do I need to insert some modules at boot prompt? Thanks in advance. --- Anas Nashif <nashif@suse.de> wrote:
Steve, I asked you for more information but I got no answer to the questions below. Could you provide some more information about where it hangs?
Anas
Anas Nashif wrote:
This is indeed strange. Where does the installation exactly stop. In YaST? In linuxrc? If in YaST, can you send me the log files from /var/log/YaST2/
There should be no difference when installaing over network, same files are used so I do not see why this is failing.
Anas
Steve Glines wrote:
suse.root is the initrd file talen from boot/loader on CD1.
SG
Anas Nashif wrote:
Steve Glines wrote:
I�m building a PXE install lab for SUSE and
other flavors of Linux.
The DHCP and tftp servers are working. Note: I
can fully install Red
Hat from this lab but SUSE (SLES9 rc5) shows the following symptoms:
1. a cdrom install on the target system runs to completion in graphics mode. System is an HP PC with SCSI disk. 2. PXE install runs in non X-window mode (text) and fails to load scsi controllers ?cannot find any disks. Fails even when modules are manually added.
Here is the content of /tftpboot/pxelinux.cfg/default:
default suse prompt 1 display boot.msg timeout 200
label redhat kernel redhat.kernel append initrd=redhat.root ramdisk_size=65536
label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536\ install=http://10.0.3.11/suse/CD1/
What is suse.root exactly?
Btw, To get graphical installer, you need to add vga=791 or something similar.
Anas
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
participants (2)
-
Anas Nashif -
Frank Samuel