:: Re: [Dng] [dng] vdev status update
Pàgina inicial
Delete this message
Reply to this message
Autor: Isaac Dunham
Data:  
A: Anto
CC: dng@lists.dyne.org
Assumpte: Re: [Dng] [dng] vdev status update
On Tue, Apr 14, 2015 at 07:40:41PM +0200, Anto wrote:
> On 14/04/15 17:48, Jude Nelson wrote:
> >I'm using it as the device manager in my copy of the alpha Vagrant image,
> >and others have tested it locally (but not for booting, AFAIK).?? I'm
> >working on getting it to boot the the qcow2 image, which boots from LVM.
> >
> >Thanks,
> >-Jude
> >
>
> Thanks Jude,
>
> I am not sure if at this stage, it is worth it to report the problems that I
> have just experienced.
>
> I followed your 3 steps instruction to have vdev on the PC that I am
> currently using for writing this email (HP EliteBook 8530w), and
> surprisingly it does not work (yet) :)
>
> Before anyone ask: no, this is not a "production" PC as I have been beating
> it up so bad in the last 3 years since I got it used from the company I work
> for.
>
> In the grub.cfg, I used the same set of files as the ones from the running
> kernel generated by update-initramfs, except the initrd that I took from the
> "example" directory under vdev source directory.
>
> It booted the initrd, but just ended up on the (initramfs) prompt. It is
> hard to get the error messages during boot. I tried to record them using my
> mobile phone and the messages at the beginning are the following:
>
> Loading, please wait...
> /init:  line 175:  resolve_device:  not found
> 00071:859055872:  [          vdev.c:0425]  vdev_init:  ERROR:
> vdev_config_load('/etc/vdev/vdevd.conf')  rc = -2
> 00071:859055872:  [         main.c:0042]  main:  ERROR:  vdev_init rc = -2

>
> <some messages that are too fast to be captured>


Not being very familiar with vdev, I can't tell you what this means beyond
that something didn't get copied or ended up in the wrong place.

> The last messages that I could see on the screen are about "modprobe:
> modules <some modules> not found in modules.dep".
>
> If you needed more information, I am quite happy to provide them.



This sounds like what I ran into with mdev.
https://github.com/idunham/mdev/blob/master/hooks/mdev-hook, last two lines:
# Apparently, this somehow only gets copied if udev is installed.
copy_modules_dir kernel/drivers/scsi

The directory where that is would probably be helpful for integration
with initramfs-tools; it's what I worked out for making mdev replace
udev.

HTH,
Isaac Dunham