Welcome!

Please read this important information about MX sources lists.
News
  • MX Linux on social media: here
  • Mepis support still here
Current releases
  • MX-17 RC1 release info here
  • MX-16.1 release info here
  • antiX-17 release info here
    New users
    • Please read this first, and don't forget to add system and hardware information to posts!
    • Read Forum Rules

Installation woes and a GRUB headache - Part 2

Message
Author
br1anstorm
Forum Novice
Forum  Novice
Posts: 45
Joined: Sun Nov 05, 2017 2:25 pm

Installation woes and a GRUB headache - Part 2

#1 Postby br1anstorm » Mon Nov 13, 2017 2:07 pm

I have posted in a separate earlier thread at https://forum.mxlinux.org/viewtopic.php?f=92&t=43203 the details of my efforts to install MX-16 on an external USB drive. In a nutshell, I could not install GRUB, and I don't know why.

Discussion about the possible reasons for the problem continues in that thread. Meanwhile, in the hope of shedding more light on the mystery, I have tried another approach.

After deleting, reformatting and creating a new partition table on that same USB drive, I then tried again to install MX-16 from a Live session, but this time on an old and rather slow laptop (1GB RAM, 2GHz Intel Pentium 4 CPU) which only has Windows XP on it. The Live session of MX-16 works fine on that computer. So i tried another install.

The good news is that it worked (or rather, seemed to). Root, swap and home all created OK on that drive (dev/sdb). And - yay - GRUB installed fine at sdb, and the installation progressed through to the finish.

I thought I was home and dry. BUT.....

I then tried to boot into the newly-installed MX-16 USB. Problem. The booting up seemed to take an age, even on this slow machine. I got the (kingfisher wallpaper) Grub bootloader screen with the choice of OSs (MX-16 or WinXP). Chose MX-16. It started loading.... kernel and initial ramdisk. But then the screen eventually filled with a mass of text about the booting process. I couldn't take a screenshot, obviously. So I just tried to note the key information. It was - roughly - as follows . I have marked it as code but my re-typing may not have copied all the text and spaces correctly.

Code: Select all

Scanning for Btrfs file system
[    numbers...] usb 1-3: device descriptor read/64, error -62
..... and several more similar lines....
usb 3-1   device not accepting address 2
usb3 - port 1 cannot disable (error = -32)
device not accepting address 4 (error -62)
device not accepting address 5 (error -62)
[and there were three or four similar lines  not accepting address 6 and 7]
[..... numbers...] usb usb2-port2: unable to enumerate USB device
[  .... numbers...] end request: I/O error, dev fd0, sector 0

Gave up waiting for root device.  Common problems
- Boot arguments (cat/proc/cmdline)
- check root delay = (did system wait long enough?)
- check root = (did system wait for right device?)
- missing modules (cat/proc/modules;  ls/ dev)

Alert!  /dev/disk/by - uuid/e5e857fg-dd3d-43b2-b252-a5531d488478 does not exist

Dropping to a shell!
modprobe:  module ehci - orion not found in modules.dep

BusyBox v 1.22.1 (Debian 1: 1.220-9+deb8u1) built in shell (ash)
Enter help for a list of built-in commands

/bin/sh:  can't access tty;  job control turned off (initramfs)


I could only exit by "hard shutdown" (powering off).


Most of that means absolutely nothing to me. But it may offer clues to the experts as to why the apparently-successful install would not boot....

Any comments (in plain English!) would be welcome.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 6917
Joined: Sun Dec 16, 2007 1:17 pm

Re: Installation woes and a GRUB headache - Part 2

#2 Postby dolphin_oracle » Mon Nov 13, 2017 3:20 pm

I would make sure your systems can otherwise boot from the device, say with a live system rather than installed. there are many systems that refuse to boot live-USB from usb3 ports. I've got a lenovo that when used with legacy bios will not boot from the usb3 ports but will from my single usb2 port. If I boot the same system in uefi boot mode, then usb3 port works fine.

One more data point for you.

I've done what you are trying to do, installing to a usb thumb drive rather than running a live system. I now don't bother and stick to live-USB when using a usb-device.
http://www.youtube.com/runwiththedolphin
eeepc 904ha antix 15 32 bit (streaming media player)
acer c720p chromebook - chromeos / MX15-64 (custom snapshot) live USB.
lenovo s21e - antiX-16 MX16(live-usb)

br1anstorm
Forum Novice
Forum  Novice
Posts: 45
Joined: Sun Nov 05, 2017 2:25 pm

Re: Installation woes and a GRUB headache - Part 2

#3 Postby br1anstorm » Mon Nov 13, 2017 3:56 pm

Thanks for those thoughts, dolphin-oracle. It seems pretty clear to me that the problem lies with the MX-16 (specifically its GRUB) on the Sandisk USB stick. The boot problem described above was on my ancient laptop which only has usb2 ports (no usb3, no UEFI). That ancient laptop boots up all my other distros-on-usb-sticks (Mint, Lite, LXLE) with no issues.

I have also tried the MX-16 USB stick in both the usb2 and usb3 ports on my newer current laptop. Didn't work. I don't even get the bootloader splash screen: when I tried to boot from the MX-16 USB stick by going to one-time boot, the list of available drives appeared and disappeared so fast that I didn't have time to choose! After several attempts I did manage to click quickly enough to choose the USB stick - but nothing happened: no MX-16 grub bootloader splash screen, no list of booting problems, nada.

So I'm still flummoxed.... I know I have the option of running MX-16 in Live session with persistence from a USB stick, but I was rather hoping to have a proper install on a stick so that I could do all the updates and add some other software as a more comprehensive trial, to help me decide whether to move over from my current preference (which is Mint).

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 6917
Joined: Sun Dec 16, 2007 1:17 pm

Re: Installation woes and a GRUB headache - Part 2

#4 Postby dolphin_oracle » Mon Nov 13, 2017 4:06 pm

br1anstorm wrote:Thanks for those thoughts, dolphin-oracle. It seems pretty clear to me that the problem lies with the MX-16 (specifically its GRUB) on the Sandisk USB stick. The boot problem described above was on my ancient laptop which only has usb2 ports (no usb3, no UEFI). That ancient laptop boots up all my other distros-on-usb-sticks (Mint, Lite, LXLE) with no issues.

I have also tried the MX-16 USB stick in both the usb2 and usb3 ports on my newer current laptop. Didn't work. I don't even get the bootloader splash screen: when I tried to boot from the MX-16 USB stick by going to one-time boot, the list of available drives appeared and disappeared so fast that I didn't have time to choose! After several attempts I did manage to click quickly enough to choose the USB stick - but nothing happened: no MX-16 grub bootloader splash screen, no list of booting problems, nada.

So I'm still flummoxed.... I know I have the option of running MX-16 in Live session with persistence from a USB stick, but I was rather hoping to have a proper install on a stick so that I could do all the updates and add some other software as a more comprehensive trial, to help me decide whether to move over from my current preference (which is Mint).


well, that probably rules out the ports.

The only other thing I can think of is that perhaps the "root" definition in the grub configurations is not correct. The live system takes care of this, but the installed kinda figures to be on an internal partition. In other words, it is possible that during install time, the usb device you are installing to has one location in the drive hierarchy of your system, but after install it has another. UUIDs should always be constant, but /dev/sdXY are not bound to be the same every boot.

posting your grub.cfg file might be useful. I noticed some of your output complained of devices not existing.
http://www.youtube.com/runwiththedolphin
eeepc 904ha antix 15 32 bit (streaming media player)
acer c720p chromebook - chromeos / MX15-64 (custom snapshot) live USB.
lenovo s21e - antiX-16 MX16(live-usb)

br1anstorm
Forum Novice
Forum  Novice
Posts: 45
Joined: Sun Nov 05, 2017 2:25 pm

Re: Installation woes and a GRUB headache - Part 2

#5 Postby br1anstorm » Mon Nov 13, 2017 5:30 pm

Hello again dolphin_oracle.

Any kind of detective work is 'way above my pay grade. But if there is a wider issue of MX-16 and its GRUB not playing nicely when placed on an external drive, then maybe doing some investigation will help others, and perhaps also improve the distro.

I wouldn't have the first clue about analysing grub.cfg. But I can at least copy and paste what I find. So I've hunted down grub.cfg in the problematic external USB drive which has the non-booting MX-16 on it (NB that install was done on a laptop which also had WinXP on it - if that's relevant).

It's in the root partition on that external USB drive, at root/boot/grub/grub.cfg. This is what I find (and it runs to 303 lines...).

Best of luck in looking through it. I'd be interested to know what it reveals!

Code: Select all

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by 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
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

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 load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
else
  search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_GB
  insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
else
  search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
fi
insmod png
background_image -m stretch /usr/local/share/backgrounds/MX16/grub/kingfisher.png
if [ "${recordfail}" = 1 ] ; then
  set timeout=-1
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
else
  search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
fi
insmod png
if background_image /usr/local/share/backgrounds/MX16/grub/kingfisher.png; then
  true
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
   set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'MX-16.1 Metamorphosis' --class mx_16_1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e5e857f9-dd3d-43b2-b252-a5531d488478' {
   load_video
   insmod gzio
   if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
   insmod part_msdos
   insmod ext2
   set root='hd2,msdos1'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
   else
     search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
   fi
   echo   'Loading Linux 3.16.0-4-686-pae ...'
   linux   /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e5e857f9-dd3d-43b2-b252-a5531d488478 ro  quiet
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initrd.img-3.16.0-4-686-pae
}
submenu 'Advanced options for MX-16.1 Metamorphosis' $menuentry_id_option 'gnulinux-advanced-e5e857f9-dd3d-43b2-b252-a5531d488478' {
   menuentry 'MX-16.1 Metamorphosis, with Linux 3.16.0-4-686-pae' --class mx_16_1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-686-pae-advanced-e5e857f9-dd3d-43b2-b252-a5531d488478' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_msdos
      insmod ext2
      set root='hd2,msdos1'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
      else
        search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
      fi
      echo   'Loading Linux 3.16.0-4-686-pae ...'
      linux   /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e5e857f9-dd3d-43b2-b252-a5531d488478 ro  quiet
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-3.16.0-4-686-pae
   }
   menuentry 'MX-16.1 Metamorphosis, with Linux 3.16.0-4-686-pae (sysvinit)' --class mx_16_1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-686-pae-init-sysvinit-e5e857f9-dd3d-43b2-b252-a5531d488478' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_msdos
      insmod ext2
      set root='hd2,msdos1'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
      else
        search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
      fi
      echo   'Loading Linux 3.16.0-4-686-pae ...'
      linux   /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e5e857f9-dd3d-43b2-b252-a5531d488478 ro  quiet init=/lib/sysvinit/init
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-3.16.0-4-686-pae
   }
   menuentry 'MX-16.1 Metamorphosis, with Linux 3.16.0-4-686-pae (systemd)' --class mx_16_1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-686-pae-init-systemd-e5e857f9-dd3d-43b2-b252-a5531d488478' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_msdos
      insmod ext2
      set root='hd2,msdos1'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
      else
        search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
      fi
      echo   'Loading Linux 3.16.0-4-686-pae ...'
      linux   /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e5e857f9-dd3d-43b2-b252-a5531d488478 ro  quiet init=/lib/systemd/systemd
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-3.16.0-4-686-pae
   }
   menuentry 'MX-16.1 Metamorphosis, with Linux 3.16.0-4-586' --class mx_16_1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-586-advanced-e5e857f9-dd3d-43b2-b252-a5531d488478' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_msdos
      insmod ext2
      set root='hd2,msdos1'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
      else
        search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
      fi
      echo   'Loading Linux 3.16.0-4-586 ...'
      linux   /boot/vmlinuz-3.16.0-4-586 root=UUID=e5e857f9-dd3d-43b2-b252-a5531d488478 ro  quiet
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-3.16.0-4-586
   }
   menuentry 'MX-16.1 Metamorphosis, with Linux 3.16.0-4-586 (sysvinit)' --class mx_16_1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-586-init-sysvinit-e5e857f9-dd3d-43b2-b252-a5531d488478' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_msdos
      insmod ext2
      set root='hd2,msdos1'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
      else
        search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
      fi
      echo   'Loading Linux 3.16.0-4-586 ...'
      linux   /boot/vmlinuz-3.16.0-4-586 root=UUID=e5e857f9-dd3d-43b2-b252-a5531d488478 ro  quiet init=/lib/sysvinit/init
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-3.16.0-4-586
   }
   menuentry 'MX-16.1 Metamorphosis, with Linux 3.16.0-4-586 (systemd)' --class mx_16_1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-586-init-systemd-e5e857f9-dd3d-43b2-b252-a5531d488478' {
      load_video
      insmod gzio
      if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
      insmod part_msdos
      insmod ext2
      set root='hd2,msdos1'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
      else
        search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
      fi
      echo   'Loading Linux 3.16.0-4-586 ...'
      linux   /boot/vmlinuz-3.16.0-4-586 root=UUID=e5e857f9-dd3d-43b2-b252-a5531d488478 ro  quiet init=/lib/systemd/systemd
      echo   'Loading initial ramdisk ...'
      initrd   /boot/initrd.img-3.16.0-4-586
   }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
   insmod part_msdos
   insmod ext2
   set root='hd2,msdos1'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  e5e857f9-dd3d-43b2-b252-a5531d488478
   else
     search --no-floppy --fs-uuid --set=root e5e857f9-dd3d-43b2-b252-a5531d488478
   fi
   linux16   /boot/memtest86+.bin
}

### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Microsoft Windows XP Professional (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-E894C3B494C38392' {
   insmod part_msdos
   insmod ntfs
   set root='hd0,msdos1'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  E894C3B494C38392
   else
     search --no-floppy --fs-uuid --set=root E894C3B494C38392
   fi
   parttool ${root} hidden-
   drivemap -s (hd0) ${root}
   chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### 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 ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

User avatar
asinoro
Forum Regular
Forum Regular
Posts: 492
Joined: Mon Feb 22, 2016 12:26 pm

Re: Installation woes and a GRUB headache - Part 2

#6 Postby asinoro » Mon Nov 13, 2017 5:51 pm

Can you post this.

Code: Select all

sudo parted -l ; lsblk --sort name --output name,label,partlabel,size,fstype,mountpoint,state
If your case is solved edit [Solved] to your initial post title to help other users.
Don’t forget to Backup your system
Fix your Grub

User avatar
richb
Administrator
Posts: 15653
Joined: Wed Jul 12, 2006 2:17 pm

Re: Installation woes and a GRUB headache - Part 2

#7 Postby richb » Mon Nov 13, 2017 6:14 pm

I successfully installed to a USB drive. The parameters I used are as follows and may not be what you want. A difference is I used MX 17 beta 1 not MX 16

1. Started with MX 17 beta 1 as I had the Live version on a USB 2.0 stick
2. Inserted another 64 MGB USB 2.0 thumb in another port
3. The Live was designated sdd in the installer, the target sde
4. I chose use entire disk, format proceeded,
5. Chose MBR and only sda popped up with no other choices. So I cancelled.
6. Chose efi and the radio button auto unchecked and went back to MBR. At that point I had a drop down box and was able to choose sdd.
5. Grub install proceeded. It took a long time, not surprising on a USB 2.0 device, but finished OK.
6. Finished the rest of the install items and booted to the installed OS from the new drive.

I am posting from it now.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX-15- 64 - migrated to MX-16 RC1
HD Test: MX-16 RC1
AMD A8 7600 FM2+ CPU R7 Graphics, fglrx driver, 16 GIG Mem. Samsung EVO SSD 250 GB, 350 GB HD

br1anstorm
Forum Novice
Forum  Novice
Posts: 45
Joined: Sun Nov 05, 2017 2:25 pm

Re: Installation woes and a GRUB headache - Part 2

#8 Postby br1anstorm » Mon Nov 13, 2017 6:45 pm

Well RichB .... the steps you describe parallel almost exactly the procedure I went through as described in my OP at the start of this thread. I too had tried in a Live session - first time around - to put GRUB on the MBR of my external USB drive (it was sdb). The installer wouldn't do it. When I tried again - from scratch, having wiped and re-done the partition table - the installer went all the way through, created root, home and swap AND allowed me to install GRUB on sdb. Yes, it took a while. I completed the other stuff (user account, password etc) and finished the install. But it won't boot. I got that long string of terminal-type text quoted as code in my OP at #1 above.

I think the phrase is "go figure...."!

jbMacAZ
Forum Novice
Forum  Novice
Posts: 26
Joined: Tue Aug 22, 2017 2:08 am

Re: Installation woes and a GRUB headache - Part 2

#9 Postby jbMacAZ » Mon Nov 13, 2017 7:34 pm

Gave up waiting for root device.

I've seen similar errors when the partition UUID's don't match those in etc/fstab. The error is essentially a partition not ready/not found timeout. Check the swap partition, as linux installers are sometimes careless about picking the first swap partition found rather than the one intended. This can happen when the installer sees other linux installs on the system. But check all entries in fstab. Resizing, moving or reformatting a partition can cause the UUID to change. You can list the UUIDs with terminal command

Code: Select all

sudo blkid

Another issue could be that the device assignments hd0, hd1, etc are not always consistent when the booting different options. Removing the liveUSB sometimes changes the drive list. On mine, a bootable USB gets hd0 and my built-in SSD is always last, hd1 or hd2. This is why UUID's are preferred. I don't see anything in your grub.cfg that requires changing as long as the UUID's are all correct.

Also, when installing to a USB that you intend to move to another machine, never use any partitions that are not on the USB (don't ask me how I know, but I don't think you've done this.)

I don't know if this is practical, but try installing to your USB with any HDD or SSD unplugged. Fewer chances for the installer to make bad guesses and no chance of an accidental over-write.

While it shouldn't be necessary, it might be worth creating a Fat32 partition for /boot on the USB. The "scanning for Btrfs" seemed to generate some errors. The boot menu is happiest dealing with FAT partitions. Once the kernel is loaded and running, any file system should work fine. Encrpytion could cause extra problems, if you were using it.
Asus T100CHI (z3775, 64 bit quad core Intel atom baytrail) mixed-mode 32 bit UEFI, 64 bit OS

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 6917
Joined: Sun Dec 16, 2007 1:17 pm

Re: Installation woes and a GRUB headache - Part 2

#10 Postby dolphin_oracle » Mon Nov 13, 2017 8:53 pm

building on what jbMacAZ stated, I would look at this line in your grub.cfg

Code: Select all

set root='hd2,msdos1'


I would bet real money that your usb, when booting as a primary boot device, is actually hd0,msdos1 (or maybe hd1,msdos1).
http://www.youtube.com/runwiththedolphin
eeepc 904ha antix 15 32 bit (streaming media player)
acer c720p chromebook - chromeos / MX15-64 (custom snapshot) live USB.
lenovo s21e - antiX-16 MX16(live-usb)


Return to “Installation”

Who is online

Users browsing this forum: No registered users and 2 guests