Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I'm part of a project called One2One2Go - we're developing a Live USB Ubuntu variant for use in schools in Somerville, MA. We have the project files compiled into an iso, and when installed using the native Ubuntu Startup Disk Creator, the USB works fine. When installed using a tool on a Windows machine (LiLi at linuxliveusb.com or liveusb-creator at fedorahosted.org/liveusb-creator), the USB works, but does not have persistence. This happens even if the creator is specifically set to allocate an area for persistent files.

When comparing files on sticks created in Windows or Ubuntu, the one file that is different is syslinux/syslinux.cfg. I have printed the contents of the file below:

Installed on Windows:

DEFAULT nomodset
LABEL debug
menu label ^debug
kernel /casper/vmlinuz
append boot=casper xforcevesa initrd=/casper/initrd.gz --
LABEL nomodset
menu label ^nomodset
kernel /casper/vmlinuz
append boot=casper quiet splash nomodset initrd=/casper/initrd.gz --
LABEL memtest
menu label ^Memory test
kernel /install/memtest
append -
LABEL hd
menu label ^Boot from first hard disk
localboot 0x80
append -
PROMPT 0
TIMEOUT 1

Installed on Ubuntu:

DEFAULT nomodset
LABEL debug
menu label ^debug
kernel /casper/vmlinuz
append noprompt cdrom-detect/try-usb=true persistent boot=casper xforcevesa
initrd=/casper/initrd.gz --
LABEL nomodset
menu label ^nomodset
kernel /casper/vmlinuz
append noprompt cdrom-detect/try-usb=true persistent boot=casper quiet splash nomodset initrd=/casper/initrd.gz --
LABEL memtest
menu label ^Memory test
kernel /install/memtest
append -
LABEL hd
menu label ^Boot from first hard disk
localboot 0x80
append -
PROMPT 0
TIMEOUT 1

For troubleshooting reasons, I changed the Windows-created syslinux.cfg to match the one created by Ubuntu and persistence worked on it.

I think the problem is that on the stick created by Windows, there is no "persistent" flag, but I don't know why. Is this a problem with our disk image or with the creator? How would I go about fixing this problem?

Thanks in advance for your help.

Derek Redfern

share|improve this question
    
This question seems abandoned, there is not further information or activity added to it for several months. I am flagging this to be closed by a moderator. If you think this issue is still affecting you you can flag a moderator to re-open it. –  Bruno Pereira Feb 3 '12 at 1:17
add comment

closed as too localized by Marco Ceppi Feb 3 '12 at 1:18

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer

If you can repeat it, and it's not a feature, maybe the Ubuntu bug reports page is a good place to start.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.