** Changed in: casper (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/125702
Title:
casper-rw fs not cleanly unmounted on persistent live USB shutdown
SourceForge has eaten the link to the ubuntu-devel-discuss thread as it
considered it an email address. Reposting with a shortened link would be
useful. I would have posted there, but without the MessageID it would
end up outside of the thread.
--
You received this bug notification because you ar
On 05/17/2012 05:20 PM, wodny wrote:
> The noxino idea is not new. I've mentioned this in comment #85 almost
> half a year ago. And it itself was based on an earlier comment.
>
> What do You mean that those 3 lines fail? Have You tried doing it in right
> order, also mentioned in this thread?
>
The noxino idea is not new. I've mentioned this in comment #85 almost
half a year ago. And it itself was based on an earlier comment.
What do You mean that those 3 lines fail? Have You tried doing it in right
order, also mentioned in this thread?
/cdrom -no remount,ro
/ -no remount,noxino,
Here is the /etc/init.d/umountroot file.
The main trick to properly unmounting aufs root is this:
mount -n -o remount,noxino / || echo "Remount noxino / failed: $?"
# This next fails, but over-all, things work, so leaving it in in case
# it has some partial benefit.
mount -n -o remount,mod:/cow=r
Well, I think I finally have this working...mainly due to lots of help from the
aufs maintainer and mailing
list.
Will attach the /etc/init.d/umountrootfs and casper initrd scripts (for Ubuntu
12.04).
You have to re-spin the live-cd initrd to get the casper changes in place. The
umountrootfs ju
Well, I think I finally have this working...mainly due to lots of help from the
aufs maintainer and mailing
list.
Will attach the /etc/init.d/umountrootfs and casper initrd scripts (for Ubuntu
12.04).
You have to re-spin the live-cd initrd to get the casper changes in place. The
umountrootfs ju
Maybe this will do the trick?
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/996668
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/125702
Title:
casper-rw fs not cleanly unmounted on persiste
I built a custom 12.04 with some added kernel patches and added a few
packages (and removed others).
It generally seems to work fine, but at some point, I started seeing
errors about /dev/loop1.
It seems this is the casper-rw file, and it is not checked by fsck on
startup. Why not?
I put the us
Ok, thanks for your tests. I'll try to spend some time on this issue so
we can have it fixed for 12.04.
** Changed in: casper (Ubuntu)
Status: Incomplete => Triaged
** Changed in: casper (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received this bug notificat
Have tried
http://cdimage.ubuntu.com/daily-live/current/precise-desktop-i386.iso (md5sum
19c7877726a0d1b20512647834d5ef85) looped in grub2. integrity check was
successfull.
This one doesn't unmount casper-rw cleanly too. Verified the /etc/init.d/casper
in this daily image is version 1.296.
--
Is it adequate to put version 1.296 onto the casper-rw partition or do we have
to create a new initrd?
I've tried to run version 1.296 manually with sudo sh /etc/init.d/casper stop
but the error remains. I've verified that this is the new file (bigger).
Grub is configured as follows:
menuentry
You can still use tools from the RO partition while it should give the
same type of write-free safety as unmounting,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/125702
Title:
casper-rw fs not clea
Looks like I've run into the equivalent problem after doing a full
install onto a USB stick (I got frustrated with live/persistent
approach). After any shutdown -h the system reports that the root fs was
not cleanly unmounted and does an fsck & reboot. I'll try adding a
sync/sleep to /etc/init.d/um
Have You considered using the tip describing the noxino trick and making
the root filesystem ro during shutdown?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/125702
Title:
casper-rw fs not cleanly
I just made a few changes to that part of casper which "may" fix this bug in
the process.
As I don't have the environment to easily reproduce and test the fix, I'm
attaching the new /etc/init.d/casper in the hope that someone can test it and
see if that fixes your problem.
** Attachment added:
Marking the bug as incomplete until I get someone to test the new
/etc/init.d/casper I attached above.
Tomorrow's daily builds of Precise should also be shipping that init script if
that's easier for you to test with that, just ensure casper is at version 1.296.
--
You received this bug notific
** Changed in: casper (Ubuntu)
Importance: Undecided => High
** Tags added: persistent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/125702
Title:
casper-rw fs not cleanly unmounted on persisten
Ubuntu 10.04.2 LTS (Lucid)
Linux 2.6.35-25-generic
I've also observed this problem. And just like others - I thought it was a
hardware problem at first.
I've experimented with a couple of configurations and it seems that the
current one decreased the number of filesystem errors.
So the theory
up for mr frank... but on the 11.04 distro, were having the same problem
on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/125702
Title:
casper-rw fs not cleanly unmounted on persistent live USB
The same casper-rw file system corruption happens here in the Lucid 10.04.2. I
was first tricked to believe there were bad blocks, then realized I was wrong
after more test and Google to this thread. I know Steve's patch is not for the
Lucid but I still tried, hoping it will work. If the initrd.
update to the updated update: I have a brand new 8GB USB device, fresh
install of Lubuntu, I still get these errors. Running fsck gives:
Block bitmap differences:
Free inodes count wrong
Inode bitmap differences:
home-rw was not cleanly unmounted, check forced.
--
You received this bug notifi
updated update: Would selecting shutdown instead of reboot have anything
to do with it? I notice casper-rw is mounted twice, once as aufs and
again as /media/casper-rw. If I unmount /media/casper-rw it doesn't
appear to have any affect.
Filesystem Size Used Avail Use% Mounted on
aufs
update: Would flush have anything to do with the problem, I notice a lot
of flushes on boot that disappear after a while, and this one seems to
be stuck.
$ps -ef
root 375 2 0 13:20 ?00:00:00 [flush-8:16]
--
You received this bug notification because you are a member of Ubunt
James wrote on 2010-12-13: I cannot. I get no errors that I can see on a
regular boot, but running a check on the casper-rw partition shows that
it gets corrupted after nearly every boot ..
Something similar here, after a few boots I keep getting errors when
running fsck on the USB device. I do se
I cannot. I get no errors that I can see on a regular boot, but running
a check on the casper-rw partition shows that it gets corrupted after
nearly every boot. I first noticed it when it kept gradually loosing
disk space and ran a check on the partition.
I'm running 10.04.1 Lucid
--
You receive
I just did a fresh install of ubuntu 9.10 on my USB drive and there was no more
error message about bad sectors.. etc.
Can someone confirm that this issue has been addressed?
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You receive
> ... even if the cdrom device is actually a thumb ...
Thank you Steve Dodd, you are a life saver :)
That resolve a huge issue with rebooting my usb livecd remix.
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received this bug
Aaaah, yes, that rings a bell. /etc/init.d/casper does an "eject" on the
'cdrom' device - even if the cdrom device is actually a thumb drive.
Some thumb drives apparently just disable themselves in response to
that, until they are un/re-plugged. Debian mention this in their
equivalent script, and w
Hey, i've been twiddling with the usb key a bit more, and i noticed that
if i change anything on the persistent filesystem (aka make changes
while running it, then reboot), i have to physically unplug the usb
briefly, then plug it in again, or it won't boot up (freezes on fetching
bootloader of usb
Hmm... here's a funny one:
First time after applying the patch @ runtime of karmic USB: fail.
But the second time i tried it, it does boot, with settings from last time
remembered! :D
I'm still not sure about the particulars, or if i need to worry about it
failing to boot from USB in the future.
@rene:
Weird. How is the boot failing - any error message? You might need to
boot with "quiet" and "splash" removed from the kernel command line to
see what's going on .. adding "debug" or "debug=y" to the kernel command
line will give even more info (one will debug to the screen, the other
to a f
Ok, i've spent 3 days now trying to get persistent storage on an Ubuntu USB
installation to work.
It fails on karmic too
Not even when using the initrd.gz + /etc/init.d/casper update listed in
this thread, do i get it to work :((
The basic install and startup of Ubuntu from USB works, but sa
Thanks again Steve. I don't see any difference from my casper and the
new one... but... I'll tell you once I reboot if it works :-)
Thank you once more!
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received this bug notification
As I said, I think there is still sometimes a residual I/O error or two,
but they don't seem to be harmful - casper-rw seems to get umounted OK
(check the kernel log to make sure, or fsck the file when booted from a
different system.) Attached is the full replacement /etc/init.d/casper
for 9.04 - m
Two days ago I made my first persitent USB with Jaunty, so this thread
comes up handy for me. I am trying the fix right now, but wouldn't it be
nice if you post also the casper file that soldonz seems to have tested
all right? (I mean with respect to the patch that seems to have some
minor errors s
On Fri, Jun 19, 2009 at 04:14:02AM -, soldonz wrote:
> If this bug occurs in every ubuntu persistent install, then it may be a
> good idea to give it a bit more attention?
Realistically, it's too late to do anything about Jaunty (9.04), and the
mechanism used on the live CDs for union mounts
On Fri, Jun 19, 2009 at 02:11:45AM -, soldonz wrote:
> I just tried the patch, now there are only a couple io error messages
> shown at shutdown screen, compare to a full page of io error messages.
I still see those sometimes - I don't think they're harmful. The
important thing to check is th
I just gave it another go, this time using the casper file that Steve
sent me over the email. The problem is now fixed completely. (not sure
what happened to my patch on casper file, it said it was done
successfully)
thank you so much, Steve.
It surprise me how few instances of this problem have
Thanks Steve,
I just tried the patch, now there are only a couple io error messages
shown at shutdown screen, compare to a full page of io error messages.
Here are the steps I have taken:
1. create a ubuntu 9.04 live USB drive from windows using the batch file from
pendrivelinux.com (using 3GB
(I've already emailed soldonz, but for anybody else who wants to fix a
9.04 live USB/CD setup..)
I've uploaded a patched version of the initrd to a hosting service, I
don't know how long they keep stuff:
http://www.datafilehost.com/download-2e60bf8e.html
The md5 is 0263a21a04c56bf5d24c8f6c16f9ac
I am kinda new with linux and am a bit confused by the new and old
version fo the patch and how they should be applied.
Would you kindly provide an instruction on how to apply the latest patch
or maybe just provide a script that we can just download it and run it
as root?
--
casper-rw fs not cle
Marking this confirmed as a number of people have seen this problem. I
hope that doesn't breach ettiquette ..
** Changed in: casper (Ubuntu)
Status: New => Confirmed
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received t
Here's a new version of the patch, this time leveraging the existing
SHOWMOUNTS functionality that I didn't notice the first time around.
This has the advantage that it works with multiple stacked .squashfs's.
It's still aufs-specific, but's that fine for jaunty and I gather the
hope for karmic is
FWIW, I've justed tested and I can confirm this problem is still present
in Jaunty, as Aleksey and bug #371477 suggest.
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received this bug notification because you are a member of Ubunt
Well done for your work Steve, so this definitely looks like a Casper
bug? In which case I'll mark the Upstart task Invalid and leave the
casper one open
** Changed in: upstart (Ubuntu)
Status: Incomplete => Invalid
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
ht
Oh... I'm sorry... "casper-rw was not cleanly unmounted" only appears after
the first reboot. Now everything is OK. I'm still have two errors on
shutdown/reboot, but after it "casper-rw clean".
Ha-ha! It's working! :) Thank you, Steve! Great job!
--
casper-rw fs not cleanly unmounted on per
OK! I have done as you wrote.
And now I have only two errors in completing the work and such an e2fsck output:
r...@aleksey-laptop:/home/aleksey# e2fsck /dev/sdb2
e2fsck 1.41.4 (27-Jan-2009)
casper-rw was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Check
Thank you very much for the help, Steve!
I would try. I will write as act in Jaunty.
I hope soon I can sleep peacefully ... :)
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received this bug notification because you are a member
Meh, you'll also need to make those patch commands:
patch ... <<'EOM'
(Note the single quotes around the delimiter..)
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received this bug notification because you are a member of Ubunt
Hi Aleksey,
Yes, I think this is the same problem. This fix requires changing two
files, one in the initrd.gz, one in the main filesystem. Fortunately you
can make this second change in the casper-rw filesystem, so there's no
need to rebuild filesystem.squashfs ..
The first _is_ a bit of a pain b
Damn, some of the lines seem to have wrapped.. see attached text file.
** Attachment added: "fix-howto.txt"
http://launchpadlibrarian.net/26318419/fix-howto.txt
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received this bug n
I think, that Alex Roper in this
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/371477 line-up of the
same problem. You can explain the details, what can we do to solve this
problem? I understand that we need to fix the scripts in filesystem.squashfs on
our USB-flash drives? Please, expl
Humph. Looks we need to sync and sleep as well. New patch attached ..
** Attachment added: "new-casper.diff"
http://launchpadlibrarian.net/25210241/new-casper.diff
--
casper-rw fs not cleanly unmounted on persistent live USB shutdown
https://bugs.launchpad.net/bugs/125702
You received this bu
I've rebuilt the intrepid ISO and this patch seems to work. I'd upload
an rdiff but it seems to be ~200Mb - anybody got any ideas about how to
make a squashfs that can be sanely rdiffed against the official live CD
image? I've tried with and without -nolzma using squashfs-tools
1:3.3-1ubuntu2 ..
-
Here's a patch, based on casper 1.152 (the version in intrepid.) I don't
know if this is the best way to achieve this, but it seems to work for
me - this problem can be tested in Virtualbox using a live CD image and
a hard disk partition labelled 'casper-rw'.
** Attachment added: "Expose /cow and
56 matches
Mail list logo
