Summary: I had upgraded my Karmic system to Lucid Alpha 2 and everything
went fine. I had also been applying updates with Update Manager
successfully until about mid-February when a whole bunch of updates came
out. After those updates, my machine would fail to completely boot. Ever
since, I found I can re-install with the Lucid Alpha 2 alternate install
CD to maintain my multi-filesystem setup (/boot, /, /home. /tmp, /var)
that uses LVM over a RAID 1 (mirrorred) disk pair. However once I try to
apply all the current updates with Update Manager, the system
successfully boots once (although perhaps slower than usual), and then
fails to complete booting up on the subsequent reboot. BTW, there also
seems to be an issue with grub2 configuration in the install CD but I
managed to bypass that by using LILO, generating a Grub configuration
once Alpha2 was running, and keeping a tarball of the /boot/grub
directory around that I could expand during subsequent Alpha 2 re-
installs.
The boot sequence hangs with the Ubuntu logo and a "Waiting for /var
[SM]" message. One thing I have noticed is that with a successful Lucid
Alpha 2 boot, the boot sequence shows banners for 5 e2fsck startups and
after the update only 4 show up. I also see the fsck results for all
the file systems on Alpha2, but results from /var are missing after the
dist-upgrade to what I presume are an early release of the Alpha 3
packages. I've tried rolling back the mountall and e2fsprogs/libs/etc
packages to the Alpha 2 versions after doing the dist-upgrade, but that
hasn't changed anything. After the upgrade, I've tried booting from the
Alpha 2 CD into rescue mode and successfully fsck'd /var (the only
problem it picked up was a "time stamp in the future" issue) but the
system still wouldn't boot completely. With 500+ update packages in the
queue it just isn't feasible for me to figure out which one is the
culprit especially when the problem takes 2 reboots to manifest, so I
need help. What should I be doing at this point to narrow down the cause
of the problem when I can't get the system to complete booting to a
shell prompt?
I just don't know what to try next but I would expect an Alpha 3 install
will have similar problems for me when it comes out. There probably
aren't too many people running Lucid Alpha on LVM/RAID with a separate
/var filesystem, so I'm presuming that one of those items is a factor in
causing this problem. Since those are more common on production systems,
it would be good to address this before Lucid gets deployed to those.
** Changed in: hal (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/hal/+question/102242
--
system hangs on reboots after upgrading lucid alpha 2 hal packages
https://bugs.launchpad.net/bugs/524135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
