You are not logged in.

#1 2010-03-15 23:21:19

ejmarkow
Member
From: Siemiechów, Poland
Registered: 2008-09-02
Posts: 84
Website

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

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"

Offline

#2 2010-03-15 23:43:43

djgera
Developer
From: Buenos Aires - Argentina
Registered: 2008-12-24
Posts: 723
Website

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

This is already reported here:

FS#18585 - [mkinitcpio] Silent error message: No medium found in autodetect hook
http://bugs.archlinux.org/task/18585

(don't worry, is not an issue)

Offline

#3 2010-03-16 10:46:36

ejmarkow
Member
From: Siemiechów, Poland
Registered: 2008-09-02
Posts: 84
Website

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

@djgera - Thanks for the link and info. I realize it's not an issue, for the RAM Disk image which was created in using Kernel 2.6.33.1 works fine. Regardless, the resulting error message (error: /dev/sr0: No medium found) should not be displayed as it is a bit misleading.

I will leave this post as unresolved until it is fixed.

[ejm@Galicja ~]$ uname -a
Linux Galicja 2.6.33.1-ARCHMOD #1 PREEMPT Mon Mar 15 21:14:26 CET 2010 x86_64 Genuine Intel(R) CPU 575 @ 2.00GHz GenuineIntel GNU/Linux

Last edited by ejmarkow (2010-03-16 10:47:43)

Offline

#4 2010-03-16 15:55:32

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

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

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?

Same thing happens on systems without optical drive (every optical drive is referred to as /dev/srX by default btw wink). It is harmless though (I don't really know why it wants to know about the optical drive anyway).


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#5 2010-04-04 01:20:00

gabscic
Member
Registered: 2008-11-15
Posts: 19

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

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)

Offline

#6 2010-04-04 11:33:32

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

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

.:B:. wrote:

It is harmless though (I don't really know why it wants to know about the optical drive anyway).

Maybe to check for any filesystems there and add the needed modules to the boot image, can't think of any other reason.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#7 2010-04-04 17:41:13

Meyithi
Member
From: Wirral, UK
Registered: 2009-06-21
Posts: 550
Website

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

Might just be me, but if there is a disk in the drive the error doesn't appear.


The mind roams more freely in empty rooms.
dwm - colours - ncmpcpp - system
irc://irc.freenode.net:meyithi

Offline

#8 2010-04-06 05:14:44

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 323

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

Well, I am saying the same: It might just be me...

However, since the last kernel upgrade, and the said error message, my DVD burner has not been working. It's a LG HL-DT-ST DVDRAM GSA-4167B.

It may of course very well be that the thing has died all on its own, as it were, but I am wondering...

Any suggestion for finding out which it is?

Offline

#9 2010-04-07 03:06:59

cecilyen
Member
From: US Capital
Registered: 2009-10-18
Posts: 27

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

Same error message here.
Have no problem with system though.


Arch Linux i686(kernel: 3.1.7-ck, xfce) running on Toshiba s100 (Pentium M 1.73GHz, 1.5GB RAM, 40GB HD, Nvidia 6600/6200 TE 64MB)

Offline

#10 2010-04-07 13:06:24

realitygaps
Member
From: Amsterdam, Netherlands
Registered: 2008-10-21
Posts: 8

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

Same error comes up here, but no issues on the system.

I dont even have a CD-ROM drive on this machine smile

Offline

#11 2010-04-07 14:53:39

whaler
Member
From: Oslo, Norway
Registered: 2008-03-25
Posts: 323

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

OK, I will break out and replace the DVD burner and see what happens :-)

Offline

#12 2010-04-07 15:21:28

MoistGod
Member
From: United States
Registered: 2010-04-07
Posts: 5

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

I see this error on my machine as well. This is on a desktop computer booted from a USB flash drive.

Offline

Board footer

Powered by FluxBB