I must be getting a different bug (though some of the symptoms are
similar).  I've never had the unmount error or segmentation fault, but I
always seem to get about a dozen or so "Buffer I/O error"s on shutdown
(after the message about removing the disc and pressing Enter...even if
I don't press enter, I eventually get the errors...of course I don't
unplug the USB drive, but if I do, I get the same result), resulting in
dramatic corruption when it was formatted ext2.

Using ext3 for casper-rw buys me some time, but I still get the errors
(I'm not sure if there's any file corruption--no evidence of any, yet).
Also, it adds "aborting journal on device sdb3" errors.

Steve:  Thanks for your help.  I ended up doing this (had to download
the deb for dpkg-repack manually...the Edgy repositories are no longer
available), along with booting the persistent system and installing
"dpkg-dev"  so I could use dpkg-scanpackages to make a local source
repository for the Edgy upstart debs I made, as well as using the
preferences file at top to downgrade the packages.  However, it didn't
help with the buffer I/O errors. (I assume this fixed the umount error,
which I've never had...maybe the bug is gone with Hardy, or is only
applicable on some installations?)

Mike: I tried doing that initially, but the Edgy repositories are no
longer available (I'm assuming because Edgy is no longer supported).
That's why I had to find a way to do it with the LiveCD of Edgy (I was
able to find a download of the iso still), and use dpkg-repack to make
the three debs for upstart.

So, in my case (which apparently is a different bug), the old upstart
packages didn't help.  Thank you, Steve and Mike, though, for helping me
downgrade those packages!

-- 
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 subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to