uboot and mlo not in boot partition after install
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| flash-kernel (Ubuntu) |
Fix Released
|
High
|
Oliver Grawert | ||
| Quantal |
Fix Released
|
High
|
Oliver Grawert | ||
Bug Description
After installing the 20120924 image on panda, I was not able to boot. Looking at the SD card, I see:
preEnv.txt
preEnv.txt.bak
uEnv.txt
uEnv.txt.bak
uImage
uImage.bak
uInitrd
uInitrd.bak
... but notably, no MLO or u-boot.bin. I can workaround this and get it to boot by simply replacing them off of the original install image.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: flash-kernel 3.0~rc.4ubuntu24
ProcVersionSign
Uname: Linux 3.5.0-211-omap4 armv7l
ApportVersion: 2.5.2-0ubuntu4
Architecture: armhf
Date: Mon Sep 24 23:25:48 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta armhf+omap4 (20120924)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: flash-kernel
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
| Paul Larson (pwlars) wrote | #1 |
| Changed in flash-kernel (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Oliver Grawert (ogra) |
| Changed in flash-kernel (Ubuntu Quantal): | |
| milestone: | none → ubuntu-12.10-beta-2 |
| Oliver Grawert (ogra) wrote | #2 |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in flash-kernel (Ubuntu Quantal): | |
| status: | Confirmed → Fix Released |
| Carla Sella (carla-sella) wrote | #4 |
| Carla Sella (carla-sella) wrote | #5 |
| Carla Sella (carla-sella) wrote | #6 |
while i fixed this bug in flash-kernel 3.0~rc.4ubuntu25, i think it exposes another bug with the flash-kernel back up logic ...
the partition was supposed to be renamed, but accidentially also got reformatted, there should not have been any files to back up
nontheless it seems flash-kernel created .bak files. do you happen to still have such a broken install around ? i would like to know if the .bak files are 0 byte files (which a potentially screwed up user might miss when he tries to copy them back in place to recover something)