Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Cloned VM fails to boot

  1. #1

    Default Cloned VM fails to boot

    Hi all,

    Host Ubuntu 12.043
    Guest OpenSUSE 13.1
    Oracle VirtualBox

    All cloned guests can't boot

    Warning:
    Timed out waiting for device dev-disk-by\x2did-ata\x...2dpart1.device.
    Dependency failed for /boot
    Dependency failed for Local File Systems


    Found following 2 threads:
    Unable to use cloned VM, OpenSUSE, VirtualBox
    linux - Unable to use cloned VM, OpenSUSE, VirtualBox - Super User

    Cannot boot OpenSuse 12 after cloning disk due to by-id access to the disk
    Digger's Blog: Cannot boot OpenSuse 12 after cloning disk due to by-id access to the disk

    but couldn't resolve how to fix the problem. Please help

    TIA

    Rgds
    satimis

  2. #2
    Join Date
    Sep 2012
    Posts
    7,102

    Default Re: Cloned VM fails to boot

    Your cloned system has different disk configuration. You need to boot from rescue DVD or any live media and fix /etc/fstab to match your actual device paths.

  3. #3

    Default Re: Cloned VM fails to boot

    Quote Originally Posted by arvidjaar View Post
    Your cloned system has different disk configuration. You need to boot from rescue DVD or any live media and fix /etc/fstab to match your actual device paths.
    Hi,

    Thanks for your advice.

    The cloned VM identifies the boot drive with UUID, which changed when the drive was cloned, resulting in unable to boot. I'm now downloading a live KDE image to fix this problem. I'll change it to boot device instead of UUID. I found similar threads on Internet.

    Rgds
    satimis

  4. #4
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Cloned VM fails to boot

    Interesting.
    What version of Virtualbox are you running?
    (I've been running 4.3.4, then updated to 4.3.6)

    I haven't yet run into any issue launching a clone.
    The error you're displaying seems to be a path <within> the Guest, so I doubt that if the clone was created properly (how <are> you creating clones?) the device path should not be an issue.

    IMO if you're using Virtualbox' own clone utility you shouldn't be experiencing problems... If you're doing it some home-grown way, YMMV.
    In other words, IMO it's unlikely for a clone utility to change the device path because there is no reason for a cloning utility to change it... The two major areas of concern typically are the system identifiers and networking.

    TSU

  5. #5

    Default Re: Cloned VM fails to boot

    Quote Originally Posted by tsu2 View Post
    Interesting.
    What version of Virtualbox are you running?
    (I've been running 4.3.4, then updated to 4.3.6)

    I haven't yet run into any issue launching a clone.
    The error you're displaying seems to be a path <within> the Guest, so I doubt that if the clone was created properly (how <are> you creating clones?) the device path should not be an issue.

    IMO if you're using Virtualbox' own clone utility you shouldn't be experiencing problems... If you're doing it some home-grown way, YMMV.
    In other words, IMO it's unlikely for a clone utility to change the device path because there is no reason for a cloning utility to change it... The two major areas of concern typically are the system identifiers and networking.

    TSU
    Hi,

    Thanks for your reply.

    VirtualBox version - 4.3.6 download on Oracle VirtualBox website

    I have cloned several VMs on OpenSUSE 13.1 including export/import. All VMs thus created failed to boot.

    Right click on VM -> clone
    creating new MAC address.

    Same steps applied on other Linux VM (Debian 7.3/Fedora/Ubuntu12.04/LinuxMint16 etc.) working w/o problem. All cloned VMs are able to boot without any problem.

    I also tried on another PC
    Host Debian7.3
    VBox version 4.3.6

    All cloned VMs created on OpenSUSE 13.1 were unable to boot

    Edit
    ===
    For your info, I also subscribe VirtualBox forum. Please refer to following thread;
    https://forums.virtualbox.org/viewtopic.php?f=7&t=59371

    satimis

  6. #6

    Default Re: Cloned VM fails to boot

    Hi all,

    Problem solved as follow;

    Start the VM with live-kde-opensuse13.1 ISO

    Start Terminal

    linux@linux:~> su

    # fdisk -l
    Code:
    Disk /dev/sda: 42.9 GB, 42949672960 bytes, 83886080 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk label type: dos
    Disk identifier: 0x0002efa7
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *        2048      819199      408576   83  Linux
    /dev/sda2          819200    83886079    41533440   8e  Linux LVM
    Mount LVM

    # pvs
    Code:
      PV         VG     Fmt  Attr PSize  PFree
      /dev/sda2  system lvm2 a--  39.61g 8.00m
    # lvdisplay /dev/system
    Code:
    ....   
      --- Logical volume ---
      LV Path                /dev/system/root
      LV Name                root
      VG Name                system
    # mount /dev/system/root /mnt

    # ls /mnt/
    Code:
    bin   dev  home  lib64       media  opt   root  sbin     srv  tmp  var
    boot  etc  lib   lost+found  mnt    proc  run   selinux  sys  usr
    # cp /mnt/etc/fstab /mnt/etc/fstab.ORIG_20140103

    # nano /mnt/etc/fstab
    change the line;
    Code:
    /dev/disk/by-id/ata-VBOX_HARDDISK_VBef165ce6-8bf1a0de-part1 /boot  ext4  acl,user_xattr 1 2
    as;
    Code:
    /dev/sda1 /boot  ext4  acl,user_xattr 1 2
    Shutdown the VM and remote the live-kde-opensuse13.1 ISO

    Start VM. Now it can boot without problem.

    Thanks

    Rgds
    satimis

  7. #7

    Default Re: Cloned VM fails to boot

    Hi all,

    To avoid the step mounting the LVM, do as follow;

    After booting the Live-CD

    Kmenu -> Applications -> System -> File Manager -> File Manager-Super User Mode

    Then it can directly edit the "fstab" file there.

    Rgds
    satimis

  8. #8
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Cloned VM fails to boot

    Quote Originally Posted by satimis View Post
    /dev/disk/by-id/ata-VBOX_HARDDISK_VBef165ce6-8bf1a0de-part1
    You should probably check to see if this entry exists.
    Can't remember for sure but it seems to me that openSUSE boot has been identifying disks "by id" for quite a long time now without a problem.

    But of course if the entry is just wrong, then it won't work.

    TSU

  9. #9

    Default Re: Cloned VM fails to boot

    Quote Originally Posted by tsu2 View Post
    You should probably check to see if this entry exists.
    Can't remember for sure but it seems to me that openSUSE boot has been identifying disks "by id" for quite a long time now without a problem.

    But of course if the entry is just wrong, then it won't work.

    TSU
    On the cloned VM the by-id changed. Therefore it can't boot.

    satimis

  10. #10
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Cloned VM fails to boot

    On 2014-01-09 23:46, tsu2 wrote:
    >
    > satimis;2613282 Wrote:
    >>
    >> /dev/disk/by-id/ata-VBOX_HARDDISK_VBef165ce6-8bf1a0de-part1
    >>

    >
    > You should probably check to see if this entry exists.
    > Can't remember for sure but it seems to me that openSUSE boot has been
    > identifying disks "by id" for quite a long time now without a problem.
    >
    > But of course if the entry is just wrong, then it won't work.


    The problem is that the "by-id" entries depend on the hardware, and the
    hardware depends on the host virtualization system, not on the virtual
    machine itself. It is like placing a hard disk on a different (same
    brand, different model) computer.

    Using "by-uuid" or "by-label" would work always.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •