From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RAID1 + LVM not detected during boot on 2.6.9
Date: Wed, 15 Dec 2004 10:16:04 -0600 [thread overview]
Message-ID: <41C06344.7030101@pbl.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
I've installed one machine (Fedora Core 3 distro) with /boot on RAID1
device (md0) and all other filesystems on LVM volumes located on another
RAID1 device (md1). There was only one volume group, with couple of
volumes for file systems (one of them was root file system).
The installation went fine, however when I try to reboot machine, Linux
kernel is unable to detect LVM volumes, and panics since it can't find
root file system. I see messages saying that it is searching for LVM
volumes, but it dosn't find any.
If I boot into rescue mode from CD (also 2.6.9 kernel), and let Fedora
installer search for existing installations, all volumes are found and I
can mount root file system.
At first I suspected that I was missing some modules from initrd image,
and attempted to recreate it by hand. However that hasn't worked (I've
attached mkinitrd -v output). It seems that all needed modules and
config files are present in initrd image (SCSI, RAID, DM, and ext3 file
system).
I do remember having this very same setup working on kernel 2.6.5.
--
Aleksandar Milivojevic <amilivojevic@pbl.ca> Pollard Banknote Limited
Systems Administrator 1499 Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7
[-- Attachment #2: mk.txt --]
[-- Type: text/plain, Size: 2911 bytes --]
Creating initramfs
Looking for deps of module scsi_mod
Looking for deps of module sd_mod scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module unknown
Looking for deps of module sym53c8xx scsi_transport_spi scsi_mod
Looking for deps of module scsi_transport_spi scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module ide-disk
Looking for deps of module dm-mod
Looking for deps of module raid1
Looking for deps of module ext3 jbd
Looking for deps of module jbd
Looking for deps of module dm-mod
Looking for deps of module dm-mirror dm-mod
Looking for deps of module dm-mod
Looking for deps of module dm-zero dm-mod
Looking for deps of module dm-mod
Looking for deps of module dm-snapshot dm-mod
Looking for deps of module dm-mod
Using modules: ./kernel/drivers/scsi/scsi_mod.ko ./kernel/drivers/scsi/sd_mod.ko ./kernel/drivers/scsi/scsi_transport_spi.ko ./kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.ko ./kernel/drivers/md/dm-mod.ko ./kernel/drivers/md/raid1.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko ./kernel/drivers/md/dm-mirror.ko ./kernel/drivers/md/dm-zero.ko ./kernel/drivers/md/dm-snapshot.ko
/sbin/nash -> /tmp/initrd.qC1073/bin/nash
/sbin/insmod.static -> /tmp/initrd.qC1073/bin/insmod
/sbin/udev.static -> /tmp/initrd.qC1073/sbin/udev
/etc/udev/udev.conf -> /tmp/initrd.qC1073/etc/udev/udev.conf
`/lib/modules/2.6.9-1.667/./kernel/drivers/scsi/scsi_mod.ko' -> `/tmp/initrd.qC1073/lib/scsi_mod.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/scsi/sd_mod.ko' -> `/tmp/initrd.qC1073/lib/sd_mod.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/scsi/scsi_transport_spi.ko' -> `/tmp/initrd.qC1073/lib/scsi_transport_spi.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.ko' -> `/tmp/initrd.qC1073/lib/sym53c8xx.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/md/dm-mod.ko' -> `/tmp/initrd.qC1073/lib/dm-mod.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/md/raid1.ko' -> `/tmp/initrd.qC1073/lib/raid1.ko'
`/lib/modules/2.6.9-1.667/./kernel/fs/jbd/jbd.ko' -> `/tmp/initrd.qC1073/lib/jbd.ko'
`/lib/modules/2.6.9-1.667/./kernel/fs/ext3/ext3.ko' -> `/tmp/initrd.qC1073/lib/ext3.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/md/dm-mirror.ko' -> `/tmp/initrd.qC1073/lib/dm-mirror.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/md/dm-zero.ko' -> `/tmp/initrd.qC1073/lib/dm-zero.ko'
`/lib/modules/2.6.9-1.667/./kernel/drivers/md/dm-snapshot.ko' -> `/tmp/initrd.qC1073/lib/dm-snapshot.ko'
/sbin/lvm.static -> /tmp/initrd.qC1073/bin/lvm
/etc/lvm -> /tmp/initrd.qC1073/etc/lvm
`/etc/lvm/lvm.conf' -> `/tmp/initrd.qC1073/etc/lvm/lvm.conf'
Loading module scsi_mod
Loading module sd_mod
Loading module scsi_transport_spi
Loading module sym53c8xx
Loading module dm-mod
Loading module raid1
Loading module jbd
Loading module ext3
Loading module dm-mirror
Loading module dm-zero
Loading module dm-snapshot
next reply other threads:[~2004-12-15 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 16:16 Aleksandar Milivojevic [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-15 16:40 RAID1 + LVM not detected during boot on 2.6.9 Stephen Warren
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=41C06344.7030101@pbl.ca \
--to=amilivojevic@pbl.ca \
--cc=linux-kernel@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