Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

" SYSLINUX 6.03 EDD 2014-10-06 Copyright (C) 1994-2014 H .Peter Anvin et al "

i have IBM x3650 M3 server and when i install petasan2.0.iso and give the ip and finished all steps ...finally we he asked me to reboot ..it dose not open and give me error

" SYSLINUX 6.03 EDD 2014-10-06 Copyright (C) 1994-2014 H .Peter Anvin et al "

what can i do now ??

can you put a photo shot image of what you see on the screen.

What disk controller are you using for your os boot disk ? is it ServeRAID ?  Do you have other disks on the system that are not connected to this controller you can try as os disk ? can you remove any RAID configuration on the os disk and try.

My first feeling is the ServeRAID  driver was not included in the initial ram disk initrd image required to boot the system.  Do you have enough RAM ? Other possibility is the installer was not able to format the disk correctly,.

I have IBM x3650 M3 Server with 265 MB Ram and Using Raid 0

Error is

" SYSLINUX 6.03 EDD 2014-10-06 Copyright (C) 1994-2014 H .Peter Anvin et al "

 

 

is that all you see on screen ?

256  GB  ?

Sorry

yaa it is 256 GB Ram and this the error massege in boot screen

 

You mean you only see  " SYSLINUX 6.03 EDD 2014-10-06 Copyright (C) 1994-2014 H .Peter Anvin et al " and nothing  else...correct ? Or is there  a boot loader prompt  ? any messages in on not finding kernel or initrd...or the rest is really blank ?

What is the controller type for the os disk : is it ServeRAID ?

Does your hardware allow you to have a disk not connected to this controller. if so can you try to install on that disk

yes this only Error  message i see ...

can you tell me which RAID kind Recommended

My syslinux.cfg file is

" display boot.msg
default installer

label installer
kernel /boot/vmlinuz
initrd /boot/initrd.gz
append loglevel=3 cde vga=791 nomodeset

implicit 0
prompt 0
timeout 300  "

All known controllers should work . But just for the boot disk i recommend you use a disk not using ServeRAID controller. The ServeRAID should be supported for your data disks, the installer was able to see disks  connected to ServeRAID and write to them. The only is during boot, i may  be possible the ServeRAID driver is not included in the initial ram disk required to load the system.  If you have other disks not connected to ServerRAID, use those as the os disk for boot and the ServeRAID for data. If  all your disks are accessed via ServeRAID, we should be able to check if its driver is included in the initial ram disk and add it if required.