I get the same error on Tribe3. I think I mentioned this, but just to be sure, I am booting into persistent mode.
I am using a "Live USB" that I create in accordance with the Ubuntu Wiki. It is a 4GB Drive. My casper-rw partition is a little over 2GB. I did also try a different USB drive and got the same error with another USB drive. I do exactly the same thing with Edgy as I do with Gutsy and I don't get the error with Edgy. Based upon some customized iso's I created to get persistence to work on Feisty, it looks like the error also occurred with the Feisty iso (unless I pin the Feisty upstart files at the Edgy versions). I have the casper-rw partition formatted as ext2. I don't have a swap partition, so the system may be using a swap file. The partition on which I am placing the "iso" files is formatted FAT32. I don't have any other disks mounted - just the Live USB. Presumably the casper-rw partition is mounted using unionfs. I don't know if this error may somehow be related to the persistence issues, but persistence does seem like it is working at least to some extent (e.g. I installed an application and it was present when I rebooted; it didn't maintain my WPA password, but it did maintain my keyring password). If I execute the "sync" command before shutting down, I still get the same error. After booting up again after I get the umount failure, I believe I may have seen some errors (I am booting in debug mode). I don't remember the error message exactly, but will try to note the details if I see it again. I think it may have been error 110 or something like that, with maybe some sort of message about inodes. My recollection is that the error was associated with the casper-rw partition (I am pretty sure that that was the case, but can double check that if I get the error again). If it would be useful to you to have me burn an actual CD and try persistence using the CD, I can try to do that as well if you think it will provide useful information. I am using an IBM X41 tablet with a mobile pentium. Obviously it has an internal drive, but again it is not mounted. I can't think of other information at the moment that might be useful, but if there is any additional info I can provide, feel free to let me know. Regards, Mike On 7/20/07, Michael Panepucci <[EMAIL PROTECTED]> wrote: > > I'll try the new version. > > It looks like your email got cut off. It looks like you were saying it > would be helpful to know something? > > On 7/19/07, Brian Murray <[EMAIL PROTECTED]> wrote: > > > > Thanks for taking the time to report this bug and helping to make Ubuntu > > better. There is now a newer Tribe CD available and we were wondering > > if the problem exists with it. Additionally, it would be quite helpful > > to know Thanks in advance. > > > > ** Changed in: Ubuntu > > Assignee: (unassigned) => Brian Murray > > Status: New => Incomplete > > > > -- > > 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. > > > > -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
