Comment 30 for bug 443080

And it booted succesfully!
I did saw that the order was different. Before, I had:
fsck 2.16
fsck2.16
/dev/sda5 clean
/dev/sda7 clean

Now, it was
fsck 2.16
/dev/sda5 clean
<another message from another process>
fsck 2.16
/dev/sda7 clean

On Fri, Oct 9, 2009 at 13:20, Ernst Blaauw <email address hidden> wrote:

> Here's the log.
>
>
> On Fri, Oct 9, 2009 at 13:01, Scott James Remnant <email address hidden>wrote:
>
>> Sorry about the issues with the previous PPA versions, as usual things
>> worked just fine when I tested it in the various rigs I have here - of
>> course it flatly failed when installed on normal systems because I
>> hadn't actually tested that ;)
>>
>> I've uploaded a new ~boot4 version, this one feels much better (and I'm
>> running it on my laptop now :p)
>>
>> As before, after installing the package but *before* you reboot, please
>> run with --debug and attach the log to the bug - then after rebooting,
>> let me know how it works out.
>>
>> Thanks for all your help with testing, this is a big change and it's
>> good to know that it's now working for 95% of people and your help
>> getting it work for the final 5% is greatly appreciated!
>>
>> ** Changed in: mountall (Ubuntu Karmic)
>> Status: New => Incomplete
>>
>> --
>> boot hangs during forced fsck
>> https://bugs.launchpad.net/bugs/443080
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>