Hi guys,I recently download LMDE and test it, in personally reason i decide to use live it from my multiboot USB Stick that grub2 installed to it.with this script http://www.panticz.de/MultiBootUSB i booted many iso file, directly from usb stick, but for LMDE i don`t know any true kernel option/cheatcodes for use as menuentry in grub.cfg file.i try several cheatcodes but all of them failed.if you look at the isolinux.cfg on iso file, find that kernel option might "live-media-path=/casper" to find location of this file : filesystem.squashfs (see the below structure)i discuse this issue on irc #linuxmint-debian , #debian-live and #grub, but so far i have not recived any true response.

Ouch! I just got hit by this same problem yesterday -- I was going to demonstrate Linux Mint Debian to a friend of mine on my grub2 'multi-boot' USB stick, and it failed to boot! I was a bit embarrassed, since I had just assumed that it would work like the other distros (including Mint Gnome and LXDE) on the stick. Here is my grub.cfg entry:

Yes, that would probably be how 'unetbootin' does it i.e. opening up the ISO file and copying the pieces to the USB stick. Personally, I want to be able to use *just* the ISO file itself -- so that I can have multiple on the single USB stick, as well as very easy replacement when new versions come out. My impression is that something is 'missing' from LMDE that currently makes direct USB booting of the ISO impossible -- but I would love to be proved wrong

wimac wrote:Yes, that would probably be how 'unetbootin' does it i.e. opening up the ISO file and copying the pieces to the USB stick. Personally, I want to be able to use *just* the ISO file itself -- so that I can have multiple on the single USB stick, as well as very easy replacement when new versions come out. My impression is that something is 'missing' from LMDE that currently makes direct USB booting of the ISO impossible -- but I would love to be proved wrong

You can just have different entries in the grub.cfg for the other iso's just can't do it for this one.

I wonder if (or why) the 'isoscan' syntax would work in this case? It did not way back in my earlier attempts, but isn't that what it is for i.e. not needing to specify the exact name/location of the ISO? Anyways, thanks for plugging away at this problem

darethehair wrote:Yes, the 'uuid' method mentioned on this thread also worked, but -- unless I am missing something -- only works on a *specific* PC for that particular UUID (?), so that is not an option for me.

Hello again! I prefer the label method, but the uuid is going to be the uuid of the parition on the usb flash drive. I don't think it would change unless you repartitioned or maybe reformatted the drive. But, yes, labels are so much more human friendly. You can also use labels to mount your partitions from a working system; http://debian-resources.org/node/9/

darethehair wrote: Hello again! I prefer the label method, but the uuid is going to be the uuid of the parition on the usb flash drive. I don't think it would change unless you repartitioned or maybe reformatted the drive

For max portability, am I not correct that the UUID *only* works for the machine that the particular UUID was generated for? That is my experience i.e. the UUID of my USB stick is *different* on my desktop PC than the one assigned on my netbook, so I cannot boot the ISO on the netbook that way (?).

Sorry if I'm necroing an old post, but I'm basically trying to boot LMDE live on a USB stick via Grub2, so I felt this was the right place. Here's my situation and reasons for doing that:

I wanna create an emergency pen drive, containing all utilities which may come in handy, like GParted, Clonezilla, qt4 and a complete and persistent live distro of Linux. For this last task I've chosen Mint Debian as it's my main Operating System, the one I use for everything, so I'm in pretty good relation with it. The problem is, to permanently install it on my hard drive, I unetbooted it, and unetbooting uses isolinux as bootloader, if I don't go wrong. I'd like to use one unique bootloader for my whole emergency USB, in particular grub2 with direct boot, without any chainloading whatsoever. I'd prefer to have the files directly on my drive just like unetbootin does, rather than booting the entire archived ISO file.

I tried a lot in the past to no avail, but I currently don't remember exactly the ways I did try and the failures I achieved. I resumed the project right now, here's what I did (as root).

I created an ext2 partition on my USB for the system files of my live distro to go (label="live"), planning to shrink it as little as possible when it worked, in order to make space for the persistent partition. Used GParted on my LMDE system.

HisDudeness wrote:I wanna create an emergency pen drive, containing all utilities which may come in handy, like GParted, Clonezilla, qt4 and a complete and persistent live distro of Linux.

I used Easy2Boot, Made using Win7, on a 8G USB flash, and had 10 iso multiboot, such as:

Debian Wheezypartedmagic ( within it there are gparted, qt4-fsarchiver, testdisk, clonezilla, etc...)RIPlinux ( used for me to boot any partition when grub boot loader took holiday and does not boot, so RIPLinux can be run on USB and boot any partition, as long as that partition is bootable, windows can be booted too).netrunnerstella (Centos+repos)PCLinuxOSetc etc

I know it can be made persistent, I have not yet tried since I do not need to.The tutorial on Easy2Boot have covered the method.

Wow, thanks for signaling that, it looks like a really outstanding piece of software. I'll definitely look into it and play some time with the thing. Can you just give me some anticipations?

Does it work with compressed archives containing all the nécessaire to be booted (I mean zips, rars, tar.gzs and such), or must them be archived with ISO extension for E2B to recognize and handle them?

Has it its own bootmenu as a personalized port of grub, or does it simply set up a plain grub for you with everything you tell him to?

HisDudeness wrote:Does it work with compressed archives containing all the nécessaire to be booted (I mean zips, rars, tar.gzs and such), or must them be archived with ISO extension for E2B to recognize and handle them?

Please read this from tutorial 72a of easy2boot website

PLEASE NOTE: With Easy2Boot I talk about 'payload files' because E2B can boot other files besides .iso files. Payload files are bootable files that E2B recognises and can boot from. So in many cases, a 'payload file' is an ISO file. However, a 'payload file' can also be a .BIN file (e.g. memtest86.bin) or a .IMA file (e.g. a DOS floppy disk 1.44MB image file), or a .IMG file (a bootable disk image) or a .VHD file (a virtual hard disk image), etc. etc.

[*]Has it its own bootmenu as a personalized port of grub, or does it simply set up a plain grub for you with everything you tell him to?[/list]

it sets up grub4dos onto your USB flash, this is covered in his tutorial 72a in great details

Probably there are some things there that are not necessary or not optimal. I wouldn't mind knowing what they are. In any case, I have found that booting from ISOs can be a tricky business and full of trial and error.

The "toram=" stuffs the whole ISO in RAM. If you don't have lots of RAM, leave that one out.