You are not logged in.

#1 2008-11-28 20:19:44

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

[Solved] What's missing in mkinitcpio.conf? EXT4 issue....

Alright I'm not sure what I'm missing in mkinitcpio.conf. I can boot with the fallback kernel without a problem, however when I'm trying to use my initrd image that is generated by mkinitcpio the kernel complains that it can not find /dev/sda2 and fails to load.

This is what my mkinitcpio.conf looks like:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="pata_acpi ata_generic ata_piix ext3 ext4dev"

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish.  This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
#    FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
#    This setup specifies all modules in the MODULES setting above.
#    No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
#    This setup will autodetect all modules for your system and should
#    work as a sane default
#    HOOKS="base udev autodetect pata scsi sata filesystems"
#
#    This is identical to the above, except the old ide subsystem is
#    used for IDE devices instead of the new pata subsystem.
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
#    This setup will generate a 'full' image which supports most systems.
#    No autodetection is done.
#    HOOKS="base udev pata scsi sata usb filesystems"
#
#    This setup assembles an pata raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev pata raid encrypt filesystems"
#
#    This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"
#HOOKS="base udev autodetect pata scsi sata usbinput keymap filesystems"
HOOKS="base udev autodetect sata usbinput filesystems"

Any help would be great wink

Last edited by pyther (2008-11-29 14:22:50)


Website - Blog - arch-home
Arch User since March 2005

Offline

#2 2008-11-28 21:09:17

shazeal
Member
From: New Zealand
Registered: 2007-06-05
Posts: 341

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

Sounds like ext4dev is being stripped? try doing a mkinitcpio to make the image without autodetect in the hooks. There is some debug option you could try in mkinitcpio as well.

Last edited by shazeal (2008-11-28 21:09:58)

Offline

#3 2008-11-28 21:31:58

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

I don't think it's being striped as its in the initrd image along with mbcache,jbd2, and crc16

[pyther@tux ~]$ bsdtar -tf /boot/kernel26.img  | grep ext4
bsdtar: Removing leading '/' from member names
lib/modules/2.6.27-ARCH/kernel/fs/ext4
lib/modules/2.6.27-ARCH/kernel/fs/ext4/ext4dev.ko

Website - Blog - arch-home
Arch User since March 2005

Offline

#4 2008-11-29 03:29:31

shazeal
Member
From: New Zealand
Registered: 2007-06-05
Posts: 341

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

Check if its trying to mount it as EXT3-fs, I know my true ext4 partitions are still considered ext3 until it hits the extents and falls back to ext4. ext4dev has some extra tune2fs parm like testfs or something you need to add, I barely touched ext4dev just went straight to 2.6.28 for the real thing so Im probably not much help.

Offline

#5 2008-11-29 14:22:26

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

Well somehow my ext4 partition was created as an ext2 partition according to fdisk!
I ended up reformatting the drive as ext4 and I was able to boot into 2.6.27-ARCH without a problem.

Now I am going to try 2.6.28-rc6 and I suppose that won't give me a problem either. (As before it told me it could not mount the rootfs)


Website - Blog - arch-home
Arch User since March 2005

Offline

#6 2008-11-29 17:02:34

klixon
Member
From: Nederland
Registered: 2007-01-17
Posts: 525

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

Switching between a 2.6.28-rc and 2.6.27 kernel might give you problems though...
On boot, a kernel i was trying (2.6.28-rc6-zen1) stripped the test_fs attribute off my ext4 partitions automagically. A 2.6.27 kernel still needs this, so before switching to a 2.6.27 from 2.6.28-rc, type this from a root-prompt:

for partition in ext4-partition1 ext4-partition2 ; do tune2fs -E test_fs /dev/$partition; done

Stand back, intruder, or i'll blast you out of space! I am Klixon and I don't want any dealings with you human lifeforms. I'm a cyborg!

Offline

#7 2008-11-29 17:31:37

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

I don't plan on switching as everything is working great!

But thanks for the tip!


Website - Blog - arch-home
Arch User since March 2005

Offline

#8 2008-12-27 13:44:51

dhave
Arch Linux f@h Team Member
From: Outside the matrix.
Registered: 2005-05-15
Posts: 1,112

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

pyther wrote:

I don't plan on switching as everything is working great!

This is no excuse for not messing with your system. tongue


Donate to Arch!

Tired? There's a nap for that. --anonymous

Offline

#9 2009-02-25 17:09:48

Convergence
Member
Registered: 2005-07-02
Posts: 377

Re: [Solved] What's missing in mkinitcpio.conf? EXT4 issue....

I completely reformatted and reinstalled using ext4 as my / fs.  I did this before the new arch boot disk came out, so I had to do a little reading, but it seemed to have worked.  I made sure that i enabled extents, and ran tune2fs, so It should be fully ext4, and mtab says that it is mounted as ext4, but cfdisk thinks that it is ext3.  is cfdisk wrong?


It's a very deadly weapon to know what you're doing
---  William Murderface

Offline

Board footer

Powered by FluxBB