You are not logged in.

#1 2010-02-02 09:51:34

kamigr
Member
Registered: 2008-12-28
Posts: 25

XFS + mkinitcpio -p kernel26 problem

Greetings!

Since the last couple kernel updates this line (in bold) appears during the parsing hook process:

[root@archdesk ~]# mkinitcpio -p kernel26
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
[b]/lib/initcpio/install/autodetect: line 17: filesystem:xfs: command not found[/b]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS

my fstab looks like that:

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
devpts                 /dev/pts      devpts    defaults            0      0
shm                    /dev/shm      tmpfs     nodev,nosuid        0      0

#/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0

/dev/sda2 swap swap defaults 0 0
/dev/sda3 /boot ext4 defaults,noatime 0 2
/dev/sda5 / ext4 defaults,noatime 0 1
/dev/sda6 /var ext4 defaults,noatime 0 2
/dev/sda7 /home ext4 defaults,noatime 0 2
/dev/sda8 /mnt/personal xfs defaults,noatime,logbufs=8 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

this is my mkinitcpio.conf

# 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="ahci"

# 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 filesystems"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"

and this is the part of dmesg regarding to XFS

SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem sda8
Ending clean XFS mount for filesystem: sda8

Any help would be appreciated... thanks!!!

Last edited by kamigr (2010-02-02 09:52:51)

Offline

#2 2010-02-02 17:09:28

bunc
Member
Registered: 2010-01-30
Posts: 6

Re: XFS + mkinitcpio -p kernel26 problem

Well, besides
/lib/initcpio/install/autodetect: line 17: filesystem:xfs: command not found
when generating hooks there's no problem, i.e. /mnt/personal mounts allright and
you can access the filesystem?
If this is so, I'd tend to ignore the mkinitcpio error and have an eye on what happens
when pacman delivers the next kernel version.

Offline

#3 2010-02-02 21:40:12

kamigr
Member
Registered: 2008-12-28
Posts: 25

Re: XFS + mkinitcpio -p kernel26 problem

bunc wrote:

Well, besides
/lib/initcpio/install/autodetect: line 17: filesystem:xfs: command not found
when generating hooks there's no problem, i.e. /mnt/personal mounts allright and
you can access the filesystem?
If this is so, I'd tend to ignore the mkinitcpio error and have an eye on what happens
when pacman delivers the next kernel version.

Hello and thanks for replying!
Yes /mnt/personal is accesible and working, i also have another arch installation that doesn't have that problem during mkinitcpio that's why im a bit confused.

btw, if i remove from the hooks line the autodetect feature then the problem goes away.

Is it ok to remove it, if my hardware remains the same?

Offline

Board footer

Powered by FluxBB