Comment 24 for bug 125702

Revision history for this message
Ron Z (rzwaal) wrote : Re: [Bug 125702] Re: failure to umount local filesystems - gutsy tribe 2

I ended up following Mikes? advice and used ext3 instead of ext2 for both
the casper-rw and the home-rw partitions. I also followed the instructions
for removing the eject cd message and the instructions here (
http://www.atworkonline.it/~bibe/ubuntu/custom-livecd.htm) to customize the
installation. I updated all the software and adjusted the packages. I've
been using this setup for almost a month without problems on both my 8Gig
verbatim and my 2G SanDisk Cruzer. I use both almost daily and just checked
them and they're error free.

I've made a 1G partition for the squash filesystem (I've loaded quite a few
extras) and on the 8G stick a 700M casper-rw partition and the rest of the
device is for my home-rw partition. On the 2G stick I have a 300M casper-rw
and the rest (700M) for my home partition.

Hope this helps. (I should check my email a little more often:-)

Ron

On Jan 9, 2008 2:40 PM, jpolizo <email address hidden> wrote:

> I believe I am running into a variant of this same problem. I installed
> 7.10 on a USB drive and it works great when using just the live CD mode.
> When I use persistence (second partition is ext2) it works great the
> first time I boot and then it steadily degrades after that. In one
> case, I had a corrupted /etc/sudoers file and when I looked at this on
> another machine the file had the contents of mtab stuffed right into the
> middle of it. In other cases it has blown up the X configuration so
> that X cannot start.
>
> No matter how bad the persistent mode boot gets, it wall always boot
> fine in "live" mode.
>
> If I do an fsck on the casper-rw drive, I get lots of errors after a
> reboot. If I fix the errors and then delete everything on the casper-
> rew drive, it will boot again fine in "persistent" mode though obviously
> that's not very persistent.
>
> I've also tried 'sync' before a shutdown of the system but that doesn't
> seem to help. I also tried doing a suspend and unsuspend and that
> seemed to work fine with no corruption.
>
> --
> failure to umount local filesystems - gutsy tribe 2
> https://bugs.launchpad.net/bugs/125702
> You received this bug notification because you are a direct subscriber
> of the bug.
>