As waxhell also reported, it seems to be working better with casper-rw formatted as ext3 instead of ext2. In fact, everything thus far seems fine after 4 re-boots and conducting persistent activity each time. But I do get some messages:
When I log out and re-boot from the live persistent session, I do get the following message (instead of the message I reported in my post above when I used ext2 for casper-rw): Unmounting local filesystems ... [failed] casper is resyncing snapshots and caching reboot files. Please remove the disk, close the tray (if any), and press Enter to continue. [After pressing Enter, then:] Will now restart. No problems, EXCEPT twice so far I got: Error-KDesktop The process for the file protocol died unexpectedly. [and the Desktop was empty of my icons] Then I pressed OK, then Refresh Desktop did not help, then Control+Alt+Backspace, and it cleared it up so everything was back on the Desktop (all the persistent stuff I had put there). Finally, if anyone is interested in the GRUB boot stanza I'm using: title Kubuntu 7.10 LIVE Persistent root (hd0,0) kernel /casper/vmlinuz boot=casper ramdisk_size=1048576 root=/dev/ram rw quite splash persistent initrd /casper/initrd.gz I don't know about wear-out issues (with either ext2 or ext3), but that is a separate issue. -- failure to umount local filesystems - gutsy tribe 2 https://bugs.launchpad.net/bugs/125702 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
