Mkinitcpio to build Initial RAM Disk: error: /dev/sr0: No medium found

Question

Prior to using mkinitcpio-busybox 1.15.3-5, building an Initial RAM Disk for my custom kernel resulted in no error messages.
Using mkinitcpio-busybox 1.15.3-5, I ran and got:
[root@Galicja linux-2.6.33.1]# mkinitcpio -k 2.6.33.1-ARCHMOD -g /boot/kernel26-2.6.33.1-ARCHMOD.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
error: /dev/sr0: No medium found
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-2.6.33.1-ARCHMOD.img'...SUCCESS
However, using this Initial RAM Disk in menu.lst for booting into my new kernel worked fine (as before when I wasn't using mkinitcpio-busybox) without any crashes, panics, or errors.
Should the message "error: /dev/sr0: No medium found" refer to a 'warning' instead of an error? What can I do to avoid this message (adjust any hooks or modules in mkinitcpio.conf)?
Note: /dev/sr0 refers to my Optical Block Device (CdRom).
Here are the contents of my mkinitcpio.conf file:
# 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=""
# 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
# '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"

Answer 1

Got the exact same error here. Did not get it before said changes to mkinitcpio (busybox).
However, there are some things I did not quite understand:
djgera: "(don't worry, is not an issue)"
By that you mean that it is not a bug or that it is not going to give the system any troubles?
.:B:. :"I don't see how the error message is 'misleading'? Do you mean you do have an optical drive while the script doesn't seem to pick it up?"
Do you mean that if I have an optical drive then I should not be getting this error? 'Cause I've got one and the error always appears to me. Or should I be getting the error output even though I have an optical device? If that is so, then in that sense I think said error message is potentially misleading for if it is an initrd-related error, then something is not going to work well on my Initial Ram Disk. I mean, by errors I understand that certain things will not be working well or mainly not working at all. If that is not the case, then I don't see why the output is given as an error. Thanks for the attention.
Last edited by gabscic (2010-04-04 01:27:51)