Oh yea. the basic error when booting this is several 100 lines saying

Cant open /dev/sr0

then

(initramfs) unable to find a medium containing a live file system.
(initramfs)

Hmm. The rescue remix uses the same kernel and intrd as does the live cd. It's funny that Ubuntu 9.10 boots while the Remix doesn't.

Maybe it's because of the presence of mdadm? The mdadm package adds a script to the initrd to look for and assemble arrays at boot time...

EDIT. I just noticed that I renamed the initrd with a gz extension instead of lz. That may be the problem. Stay tuned...

https://bugs.launchpad.net/ubuntu/+source/casper/+bug/406192

This explains the "cannot open /dev/sr0" phenomenon.

Are you pointing your loopback to the wrong iso? See comment in quoted part of your first post:

Quote:

menuentry "Ubuntu rescue remix - /boot/iso/ubuntur.iso (Not working Properly)" {
loopback loop /boot/iso/netbook.iso <<--- Is this wrong? Should it be /boot/iso/ubuntur.iso?
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/boot/iso/ubuntur.iso --
initrd (loop)/casper/initrd.gz
}

# NOTE the initrd.gz is NOT the same as the initrd.lz the other iso files use.

End Quote.

So, should the stanza look like this?:
menuentry "Ubuntu rescue remix - /boot/iso/ubuntur.iso (Not working Properly)" {
loopback loop /boot/iso/ubuntur.iso
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/boot/iso/ubuntur.iso --
initrd (loop)/casper/initrd.gz
}

that was a typo on my part. :) i got the right iso file on the actual entries. I got so many testing entries i cant keep them straight.
I even changed the name from 'ubuntur.iso' to ur.iso so its easier for me to spell/check now. Still trying to figure this out.

Stay tuned for Further Developments.

I have reproduced your problem.

I can use GRUB2 to boot the official Ubuntu iso but not the Remix from a USB stick..

It seems to throw the same errors on boot, but Casper is able to find the filesystem on the official ISO image where the remix cannot. I excluded the /.disk/casper-uuid-generic file since I didn't know it's purpose and it works fine without it, but I am rebuilding the iso with it and will see if that's what it's looking for. If that doesn't work, I will look for other possibilities.

What I did.

Installed grub-pc

determined that my particular usb drive is /dev/sdc and /dev/sdc1. Sdc1 is mounted in /media/disk

grub-install --no-floppy --root-directory=/media/disk /dev/sdc

Then, edited /media/disk/boot/grub/grub.cfg and added

menuentry "Ubuntu-Rescue-Remix 9.10" {
loopback loop /boot/iso/ubuntu-rescue-remix-9-10.iso
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/boot/iso/ubuntu-rescue-remix-9-10.iso --
initrd (loop)/casper/initrd.lz
}

menuentry "Ubuntu 9.10" {
loopback loop /boot/iso/brasero.iso
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/boot/iso/brasero.iso --
initrd (loop)/casper/initrd.lz
}

I copied the isos to the drive, too.

Note, I am working with a rebuilt iso that uses initrd.ls instead of gz.

No change.

I notice that I didn't include lupin-casper:
Description: Add support for loop-mount installations to casper

I am adding that package to the iso image and will test that....

That worked!

I will build it properly and upload a revision soon.

For now, the quick-and-dirty iso is here:

http://ubuntu-rescue-remix.org/files/URR/iso/ubuntu-rescue-remix-9-10-r2.iso

Glad i could help track down a problem. :) Ive been posting similer suggestions/messages to other disrtos forums so Hopefully in a month or so Every disrto out can support this cool feature..

Too bad people cant agree on the proper kernel option to tell it where the iso file is. the 2 disrtos ive gotten it working with so far use diffrent named options. And Ubuntus option is a little.. odd.

iso-scan/filename=/boot/iso/ubuntu-rescue-remix-9-10.iso

Just seems a tad overkill. a / In the option name. :)

Well off to test this out.

I updated the release to use today's revision.

http://ubuntu-rescue-remix.org/node/195