There is no vfat module in the 2.6.24-17 initrd
Bug #236021 reported by
cato
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
Undecided
|
Evan | ||
Hardy |
Fix Released
|
Undecided
|
Evan |
Bug Description
The initramfs lacks vfat support. This means that Wubi users coming from a FAT Windows partition will be able to install (casper has vfat), but they will be left with an unbootable system at the first update-initramfs.
TEST CASE:
Install Ubuntu using Wubi on a Windows FAT partition and install all available updates. Reboot and you will be presented with an initramfs prompt.
A debdiff of the proposed upload can be found here:
http://
Changed in initramfs-tools: | |
assignee: | ago → evand |
Changed in initramfs-tools: | |
assignee: | nobody → evand |
milestone: | none → ubuntu-8.04.1 |
status: | New → Confirmed |
To post a comment you must log in.
Based on a very quick code scan, I believe that this is an old bug never discovered rather than a recent regression (now that I think of it, I did see other people in the past unable to mount from vfat after kernel upgrade).
The initrd in the live cd explicitly adds vfat via casper hooks:
./hooks/ casper: manual_ add_modules vfat
but the same does not hold for regular initramfs-tools.
In particular, there is no vfat reference in initramfs- tools/hook- functions auto_add_ modules> base and dep_add_modules. So when a new initramfs is generated there is no vfat.