Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: Ubuntu server on Virtualbox - no disk dev

  1. #1
    Join Date
    May 2010
    Beans
    12

    Ubuntu server on Virtualbox - no disk dev

    [UPDATE: the solution is to install Ubuntu server as normal and not as minimal virtual machine]

    Hello
    I'm trying to install ubuntu-10.04-server-i386 in Virtualbox on Windows XP Home (for use as a Drupal development server) using the instructions here
    https://help.ubuntu.com/community/VirtualBox
    and here
    https://help.ubuntu.com/community/Ubuntu_as_Guest_OS

    However, the Ubuntu server will not start properly. Instead it goes to an initramfs prompt as follows

    Code:
    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/7fe12763—234b—4a75—910b—3fb00Bebb2f1 does not exist. Dropping to a shell!
    BusyBox v1.13.3 (Ubuntu 1:1.13.3—1ubuntu11) built—in shell (ash)
    Enter 'help' for a list of built—in commands.
    (initramfs) _
    Another thread suggested typing 'exit' after a while but it just repeats the same output.

    It seems the root disk doesn't exist. I allowed the installer to set up partitions to its own recommendation (Guided?) although I'm not entirely sure what it did - I think there are two partitions but you guys will know that.

    The host disk is SATA. The CPU is a dualcore but I've only enabled one CPU on the guest within Virtualbox. Also, I had to enable PAE mode as without it Virtualbox crashed every time I started the guest. PAE wasn't mentioned in the instructions mentioned above.

    I've tried changing the various other disk parameters in Virtualbox (without fully understanding them) but no luck.

    I also ran run the boot info script from a desktop LiveCD and the results are given below.
    Any help would be appreciated.
    Thanks



    Code:
    cat /proc/modules
    e1000 97845 0 - Live 0xe0832000
    Code:
                    Boot Info Script 0.55    dated February 15th, 2010                    
    
    ============================= Boot Info Summary: ==============================
    
     => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in 
        partition #1 for /boot/grub.
    
    sda1: _________________________________________________________________________
    
        File system:       ext4
        Boot sector type:  -
        Boot sector info:  
        Operating System:  Ubuntu 10.04 LTS
        Boot files/dirs:   /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img
    
    sda2: _________________________________________________________________________
    
        File system:       Extended Partition
        Boot sector type:  -
        Boot sector info:  
    
    sda5: _________________________________________________________________________
    
        File system:       swap
        Boot sector type:  -
        Boot sector info:  
    
    =========================== Drive/Partition Info: =============================
    
    Drive: sda ___________________ _____________________________________________________
    
    Disk /dev/sda: 8589 MB, 8589934592 bytes
    255 heads, 63 sectors/track, 1044 cylinders, total 16777216 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    
    Partition  Boot         Start           End          Size  Id System
    
    /dev/sda1    *          2,048    15,958,015    15,955,968  83 Linux
    /dev/sda2          15,960,062    16,775,167       815,106   5 Extended
    /dev/sda5          15,960,064    16,775,167       815,104  82 Linux swap / Solaris
    
    
    blkid -c /dev/null: ____________________________________________________________
    
    Device           UUID                                   TYPE       LABEL                         
    
    /dev/loop0                                              squashfs                                 
    /dev/ramzswap0                                          swap                                     
    /dev/sda1        7fe12763-234b-4a75-910b-3fb008ebb2f1   ext4                                     
    /dev/sda2: PTTYPE="dos" 
    /dev/sda5        e7947be9-e634-4d49-9b6d-bfc9e2000cfe   swap                                     
    /dev/sda: PTTYPE="dos" 
    
    ============================ "mount | grep ^/dev  output: ===========================
    
    Device           Mount_Point              Type       Options
    
    aufs             /                        aufs       (rw)
    /dev/sr0         /cdrom                   iso9660    (ro,noatime)
    /dev/loop0       /rofs                    squashfs   (ro,noatime)
    
    
    =========================== sda1/boot/grub/grub.cfg: ===========================
    
    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by /usr/sbin/grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #
    
    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
      load_env
    fi
    set default="0"
    if [ ${prev_saved_entry} ]; then
      set saved_entry=${prev_saved_entry}
      save_env saved_entry
      set prev_saved_entry=
      save_env prev_saved_entry
      set boot_once=true
    fi
    
    function savedefault {
      if [ -z ${boot_once} ]; then
        saved_entry=${chosen}
        save_env saved_entry
      fi
    }
    
    function recordfail {
      set recordfail=1
      if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
    }
    insmod ext2
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set 7fe12763-234b-4a75-910b-3fb008ebb2f1
    if loadfont /usr/share/grub/unicode.pf2 ; then
      set gfxmode=640x480
      insmod gfxterm
      insmod vbe
      if terminal_output gfxterm ; then true ; else
        # For backward compatibility with versions of terminal.mod that don't
        # understand terminal_output
        terminal gfxterm
      fi
    fi
    insmod ext2
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set 7fe12763-234b-4a75-910b-3fb008ebb2f1
    set locale_dir=($root)/boot/grub/locale
    set lang=C.UTF-8
    insmod gettext
    if [ ${recordfail} = 1 ]; then
      set timeout=-1
    else
      set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    ### END /etc/grub.d/05_debian_theme ###
    
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Ubuntu, with Linux 2.6.32-21-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod ext2
        set root='(hd0,1)'
        search --no-floppy --fs-uuid --set 7fe12763-234b-4a75-910b-3fb008ebb2f1
        linux    /boot/vmlinuz-2.6.32-21-generic-pae root=UUID=7fe12763-234b-4a75-910b-3fb008ebb2f1 ro   quiet
        initrd    /boot/initrd.img-2.6.32-21-generic-pae
    }
    menuentry 'Ubuntu, with Linux 2.6.32-21-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod ext2
        set root='(hd0,1)'
        search --no-floppy --fs-uuid --set 7fe12763-234b-4a75-910b-3fb008ebb2f1
        echo    'Loading Linux 2.6.32-21-generic-pae ...'
        linux    /boot/vmlinuz-2.6.32-21-generic-pae root=UUID=7fe12763-234b-4a75-910b-3fb008ebb2f1 ro single 
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initrd.img-2.6.32-21-generic-pae
    }
    ### END /etc/grub.d/10_linux ###
    
    ### BEGIN /etc/grub.d/30_os-prober ###
    if [ ${timeout} != -1 ]; then
      if keystatus; then
        if keystatus --shift; then
          set timeout=-1
        else
          set timeout=0
        fi
      else
        if sleep --interruptible 3 ; then
          set timeout=0
        fi
      fi
    fi
    ### END /etc/grub.d/30_os-prober ###
    
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries.  Simply type the
    # menu entries you want to add after this comment.  Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    
    =============================== sda1/etc/fstab: ===============================
    
    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    nodev,noexec,nosuid 0       0
    # / was on /dev/sda1 during installation
    UUID=7fe12763-234b-4a75-910b-3fb008ebb2f1 /               ext4    errors=remount-ro 0       1
    # swap was on /dev/sda5 during installation
    UUID=e7947be9-e634-4d49-9b6d-bfc9e2000cfe none            swap    sw              0       0
    
    =================== sda1: Location of files loaded by Grub: ===================
    
    
       4.5GB: boot/grub/core.img
       4.5GB: boot/grub/grub.cfg
       4.5GB: boot/initrd.img-2.6.32-21-generic-pae
        .2GB: boot/vmlinuz-2.6.32-21-generic-pae
       4.5GB: initrd.img
        .2GB: vmlinuz
    Last edited by bind00; June 11th, 2010 at 03:51 PM. Reason: Posted the solution in first post to save others searching for it.

  2. #2
    Join Date
    May 2010
    Beans
    12

    Re: Ubuntu server on Virtualbox - no disk dev

    Hello?
    Any ideas? I'm stuck.

  3. #3
    Join Date
    Jun 2010
    Beans
    4
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Ubuntu server on Virtualbox - no disk dev

    Quote Originally Posted by bind00 View Post
    Hello?
    Any ideas? I'm stuck.
    I've got a similar issue, but I'm trying to run ubuntu guest on solaris host. Using the latest Virtualbox available (3.2.0).
    Tried ubuntu jeos 8.04.3 and 10.04.

  4. #4
    Join Date
    May 2010
    Beans
    12

    Re: Ubuntu server on Virtualbox - no disk dev

    Quote Originally Posted by zdev View Post
    I've got a similar issue, but I'm trying to run ubuntu guest on solaris host. Using the latest Virtualbox available (3.2.0).
    Tried ubuntu jeos 8.04.3 and 10.04.
    How similar? I'm also using VB 3.2.0. Are you also getting the '/dev/disk..... does not exist' with initramfs prompt?
    Is your guest server or desktop?

    I think I'll post this over at the VB forums. For one thing, VB shouldn't crash when PAE is unchecked. I only checked it so it wouldn't crash. I don't know if it's the correct setting and there's nothing about it in the instructions on this site.

  5. #5
    Join Date
    Jun 2010
    Beans
    4
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Ubuntu server on Virtualbox - no disk dev

    Quote Originally Posted by bind00 View Post
    How similar? I'm also using VB 3.2.0. Are you also getting the '/dev/disk..... does not exist' with initramfs prompt?
    I've got exactly the same issue except that I run Ubuntu server in Virtualbox on Solaris 10 host.

    Is your guest server or desktop?
    Tried ubuntu server jeos 8.04.3 and ubuntu server 10.04 with "Install a minimal virtual machine" option. Installations went ok, no issues were reported, but after reboot I got forementioned '/dev/disk.... does not exist'.

    I think I'll post this over at the VB forums. For one thing, VB shouldn't crash when PAE is unchecked. I only checked it so it wouldn't crash. I don't know if it's the correct setting and there's nothing about it in the instructions on this site.
    Unchecking PAE didn't work for me.

  6. #6
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,116

    Re: Ubuntu server on Virtualbox - no disk dev

    Quote Originally Posted by bind00 View Post
    However, the Ubuntu server will not start properly. Instead it goes to an initramfs prompt as follows

    Code:
    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/7fe12763—234b—4a75—910b—3fb00Bebb2f1 does not exist. Dropping to a shell!
    BusyBox v1.13.3 (Ubuntu 1:1.13.3—1ubuntu11) built—in shell (ash)
    Enter 'help' for a list of built—in commands.
    (initramfs) _
    I also ran run the boot info script from a desktop LiveCD and the results are given below.
    Code:
                    Boot Info Script 0.55    dated February 15th, 2010 ................................................
    .......................................
    .........................
    ..................
    
    blkid -c /dev/null: ____________________________________________________________
    
    Device           UUID                                   TYPE       LABEL                         
    
    /dev/loop0                                              squashfs                                 
    /dev/ramzswap0                                          swap                                     
    /dev/sda1        7fe12763-234b-4a75-910b-3fb008ebb2f1   ext4                                     
    /dev/sda2: PTTYPE="dos" 
    /dev/sda5        e7947be9-e634-4d49-9b6d-bfc9e2000cfe   swap                                     
    /dev/sda: PTTYPE="dos" 
    .........................
    ..........................
    ..............
    Notice the difference in UUID the boot-loader is searching (7fe127.....-3fb00Bebb2f1) for & that actually given to sda1 (7fe127.....-3fb008ebb2f1).
    Can't say if it really has any significance. Besides, it may be just a typo on your part. But if it isn't, then the problem seems to exist in the fact that the boot loader is somehow searching for a wrong UUID as a boot partition.

    Now 'how to change the UUID the boot loader is looking for', is beyond my knowledge.

    Maybe someone else can shed some light on it. But first you need to confirm that it is not a typo & the difference does actually lie there.
    Last edited by varunendra; June 3rd, 2010 at 09:55 AM.

  7. #7
    Join Date
    May 2010
    Beans
    12

    Re: Ubuntu server on Virtualbox - no disk dev

    Quote Originally Posted by varunendra View Post
    Notice the difference in UUID the boot-loader is searching (7fe127.....-3fb00Bebb2f1) for & that actually given to sda1 (7fe127.....-3fb008ebb2f1).
    Can't say if it really has any significance. Besides, it may be just a typo on your part.
    Many thanks for taking a look and well observed. Actually it is just a typo. I didn't know how to copy and paste the text from that screen so I copied it as an image and ran it through an OCR program. I tidied up most of it but missed that. That was a job in itself.


    Virtualbox 3.2.2 has been released today. I couldn't see anything pertinent in the release notes and sure enough I still have the same problem.

    I've cross-posted this at the Virtualbox forum.
    Last edited by bind00; June 3rd, 2010 at 10:08 AM.

  8. #8
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,116

    Re: Ubuntu server on Virtualbox - no disk dev

    You may try VMware Server or Player. They are free.
    Although VMware is quite a bit heavier on resources as compared to VirtualBox, yet most perfected virtualization platform out there.

    I know it's a workaround rather than a solution but should serve your purpose for the moment. Just try & see what happens!


    PS: I'd suggest to use Ubuntu 9.10 Server, as 10.04 is rather a new release & virtualization platforms may not have native support for it (which does matter to a certain extent).
    Last edited by varunendra; June 3rd, 2010 at 10:25 AM.

  9. #9
    Join Date
    May 2010
    Beans
    12

    Re: Ubuntu server on Virtualbox - no disk dev

    Thanks. I'll consider it. Last time I used VMware I did find it took over the PC somewhat with several background processes and for some reason the computer took an extra minute and a half to shutdown. Maybe it's improved in the meanwhile but I do have other resource sensitive applications.

    I did get Unbuntu server running on MS Virtual Machine too but the system I need it on is XP Home which doesn't support it.

  10. #10
    Join Date
    May 2010
    Beans
    12

    Re: Ubuntu server on Virtualbox - no disk dev

    Saw your edit about 9.10 after my last post. I've tried it and it works. That will do for my purposes.

    Many thanks for your help.

Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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