Author Topic: problems installing  (Read 9286 times)

superwow

  • Posts: 86
  • the Earth has music for those who listen-Santayana
    • View Profile
Re: problems installing
« Reply #15 on: February 02, 2014, 12:58:21 AM »
Thanks all for the advice.

@jedi, thanks also for the super detailed posts. Thanks for outlining those steps. I would like to use MSW on the laptop in the future, or at least the possibility of doing so. What I think I will do first is wipe the drive with gparted then reinstall MSW as other users have done and then try reinstalling VSIDO. If that does not work, I may indeed try your suggestion of wiping the protected/hidden drive. And yes, I believe that is one of the reasons why MS now employs UEFI, to prevent users from switching to imo vastly superior linux of choice.

@PackRat, regarding Arch, my company permits it, but I don't fall into the usage scenario. My options are Suse, Debian, and Ubuntu. These systems have been verified as to analytical reproducibility, which is important because I am in an internationally regulated profession and analyses submitted to regulators must be accurate and reproducible. They are getting ready to de-list Ubuntu for some reason(s). ALSO, I think you have said an important thing though about that force BIOS option. Perhaps my recent MSW install has done something related to this.

@lwfitz, you also may be correct that grub is getting installed in some unintended place. Will check.

I do want to have the option of using MSW7 in the future on this machine, but won't have an opportunity to use another MSW machine until Monday. I'll ring back in here after my attempts then. Until then though, thanks for all the advice.

Digit

  • Techno Hippie
  • Posts: 295
  • savant (alegedly), polymath (wannabe)
    • View Profile
    • wastedartist.com
Re: problems installing
« Reply #16 on: February 03, 2014, 06:46:53 PM »
i hope it all goes well for you. 
i've not had a dual boot [with windows] since 2006ish iirc, so cant offer any suggestions about how to deal with the new issues for dual boot that uefi brought.  while it's great to be able to split up your linux os across many partitions across different physical drives, there's diminished gains for using more than just a single root partition (+swap) if you're not spanning physical drives.  it just adds complexity and increased chance of things going wrong.

all the best, superwow.  keep us in the loop. 
maybe share some relevant screen output to help us diagnose and help.  :)

superwow

  • Posts: 86
  • the Earth has music for those who listen-Santayana
    • View Profile
Re: problems installing
« Reply #17 on: February 08, 2014, 11:50:24 PM »
Thanks for the help all. It's been a while and life has been intervening for me, but a nice Saturday afternoon to revisit this install issue is proving useless. This is a stub post for now, from my live VSIDO. I will update in just a moment with more details from another computer, editing this post.

I have tried numerous options, including those in this thread, letter by letter, as well as the letter by letter instructions of supergrub and it's big brother rescatux. I did not save supergrub output, however rescatux output is here:

Code: [Select]
+ set -v

# Install Grub from the choosen Linux partition to the choosen hard disk
# 1 parametre = Selected hard disk
# 2 parametre = Selected partition
# While it is being run user is shown the hard disks
# and it is asked to order them
function rtux_Grub_Install () {

  local EXIT_VALUE=1 # Error by default
  local SELECTED_HARD_DISK="$1"
  local SELECTED_PARTITION="$2"

  local DETECTED_HARD_DISKS=$(rtux_Get_System_HardDisks);

  local SELECTED_HARD_DISK_DEV="/dev/${SELECTED_HARD_DISK}"
  local n_partition=${SELECTED_PARTITION}

  local TMP_MNT_PARTITION=${RESCATUX_ROOT_MNT}/${n_partition}
  local TMP_DEV_PARTITION=/dev/${n_partition}
  mkdir --parents ${TMP_MNT_PARTITION}
  if $(mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
    then
    mount -o bind /dev ${TMP_MNT_PARTITION}/dev
    mount -o bind /proc ${TMP_MNT_PARTITION}/proc
    mount -o bind /sys ${TMP_MNT_PARTITION}/sys

    if [[ -e ${TMP_MNT_PARTITION}${LINUX_OS_DETECTOR} ]] ; then
       rtux_File_Reordered_Device_Map \
      > ${TMP_MNT_PARTITION}/${DEVICE_MAP_RESCATUX_STR}


      # TODO: Improve with a cat command ended with a EOF mark
      local TMP_SCRIPT="/tmp/$$.sh"
      local TMP_MNT_PARTITION_SCRIPT="${TMP_MNT_PARTITION}${TMP_SCRIPT}"

      rtux_File_Chroot_Script_Device_Map \
      "if ${GRUB_INSTALL_BINARY}.unsupported --version ; then " \
      "${GRUB_INSTALL_BINARY}.unsupported ${SELECTED_HARD_DISK_DEV} ;"\
      " elif ${GRUB_INSTALL_BINARY} --version ; then " \
      "${GRUB_INSTALL_BINARY} ${SELECTED_HARD_DISK_DEV} ;" \
      " else " \
      "grub2-install ${SELECTED_HARD_DISK_DEV} ;" \
      "fi" \
      > ${TMP_MNT_PARTITION}${TMP_SCRIPT}
     
      chmod +x ${TMP_MNT_PARTITION_SCRIPT}

      # TODO: Let the user use other than now hard-coded /bin/bash
      chroot ${TMP_MNT_PARTITION} /bin/bash ${TMP_SCRIPT}
      EXIT_VALUE=$?
      mount -t auto -o remount,rw ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} # Workaround
      rm ${TMP_MNT_PARTITION_SCRIPT}
 
    fi # Linux detector was found
    umount ${TMP_MNT_PARTITION}/sys
    umount ${TMP_MNT_PARTITION}/proc
    umount ${TMP_MNT_PARTITION}/dev
    umount ${TMP_MNT_PARTITION};
  fi # Partition was mounted ok

  return ${EXIT_VALUE}

} # function rtux_Grub_Install ()

# TODO: Program check runtime (Maybe to be stolen from bootinfoscript)

# MAIN PROGRAM

GRUB_INSTALLED_OK_STR="Grub was installed OK! :)"
+ GRUB_INSTALLED_OK_STR='Grub was installed OK! :)'
GRUB_NOT_INSTALLED_STR="Grub was not installed. Something went wrong! :("
+ GRUB_NOT_INSTALLED_STR='Grub was not installed. Something went wrong! :('
WHICH_HARD_DISK_INSTALL_GRUB_STR="Which hard disk to install Grub on?"
+ WHICH_HARD_DISK_INSTALL_GRUB_STR='Which hard disk to install Grub on?'

SELECTED_PARTITION=$(rtux_Choose_Linux_partition);
rtux_Choose_Linux_partition)
rtux_Choose_Linux_partition
++ rtux_Choose_Linux_partition
rtux_Get_Linux_Os_Partitions)
rtux_Get_Linux_Os_Partitions
+++ rtux_Get_Linux_Os_Partitions
rtux_Get_System_Partitions)
rtux_Get_System_Partitions
++++ rtux_Get_System_Partitions
++++ awk '{ if ( ( NR>2 ) && ( $4 ~ "[0-9]$" ) ) {print $4} }' /proc/partitions
+++ local 'TARGET_PARTITIONS=sda1
sdb1
sdb2
sdc1
loop0
loop1'
+++ local SBIN_GRUB_PARTITIONS=
+++ for n_partition in '${TARGET_PARTITIONS}'
+++ local TMP_MNT_PARTITION=/mnt/rescatux/sda1
+++ local TMP_DEV_PARTITION=/dev/sda1
+++ mkdir --parents /mnt/rescatux/sda1
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/sda1 /mnt/rescatux/sda1
+++ [[ -e /mnt/rescatux/sda1/etc/issue ]]
+++ umount /mnt/rescatux/sda1
+++ for n_partition in '${TARGET_PARTITIONS}'
+++ local TMP_MNT_PARTITION=/mnt/rescatux/sdb1
+++ local TMP_DEV_PARTITION=/dev/sdb1
+++ mkdir --parents /mnt/rescatux/sdb1
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/sdb1 /mnt/rescatux/sdb1
+++ [[ -e /mnt/rescatux/sdb1/etc/issue ]]
+++ SBIN_GRUB_PARTITIONS=' sdb1'
+++ umount /mnt/rescatux/sdb1
+++ for n_partition in '${TARGET_PARTITIONS}'
+++ local TMP_MNT_PARTITION=/mnt/rescatux/sdb2
+++ local TMP_DEV_PARTITION=/dev/sdb2
+++ mkdir --parents /mnt/rescatux/sdb2
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/sdb2 /mnt/rescatux/sdb2
+++ for n_partition in '${TARGET_PARTITIONS}'
+++ local TMP_MNT_PARTITION=/mnt/rescatux/sdc1
+++ local TMP_DEV_PARTITION=/dev/sdc1
+++ mkdir --parents /mnt/rescatux/sdc1
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/sdc1 /mnt/rescatux/sdc1
+++ for n_partition in '${TARGET_PARTITIONS}'
+++ local TMP_MNT_PARTITION=/mnt/rescatux/loop0
+++ local TMP_DEV_PARTITION=/dev/loop0
+++ mkdir --parents /mnt/rescatux/loop0
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/loop0 /mnt/rescatux/loop0
+++ [[ -e /mnt/rescatux/loop0/etc/issue ]]
+++ umount /mnt/rescatux/loop0
+++ for n_partition in '${TARGET_PARTITIONS}'
+++ local TMP_MNT_PARTITION=/mnt/rescatux/loop1
+++ local TMP_DEV_PARTITION=/dev/loop1
+++ mkdir --parents /mnt/rescatux/loop1
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/loop1 /mnt/rescatux/loop1
+++ [[ -e /mnt/rescatux/loop1/etc/issue ]]
+++ SBIN_GRUB_PARTITIONS=' sdb1 loop1'
+++ umount /mnt/rescatux/loop1
+++ echo ' sdb1 loop1'
++ rtux_Abstract_Choose_Partition sdb1 loop1
++ local n=0
++ local LIST_VALUES=
++ local DESC_VALUES=
++ local 'SBIN_GRUB_PARTITIONS=sdb1 loop1'
++ for n_partition in '${SBIN_GRUB_PARTITIONS}'
rtux_Get_Etc_Issue_Content ${n_partition}
+++ rtux_Get_Etc_Issue_Content sdb1
+++ local PARTITION_TO_MOUNT=sdb1
+++ local n_partition=sdb1
+++ local TMP_MNT_PARTITION=/mnt/rescatux/sdb1
+++ local TMP_DEV_PARTITION=/dev/sdb1
+++ mkdir --parents /mnt/rescatux/sdb1
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/sdb1 /mnt/rescatux/sdb1
+++ [[ -e /mnt/rescatux/sdb1/etc/issue ]]
head -n 1 ${TMP_MNT_PARTITION}${ETC_ISSUE_PATH} | sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g')
head -n 1 ${TMP_MNT_PARTITION}${ETC_ISSUE_PATH} | sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g')
head -n 1 ${TMP_MNT_PARTITION}${ETC_ISSUE_PATH} | sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g'
++++ head -n 1 /mnt/rescatux/sdb1/etc/issue
++++ sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g'
+++ echo VSIDO-
+++ umount /mnt/rescatux/sdb1
++ local issue_value=VSIDO-
echo $issue_value | sed 's/\ /\-/')
echo $issue_value | sed 's/\ /\-/'
+++ echo VSIDO-
+++ sed 's/\ /\-/'
++ issue_value=VSIDO-
echo $issue_value | sed 's/ /\-/')
echo $issue_value | sed 's/ /\-/'
+++ echo VSIDO-
+++ sed 's/ /\-/'
++ issue_value=VSIDO-
++ [[ n -eq 0 ]]
++ LIST_VALUES='TRUE sdb1 VSIDO-'
++ let n=n+1
++ for n_partition in '${SBIN_GRUB_PARTITIONS}'
rtux_Get_Etc_Issue_Content ${n_partition}
+++ rtux_Get_Etc_Issue_Content loop1
+++ local PARTITION_TO_MOUNT=loop1
+++ local n_partition=loop1
+++ local TMP_MNT_PARTITION=/mnt/rescatux/loop1
+++ local TMP_DEV_PARTITION=/dev/loop1
+++ mkdir --parents /mnt/rescatux/loop1
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++++ mount -t auto /dev/loop1 /mnt/rescatux/loop1
+++ [[ -e /mnt/rescatux/loop1/etc/issue ]]
head -n 1 ${TMP_MNT_PARTITION}${ETC_ISSUE_PATH} | sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g')
head -n 1 ${TMP_MNT_PARTITION}${ETC_ISSUE_PATH} | sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g')
head -n 1 ${TMP_MNT_PARTITION}${ETC_ISSUE_PATH} | sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g'
++++ head -n 1 /mnt/rescatux/loop1/etc/issue
++++ sed -e 's/\\. //g' -e 's/\\.//g' -e 's/^[ \t]*//' -e 's/\ /-/g' -e 's/\ \ /-/g' -e 's/\n/-/g'
+++ echo Debian-GNU/Linux-6.0-
+++ umount /mnt/rescatux/loop1
++ local issue_value=Debian-GNU/Linux-6.0-
echo $issue_value | sed 's/\ /\-/')
echo $issue_value | sed 's/\ /\-/'
+++ echo Debian-GNU/Linux-6.0-
+++ sed 's/\ /\-/'
++ issue_value=Debian-GNU/Linux-6.0-
echo $issue_value | sed 's/ /\-/')
echo $issue_value | sed 's/ /\-/'
+++ echo Debian-GNU/Linux-6.0-
+++ sed 's/ /\-/'
++ issue_value=Debian-GNU/Linux-6.0-
++ [[ n -eq 0 ]]
++ LIST_VALUES='TRUE sdb1 VSIDO- FALSE loop1 Debian-GNU/Linux-6.0-'
++ let n=n+1
zenity ${ZENITY_COMMON_OPTIONS}  --list  --text "${WHICH_PARTITION_STR}" --radiolist  --column "${SELECT_STR}" --column "${PARTITION_STR}" --column "${DESCRIPTION_STR}" ${LIST_VALUES})"
zenity ${ZENITY_COMMON_OPTIONS}  --list  --text "${WHICH_PARTITION_STR}" --radiolist  --column "${SELECT_STR}" --column "${PARTITION_STR}" --column "${DESCRIPTION_STR}" ${LIST_VALUES})
zenity ${ZENITY_COMMON_OPTIONS}  --list  --text "${WHICH_PARTITION_STR}" --radiolist  --column "${SELECT_STR}" --column "${PARTITION_STR}" --column "${DESCRIPTION_STR}" ${LIST_VALUES}
+++ zenity --width=600 --height=400 --list --text 'Which partition?' --radiolist --column Select --column Partition --column Description TRUE sdb1 VSIDO- FALSE loop1 Debian-GNU/Linux-6.0-
++ echo sdb1
+ SELECTED_PARTITION=sdb1



SELECTED_HARD_DISK=$(rtux_Choose_Hard_Disk ${WHICH_HARD_DISK_INSTALL_GRUB_STR});
rtux_Choose_Hard_Disk ${WHICH_HARD_DISK_INSTALL_GRUB_STR})
rtux_Choose_Hard_Disk ${WHICH_HARD_DISK_INSTALL_GRUB_STR}
++ rtux_Choose_Hard_Disk Which hard disk to install Grub 'on?'
++ local 'text_to_ask=Which hard disk to install Grub on?'
++ local n=0
++ local HD_LIST_VALUES=
rtux_Get_System_HardDisks)
rtux_Get_System_HardDisks
+++ rtux_Get_System_HardDisks
+++ awk '{ if ( ( NR>2 ) && ( $4 ~ "[[:alpha:]]$" ) ) {print $4} }' /proc/partitions
++ local 'DETECTED_HARD_DISKS=sda
sdb
sdc'
++ for n_hard_disk in '${DETECTED_HARD_DISKS}'
++ [[ 0 -eq 0 ]]
${FDISK_COMMAND} -l       | egrep ${n_hard_disk}       | egrep 'Disk.*bytes'       | awk '{ sub(/,/,"");  print $3 "-" $4 }'
+++ /sbin/fdisk -l
+++ egrep sda
+++ egrep 'Disk.*bytes'
+++ awk '{ sub(/,/,"");  print $3 "-" $4 }'

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

++ local 'HD_LIST_VALUES=TRUE sda 500.1-GB'
++ let n=n+1
++ for n_hard_disk in '${DETECTED_HARD_DISKS}'
++ [[ 1 -eq 0 ]]
${FDISK_COMMAND} -l       | egrep ${n_hard_disk}       | egrep 'Disk.*bytes'       | awk '{ sub(/,/,"");  print $3 "-" $4 }'
+++ /sbin/fdisk -l
+++ egrep sdb
+++ egrep 'Disk.*bytes'
+++ awk '{ sub(/,/,"");  print $3 "-" $4 }'

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

++ local 'HD_LIST_VALUES=TRUE sda 500.1-GB FALSE sdb 32.0-GB'
++ let n=n+1
++ for n_hard_disk in '${DETECTED_HARD_DISKS}'
++ [[ 2 -eq 0 ]]
${FDISK_COMMAND} -l       | egrep ${n_hard_disk}       | egrep 'Disk.*bytes'       | awk '{ sub(/,/,"");  print $3 "-" $4 }'
+++ /sbin/fdisk -l
+++ egrep sdc
+++ egrep 'Disk.*bytes'
+++ awk '{ sub(/,/,"");  print $3 "-" $4 }'

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

++ local 'HD_LIST_VALUES=TRUE sda 500.1-GB FALSE sdb 32.0-GB FALSE sdc 4007-MB'
++ let n=n+1
zenity ${ZENITY_COMMON_OPTIONS}  --list  --text "${text_to_ask}" --radiolist  --column "${SELECT_STR}" --column "${HARDDISK_STR}" --column "${SIZE_STR}" ${HD_LIST_VALUES})
zenity ${ZENITY_COMMON_OPTIONS}  --list  --text "${text_to_ask}" --radiolist  --column "${SELECT_STR}" --column "${HARDDISK_STR}" --column "${SIZE_STR}" ${HD_LIST_VALUES})
zenity ${ZENITY_COMMON_OPTIONS}  --list  --text "${text_to_ask}" --radiolist  --column "${SELECT_STR}" --column "${HARDDISK_STR}" --column "${SIZE_STR}" ${HD_LIST_VALUES}
+++ zenity --width=600 --height=400 --list --text 'Which hard disk to install Grub on?' --radiolist --column Select --column 'Hard Disk' --column Size TRUE sda 500.1-GB FALSE sdb 32.0-GB FALSE sdc 4007-MB
++ echo sdb
+ SELECTED_HARD_DISK=sdb

if rtux_Grub_Install ${SELECTED_HARD_DISK} ${SELECTED_PARTITION} ; then
  rtux_Message_Success ${GRUB_INSTALLED_OK_STR}
else
  rtux_Message_Failure ${GRUB_NOT_INSTALLED_STR}
fi
+ rtux_Grub_Install sdb sdb1
+ local EXIT_VALUE=1
+ local SELECTED_HARD_DISK=sdb
+ local SELECTED_PARTITION=sdb1
rtux_Get_System_HardDisks)
rtux_Get_System_HardDisks
++ rtux_Get_System_HardDisks
++ awk '{ if ( ( NR>2 ) && ( $4 ~ "[[:alpha:]]$" ) ) {print $4} }' /proc/partitions
+ local 'DETECTED_HARD_DISKS=sda
sdb
sdc'
+ local SELECTED_HARD_DISK_DEV=/dev/sdb
+ local n_partition=sdb1
+ local TMP_MNT_PARTITION=/mnt/rescatux/sdb1
+ local TMP_DEV_PARTITION=/dev/sdb1
+ mkdir --parents /mnt/rescatux/sdb1
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null)
mount -t auto ${TMP_DEV_PARTITION} ${TMP_MNT_PARTITION} 2> /dev/null
++ mount -t auto /dev/sdb1 /mnt/rescatux/sdb1
+ mount -o bind /dev /mnt/rescatux/sdb1/dev
+ mount -o bind /proc /mnt/rescatux/sdb1/proc
+ mount -o bind /sys /mnt/rescatux/sdb1/sys
+ [[ -e /mnt/rescatux/sdb1/etc/issue ]]
+ rtux_File_Reordered_Device_Map
rtux_Get_System_HardDisks)
rtux_Get_System_HardDisks
++ rtux_Get_System_HardDisks
++ awk '{ if ( ( NR>2 ) && ( $4 ~ "[[:alpha:]]$" ) ) {print $4} }' /proc/partitions
+ local 'DETECTED_HARD_DISKS=sda
sdb
sdc'
+ local COLUMN_NUMBER=2
+ local HARD_DISK_NUMBER=0
+ for n_hard_disk in '${DETECTED_HARD_DISKS}'
+ let HARD_DISK_NUMBER=HARD_DISK_NUMBER+1
+ for n_hard_disk in '${DETECTED_HARD_DISKS}'
+ let HARD_DISK_NUMBER=HARD_DISK_NUMBER+1
+ for n_hard_disk in '${DETECTED_HARD_DISKS}'
+ let HARD_DISK_NUMBER=HARD_DISK_NUMBER+1
+ '[' 3 -gt 1 ']'
+ ARGS_ARRAY_INDEX=0
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=2
+ let ARGS_ARRAY_INDEX=0+1
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]='Order hard disks'
+ let ARGS_ARRAY_INDEX=1+1
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]='Order hard disks according to boot order. Press OK to continue.'
+ let ARGS_ARRAY_INDEX=2+1
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]='Hard disk'
+ let ARGS_ARRAY_INDEX=3+1
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=Size
+ let ARGS_ARRAY_INDEX=4+1
+ for n_hard_disk in '${DETECTED_HARD_DISKS}'
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=sda
+ let ARGS_ARRAY_INDEX=5+1
/sbin/fdisk -l /dev/${n_hard_disk}     | egrep 'Disk.*bytes'     | awk '{ sub(/,/,"");  print $3 "-" $4 }'
++ /sbin/fdisk -l /dev/sda
++ egrep 'Disk.*bytes'
++ awk '{ sub(/,/,"");  print $3 "-" $4 }'

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=500.1-GB
+ let ARGS_ARRAY_INDEX=6+1
+ for n_hard_disk in '${DETECTED_HARD_DISKS}'
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=sdb
+ let ARGS_ARRAY_INDEX=7+1
/sbin/fdisk -l /dev/${n_hard_disk}     | egrep 'Disk.*bytes'     | awk '{ sub(/,/,"");  print $3 "-" $4 }'
++ /sbin/fdisk -l /dev/sdb
++ egrep 'Disk.*bytes'
++ awk '{ sub(/,/,"");  print $3 "-" $4 }'

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=32.0-GB
+ let ARGS_ARRAY_INDEX=8+1
+ for n_hard_disk in '${DETECTED_HARD_DISKS}'
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=sdc
+ let ARGS_ARRAY_INDEX=9+1
/sbin/fdisk -l /dev/${n_hard_disk}     | egrep 'Disk.*bytes'     | awk '{ sub(/,/,"");  print $3 "-" $4 }'
++ /sbin/fdisk -l /dev/sdc
++ egrep 'Disk.*bytes'
++ awk '{ sub(/,/,"");  print $3 "-" $4 }'
+ ARGS_ARRAY[ARGS_ARRAY_INDEX]=4007-MB
+ let ARGS_ARRAY_INDEX=10+1
${RESCATUX_PATH}order.py "${ARGS_ARRAY[@]}"
++ /home/user/Desktop/rescapp/order.py 2 'Order hard disks' 'Order hard disks according to boot order. Press OK to continue.' 'Hard disk' Size sda 500.1-GB sdb 32.0-GB sdc 4007-MB
+ DESIRED_ORDER='sdb
sda
sdc'
+ local n=0
+ for n_hard_disk in '${DESIRED_ORDER}'
+ echo -e -n '(hd0) /dev/sdb\n'
+ let n=n+1
+ for n_hard_disk in '${DESIRED_ORDER}'
+ echo -e -n '(hd1) /dev/sda\n'
+ let n=n+1
+ for n_hard_disk in '${DESIRED_ORDER}'
+ echo -e -n '(hd2) /dev/sdc\n'
+ let n=n+1
+ local TMP_SCRIPT=/tmp/3295.sh
+ local TMP_MNT_PARTITION_SCRIPT=/mnt/rescatux/sdb1/tmp/3295.sh
+ rtux_File_Chroot_Script_Device_Map 'if grub-install.unsupported --version ; then ' 'grub-install.unsupported /dev/sdb ;' ' elif grub-install --version ; then ' 'grub-install /dev/sdb ;' ' else ' 'grub2-install /dev/sdb ;' fi
+ local 'command_line_to_run=if grub-install.unsupported --version ; then  grub-install.unsupported /dev/sdb ;  elif grub-install --version ; then  grub-install /dev/sdb ;  else  grub2-install /dev/sdb ; fi'
+ cat
+ chmod +x /mnt/rescatux/sdb1/tmp/3295.sh
+ chroot /mnt/rescatux/sdb1 /bin/bash /tmp/3295.sh
/tmp/3295.sh: line 10: grub-install.unsupported: command not found
grub-install (GRUB) 2.00-22
/usr/sbin/grub-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
/usr/sbin/grub-bios-setup: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub-bios-setup: error: will not proceed with blocklists.
+ EXIT_VALUE=1
+ mount -t auto -o remount,rw /dev/sdb1 /mnt/rescatux/sdb1
+ rm /mnt/rescatux/sdb1/tmp/3295.sh
+ umount /mnt/rescatux/sdb1/sys
+ umount /mnt/rescatux/sdb1/proc
+ umount /mnt/rescatux/sdb1/dev
umount: /mnt/rescatux/sdb1/dev: not mounted
+ umount /mnt/rescatux/sdb1
+ return 1
+ rtux_Message_Failure Grub was not installed. Something went 'wrong!' ':('
+ local 'text_to_show=Grub was not installed. Something went wrong! :('
+ zenity --width=600 --height=400 --info '--title=Failure!' '--text=Grub was not installed. Something went wrong! :('



No option fixes the problem. But I remembered http://bootinfoscript.sourceforge.net/ so downloaded and ran the script. Here is my output for now:

Code: [Select]
                  Boot Info Script 0.61      [1 April 2012]


============================= Boot Info Summary: ===============================

 => Windows is installed in the MBR of /dev/sda.
 => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 98 for .
 => Grub2 (v1.99) is installed in the MBR of /dev/sdc.

sda1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System: 
    Boot files:       

sdb1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System:  VSIDO
    Boot files:        /boot/grub/grub.cfg /etc/fstab

sdc1: __________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info:
    Operating System: 
    Boot files:       

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1    *          2,048   976,771,071   976,769,024   7 NTFS / exFAT / HPFS


Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *          2,048    62,531,583    62,529,536   c W95 FAT32 (LBA)


Drive: sdc _____________________________________________________________________

Disk /dev/sdc: 2003 MB, 2003828736 bytes
64 heads, 32 sectors/track, 1911 cylinders, total 3913728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdc1    *              0       782,335       782,336  17 Hidden NTFS / HPFS


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/loop0                                              squashfs   
/dev/sda1        6a4ac40d-b251-4b0b-aa93-e5ab0e132a6c   ext4       
/dev/sdb1        d1e04a9f-3824-4505-b906-42fe2a471692   ext4       
/dev/sdc1                                               iso9660    VSIDO x64 LiveCD

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/loop0       /lib/live/mount/rootfs/filesystem.squashfs squashfs   (ro,noatime)
/dev/sdc1        /lib/live/mount/medium   iso9660    (ro,noatime)


=========================== sdb1/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# 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
set default="0"

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='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
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_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=-1
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
insmod png
if background_image /boot/grub/vsido_grub.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 'VSIDO GNU/Linux' --class vsido --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-d1e04a9f-3824-4505-b906-42fe2a471692' {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
echo 'Loading Linux 3.12-1-amd64 ...'
linux /boot/vmlinuz-3.12-1-amd64 root=UUID=d1e04a9f-3824-4505-b906-42fe2a471692 ro  quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.12-1-amd64
}
submenu 'Advanced options for VSIDO GNU/Linux' $menuentry_id_option 'gnulinux-advanced-d1e04a9f-3824-4505-b906-42fe2a471692' {
menuentry 'VSIDO GNU/Linux, with Linux 3.12-1-amd64' --class vsido --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.12-1-amd64-advanced-d1e04a9f-3824-4505-b906-42fe2a471692' {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
echo 'Loading Linux 3.12-1-amd64 ...'
linux /boot/vmlinuz-3.12-1-amd64 root=UUID=d1e04a9f-3824-4505-b906-42fe2a471692 ro  quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.12-1-amd64
}
menuentry 'VSIDO GNU/Linux, with Linux 3.12-1-amd64 (recovery mode)' --class vsido --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.12-1-amd64-recovery-d1e04a9f-3824-4505-b906-42fe2a471692' {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
echo 'Loading Linux 3.12-1-amd64 ...'
linux /boot/vmlinuz-3.12-1-amd64 root=UUID=d1e04a9f-3824-4505-b906-42fe2a471692 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.12-1-amd64
}
}

### 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='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
menuentry "Memory test (memtest86+, experimental multiboot)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
multiboot /boot/memtest86+_multiboot.bin
}
menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  d1e04a9f-3824-4505-b906-42fe2a471692
else
  search --no-floppy --fs-uuid --set=root d1e04a9f-3824-4505-b906-42fe2a471692
fi
multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### 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 ###
--------------------------------------------------------------------------------

=============================== sdb1/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc /proc proc defaults 0 0
# /dev/sdb1
/dev/sdb1 / ext4 relatime,errors=remount-ro 0 1
# /dev/sda1 home
/dev/sda1 /home ext4 relatime 0 0
# /dev/
/dev/ none swap sw 0 0
# cdrom
/dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0

--------------------------------------------------------------------------------

=================== sdb1: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)


======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on sdc1

00000000  33 ed 90 90 90 90 90 90  90 90 90 90 90 90 90 90  |3...............|
00000010  90 90 90 90 90 90 90 90  90 90 90 90 90 90 90 90  |................|
00000020  33 ed fa 8e d5 bc 00 7c  fb fc 66 31 db 66 31 c9  |3......|..f1.f1.|
00000030  66 53 66 51 06 57 8e dd  8e c5 52 be 00 7c bf 00  |fSfQ.W....R..|..|
00000040  06 b9 00 01 f3 a5 ea 4b  06 00 00 52 b4 41 bb aa  |.......K...R.A..|
00000050  55 31 c9 30 f6 f9 cd 13  72 16 81 fb 55 aa 75 10  |U1.0....r...U.u.|
00000060  83 e1 01 74 0b 66 c7 06  f1 06 b4 42 eb 15 eb 00  |...t.f.....B....|
00000070  5a 51 b4 08 cd 13 83 e1  3f 5b 51 0f b6 c6 40 50  |ZQ......?[Q...@P|
00000080  f7 e1 53 52 50 bb 00 7c  b9 04 00 66 a1 b0 07 e8  |..SRP..|...f....|
00000090  44 00 0f 82 80 00 66 40  80 c7 02 e2 f2 66 81 3e  |D.....f@.....f.>|
000000a0  40 7c fb c0 78 70 75 09  fa bc ec 7b ea 44 7c 00  |@|..xpu....{.D|.|
000000b0  00 e8 83 00 69 73 6f 6c  69 6e 75 78 2e 62 69 6e  |....isolinux.bin|
000000c0  20 6d 69 73 73 69 6e 67  20 6f 72 20 63 6f 72 72  | missing or corr|
000000d0  75 70 74 2e 0d 0a 66 60  66 31 d2 66 03 06 f8 7b  |upt...f`f1.f...{|
000000e0  66 13 16 fc 7b 66 52 66  50 06 53 6a 01 6a 10 89  |f...{fRfP.Sj.j..|
000000f0  e6 66 f7 36 e8 7b c0 e4  06 88 e1 88 c5 92 f6 36  |.f.6.{.........6|
00000100  ee 7b 88 c6 08 e1 41 b8  01 02 8a 16 f2 7b cd 13  |.{....A......{..|
00000110  8d 64 10 66 61 c3 e8 1e  00 4f 70 65 72 61 74 69  |.d.fa....Operati|
00000120  6e 67 20 73 79 73 74 65  6d 20 6c 6f 61 64 20 65  |ng system load e|
00000130  72 72 6f 72 2e 0d 0a 5e  ac b4 0e 8a 3e 62 04 b3  |rror...^....>b..|
00000140  07 cd 10 3c 0a 75 f1 cd  18 f4 eb fd 00 00 00 00  |...<.u..........|
00000150  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  a4 00 00 00 00 00 00 00  9b 0a 4e 0e 00 00 80 00  |..........N.....|
000001c0  01 00 17 3f 60 7d 00 00  00 00 00 f0 0b 00 00 00  |...?`}..........|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200


=============================== StdErr Messages: ===============================

initrd.img: FIBMAP unsupported
cat: /tmp/BootInfo-e0Js4qwL/Tmp_Log: No such file or directory
  No volume groups found


I thought I would check back in here for advice from the experts while I educate myself at a couple of informative ubuntuforums (http://ubuntuforums.org/showthread.php?t=1736409 and http://ubuntuforums.org/showthread.php?t=1719851&page=6).

Once again thanks for the feedback you have given so far.

jedi

  • DEFCON 1
  • Posts: 1540
  • Not all those who wander are lost.
    • View Profile
    • NixNut.com
Re: problems installing
« Reply #18 on: February 09, 2014, 12:00:56 AM »
Wow!  Or should I say Super Wow!  That's a lot of info.  Will look it over and see if I can come up with something for you.  It does show right of the bat that Windows is installed in the MBR of /dev/sda.  I don't remember asking this before, but does Windows currently boot OK?  Just curious.  Linux should have no problems dual booting with Windows, so this is indeed puzzling.  Thanks for the detailed info, I'll look at it a little closer...
By the way, in all the reading I've done and from personal experience, GPT is the best partitioning scheme IF YOU AREN'T GOING TO DUAL BOOT!  Linux will boot to a GPT partition, I've done it, however looking at your logs above, they clearly state that both /dev/sda and /dev/sdb are GPT disks, and not only that, but /dev/sda is housing an EFI boot area in the MBR.  This is your whole problem in a nutshell!!!
As stated previously, your hardware is quite obviously UEFI enabled.  Debian by default, and therefore VSIDO as well, will not be seen while this EFI partition remains in place.  It is the first place your BIOS looks for a bootable OS disk.  Unfortunately you are not going to get VSIDO installed while the EFI partition is in place and enabled in BIOS.  I know of no way currently to get around this issue.  (short of the aforementioned post where I mentioned deleting said partition)
At this point I do not know of a way for you to do what you are trying to do and still be able to run Windows at a later date.  There are disk-cloning tools you could use to BU the current state of your drives, however, I'm not 100% certain the EFI partition in the MBR would be saved.  So I don't feel confident in telling you to go to the extreme of deleting that partition.  As I said before, doing so would surely guarantee that your Windows OS would not install again.  This is MY experience with EFI, and someone else may have a way around this.  If so, I've not found or read about it anywhere.

Also, before everyone jumps on my back and starts pummeling me, I know that Debian does indeed now have a working EFI installer.  VSIDO does not.  While I have done it, I believe it to be beyond the scope of these forums for me to tell you to "do it my way"!

Again, your log files tell the story.  Both disks are GPT partitioned, and /dev/sda does indeed have an EFI boot partition on it.  You will NOT be able to get Grub2 (or SuperGrub) to install to that particular partition.

As an aside, I have a UEFI enabled laptop that came preinstalled with Windows 8.  I created the BU DVD's that MS recommends you do since they are to cheap to include install media.  I just tried to "restore" my Windows 8 using these DVD's.  As I have deleted my EFI partition in order to insure Windows never again graces this particular PC, the restore procedure failed flat and right away.  So, with that in mind I would assume your situation to be the same.  Delete the partition, and Windows will NOT restore to your machine.  I will never use MS products again, so it was with some glee that I deleted that partition off of my laptop! :)

Ubuntu and Debian (Ubuntu is Debian based) both indeed have UEFI enabled installers.  However, these do not include Grub2.  They both use what is called 'grub-efi-amd64' (or 32 I assume for 32bit systems) to boot the system utilizing a FAT32 EFI partition just like Windows.  The grub-efi-amd64 has a "signing" feature which allows for the EFI boot process as well as even being able to take advantage of the "Secure Boot" feature.
Forum Netiquette

"No matter how smart you are you can never convince someone stupid that they are stupid."  Anonymous

lwfitz

  • DEFCON 1
  • Posts: 1752
  • sudo rm -rf /
    • View Profile
Re: problems installing
« Reply #19 on: February 09, 2014, 05:36:19 AM »
Quote from: jedi
Again, your log files tell the story.  Both disks are GPT partitioned, and /dev/sda does indeed have an EFI boot partition on it.  You will NOT be able to get Grub2 (or SuperGrub) to install to that particular partition.

Absoluetly correct!

If you want VSIDO installed you will need to switch from GPT to MBR with gparted. This will wipe your Windows 7 install out but you can then install windows 7 on the disk as MBR and then install vsido and grub2 should boot just fine.

If you dont have a a windows 7 disk you can just torrent one. Nothing illegal about it as long as you use your license that you (or your company) paid for which is on the bottom of the laptop. If you do wipe your windows 7 install and reconfigure for MBR just make sure you install windows before vsido because the the Windows boot loader will override grub.

superwow

  • Posts: 86
  • the Earth has music for those who listen-Santayana
    • View Profile
Re: problems installing
« Reply #20 on: February 12, 2014, 07:50:59 AM »
Everybody: thanks a ton for your patient advice. I learned a lot from each of you. And also from the install itself. As you may see from my first screenshot, I have gotten VSIDO up and running. Here is what I did and found.

I could be wrong, but it seems Gparted is apparently unable to see or affect the MBR. For me, changing the partition type, or changing the boot flags, or doing all permutations of things via Gparted, even as root, did nothing to change my problem and get me past a blank black screen with a blinking cursor, or the other error messages. Copious web searches and cross-searches suggested I was right and that gparted isn't gifted this way, but other tools, like gdisk, are. But reading its manpage and various tutorials suggested I could brick my laptop. Arrgg. Too much reading and too many conflicting tutorials. I got fed up :) and then remembered I made copious ISO9000 quality notes regarding the first nix install on this computer, which at the time was Ubuntu, and which was incidentally also a bear to install, thanks UEFI. I dug out my notes, paroused the pages and found several posts with red underlining and stars, etc.

The tool that did the trick was Boot-Repair, which I used from a Lubuntu USB drive. There's a decent description here: https://help.ubuntu.com/community/Boot-Repair. I believe it combines the bootinfoscript with some additional nixfu which is out of my expertise. I do like me some terminal and bash and config files, but, I can appreciate a nice GUI program which works. I don't know if it is in the Debian repositories, but, it was in Lubuntu's, it worked, and now I am happy.

Task accomplished. Now on to get the volume and brightness keys to work --- arrrgg darn lxde.....

Thanks again everybody!

VastOne

  •      v-ger
  • Posts: 3948
    • View Profile
    • VSIDO Community
Re: problems installing
« Reply #21 on: February 12, 2014, 03:10:56 PM »
Great news superwow and thank you all who assisted and developed an incredible installation scenario and fix
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

lwfitz

  • DEFCON 1
  • Posts: 1752
  • sudo rm -rf /
    • View Profile
Re: problems installing
« Reply #22 on: February 12, 2014, 05:42:22 PM »
Fantastc superwow! Glad things got worked out for you.

jedi

  • DEFCON 1
  • Posts: 1540
  • Not all those who wander are lost.
    • View Profile
    • NixNut.com
Re: problems installing
« Reply #23 on: February 12, 2014, 11:12:46 PM »
Good job superwow!  Way to stick with it.  Glad you got it installed finally.  Hopefully all this will help another user in the future!
Forum Netiquette

"No matter how smart you are you can never convince someone stupid that they are stupid."  Anonymous

ew

  • Posts: 67
  • Linux may very well be my midlife crisis :D
    • View Profile
Re: problems installing
« Reply #24 on: February 13, 2014, 01:50:43 AM »
Quote from: jedi
Again, your log files tell the story.  Both disks are GPT partitioned, and /dev/sda does indeed have an EFI boot partition on it.  You will NOT be able to get Grub2 (or SuperGrub) to install to that particular partition.

Absoluetly correct!

If you want VSIDO installed you will need to switch from GPT to MBR with gparted. This will wipe your Windows 7 install out but you can then install windows 7 on the disk as MBR and then install vsido and grub2 should boot just fine.

If you dont have a a windows 7 disk you can just torrent one. Nothing illegal about it as long as you use your license that you (or your company) paid for which is on the bottom of the laptop. If you do wipe your windows 7 install and reconfigure for MBR just make sure you install windows before vsido because the the Windows boot loader will override grub.

Not true. I have no issues installing VSIDO on gpt-disks. The solution is quite simple. Use the installer-version that is WITHOUT swap. The swap-installer fails because of this:
 
Code: [Select]
#find the swap partition
TARGETSWAP=`fdisk -l | grep swap | awk '{print $1}' | cut -d "/" -f3`

On a gpt-system, the output will be this:
Code: [Select]
ew@Ubuntu-G580:~$ sudo fdisk -l | grep swap | awk '{print $1}' | cut -d "/" -f3
[sudo] password for ew:

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

ew@Ubuntu-G580:~$

But by replacing "fdisk -l" with "blkid" the above command will give this output:
Code: [Select]
ew@Ubuntu-G580:~$ sudo blkid  | grep swap | awk '{print $1}' | cut -d "/" -f3
sda7:

As you see, it now detects sda7 as my swap partition...

But this is just a sidenote. Also, it`s no problem writing grub to a disk with a efi-partition. The same disk can be bootable both in efi-mode and bios/legacy-mode at the same time, and you can actually have one distro/os handling the efi-boot, and another distro handling the bios-boot. Very useful. You can efi-boot Windows, and legacy-boot Linux. Then set legacy as the first/primary boot-option,. That way you will boot linux by default, while you can interrupt boot with F12 or wahtever gives you the boot-prioritary and select the Windows-bootloader when you want to boot that.

Personally, I have Ubuntu to handle my efi-boot, and it detects and adds efi-entrys for all other distros that I install. But even if I do this, I still let one of the other grubs be installed to mbr, and use it as a secondary way to boot. A backup if you may, if something happens to the efi-boot.

Edit: One question though. Is the font-size in the code-snippets supposed to be so big. I find it hard to read this way.
-ew
-----------------------------
 "What happens when you read some doc and either it doesn't answer your question or is demonstrably wrong? In Linux, you say "Linux sucks" and go read the code. In Windows/Oracle/etc you say "Windows sucks" and start banging your head against the wall."
--- Denis Vlasenko on lkml

lwfitz

  • DEFCON 1
  • Posts: 1752
  • sudo rm -rf /
    • View Profile
Re: problems installing
« Reply #25 on: February 13, 2014, 05:58:30 AM »
Wow, my mistake. Thanks for the correction ew

jedi

  • DEFCON 1
  • Posts: 1540
  • Not all those who wander are lost.
    • View Profile
    • NixNut.com
Re: problems installing
« Reply #26 on: February 13, 2014, 08:58:42 AM »
Sorry posted after I noticed it was locked.  Post removed...
Perhaps I should be taking a break...
Forum Netiquette

"No matter how smart you are you can never convince someone stupid that they are stupid."  Anonymous

VastOne

  •      v-ger
  • Posts: 3948
    • View Profile
    • VSIDO Community
Re: problems installing
« Reply #27 on: February 13, 2014, 02:50:35 PM »
Unlocked... It had to have been some mistake that it was locked in the first place

VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

lwfitz

  • DEFCON 1
  • Posts: 1752
  • sudo rm -rf /
    • View Profile
Re: problems installing
« Reply #28 on: February 13, 2014, 10:03:29 PM »
Maybe it was a sign.......  ??? ???


Now I wonder what Jedi posted!

VastOne

  •      v-ger
  • Posts: 3948
    • View Profile
    • VSIDO Community
Re: problems installing
« Reply #29 on: February 13, 2014, 11:39:27 PM »
^ It wasn't pretty... and said a whole lot!   ::)
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO