Resolved a few issues. Metapackage and Grub2

Thanks to everyone who help bring a few issues to my attention. Namely, the fact that the ubuntu-rescue-remix-tools metapackage included a dependency that could not be resolved and that the iso image would not work properly when using GRUB2 to boot it. The iso image still worked fine with the regular USB creator, though.

To install the ubuntu-rescue-remix metapackage on any Ubuntu system (including live USB systems), add the following software source:

deb karmic main

Then authenticate this software source by runing the following command:

sudo apt-key adv --keyserver --recv-keys BDFD6D77

Then, install the "ubuntu-rescue-remix-tools" package.

This can be done on a live USB Ubuntu desktop. So you can have a full data recovery toolkit on top of your regular Ubuntu graphical interface (GUI). That's because if you create your USB live system with persistent data, you can install packages and they will still be there the next time you boot the USB drive.

Step 1, create a live USB system:

Insert a USB drive with enough space to hold the Ubuntu Desktop iso (700 MG) plus persistent data - I use a 4 Gig USB stick, but you can get away with a 1 gig stick.

Start the USB Creator (System - Administration - USB Startup Disk Creator)

Browse your filesystem for the iso image of the Ubuntu desktop. Pick the "stored in reserved extra space" option and move the slider to use as much extra space as you want. Make it go.

Screenshot-Make USB Startup DiskScreenshot-Make USB Startup Disk

Setp 2, boot into your live USB system:

Once you are at the Ubuntu desktop in your live USB, select System - Administration - Software Sources and enable the four software channels (Main, Universe, Restricted and Multiverse) You don't need the Source Code channel.

Screenshot-Software SourcesScreenshot-Software Sources

Next click the Other Software tab and add this line:

deb karmic main

Screenshot-Untitled WindowScreenshot-Untitled Window

You will need to reload your list of available packages:

Screenshot-Untitled Window-1Screenshot-Untitled Window-1

Next, open a terminal and run the following commands:

sudo apt-key adv --keyserver --recv-keys BDFD6D77

sudo apt-get install ubuntu-rescue-remix-tools

Screenshot-ubuntu@ubuntu: ~Screenshot-ubuntu@ubuntu: ~

And the packages are being installed to the persistent data on your USB drive.

Screenshot-ubuntu@ubuntu: ~-1Screenshot-ubuntu@ubuntu: ~-1

Now every time you reboot into your Live USB system, the ubuntu-rescue-remix tools will be there for you.


For details on how to boot the Ubuntu-Rescue-Remix live iso using Grub2, see this forum discussion

Thanks again for everyone's help.

This has the md5sum of the

This has the md5sum of the md5sum.txt in the md5sum.txt file which will never work*, because adding the md5sum of the 'old' md5sum.txt to the 'old' md5sum.txt changes it's md5sum to the md5sum of a 'new' md5sum.txt and thus the added md5sum will be invalid.

Aka when creating checksums don't put the checksum of md5sum.txt in md5sum.txt
If you want to add a checksum of the checksum to something, do it in a separate file. note: there will always be one file that doesn't get a checksum.**

*This information applies to other checksums not just md5, it's just written in terms of 'md5sum' instead of 'checksum'.
**Come to think of it, I suppose the checksuming utility could during checking detect that the checksum refers to itself, and could verify that the checksum on that line matches the checksum of that file without that line, and forward. Not that I've seen one do it that way. Is there one? Anyone want to make a md5sum program that works that way?

Example result of adding md5sum of a file to itself:

md5sum -c md5sum.txt
./casper/filesystem.squashfs: OK
./casper/initrd.lz: OK
./casper/vmlinuz: OK
./isolinux/isolinux.bin: OK
./isolinux/isolinux.cfg: OK
./isolinux/splash.rle: OK
./isolinux/isolinux.txt: OK
./install/sbm.img: OK
./install/memtest: OK
./README.diskdefines: OK
./ubuntu: OK
./.disk/info: OK
./.disk/base_installable: OK
./.disk/casper-uuid-generic: OK
./.disk/release_notes_url: OK
./.disk/cd_type: OK
./md5sum.txt: FAILED
md5sum: WARNING: 1 of 17 computed checksums did NOT match

This is how the ISO is

This is how the ISO is made:

And this is how the MD5SUM.txt file is made.

I never noticed that the md5sum.txt file is part of that - and that is obviously not correct. On an ISO image so small, I never had a use for the ms5sums anyway.

I will edit the page for correctness.

Thanks for pointing this out.

(Page edited: 136 2009-11-06 14:31:51 20381 Andrew Zajac md5sum eats itself.

I edited the page of link

I edited the page of link that you gave me; so that if there are any md5sum.txt files in subdirectories they will get a md5sum, but the file that the new md5sums are going to go is left alone, so that the md5sum won't "eat itself".

Hi Brian. I had already

Hi Brian.

I had already edited that page so the problem is no longer there (check the history). The image folder is pristine and there is no other reason for an md5sum.txt file to be there. So now that added complexity is redundant.

I have removed the two-step

I have removed the two-step procedure in favor of your more robust solution.

When the USB Boot flash

When the USB Boot flash drive was made how was it formated?
FAT FAT16, FAT32 or other?

My 4G flash drive will not work as a USB Boot as I can not burn it.
IT shows up as one drive with one partition, and the USB
startup creator will not let me do anything with it.
I can read and write to it, hence it is ok.

Any other sugestions?


No trees were killed in the sending of this message. However,

a large number of electrons were temporally inconvenienced.

What does cat

What does
cat /proc/partitions

If your USB drive is present as, say, /dev/sdc (and not both /dev/sdc and /dev/sdc1), then it is a single drive with no partition table. Often but not always, you can still boot from these drives. Your motherboard can run syslinux (the bootloader) without having been directed to do so by the MBR. I reckon the USB creator is refusing to use it because it has no partition table.

You can try to create a partition table on the drive. First, make a backup of all the data on the drive, since we will be reformatting it.

Run a partition tool on your drive. For example parted. You can use cfdisk if you prefer a curses interface.

andy@andy-desktop:~/usb$ sudo parted /dev/sdc print
Error: /dev/sdc: unrecognised disk label

andy@andy-desktop:~/usb$ sudo parted /dev/sdc mklabel "msdos"

andy@andy-desktop:~/usb$ sudo parted /dev/sdc print
Model: (sdc)
Disk /dev/sdc: 4295MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags

Then create a partition on it and format it to FAT 32. Unplug and then replug the drive to make sure it works and you can see the filesystem. If that's fine, then try the USB creator on it. If the drive doesn't work, reformat the drive back to a fat filesystem on it:

sudo mkfs.msdos /dev/sdc

Note: In all of the examples, make sure you are using the correct device (/dev/sdc may be incorrect for your hardware!)

I added ubuntu-rescue-remix

I added ubuntu-rescue-remix to Live USB, and it has stopped work under VirtualPC. Spent a whole day to find out a solution but no luck. Any ideas?
Online md5 generator.

Sounds like a bug in Virtual

Sounds like a bug in Virtual PC.

I followed the instructions

I followed the instructions to create a bootable USB stick with Ubuntu (v.12.04) and was (after some issues) able to install ubuntu-rescue-remix tools.

I confirmed installation by typing ddrescue in a terminal.

However, after I rebooted the USB stick, ddrescue was no longer installed (and the changes to software sources had reverted back).

I appears that the changes to Ubuntu are not persistent after a reboot.
How can make the installation etc persistent?