* [linux-lvm] Re: LVM 1.03 root file system on Redhat 7.3
[not found] <E17DJKw-0006ou-00@hermes.sistina.com>
@ 2002-05-30 12:42 ` James B. Byrne
2002-05-30 19:21 ` [linux-lvm] " Daniel Savard
1 sibling, 0 replies; 3+ messages in thread
From: James B. Byrne @ 2002-05-30 12:42 UTC (permalink / raw)
To: linux-lvm
On 30 May 2002 at 1:22, linux-lvm-request@sistina.com wrote:
> What I am seeing is this:
>
> kmod: failed to exec /sbin/modprobe -s -k block-major-7 errno = 2
>
> repeated 16 times, followed by
>
> vgvchange -- volume group "vg00" successfully activated
>
> VFS: Cannot open root device "vg00"/lv01: or 00:00
> Please append correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 00:00
The kmod error is reputedly caused by the ramdisk image file
(created by lvmcreate_initrd) not containing a /sbin/modprobe
command. How can I verify if this is so? I note that redhat has
/sbin/modprobe as a logical link to insmod. Could this be confusing
lvmcreate_initrd?
Regards,
Jim
--- e-mail is NOT a secure channel
James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] LVM 1.03 root file system on Redhat 7.3
[not found] <E17DJKw-0006ou-00@hermes.sistina.com>
2002-05-30 12:42 ` [linux-lvm] Re: LVM 1.03 root file system on Redhat 7.3 James B. Byrne
@ 2002-05-30 19:21 ` Daniel Savard
1 sibling, 0 replies; 3+ messages in thread
From: Daniel Savard @ 2002-05-30 19:21 UTC (permalink / raw)
To: linux-lvm
le jeu 30-05-2002 à 02:22, James B. Byrne a écrit :
>
> We are using the grub bootloader. We have followed the
> instructions contained in the the lvm howto document provided by
> sistina, to the best of my ability to understand them.
>
> The problem is that system gives a kernel panic when started using
> the lvm boot option. Is there a way to redirect the boot dialogue
> output to a file? It appears that the most informative messages may
> be scrolling of the top of the screen. What I am seeing is this:
>
> kmod: failed to exec /sbin/modeprobe -s -k block-major-7 errno = 2
>
> repeated 16 times, followed by
>
> vgvchange -- volume group "vg00" successfully activated
>
> VFS: Cannot open root device "vg00"/lv01: or 00:00
> Please append correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 00:00
>
> Help?
>
> Regards,
> Jim
> --- e-mail is NOT a secure channel
> James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
> Harte & Lyne Limited http://www.harte-lyne.ca
> 9 Brockley Drive vox: +1 905 561 1241
> Hamilton, Ontario fax: +1 905 561 0757
> Canada L8E 3C3
>
Although I am using lilo, I suppose it is the same problem I
encountered.
Don't know GRUB, but I suppose there is a line which specify your root
filesystem. You should have something like: /dev/myvg/mylv instead of
/dev/sdaX or /dev/hdaX or any disk name.
Regards,
--
=======================================
Daniel Savard
Consultation Informatique Daniel Savard
551, boul. Sir-Wilfrid-Laurier
suite 105
Beloeil, (Québec)
Canada J3G 4J1
Tél: (450) 467-8014
Internet: dsavard@cids.ca
=======================================
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] Re: LVM 1.03 root file system on Redhat 7.3
[not found] <E17DTyw-0008Hp-00@hermes.sistina.com>
@ 2002-05-30 19:37 ` Daniel Savard
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Savard @ 2002-05-30 19:37 UTC (permalink / raw)
To: linux-lvm
le jeu 30-05-2002 à 13:44, James B. Byrne a écrit :
>
> The kmod error is reputedly caused by the ramdisk image file
> (created by lvmcreate_initrd) not containing a /sbin/modprobe
> command. How can I verify if this is so? I note that redhat has
> /sbin/modprobe as a logical link to insmod. Could this be confusing
> lvmcreate_initrd?
The symlink won't cause lvmcreate_initrd to create a ramdisk image with
the missing executable.
To check, just copy your initrd image somewhere, say /tmp, uncompress it
(gunzip) there and mount it on a mount point as a loop device:
Given an initrd uncompressed file name: my_image
Given a mount point named: /tmp/my_mount_point
Just type: mount -o loop /tmp/my_image /tmp/my_mount_point
After that, you can cd to /tmp/my_mount_point and look at the files and
executables there.
Regards,
>
> Regards,
> Jim
>
> --- e-mail is NOT a secure channel
> James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
> Harte & Lyne Limited http://www.harte-lyne.ca
> 9 Brockley Drive vox: +1 905 561 1241
> Hamilton, Ontario fax: +1 905 561 0757
> Canada L8E 3C3
>
--
=======================================
Daniel Savard
Consultation Informatique Daniel Savard
551, boul. Sir-Wilfrid-Laurier
suite 105
Beloeil, (Québec)
Canada J3G 4J1
Tél: (450) 467-8014
Internet: dsavard@cids.ca
=======================================
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-05-30 19:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <E17DJKw-0006ou-00@hermes.sistina.com>
2002-05-30 12:42 ` [linux-lvm] Re: LVM 1.03 root file system on Redhat 7.3 James B. Byrne
2002-05-30 19:21 ` [linux-lvm] " Daniel Savard
[not found] <E17DTyw-0008Hp-00@hermes.sistina.com>
2002-05-30 19:37 ` [linux-lvm] " Daniel Savard
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.