search for: rootdelay

...y mode because it does not find any of the >> logical volumes defined, because it does not enable the LVM volume >> group. >> >> Giving "lvm", then "vgchange -a y", followed by CTRL-D continues to >> boot to full multiuser mode. > > maybe 'rootdelay=5' as kernel parameter will solve this issue. No. Even rootdelay=20 does not solve this issue. Volume groups are just not activated automatically and thus no active volume group is found and system boots into emergency mode. Simple question is: where and how are volume groups activated while b...

Hi! Folowing setup: 4x HD 500TB 1st: /boot 4GB, remaining part LVM 2nd, 3rd, 4th all LVM LVM volumes: - 30G /root - 8G /var - 8G /tmp - 200G /var/log/pgsql - 800G /var/spacewalk - 4G swap System boots into emergency mode because it does not find any of the logical volumes defined, because it does not enable the LVM volume group. Giving "lvm", then "vgchange -a y",

Hello, I have installed the Xen 4.1.1 and a working kernel 2.6.32.43 which supports Xen on a Ubuntu Linux 10.04 LTS. However, I have never successfully booted the Hypervisor and Dom0. The screen is always black after some kernel messages rapidly go by. I think that I may pass the wrong parameters to the kernel or Hypervisor with GRUB2. Can any one share his/her working grub.cfg for GRUB2 with

...ind any of the >>> logical volumes defined, because it does not enable the LVM volume >>> group. >>> >>> Giving "lvm", then "vgchange -a y", followed by CTRL-D continues to >>> boot to full multiuser mode. >> >> maybe 'rootdelay=5' as kernel parameter will solve this issue. > > No. Even rootdelay=20 does not solve this issue. Volume groups are > just not activated automatically and thus no active volume group is > found and system boots into emergency mode. Simple question is: where > and how are volume...

After successful creation of the Xen kernel and entry into grub, whenever I try and boot into the Xen kernel I receive the following error: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sda6 does not exist. Dropping to a shell! Here is the entry in /boot/grub/menu.lst -------------------------------------------...

...essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/xvda1 does not exist. Dropping to a shell! BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash) Enter ''help'' for a li...

...essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/xvda1 does not exist. Dropping to a shell! BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash) Enter ''help'' for a li...

...building "make bios ..", partitioning disk as gpt and plan to boot a single linux distro: PROMPT 1 TIMEOUT 50 DEFAULT xxx LABEL xxx LINUX /boot/vmlinuz-3.12.19 APPEND root=PARTUUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \ rootfstype=ext4 rootdelay=1 I might add some options in text menu, but that's more less all of what I need. Regards, Alexey

Hi I have a problem booting dom0 on Xen 3.1 under 2.6.18 kernel. At system start I obtain the next message: gave up waiting for root device. common problems: boot args (cat /proc/cmdline) check rootdelay= (did the system wait long enough?) check root= (did the system wait for the righ device?) missing modules (cat /proc/modules: ls /dev) /dev/sd* are not present in /dev dir and I tried to insert the rootdelay=90 in grub configuration without any result. Without initrd I obtain a kernel p...

...console mode, use the vga= parameter (press F1 to see a table). You may also add any other kernel parameters you might need depending on your hardware, and which drivers are included in your kernel. --- So there is just a kernel to boot and indeed no chain.c32. Please note that there is no "rootdelay" or "rootwait" kernel parameter by default. In some cases (e.g. USB connected hard disk) this can result in a not ready root partition when it's needed in the boot sequence. So the intended usage of the boot stick is: _ plug in the stick and (re)boot _ (this displays message.tx...

> ]You seem to be assuming that changing from a direct SATA and IDE > ] connections to some USB adapter would have no impact on how the > ] respective HDDs are recognized/detected by the BIOS. > > ] You seem to be > ] assuming that the BIOS from 2 different PCs/Laptops would recognize all > ] your devices in the same exact way and that there would be no changes > ] in

I just subscribed to this list so in case this subject has already been discussed at length, my apologies. I have been waiting for btrfs forever. I have been waiting for it to become reasonably stable. In the wake of escalating problems with my old hardware RAID setup, I decided now was the time to make the transition. At this point I have been completely transitioned to btrfs for nearly

Hi guys! I installed XEN 4.0 on Debian Squeeze but I cannot get the first DomU (not an image) started. Attached you will find /etc/xen/xen1.conf and the result of "xm create -c /etc/xen/xen1.conf" in xen1.log. Can you help me? What did I wrong? Is it about the fstab in xen1 (see also attached)? Many thanks in advance! Regards Stefan

...g essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/xvda2 does not exist. Dropping to a shell! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org...

...te-image --hostname mail1 --ip 172.16.10.154 --vcpus 4 --role udev --dist squeeze at the end of domU creation I run xm console mail1 but here is what I see: Begin: Waiting for root file system ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/xvda2 does not exist. Dropping to a shell! Arghhhhhhh!!!!!! I think there is nothing wrong in my creation procedure, I have a lot of DomU w...

...; System boots into emergency mode because it does not find any of the > logical volumes defined, because it does not enable the LVM volume > group. > > Giving "lvm", then "vgchange -a y", followed by CTRL-D continues to > boot to full multiuser mode. maybe 'rootdelay=5' as kernel parameter will solve this issue. best regards Ulf

Hi, i have a problem to booting xen kernel. At system start i obtain the next message: gave up waiting for root device. common problems: boot args (cat /proc/cmdline) check rootdelay= (did the system wait long enough?) check root= (did the system wait for the righ device?) missing modules (cat /proc/modules: ls /dev) You have some idea to fix this problem? Many thanks. Bye _______________________________________________ Xen-users mailing list Xen-users@lists.xensourc...

...t-channel device installed. done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Waiting for root file system ... Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-label/PLANTILLA_D1 does not exist. Dropping to a shell! BusyBox v1.18.4 (Debian 1:1.18.4-2) built-in shell (ash) Enter ''h...

...nformation to boot from /dev/sda1 is as follows. 1. /boot/grub/menu.lst: title Xen uuid 30ec981c-187e-4488-ae98-fe54ad13a77b kernel /boot/xen-3.4.gz console=vga module /boot/vmlinuz-2.6.18.8-xen root=UUID=30ec981c-187e-4488-ae98-fe54ad13a77b ro console=tty0 rootdelay=90 module /boot/initrd-2.6.18.8-xen.img 2. fdisk: Disk /dev/sda: 122.9 GB, 122942324736 bytes 255 heads, 63 sectors/track, 14946 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000e4ad4 Device Boot Start End Blocks Id System /dev/sd...

....1.2* Where can be the problem? if the kernel is missing that module which package should i install to fix it? also i tried to change to *tap:aio: *In this case VM booted but inside vm i am getting *Gave up waiting for root device. Common problems:* * - Boot args (cat /proc/cmdline)* * - Check rootdelay= (did the system wait long enough?)* * - Check root= (did the system wait for the right device?)* * - Missing modules (cat /proc/modules; ls /dev)* *ALERT! /dev/disk/by-uuid/52e5d884-2d59-437d-b890-313266995a42 does not exist. Dropping to a shell!* * * * * *BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubu...