Just checked that again, and the journal does get replayed, so the rw fs
isn't being umounted cleanly. I also noticed block device I/O errors on
shutdown.
Digging into this a bit deeper, some observations:
* Whatever this line from /etc/rc0.d/S40umountfs is supposed to do ..
PROTECTED_MOUNTS="$(
I created a persistent setup on a USB stick using the 'official' USB
installer in Intrepid. I haven't had any corruption problems (yet), but
the ext3 journal on the casper-rw (loopback) filesystem still seems to
get replayed on start up, which presumably means it wasn't cleanly
unmounted (or the bl
Since it seems to be still alive issue, I would like to add recent
experience.
I have tried to do the same setup as before using new 8.04.1 version.
Using the same 1GB stick I used before led to the same problems (with
corruption and missing files). Then I got 8GB stick, brand new, and did
the ins
** Changed in: upstart (Ubuntu)
Status: Confirmed => Incomplete
--
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
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 en
drewster:
I think you can also boot up into your persistent system, add the
preferences file to /etc/apt as described above, change your
sources.list repositories to edgy rather than hardy, and then run sudo
apt-get install [list the upstart files that were pinned]. That should
cause the files to
drewster: you could boot from the Live CD, then install dpkg-repack and
use it reconstruct the packages you need.
--
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 subs
I am getting the exact same errors with my persistent 8.04 LiveUSB
drive. Using ext3 on the casper-rw partition helped a little, but I
still get a string of buffer I/O errors on shutdown.
Since Edgy Eft is no longer supported (as of 4-25-08), it seems rather
hard to find the versions of the 3 ups
Mike,
Thanks for the info. I tried cloning a drive as per your instructions below
and it worked flawlessly. Still, copying the files using cp -rf seems to
corrupt them during the copy process. Also, I blew away the casper-rw
partition after cloning and ended up with the same issues I had before (th
mikeXYZ: If it is shutdown issue, what about files with access
mode? I believe these are created on the fly.
--
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 subs
Ron Z, that's not the case for my experience with this bug (corrupt
files already there somehow)--it's clearly a shutdown issue for me &
have seen this elsewhere, too.
btw,
As for the flash drive, if I have a working, bootable flash drive (e.g., live
persistent Kubuntu 7.10), I clone it easily w
Here is another thought. I'm not confident at all that the problem is with
shutting down the system at all. I've noticed that files created on the
pendrive when running from the pendrive are often corrupt.
One of the things I use pendirive linux for is downloading podcasts while on
the road. Often
Just a thought - and I am the first to admit my limited knowledge - but
maybe it is not completely the code that is shutting down the system
that is causing the issue. Maybe the more recent version of upstart is
somehow creating a system state that is not created by the earlier
version of upstart.
This bug still baffles me.
Upstart is barely involved in shutting down the machine, so it should
make no difference which version is running.
** Also affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
failure to umount local filesystems - gutsy tribe 2
https://bugs.launchpa
Thanks all, pinning preferences at first post fixes the primary issue in
whatever tribe I would get if I ran update last week.
I found my new problem with ttys is related to a video bug since
everything works fine when I plug ubuntu into an intel915 but totally
fails with my ati9600. Must of upda
Christopher:
I do an tune2fs -c 1 to force a check everytime the volume is
mounted.
My setup still is without errors, but I don't use my persistent thumbdrive that
often (maybe once every two weeks or so).
--
failure to umount local filesystems - gutsy tribe 2
https://bugs.launchpad.net/bugs
It's been so long since I looked at this, I don't remember for sure,
but I think there are actually 3 upstart files that need to pinned at
the edgy level. I used aptitude to downgrade, so whenever I pinned
one, the other two were downgraded automatically. But, you may want
to make sure all three
Maybe something different about our systems.
On Jan 20, 2008 10:56 AM, Michael Panepucci <[EMAIL PROTECTED]> wrote:
> It always works for me that way, with both feisty and gutsy.
>
>
> On Jan 18, 2008 6:29 AM, Christopher Barth <[EMAIL PROTECTED]> wrote:
> > I pinned upstart at edgy and downgraded
It always works for me that way, with both feisty and gutsy.
On Jan 18, 2008 6:29 AM, Christopher Barth <[EMAIL PROTECTED]> wrote:
> I pinned upstart at edgy and downgraded by adding edgy repositories to
> sources.list, but my 7.10 hangs on halt
> >From init1 I get hang or usr prompt (I can call
I pinned upstart at edgy and downgraded by adding edgy repositories to
sources.list, but my 7.10 hangs on halt
>From init1 I get hang or usr prompt (I can call for shutdown as many times as
>I want; system won't halt), from x I get the shutdown splash with moving bar
>than flashing cursor
How d
I also wanted to confirm that this problem still exists in 8.04 alpha 1
and alpha 3 for Ubuntu and Xubuntu. Also, some random daily-builds in
the middle. I haven't checked Kubuntu or any daily-builds since. Are
there any log files we can view/post to make triaging this easier? Can
anyone figure ou
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
One possibly important thing I failed to mention is that I'm testing on
a laptop with a dual-core Centrino.
--
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 co
I concur to what jpolizo wrote. I spent the whole day playing with this
setup (i.e. Gutsy on 1GB USB as per
http://www.pendrivelinux.com/2007/09/28/usb-ubuntu-710-gutsy-gibbon-
install/) and noticed following details when booting into persistent:
1) some settings are stored, some not (like new use
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
For me, same as reported by waxhell (above). Issue with: Kubuntu 7.10 on UFD,
Live Persistent.
I've tried using ext3 and I get the same segmentation fault. I did not test
the extent of data corruption using ext3 (vs ext2), but I suspect it will show
up upon repeated re-boots.
I have also seen
I tried persistence in the 6.10 version and I think there are problems
there too although much less than in 7.10.
When the 6.10 version is shutting down, I would see I/O errors to the
USB device. I ran fsck on the casper partition and it did find a number
of errors. Most notably, mtab had errors
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 co
It seems to me that the problem exists with the live cd as well. I've
tried this with the AMD64 and the i386 versions of ubuntu and kubuntu on
an AMD64 laptop and desktop and an intel laptop all with the same
segfault unmounting the filesystem on shutdown/reboot from the cd.
The problem seems to b
Confirmation that I'm seeing similar results with corrupted/unmounted
casper partitions in the released Gutsy, using a LiveUSB install.
--
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 Ubun
Also, at least for the problem I experienced, reverting to the edgy
version of upstart made at least that particular problem go away
(although I don't know if that will meet your needs).
On Oct 29, 2007 10:23 PM, waxhell <[EMAIL PROTECTED]> wrote:
> Ext3 seems to help the data corruption (probably
Ext3 seems to help the data corruption (probably at the expense of the
drive lifetime).
I've set my drive to run e2fschk every boot, and it seems to be better.
--
failure to umount local filesystems - gutsy tribe 2
https://bugs.launchpad.net/bugs/125702
You received this bug notification because
I confirmed the waxhell's report. The writing features for home folder
sometimes works sometimes don't. The system writing is not working yet.
live-initramfs of Debian does not produce the error, however persistent
writing is not yet working. I think Ubuntu and Debian should merge in
together and
I may have this bug in Gutsy release, however in my instance, I get a seg fault.
Persistence enabled on a pen-drive. Experiencing some data corruption as a
result of this (not all files are copied properly to the casper-rw partition)
Reference Bug #147117
* Umounting local filesystem
umount2:
Is there any additional information that you need from me?
--
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
u
Bug has not been triaged: there is insufficient information here to
identify the fix, only sufficient information to confirm that there is a
bug.
** Changed in: upstart (Ubuntu)
Status: Triaged => Confirmed
--
failure to umount local filesystems - gutsy tribe 2
https://bugs.launchpad.net/
bug still present in Gutsy beta
--
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
** Changed in: upstart (Ubuntu)
Assignee: Brian Murray (brian-murray) => (unassigned)
--
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.
Error still present in the Gutsy beta candidate iso.
--
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-
** Changed in: upstart (Ubuntu)
Sourcepackagename: None => upstart
Importance: Undecided => Medium
Status: Incomplete => Triaged
--
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 U
Error still shows up in tribe 5.
On 7/21/07, Michael Panepucci <[EMAIL PROTECTED]> wrote:
>
> Although it says it is activating a swap file when I am booting up, it
> looks like my system may not be using swap. If I type "free" in a terminal,
> I get the following:
>
> total u
Although it says it is activating a swap file when I am booting up, it looks
like my system may not be using swap. If I type "free" in a terminal, I get
the following:
total used free sharedbuffers cached
Mem: 1026464 572388 454076 0
My fstab file contains the following when booted up:
unionfs / unionfs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
My mtab file contains the following:
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /lib/modules/2.6.22-8-generic/volatile tmpfs rw,mode=0755 0 0
varrun /var/run tmpfs rw,noexec,
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 go
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 Tr
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) => B
It is possible to make this failure go away by reverting to the edgy
version of the upstart files.
I.e. by including a preferences file in the /etc/apt directory that
contains the following and downgrading to these versions:
Package: upstart
Pin: version 0.2.7-7
Pin-Priority: 1001
Package: upsta
47 matches
Mail list logo
