linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Dreger <jens.dreger@physik.fu-berlin.de>
To: linux-hotplug@vger.kernel.org
Subject: /dev/disk/by-label/* not populated by initrd
Date: Wed, 17 May 2006 14:58:20 +0000	[thread overview]
Message-ID: <20060517145820.GK12875@smart.physik.fu-berlin.de> (raw)

Hi!

A few days ago I installed debian/testing amd64 on one of our servers
to test some 64bit stuff. Upon bootup the machine loaded the SAN
modules (qla*) before the modules for the system disk, so it didn't
make it. I could fix this by blacklisting the modules.

After reading up on udev I understood that I am supposed to write
some rules which make sure the system disks get's a persistent
name. So I gave the disk a label and udevtest shows that it would be
assigned:

  root@zs11:~> udevtest /block/sda/sda1 | grep label
  udev_rules_get_name: add symlink 'disk/by-label/zs11_system'
  create_node: creating symlink '/dev/disk/by-label/zs11_system' to '../../sda1'

The problem is that this does not work inside initrd, but I obviously
need that link for the rootfs. I unpacked the initrd and init has
support for this:

  root@zs11:/boot/initrd.img-2.6.15-1-amd64-generic.unpack> grep LABEL init
                LABEL=*)
                        ROOT="/dev/disk/by-label/${ROOT#LABEL=}"

Booting with kernel-commandline root=LABEL=zs11_system didn't work.

I copied udevtest to the initrd. It shows:

[...]
main: looking at device '/block/sda/sda1' from subsystem 'block'
udev_rules_get_name: no node name set, will use kernel name 'sda1'
lookup_group: specified group unknown 'disk'
create_node: creating device node '/dev/sda1', major = '8', minor = '1', mode = '0660', uid = '0', gid = '0' 
main: run: 'socket:/org/kernel/udev/monitor'
[...]

I know that this is probably a debian issue but I would like to know
how to debug this further. In initrd there is no syslog, so increasing
the udev_log in udev.conf won't help unless I get syslog running
inside initrd. Apparently also groups are unknown at that time. Is
there a better way to find out what's wrong? Any ideas why
/dev/disk/by-label is not populated? vol_id is available in the
initrd.

Thanks in advance,

Jens.

-- 
Jens Dreger                      Freie Universitaet Berlin
dreger@physik.fu-berlin.de       Fachbereich Physik - ZEDV
Tel: +49 30 83854774             Arnimallee 14
Fax: +49 30 83855902	         14195 Berlin


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2006-05-17 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 14:58 Jens Dreger [this message]
2006-05-17 16:30 ` /dev/disk/by-label/* not populated by initrd Greg KH
2006-05-18 11:15 ` Jens Dreger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060517145820.GK12875@smart.physik.fu-berlin.de \
    --to=jens.dreger@physik.fu-berlin.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).