Comment 3 for bug 1004151
Revision history for this message
| David Williams (david-williams) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
BTW, I was able to work around this. I booted by 64 bit version (which is in a separate partition) then mounted the 32 bit partition as "plain data" mount (not to run anything). It had an empty boot folder (presumably since I have my own boot partition, where "the real" files reside) and a few symbolic links that pointed to non-existed files in the empty boot folder. So, I removed those (and, the empty boot folder). unmounted it. reboot back onto the 32 bit partition, and could then complete the update just fine.
Thanks.