Comment 25 for bug 84591

Well, I took my revised livecd in which I had reverted the casper and ubiquity packages to the version used by feisty herd3 and I tried to additionally revert udev to the herd3 version of udev.

This did break the distribution (it hangs on boot when executing the local scripts), but there was one potentially important difference in my boot messages.

My casper-rw filesystem is an ext2 filesystem. When I boot up and persistence works, I always get the message "EXT2-FS Warning: Mounting unchecked filesystem. Running E2FSK is recommended" (or something to that effect). When persistence does not work, that message is conspicuously absent in my boot messages. When it shows up, it comes right after the message "SquashFS: version . . . ."

In my customized livecd that uses the herd3 version of udev, this message showed up again. This seems to suggest that reverting to the herd3 version of udev may fix the timing issue because this message suggests that the casper-rw filesystem is mounting with the old udev. Note, in order to use the old udev, I did also have to revert on a few other packages, so it could be in udev or one of the related packages that I reverted (these other files were either listed with the udev binaries on launchpad or were the files dpkg forced me to revert when I tried to install the old udev - dmsetup was one of them; I think there were two that had "volumeid" in the name).