the drive you are writing the file
to has to be mounted
the drive must not be write-only
you must spell the path correctly
partimage probably doesn't have the right user priveleges to run right
One or more of the following fixed my problem. I did all of them, so you tell me which was the key one.
1. Fix user priveleges, Fix ReadOnly,
Selected the drive I was copying to from the desktop.
Right click: get device properties.
Picked permissions tab, changed Group and Others to "can read and write", select the "executable" checkbox. (These steps are probably redundant, since I logged in as root later. Not sure how root treats the "readonly" media property, though.)
Picked Device tab.
Unchecked "read only" checkbox.
Noted the mount point was "/mnt/uba1" in the device tab.
2. Fix Mounting the drive.
Opened a terminal.
# sudo su
(logged in as root)
(just to be sure. redundant? Note that it's umount
(use dev, since you are mounting a device. Don't use /mnt, that's the mount point)
"dev/cloop0 inode error" Do you want to create it.
4. Spelled the path correctly.
In partimage I highlighted hda1.
I wrote: /mnt/uba1/image.img
Note that mnt/uba1/image.img isn't the same thing, nor is dev/uba1/image.img
4. In the subsequent page, there's an option to set the split size in MiB. In http://www.partimage.org/forums/viewtopic.php?t=232
someone claims a hard limit of 4 Gigs when writing to FAT32 drives. The default
split size seems to be 2 Gigs (the old FAT32 limit), so you get a series of image files. Seems like a great solution.
5. etc. etc. Created a partition image. w00t!
1. I haven't restored the image yet, so I don't know if it is okay
2. This is because I can't seem to pass the keyboard commands to the menu to pick different options. (Restore vs. backup.) I'm used to dos, throw me a bone here! :) )
3. I don't understand what the cloop error is
4. I know that some of the steps are redundant, but I don't know which ones are.
Can anyone who can give me some insight into what happened that made this work?