Well my Dell Mini 10 wouldn't boot at a coffee shop and I couldn't figure out what was going on. This is my first shot at Ubuntu (been a Gentoo user for years) and I got all the errors I'm reading about in this bug when booting on battery. I used JFS (I like JFS) and it does need to have fsck run. I don't see why it's such a big deal to not run it on battery. Even with ext3, does it take THAT long? Seriously?!
So I tried all the normal tricks like "mount / -o remount -o rw" and all kinds of combinations. Never seen an fstab that attaches a UUID to a drive before now, but I can understand how that's useful. Not even "init=/bin/sh" as a kernel param worked. There was no way for me to fix this until I got home, found this bug, and commented those lines out of the checkroot.sh and checkfs.sh boot scripts while on A/C power. I'm about to go back to Gentoo. I like being able to actually fix stuff when it goes bad without having to plug in an A/C adapter. This is a serious bug. Won't fix? Seriously? You have got to be kidding me! And I though the guys on the Gentoo bugzilla were jerks. This is a serious bug. I guess it just doesn't apply to ext3 (probably xfs too)? -- fsck not run on boot if on battery power https://bugs.launchpad.net/bugs/219382 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
