Comments on: Remote CentOS 6 install with VNC

By: EvolutionCrazy

EvolutionCrazy — Wed, 13 Oct 2010 23:49:45 +0000

hi joek

that sounds very strange… I would say: impossible (unless you got something changed at the bios level…)

I suppose you already left the box in “starting process” for at least 15mins just to be sure it wasn’t a mirror problem…
A thing I would try would be passing a different mirror to the boot command line (maybe even the OVH internal one: http://mirror.ovh.net/ftp.centos.org/ )

By: joek

joek — Sun, 10 Oct 2010 19:31:29 +0000

Hello,

It has worked before on OVH i7-4T the same method is now not working hardware cheks all done.

Booting Very fine but when i arrive at the step to start the installations it formats the drivers sucessfully then it says: starting process etc.. then nothing happens and the box hangs up.

Tested CentOS, 5.0 , 5.4, 5.5 = Not Working * Worked Before on Same Node *
Tested: CentOS 4.8 = Working * Tested Today *

Why is CentOS 5.5 not working now but before 2 weeks it worked with the same method ?

By: EvolutionCrazy

EvolutionCrazy — Thu, 17 Jun 2010 12:53:37 +0000

ehm…

if you had a previous centos installation (maybe 5.4) when booting the pxe it will asks you if you want to:

- upgrade existing installation (what I think you did)
- install the operating system from scratch (what this guide should be handy to )

if you do not need the data on that box and can format/re-image it I highly suggest you to do again the pxe install choosing the NEW INSTALLATION

By: brai

brai — Thu, 17 Jun 2010 12:49:14 +0000

Hi,

i found there is only pxe entry in /boot/grub/menu.lst
and after boot from grub i found os is updated. this indicate up gradation was successful . I think now we have to do some changes in menu.lst or something else ?
Please guide.

Thanks

By: EvolutionCrazy

EvolutionCrazy — Thu, 17 Jun 2010 12:37:51 +0000

Hi brai.

If after the reboot it’s still booting the pxe kernel it means that the centos install didn’t properly wrote the grub boot loader or you have a network boot (or something else) taking over the centos install…

Re-try maybe specifing something different on the grub bootloader section during the install (try to place it on another partition…)

By: brai

brai — Thu, 17 Jun 2010 12:29:43 +0000

Hello,
This is great . You make a difficult task so simple. After completion it asks for “Reboot” and start in Centos Install (PXE) mode. What to do ?

Thanks in Advance

By: ricola

ricola — Mon, 15 Feb 2010 07:55:03 +0000

Mate Thank you so Much.

This Is Great Tuto i have Tested on C-05G Before 10 Minutes
It works Great!

CentOS Sucessfully Installed. Via VNC Remote Method.

Thank you.

PS. If you need Web-Hosting contact me.

By: EvolutionCrazy

EvolutionCrazy — Tue, 19 Jan 2010 23:41:40 +0000

you are welcome

By: juangake

juangake — Tue, 19 Jan 2010 20:20:34 +0000

Worked like a charm. Tested on OVH server “SP-09 SSD”, Intel Core i5, CentOS 5, the 64 bit version

Thanks a lot!

By: bago

bago — Wed, 04 Nov 2009 09:20:32 +0000

K3XL, just did it.
1) PXE initrd must be patched to indlude the atl1.ko module (from elrepo)
2) Complete install
3) Reboot in rescue-pro
4) From rescue pro mount your root and “download” its initrd and patch it to include the atl1.ko. (rescue-pro does not include the needed tools)
5) Reboot.

Note that adding the atl1.ko module to the PXE initrd means adding it to modules.cgz (cpio gzipped) and to the modules-info and modules.alias files, while adding it to the last initrd means adding it to the lib folder and change the init file to insmod it.

Decompress a centos 5.4 initrd: gzip -dc /boot/initrd-XXXX.img | cpio -ivd
Recompress a centos 5.4 initrd: find . | cpio -o -H newc | gzip -9 > /boot/initrd-XXXX.img