similar to: booting clonezilla *.iso via PXE fails

The clonezilla live project is a really nice way to do image-copies of machines: http://clonezilla.sourceforge.net/clonezilla-live/ but it's based on a Debian live OS which has some unfamiliar quirks. Has anyone built something like this on a Centos base? For anyone who hasn't seen it, it can do whole disk or partition copies of windows and most Linux filesystems and it knows enough to

Hi all, I'm looking for a cloning solution for our Windows/Linux/*nix computer park and ran into Clonezilla. Apparantely the DRBL and other documentation mentions CentOS as a suitable base for it. Does anybody on this list use this solution and can say something about it in the running-Clonezilla-with-CentOS-context, be it recommendations, gotchas', warnings or whatever? Thanks. -- BW,

Hi, I wanted to set up Clonezilla Tools on my client machine via PXE Boot. How do I do it. I got information from the web, but after making changes in the dhcpd.conf file, the dhcpd fails to start. In the BIOS after enabling the PXE Boot, iam not able to see an Clonezilla menu options that i have placed in /pxelinux.cfg file. Iam using centos-5.3 on Intel Board Please provide me with some

I want to clone a small (80GB) disk on my CentOS server to a large (1.5TB) disk, as smart has been giving me warnings of unreadable sectors. Both disks are Western Digital, and WD has a WD version of Acronis True Image. I'm not sure whether to use this or Clonezilla. My worry with Acronis is that I want to keep the original disk, and I'm not sure from the documentation if True Image

In message <BLU0-SMTP4359BC7EA366B1FB76EA9188BBF0 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >I am probably misunderstanding something. We seem to go backwards. Yes, and ever moreso. >"Something" changed. If you now cannot see your USB drive in your >list (press F12 during POST), there is no point on redacting >instructions. *Now* that I have set up

Ady, before responding to you further, I'll ask you now to take onje more (fresh) look at this thread that I started over in the GParted forums: http://gparted-forum.surf4.info/viewtopic.php?pid=31834 Please note that I have now followed-up on myself and that I have added quite a lot of new & additional information. It now appears to me that GParted's reporting of the status of

In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Recent (testing) Clonezilla versions include changes related to >booting problems, so there are valid reasons to try the very latest >version available. At the time I am writing this email, Clonezilla >Live 2.2.1-22 is the latest available (at this moment, under

First, allow me to apologize for taking such a long time to get back to this small project. I just had other things on my plate. My apology extends to everyone who has offered suggestions or advice, but most particularly to Ady <ady-sf at hotmail.com>, who has clearly gone the extra mile to try to help me get this boot problem worked out. Before describing the results of his last set of

I would like to boot FreeDOS ISO image from USB memory stick using syslinux. I have done following: 1) I created a partition to my 2GB memory stick: root at debian64:~# fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size

> > > Ady, before responding to you further, I'll ask you now to take onje > more (fresh) look at this thread that I started over in the GParted > forums: > > http://gparted-forum.surf4.info/viewtopic.php?pid=31834 > > Please note that I have now followed-up on myself and that I have added > quite a lot of new & additional information. > > It now

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

To make say a BIOS flash tool available over PXE, my impression is that a typical procedure goes like this: modify a generic FreeDOS 1440K disk image to contain the EXE and change the AUTOEXEC.BAT to launch that EXE, then make the 1440K IMG available on the PXE server. But more recent BIOS flash EXE are too large and won't fit on the 1440K, not even 3840K, so now we have to look into

The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. If you are interested I could provide a 5MB FDD image template based on FreeDOS 2041 kernel (the latest available at that time in 2014) where you would just inject your ROM and EXE (and possibly adjust autoexec.bat to autostart/apply the FW update). It's a minimal FreeDOS FDD image that defaults to a clean boot with

In the past I have used clonzilla under xen to backup windows domains. I just tried it and it will not work. this is xen 4.1.2 and clonzilla-live 1.2.10-14 the disk line is: disk = [ ''phy:/dev/xvg0/nfdlts-c,hda,w'', ''file:/extra/isoimages/clonzilla.iso,hdc:cdrom,r'' ] It boots cd OK. The problem is devices are xvda not hda and clonzilla is not happy with

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

Dear Syslinux folks, For a firmware update I am following the Gentoo Wiki [1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

Hi, I saw the Nov. 2006 message on Memdisk having a problem with ThinkPads. I also saw the comment in the memdisk code enabling and disabling A20. I've got a ThinkPad x61t that memdisk is not loading disk images on. The symptom is that it gets as far as saying "Loading boot sector... booting..." Then image partially runs - FreeDOS prints out its kernel message and it's

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since