Bug 57015
Summary: | Ext3 boot fail after crashed ... | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Phattanon Duangdara <sf_alpha> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-12-03 15:10:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Phattanon Duangdara
2001-12-03 10:09:26 UTC
If you use ext3 as module (as the default kernel does) then you must make use of an initrd (which the default setup also does)....... then it will use ext3 instead of ext2. I use grub loader when install and this happen without having modified any grub config or kernel. Did you upgrade to ext3 by hand? If so, you must create a new initrd ramdisk. The requirements for booting from a kernel with modular ext3 are: * You must have an initrd boot ramdisk which is configured to load ext3 (which means you must create this initrd *after* setting the fs type for the root filesystem to "ext3" in /etc/fstab), and * You must instruct the boot loader to load this initrd. If you upgraded to ext3 during a normal 7.2 upgrade, then the installer should deal with all of this for you. This might only be a kernel fault if you did in fact have ext3 loaded at boot but the kernel still couldn't load the root filesystem, but in that case there would be extra boot-time log messages indicating a failure to load root inside ext3. The only log message you supplied was: EXT2fs: Filesystem option not supported by kernel which on its own indicates that this is a configuration problem, not a kernel problem: the system has not been configured to load ext3 at boot time so the kernel is trying to load root as ext2 instead. |