Page 1 of 5 123 ... LastLast
Results 1 to 10 of 46

Thread: Clean install fails to reboot

  1. #1
    Join Date
    Jun 2009
    Beans
    192

    Clean install fails to reboot

    I'm installing 10.4 x64 on a Dell PowerEdge R610 in a RAID 1 configuration and the install goes fine until I have to reboot the server to finish the install. On reboot after about a minute it gives the error

    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/mapper/mysql1-root does not exist. Dropping to shell!
    And then it drops to a (initramfs) at which point I have no idea what to do and my co-worker who knows a little more about Linux can't get it to let him check any of the above common problems. From the (initramfs) I can cd to /dev/mapper/ and mysql1-root does exist why it can't be found during boot I have no idea or any idea how to make it find it.

    We've tried letting GRUB manually configure itself at the end of the install before we reboot and we've also pointed it to /dev/sba partition which is what should be the boot partition.

    In the code tag it's ALERT! /dev/mapper/mysql(one)-root.... the L and 1 look the same.

    I've got 3 of these server to get setup and running as part of our back end and network restructuring and have been stuck at this point on the first one since Friday.


  2. #2
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    After reading page after page of these forums I tried the holding down shift while booting to configure GRUB and I can get to the GRUB menu but have no idea what to do from there. The menu gives me 3 options:

    Code:
    Ubuntu, with Linux 2.6.32-21-server
    Ubuntu, with Linux 2.6.32-21-server (recovery mode)
    Memory test (memtest86+)
    Memory test (memtest86+, serial console 115200)
    Trying the first option gives me the same results as just rebooting in the OP.
    Trying the second option the same gave up error happens then there's a bunch of screen spam and I'm back to the same (initramfs) prompt.

    Any help getting this sorted is greatly appreciated, I've been trying to learn Linux over the last year and still know next to nothing about how to do things like troubleshoot problems with it.

  3. #3
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    Pressing e while the first option is highlighted gives me the following:

    Code:
    recordfail
    insmod ext2
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set 77e9b156-7d83-476a-b930-4475f04a9\a54
    linux /boot/vmlinux-2.6.32.31-server root=UUID=77e9b156-7d83-476a-b930-4475f04a9\a54 ro     quite    
    initrd /boot/initrd.img-2.6.32.21-server
    If I go to a cmd line I get a grub> prompt, doing ls shows (hd0) (hd0,5) (hd0,1)

  4. #4
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    Ok following suggestions I've read in another thread I've made a Live CD and booted in it and ran the boot info script from http://bootinfoscript.sourceforge.net/


    And the results are:

    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: 72.7 GB, 72746008576 bytes
    255 heads, 63 sectors/track, 8844 cylinders, total 142082048 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   136,198,143   136,196,096  83 Linux
    /dev/sda2         136,200,190   142,079,999     5,879,810   5 Extended
    /dev/sda5         136,200,192   142,079,999     5,879,808  82 Linux swap / Solaris
    
    
    blkid -c /dev/null: ____________________________________________________________
    
    Device           UUID                                   TYPE       LABEL                         
    
    /dev/loop0                                              squashfs                                 
    /dev/sda1        77e9b156-7d83-476a-b930-4475f04a9a54   ext4                                     
    /dev/sda2: PTTYPE="dos" 
    /dev/sda5        b048d478-e6ea-4bb6-9642-d7cd4f9beb35   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 77e9b156-7d83-476a-b930-4475f04a9a54
    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 77e9b156-7d83-476a-b930-4475f04a9a54
    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-server' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod ext2
        set root='(hd0,1)'
        search --no-floppy --fs-uuid --set 77e9b156-7d83-476a-b930-4475f04a9a54
        linux    /boot/vmlinuz-2.6.32-21-server root=UUID=77e9b156-7d83-476a-b930-4475f04a9a54 ro   quiet
        initrd    /boot/initrd.img-2.6.32-21-server
    }
    menuentry 'Ubuntu, with Linux 2.6.32-21-server (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod ext2
        set root='(hd0,1)'
        search --no-floppy --fs-uuid --set 77e9b156-7d83-476a-b930-4475f04a9a54
        echo    'Loading Linux 2.6.32-21-server ...'
        linux    /boot/vmlinuz-2.6.32-21-server root=UUID=77e9b156-7d83-476a-b930-4475f04a9a54 ro single 
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initrd.img-2.6.32-21-server
    }
    ### END /etc/grub.d/10_linux ###
    
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
        insmod ext2
        set root='(hd0,1)'
        search --no-floppy --fs-uuid --set 77e9b156-7d83-476a-b930-4475f04a9a54
        linux16    /boot/memtest86+.bin
    }
    menuentry "Memory test (memtest86+, serial console 115200)" {
        insmod ext2
        set root='(hd0,1)'
        search --no-floppy --fs-uuid --set 77e9b156-7d83-476a-b930-4475f04a9a54
        linux16    /boot/memtest86+.bin console=ttyS0,115200n8
    }
    ### END /etc/grub.d/20_memtest86+ ###
    
    ### 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=77e9b156-7d83-476a-b930-4475f04a9a54 /               ext4    errors=remount-ro 0       1
    # swap was on /dev/sda5 during installation
    UUID=b048d478-e6ea-4bb6-9642-d7cd4f9beb35 none            swap    sw              0       0
    
    =================== sda1: Location of files loaded by Grub: ===================
    
    
      64.5GB: boot/grub/core.img
       2.5GB: boot/grub/grub.cfg
      64.5GB: boot/initrd.img-2.6.32-21-server
        .2GB: boot/vmlinuz-2.6.32-21-server
      64.5GB: initrd.img
        .2GB: vmlinuz
    I kinda understand everything up to the "mount | grep ^/dev output:" part after that its all gibberish to me.

  5. #5
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    Morning Ubuntu land hopefully today will bring more insight to my on going issue, but for now its time for coffee.

  6. #6
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    Well I tried changing the set root entry to '(/dev/sda1)' instead of '(hd0,1)' and still got the same error.

    Seams like a pretty basic function for an OS to be able to do 'out of the box' and yet it doesn't work, I'm going to have to look into using a different OS soon because I don't have time to read page after page of various forums trying to get basic functionality working.

  7. #7
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    Used the server disk to boot into recovery mode and reinstalled GRUB to /dev/sda rebooting now to see if anything works

  8. #8
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    Installing GRUB to /dev/sda/ didn't help still getting the same error message.

    I could really use some insight into what could be causing this and how to fix it. Thanks in advance for any suggestions.

  9. #9
    Join Date
    Nov 2009
    Location
    Mataro, Spain
    Beans
    13,640
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Clean install fails to reboot

    I haven't worked with the server version unfortunately, so I might totally miss the point, but...

    Why does the script report only one disk, /dev/sda? And why is the partition reported as Linux instead of RAID member?

    You mentioned in the first post it's RAID1. Hardware controller? Willing to try ubuntu's software raid function?

    During the install, was the raid detected at all and were you asked whether you want to use it?
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 14.04 LTS 64bit & Windows 10 Pro 64bit

  10. #10
    Join Date
    Jun 2009
    Beans
    192

    Re: Clean install fails to reboot

    It's a SAS 6/iR Integrated hardware RAID controller, during the install it was detected as "Dell Virtual Disk" which is the name of the array and afaik should only be seen by the OS as a single "disk" with the controller managing the 2 separate HDD's.

    http://www.dell.com/content/topics/t...us&l=en&cs=555




Page 1 of 5 123 ... LastLast

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
  •