Kernel panic when reading ramdisk from dirty ext3 file system
Bug #76259 reported by
Thorbjørn Ravn Andersen
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-source-2.6.15 (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
I have a Xubuntu 6.06 machine which has worked perfectly but after the power was pulled, it fails to load the initial ramdisk (a decompression error), and panics.
Booting on a live CD and fcsk'ing the filsystem caused it to be fixed from the ext3 journal, but it never got that far in the initial boot process,so apparently the ramdisk file was for some reason dirty.
Revision history for this message
| Ben Collins (ben-collins) wrote | #1 |
| Changed in linux-source-2.6.15: | |
| status: | Unconfirmed → Rejected |
To post a comment you must log in.
Nothing I can do to fix this. Requires the recovery CD. The kernel also does not read the ext3 filesystem. Grub does this, and loads the file into memory. The kernel decompresses from memory.
The ext3 and storage modules are not even loaded at this point, so the kernel can't even begin to fix this.