Tag Info

Hot answers tagged

4

I finally got to the bottom of this and did manage to get it working. In the process, though, I've come to the conclusion that iSCSI boot functionality in Windows, gPXE, and iPXE are all half-baked. I'll share the approach that worked for me in case it helps anyone else, but please be aware of some caveats: This is a poor solution. A hardware-based ...


3

sysinstall has been deprecated in FreeBSD 9. The new, and better way, to install FreeBSD is using the bsdinstall software. If you want to use a Linux Server I would recommend you to create a custom mfsBSD image with FreeBSD 10.0-RELEASE as the basis. In this image you can create a custom rc.local file to automatically start bsdinstall and even make an ...


3

(My initial answer was premature. As promised, I've rewritten it after having gotten everything working.) First of all, I've found that in general iSCSI-boot-enabling software is half-baked, and the disparate systems involved interoperate very poorly. For this reason I recommend instead going with a hardware-based solution such as iSCSI HBAs if possible. ...


2

A memdisk approach usually needs RAM >= 1.3 x ISO image size at the client; could it be you are running out of memory? A memdisk approach will fail as soon as the booted kernel enters in protected mode. gpxe/ipxe are full of feature projects but also full of bugs and inconsistencies. Also gpxe hasn't been maintained in long time. Today a safe PXE server ...


2

PXE boot does use TFTP to transfer the image, while TFTP bases on UDP which has alot of disadvantages. Modern GPXE does use HTTP or FTP to transfer the image which much more better speed. To satisfy your demand, all you need is a working GPXE server and Grub4dos bootloader. Diskless client will request IP by DHCP, then download the gpxe module, then ...


1

To answer my own question. sanboot --no-describe --drive 0x80 or it might be 0x81 or 0x82 I was able to boot a linux USB drive on 0x82.


1

I assume you already have some idea about PXE boot or network boot. In most cases, you don't need to install gPXE in your hard drive. All you need is enable PXE/Network boot in your bios and make it the 1st booting device. Following are some links related to PXE boot http://superuser.com/a/521077/170017 <- This is a guild line for setting up Windows ...


1

I'm afraid your network hardware doesn't support boot images of that size, try to reduce your boot image or make it a two steps loader. There's a good guide on the gPXE wiki about chanining gPXE into a 2 steps boot, have a look here


1

PXE sounds a bit late to me. I'd rather configure the DHCP server to give those windows systems their boot server and not the linux TFTP server: http://tspycher.com/booting-into-wds-windows-deployment-service-from-linux-dhcpd/


1

In general, there is not much to booting a Linux kernel off PXE - the PXELinux / Syslinux web page has a number of examples. You even can boot up an entire distro like SysRescueCD and do your restore from there. But since you have a specialized requirement for imaging and restoration, you might want to look at Clonezilla - it is an OSS Linux distro doing ...



Only top voted, non community-wiki answers of a minimum length are eligible