The current version can only read/write from/to a partition. Partimage doesn’t use the partition table at all. (The Linux kernel reads it, and Partimage can directly use hda1, hda2, …). But I’d like to implement this in the future, to allow users to select partition to save/restore from a list (with name, size, filesys, usage, …), and Partimage would be able to create the partition if needed at restore, or resize it…
You can’t restore to a smaller partition (you will have an error), but it’s possible to restore to a lager one. In this case, some space will be lost (I suppose the OS cannot use all the size). Partimage don’t have a resize feature, but you can use other tools. I’d like to add this in the future too. It will allow to restore into a smaller or larger partition. Indeed, as Partimage is low level it uses data blocks. So resizing is possible, but that’s a complex feature to implement. With some File Systems made to be easily resizable (as NTFS, ext2, ReiserFS), it may be easy, but with FAT, it’s hard to do. For example, when resizing from 1,5 GB to 3 GB, you must change FAT16 into FAT32… You can use GNU Parted to do it.
NTFS write support, as UFS write support are dangerous and supported only by experimental drivers. It can damage partitions, and corrupt data. That’s why it’s not enabled in partimage-bootdisk. Users who weren’t aware of this problem could lose their data if the support was enabled.
If you need the write support, you will have to use another bootdisk. Please, have a look at the question in this FAQ which explains how to build your own bootdisk.
A segmentation fault means that some part of the program was not coded correctly. Report this to authors. Give as many details as you can (architecture, package version, what you did, /proc/partitions file, output of dmesg, logfiles…). If you can reproduce the matter, tell us what you did step by step. In any case, if you can, try with -g10 option to create full log file. We may need your help so don’t delete images or don’t erase your partition.
Quick answer: no. A bit longer, partimage/partimaged 0.6.x can’t work on Big Endian machine. On Little Endian machine, you may have luck any make it working but you’ll be on your own because we won’t be able to help you. If someone has an old Sparc, HPUX, MIPS or whatever he doesn’t use, please, give it to us and we’ll be able to make partimage working on non-i386.
Yes. You just need to use -b (batch) option on command line. You may use something like this: partimage -b -z3 save /dev/sda9 /mnt/image_sda9.
dd if=/dev/zero of=/mnt/filetmp
rm /mnt/filetmp
dd if=/dev/xxx
gzip > image_file.gz
Sorry, Partition Image is not a high level program, like Ghost. Ghost makes a file copy, and we obtain a file in a tar.gz archive, with other details (such as the boot sector). But Partimage works at a low level, as Drive Image: it copies used blocks of the disk. So, it doesn’t know where files are written, and cannot allow to see files in the image without restoring. But maybe it will become possible in future versions. We will try to make partimage image files mountable: a driver, such as the loop one, could allow us to make an image file be a block device. If you know how to write block device drivers, please contact us.
Many users write us because they can’t use the network (or another device). In most cases, the problem comes from the bootdisk/bootcd which does not support all drivers.
Space is limited in both partimage-bootdisk and partimage-rootdisk. We can’t include all drivers that exists in the kernel sources. That’s why only the most common NE2000 cards, and the most common AIC7xxx SCSI drivers are supported. It provides support for a lot of devices, but some of them need another driver. For example, 3COM cards are not supported. There are many ways to solve this problem:
Initial RAM disk initrd support. In the File systems, you must choose Yes for the Minix FS support. In the loadable module support page, you must choose No, in order to disable modules. After compiling your kernel, you will obtain bzImage. You must type three commands to make it the same thing as an official partimage-bootdisk image:
I’m having a problem with booting from the bootdisk.
I’ve created the disk from the partimage-0.3.5-bootdisk-1.raw file, and when booting, all I see is
090009000900090009000900090009000900090009000900090009000900090009000900090 0090009000900090009000900090009000900090009000900090009000900090009000900090 0090009000900090009000900090009000900090009000900
all over the screen.
This is a problem when you download the file with Netscape, and the ASCII mode. Try using FTP, or another tool: type wget AdressOfTheFileToDownload
The path is the one you choose with partimage in “Image file to create/use” on first screen. 2 cases: 1. If you entered absolute path (name starts by a ‘/'), it will be used as it. 2. You entered a relative path (name starts by anything else than ‘/'). The path will be related to the one you started partimaged from. If you only gave image filename, the path will be the current directory (where you started partimaged).
partimaged switched to ‘partimag’ user for security reasons but ion your system, this user can’t write in the directory you choose to save images. You have to change permissions of the directory. Man chmod and chown can help you here.
First: run
Then, put partimaged.key and partimaged.cert into appropriate directory and chmod them 0600
If partimaged –chroot {your directory} doesn’t fail, you’ll be able to run partimaged as daemon into chrooted environment with `partimaged -D –chroot {your directory}’
Not yet. Once we’ll have a working boot cdrom we’ll try to add this feature via Samba.
Yes. Partimage makes a physical copy of the partition. It’s not a simple “tar.gz” of files. In other words, it does the same work than dd does, but it forget to copy all free blocks in order to save space and time. All blocks which are not marked as free will be copied. Then everything is kept (boot sector informations, all attributes that can exist, …) It even keeps location of files on the disk, then the vmlinuz file won’t be moved, and LILO will continue to work.
Copyright 2002-2003 François Dupoux, Franck Ladurelle.
We disclaim everything. The contents of this article might be totally inaccurate, inappropriate, misguided, or otherwise perverse.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.
Note: it’s not a call to make this document unusable .