I followed the steps till PXE boot my p2v server.
PXE boot works properly, finds my servers, but ends with an error: RAM disk could not be created
Other DHCP server
Other network switch (1000Mb and 100Mb)
Other NIC in server
but no results
What could be the solution ?
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
First, it's not booting from a CD or Hard Disk if you've reached that error. The 'last-ditch' effort to boot is to attempt a PXE boot from the network card, but your Ethernet cable isn't plugged in. Unless you know you've setup such a PXE boot server, you'll want to check the BIOS settings to be sure the CD-ROM is set to boot first, followed by the Hard Disc. Be sure you have Disc 1 of the Linux installation set in the CD-ROM Drive and reboot. If you don't get the install screen, you may have another issue (bad CD-ROM Drive, bad cable/controller, no power to CD-ROM, etc.)
Another note on the DL380, if there is a RAID controller, you'll need to setup the RAID before installing the OS. You'll want to make sure your hard drives are properly installed and aren't failed. The RAID configuration screen will verify the RAID status once it has been initialized, which will somewhat verify the drive status.
Your computer tries to "boot" (start-up) from several devices:
* floppy-disk (if installed)
* disk-drive (if not "dead"),
* CD/DVD optical device (if "bootable" media has been loaded)
* PXE --> Pre-Execution Environment -- checks if there is a connection between the network-adapter on your computer to a "boot-server" on your local network -- it can load Windows from that "boot-server".
The "media-test failure" indicates that there is no network-cable attached to your computer *AND* the other-end of the network-cable is *NOT* connected to the "boot-server". So, you can that "error" message.
Your computer tries to "boot" from several devices:
* floppy disk
* CD/DVD optical device
* external CD/DVD
* USB memory stick
* PXE ("Pre eXecution Environment)
To use PXE, you need "media" -- a network cable connecting yur computer to a "boot-server". The "media test faiure, check cable" reports that no network-cable exists, or that it does exist WITHOUT being connected to a boot-server.
Probably, your computer failed to boot from a DEAD disk-drive, and then tried floppy/CD/USB before checking PXE.
Your server tries to "boot" from several sources:
* network (if you have a "boot-server" somewhere on your network)
So, if your computer FAILS to boot from the first 3 devices, above, it will try the 4th, namely via your network-adapter.
When your computer finds that its network-adapter is *NOT* connected via an Ethernet cable to a boot-server, it reports "check cable" and "test of the media has failed".
So, why did your server *NOT* boot from the 3rd device, namely your disk-drive? Solve that problem, and the 4th device (the "network-boot") will not be tried, and the error-messages will not appear.
Your computer has been configured to try to "boot" by loading the Operating System from a network-connected "boot-server". Since you're _NOT_ likely to have such a "boot-server" in your home-network, the error-messages that you get are what are _expected_ when your computer is _NOT_ connected via the Ethernet cable to a 'PXE' (Pre-Boot Execution Environment) boot-server.
Enter BIOS-setup, and disable the "boot from network" option.
I don't have any experience with this product but I am 99.9% sure your problem is with Option 67. This path is from the root as defined for the TFTP server, i.e. root for the TFTP service is not the same as root for the server proper.