SystemRescueCd
 

Does anyone use SystemRescueCd to make disk images ?

SystemRescueCd
 

I mostly use it to boot up systems with a broken boot loader.

If it has dd on it, & I expect it has, yes you could make disk images using it.

I think most distros have dd.

I used dd twice to make a bootable disk and it failed twice.

Then it may be the method you use. Please tell us exactly what you want to do and show us the commands you used, including their output.

dd if=/root/Downloads/slacko-5.7.0-PAE.iso of=/dev/sdi1 bs=4M

root# ./iso.sh
40+1 records in
40+1 records out
169869312 bytes (170 MB) copied, 45.0313 s, 3.8 MB/s

When booting with pendrive, this message appears.

isolinux.bin Missing or corrupted

AFAIK, the Slacko Puppy image is not in the isohybrid format that would be needed for doing it the dd way. You may have luck with converting it using the isohybrid command, alternatively Unetbootin will help you to get a working Slacko USB drive.

It did the same with Debian and other distros.

Copying the entire ISO image to a USB flash drive works only for "dual format" images that have been built to work as both a CD/DVD image and as a partitioned, bootable device when copied to a flash drive. To make a bootable flash drive for SystemRescueCd, you need to follow the instructions on the sysresccd.org web site.

[EDIT] Sorry, I've misunderstood what you are trying to do.

I tried Unetbootin.

It said there was no USB drive present.

There was a pendrive present.

If I did not have Windows, I could never make a bootable pendrive.

That should be a priority for Linux programmers.

I got a bootable Systemrescue cd on a pendrive.

But I could not find anything that would let me make a disk image to another drive.

This of=/dev/sdi1 should be of=/dev/sdi the device, not a partition.;)

Indeed, I totally missed that. Shame on me.

Unetbootin is hit and miss. It sometimes does not write the right disk to the ISOLINUX boot loader configuration for some distributions. It affects USB devices. As a result it will boot to the wrong partition and the system will not be able to find the kernel or filesystem.

I am not sure exactly what happens with Unetbootin that causes this. I have observed it happen with a number of different ISO images while creating USB bootable disks. Please do not quote me on this, as I am not 100% positive of the cause or it's accuracy.

As a result, I try to avoid using Unetbootin in favor of dd.

Unfortunately, it did not change anything.

I tried it on two different brands of pen drives and none would boot.