I was lured here by VastOne's copious detailed posts on #! forums - I feel compelled to experience VO's nix spin. But I am having problems. I have tried installing 64 bit from usb drive (which live boots fine, though never got either 32 or 64 to work in VirtualBox). After first formatting both HDD and SSD in my laptop (HP Envy 4) using Gparted, I then installed, making sure to put / and * on the SSD. I have tried several times but booting sans USB always gives "no bootable disks" message.
More info: this notebook has just now come from a romp through #!, MSW7, Lubuntu, and now VSIDO. I chose Lubuntu because I have a strict IT department at work who does not want either #!, VSIDO, or other downstream OS's but will permit the bigger "primary" linux distros (they have a short list) and I was building a #! like Openbox session to load at work. This is only important because I have the feeling the Ubuntu installer may do something with the MBR, grub, or something else.
I am not sure if I need to fix MBR or grub, or if that is even relevant in this instance.
Any advices?
First of all superwow, welcome to VSIDO!
Im assuming that when you installed you selected to install grub to your ssd? MAke sure the ssd is set as your first bootable device and not the other drive.
Hi superwow.. welcome to the forum and thank you for the kind words and for giving VSIDO a tryout...
What option did you choose for grub when you installed VSIDO? To put it on the MBR or it's own drive?
Since you already have a grub, I would install VSIDO and tell it to install grub to it's own partition (an option) and then go into your existing grub and do a grub-update and it should find it...
First, make sure your USB is good by downloading, and then creating the LiveUSB, making sure to follow these directions; http://vsido.org/index.php?topic=10.msg14#msg14 (http://vsido.org/index.php?topic=10.msg14#msg14)
It sounds as if you've already successfully gotten this far! Going through with what I've written below, will ENSURE that you've disabled and irretrievably lost the ability to boot your system in UEFI/Secure Boot mode, and unless you have a good recovery DVD or backup of some kind, you will not easily be able to fix this. (if at all!!! So do the following at your own risk. You've stated you work in an IT dept. so this is "assuming" your knowledge level is probably higher than someone who just bought a Best Buy laptop and is trying Linux for the first time)
Once your sure you've got a good downloaded ISO that is properly dd'd to the USB, I would Live boot and use the gparted tool that comes with the VSIDO installer to totally rebuild the hdd or ssd your going to install VSIDO on. By this, I mean deleting all partitions, creating a new disk using the default setting (msdos) and not GPT. This will make life much simpler and the only drawback to the msdos partitioning scheme, is the 2 TB limit to hdd's. GPT allows for much larger drives. (Only real benefit of it I know of) Yes there are more such as specific block alignment stuff and things that are beyond the scope of this 'hopefully', helpful post.
I would then create three (3) new partitions, one for root (/), and one for home (/home), and one for your swap partition. I usually allow 20 Gb's for the root drive, (though this is huge overkill, I have the space, and I know I'll never fill the root directory by making it this large. I would say a minimum size of 5Gb's for root (/) and if you have the space, at least 10Gb) and using the rest of the drive space for /home and swap. Personally, my feeling on swap is, if you have 8Gb's or more of RAM, the swap is NOT needed. If you do need to create a swap partition, (the VSIDO installer offers both ways, with swap or without swap) use your best judgment for how big you'd like it to be. At this point your physical hdd's/ssd's should be ready for a VSIDO full install. Make note that you can and should install swap to the hdd and not the ssd.
As to not being able to find the installed system at boot, make sure the correct disk is selected in your BIOS as the bootable disk. Other things to check in BIOS would be to insure that "Secure Boot" is disabled, and that the BIOS is set to "Legacy" mode, and not UEFI. (on some machines this is done by ENABLING the "CSM" feature in your BIOS) I'm not 100% certain, but I believe there are issues with a GPT partitioned hdd being 'seen' by Legacy enabled BIOS. (thus the instructions above to delete the current partitions and drives, and start over with the "Default" partition scheme which is msdos, and not GPT)
Remember this is written with me having to "assume" a lot of things about your system. I have successfully done a GPT install on an EFI enabled BIOS laptop. I would not recommend it to anyone at this point in time. If though, in your BIOS, it is trying to find the UEFI boot partition, this would be one reason it is not finding a bootable disk in your system, and why you would need to choose to enable booting in "Legacy" mode. The "Secure Boot" feature in BIOS is 'specifically' designed for booting UEFI/GPT systems and if it is enabled, the system will NOT boot.
Currently UEFI/Secure Boot mode is handled by a small FAT32 partition situated at the beginning of the first bootable drive in a system. In order for VSIDO to be installed, you must be sure you have overwritten this part of the hdd. (ssd) Otherwise, after a fresh install of VSIDO, on reboot your BIOS will first look at the beginning of the disk, see the FAT32 partition with the UEFI information on it, and conclude that there is no 'bootable' drive to start.
All of the above will definitely overwrite and destroy any MBR you have on your laptop! It WILL destroy any of the current OS's you have installed. VSIDO boots using Grub2. The VSIDO installer relies on Remastersys, which in turn depends upon Grub2. There is no getting around this at the time of this writing.
Another thing to note, your strict IT dept. allows 'some' of the bigger 'primary' Linux distros. This would definitely describe VSIDO, (as well as #!) as it is wholly built upon Debian, which to my knowledge is the biggest Linux of them all!
One more thing to note, during the install process it will ask you where you want to install Grub to. If what you've said above is true, then your laptop will ONLY have VSIDO installed, so when choosing where to install Grub2 to, choose the MBR selection.
If you need any further help just let us know. Good luck and I know you'll really enjoy VSIDO...
Thanks to @VastOne, @Jedi, & @lwfitz for the response. To answer a couple of questions,
1) I completely wiped both drives first with gparted. Did this several times from VSIDO and #! USBs. It seems to me this should have wiped out both Windows and Lubuntu with heavy overkill. After wiping, I initiated the installation.
2) In the installation process I placed both / and * on the SSD. I tried placing /home there too, but when I did so, of course, / went a way. My intention is to leave / and /home on the same disk, and then symlink to the 500 gb drive after install. How can I place both / and /home on the same disk, the SSD, using VSIDO installer?
3) Regarding GRUB, this may be where the install fails. I read the VSIDO Installation Guide and there is clearly a GRUB step in it, but I do not recall seeing it during my install. This may be the culprit here.
4) BIOS. I did not actively do anything to BIOS on any of my installs (#!, *buntus, MSW7, VSIDO, etc) but perhaps the *buntu installers can affect it?). I will check.
What I will do is re-download VSIDO & rebuild the USB drive first. And then reinstall with / to SSD and home to the 500 gb HDD and pay attention for a GRUB step. I will report back in after that (and a little time at the beach hehe).
NOTES: my IT department wants only distros that pull sources directly from their approved list of Debian, Ubuntu, Arch, Suse, RHL, and CentOS (seems like there is another but cannot remember, and they are still debating Scientific ?!?!). They said #! was out of the question since it had modified packages and used an old insecure kernel; they recommend a vanilla Openbox Debian install if that's what I want. If I need to I can try that at some point, but I need to romp a bit with VSIDO first. It surprises me they approve *buntu though, what with all the user tracking. After the install I will check the sources list for VSIDO since that is one of the things they will ask me for. They are ok with pulling configuration files from various distros but leaving sources and packages unmodified.
Quoteboth / and *
is "*" your shorthand for swap? that's quite iregular. havnt seen that before. if not, i wonder it that may be the source of your issue.
my suggestion would be KISS [keep it simple stupid]
just a small partition for swap, and leave the rest of the space for the / (root) partition which will contain all else you need without any extra effort on your part.
if that still throws up issues....
When it gets to the point of installing Grub, you'll have (I think) 3 choices. The first one is the one you want to choose. Install Grub to the MBR. Let us know...
Not sure what you are referring to when you say * as a partition... If you just put / and /home on the ssd, you should be good to go with the rest of the install. At that point, the next time you boot into your new install, you can then do whatever you need to the 500Gb hdd.
The sources is the following
## Official Debian Repos ##
deb http://ftp.us.debian.org/debian/ sid main non-free contrib
deb-src http://ftp.us.debian.org/debian/ sid main non-free contrib
## Unofficial Repos ##
deb http://ftp.us.debian.org/debian/ experimental main non-free contrib
deb http://www.deb-multimedia.org sid main non-free
deb http://mozilla.debian.net/ experimental iceweasel-aurora
You could probably comment out the last two and safely pass your IT dept... VSIDO is debian, and not additional repo or packaging
All, thanks again for the comments and help. I have tried a few more times, and sadly no joy. Here's an update with details.
1. BIOS details first: BIOS is set to legacy and Secure Boot is disabled.
2. I tried installing a few more times with the previously burned USB, making sure to actively place /, /home, grub, and MBR (which I referred to as *, because I had just been looking at fstab which uses a * for boot, sorry to confuse). I placed MBR, /, and grub on sdb (my 32 gb SSD). /home is on sda (500gb HDD).
Incidentally, 'Install with Swap' option in the fluxbox menu does nothing, or, tries because it cannot see the on of the disks, usually the swap or the SSD. 'Install VSIDO' lets me install a swap, which I did, a 2.5 gb swap on the SSD.
3. When that did not work, I wiped and recreated the USB on a Mac host. For the record, here are terminal commands for Mac, assuming VSIDO.iso (generic naming) is in ~/Downloads:
diskutil list # run without usb drive inserted
diskutil list # run after usb drive inserted, pick usb drive, for me was /dev/disk1
sudo disutil unmount /dev/disk1
sudo dd if=~/Downloads/VSIDO.iso of=/dev/disk1 bs=1m
# wait a few minutes till done
sudo diskutil unmountDisk /dev/disk1
4. I tried formatting the 2 drives as ext4 and installling per #2 above. No joy. I then tried formatting the 2 drives as fat32. When entering the installation wizard, I then formatted as ext4, adding boot flag and adding grub to sdb. The interesting thing about formatting the disks as fat32, then installing via wizard, is that an xterm popped up that time with grub install IO; based on that, I guess grub install worked. Alas, no joy. Booting back into USB, I ran 'sudo grub-install /dev/sdb' per VO's http://vsido.org/index.php?topic=8.msg12#msg12 (http://vsido.org/index.php?topic=8.msg12#msg12) Grub2Meth post. Also, no joy. Actually, output was 'Path `/boot/grub' is not readable by GRUB on boot. Installation is impossible. Aborting.' I am thinking this is important and reading now on its meaning. As to what next to do, questions remain, so read on....
5. Boot flags (in gparted)? What should the boot flags be on sdb (my 32 gb SSD where / is)? 'boot', 'bios_grub', or 'legacy_grub'? I chose 'boot' but this could be miserably wrong.
Further advice and handholdings are appreciated :D
6. IT: I am not an IT professional. I am a scientist, no formal OS/codewarez trainings. I have nearly always had linux machines at work, which are maintained by government / corporate linux maesters with hallowed policies, am no stranger to the CLI or complex software coding to accomplish data analysis. Architecture & install problems though are out of my comfort zone a tad. In the case of VSIDO, I am guessing IT may be permissive, unless they don't want Sid, or I don't take them enough bacon, kolaches, doughnuts, etc. Their decision will probably be based on minimizing risk to the corporation? or Roll d20?
Back to the fun, what am I missing with this install? This machine has happily hosted various nixes and multiple MSW7 installs with nary a wry look.
If the install seems to be ok and you don't see an error when grub is installing then I would tend to lean towards a bios setting.
I know you said you didnt change anything in the bios except setting it to legacy boot but have you tried manually booting to the ssd? Maybe double check that the drive where grub is installed is set to your first boot option? Maybe boot to a live disc and make sure that you have the boot flag set on your install drive?
Also, on some machines its more than just setting to legacy boot. Double check that theres not a force bios option or anything enabled for windows 8.
Can you remove the secondary drive? This would help to figure out if it is the bios messing you up or if its a software issue. You dont have an external drive connected that it might have installed grub too? Or that its trying to boot too?
@lwfitz I have followed your suggestions (sorry for the delay, work & life are happening) and here's what I've got:
1. Top priority in BIOS was set to Boot from USB. Changing boot order in BIOS, moving Boot OS from Hard Drive up to higher priority over Boot from USB, for both Legacy and EFI sections, does nothing, same error message.
2. This machine never had MSW8 but instead had MSW7. I am not sure if that detail is relevant but I seem to recall reading their pre-OS environs are different. But regarding your MSW8 comment, how would I go about checking the 'force bios' option? <Also, I got the laptop to boot before into #! and also Lubuntu, so, could it have changed without me changing it? say, after a Lubuntu install?>
3. The SSD and HDD are both internal to the notebook and cannot be removed without me disemboweling my laptop, typical HP Ultrabook configuration. There is actually a 500 gb HDD, a 32 gb SSD for the OS, and a non-accessible 32 gb SSD, only visible or accessible from MSW7.
According to the interwebz (Arch, Manjaro, Ubuntu fora), looks like this problem comes up from time to time and lots of head scratching and speculation but without a technical resolution other than to reinstall MSW and then wipe the disk and reinstall nix-of-choice. I may have to resort to that. Or the supergrub option linked in your signature.
And that post was the winner! Please read this entire post before making a decision! Sounds like you have a 64Gb SSD drive of which half is dedicated to Windows 7 being able to boot using UEFI/EFI. This can be overcome, but at the cost of losing the ability to get Windows 7 installed again. That non-accessible 32Gb SSD has the small EFI boot sector I mentioned in my earlier/first post. This will not be overcome without eliminating it (and possibly even deleting it as one of the "boot options" in BIOS, as there maybe a 'pointer' to it in the BIOS.)
This is not as scary as it sounds. I have had this particular problem myself, and as you report, is fairly common on some of the web forums.
(If indeed you are ready to forsake, forever, (on this particular laptop) Windows 7, there is a pretty simple solution. You'll need to create an ISO from the Gparted Partition utility found here (http://sourceforge.net/projects/gparted/files/gparted-live-stable/0.17.0-4/gparted-live-0.17.0-4-amd64.iso/download). Create a liveUSB image with it basically the same as you did with the VSIDO ISO image.)
Remember this same tool is already available via the VSIDO LiveUSB you've already created, so the above is probably not needed, unless, after this attempt it still fails.
Once booted into the VSIDO LiveUSB, open a terminal and "sudo su" to get to a 'root' prompt. (from the Live Session, I don't think you'll need a password for that ability) Type in 'gparted'. Peruse the available drives by clicking on the drop down menu at the top right of the Gparted utility. You "SHOULD" see that pesky Windows 7 32Gb portion of the SSD, and from there, be able to delete it. If not, you may also have to (from the same root prompt in terminal) type in "disk-manager" and put a check mark next to the hidden 32Gb partition to get it to appear in Gparted. WARNING!(THIS WILL RESULT IN YOU "NOT" BEING ABLE TO REINSTALL WINDOWS 7 AFAIK!)WARNING! (perhaps a backup of that partition using a tool such as fsarchiver would eliminate this issue, but I never went that far, as I was never going to use Windows again anyway. There are some good docs here in the "HowTo" section concerning how to do this with the 'fsarchiver' tool)
Once you've done this little trick, you should be able to continue with VSIDO with no issues. With the advent of UEFI/EFI in some of todays newer computers, this is an annoyance to anyone trying to install Linux. MS's way of saying "No *%$^&&#@ way are you ever going to install any other OS than what WE deem is needed by you, for your computer.
That is all there is to it, and once you have eliminated that drive using a partitioning tool, you should be good to go.
Pay heed to the warnings and cautionary statements above as removing that 32Gb's of space removes the EFI info that is trying to make your laptop boot first. I have no idea why #! or Lubuntu wouldn't have thrown this same issue at you as well. That is definitely mysterious to me and a little troubling. I tend to never do things half-way, and would not hesitate to 'break' the laptop by destroying that nasty little 32Gb Windows partition. (that is what it is) It is hard for me to imagine HP putting in two separate 32Gb SSD's, thus my above statement about it being one large 64Gb SSD. SO, that said, I'm once again "assuming" something about your laptop that is just that; an assumption. It is a fairly common practice today for manufacturers to setup their machines like this in order to be able to label them with the Windows Compatibility stickers that MS requires for Windows 7 or 8 pc's.
Also just remember this little analogy about following guidance off of the Internet. Today if you have a serious illness, you go to a licensed doctor for a diagnosis and, hopefully, a cure. The Internet is kind of like the tribal shaman or witch doctor, who blows some smoke on you that smells suspicious, gives you a mixture of an awful tasting herbal/weed/dirt substance to swallow, and tells you your cured. Two weeks later your dead, or getting something amputated! OR YOUR CURED! The wonderful world of the digital age. It is wise to pick and choose your sources for help. We try here at the VSIDO forums to always be thorough about advising users. Unfortunately, we cannot know every detail about your PC and when we tell you to do something to it, it may just start smoking, or indeed, even catch on fire! I'm just telling you in a round-about way to carefully consider anything you do to your personal equipment on the advice of someone you've never met or heard of!
pesky uefi complicating things. whatever happened to the good old days of just root, swap, and install grub to the mbr*. ^_^
*unless it was legacy grub, before we had update-grub, and you had other os u wanted to boot too. in which case you would want to install grub to the root partition "/"
QuoteNOTES: my IT department wants only distros that pull sources directly from their approved list of Debian, Ubuntu, Arch, Suse, RHL, and CentOS (seems like there is another but cannot remember, and they are still debating Scientific ?!?!). They said #! was out of the question since it had modified packages and used an old insecure kernel; they recommend a vanilla Openbox Debian install if that's what I want. If I need to I can try that at some point, but I need to romp a bit with VSIDO first. It surprises me they approve *buntu though, what with all the user tracking. After the install I will check the sources list for VSIDO since that is one of the things they will ask me for. They are ok with pulling configuration files from various distros but leaving sources and packages unmodified.
Your IT doesn't allow #! but they allow Arch? That's downright comical. VSIDO I can understand since Sid is, by Debian's own admission, unstable so it wouldn't pass ant QA/QC you have going on.
Back on topic - I looked up the specs for the HP Envy 4 and it lists the drives as 500gb and 32gb. Hopefully jedi is correct and that 32gb Win7 drive is a hidden partition you can quickly deal with.
Also this from lwfitz -
QuoteAlso, on some machines its more than just setting to legacy boot. Double check that theres not a force bios option or anything enabled for windows 8.
be sure to double check that; I ran into that checking out a relative's new computer - doing a dummy install just to see what would be required.
^ exactly.
Some new machines that came with windows 8 preinstalled have specific settings in the bios for Windows 8 compatibility or abilities. I'm on Uefi boards and boot with no problem.
If other distros are installing and booting ok then maybe grub is getting installed in the wrong place? Maybe it's installing to /dev/sda but your ssd isn't being labeled as sda?
Also, you could download a super grub disk and use that disk to boot into vsido. From there you can find where grub is installed and make sure it's installed to the correct drive.
Btw Jedi, great post.
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.
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. :)
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:
+ 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/ (http://bootinfoscript.sourceforge.net/) so downloaded and ran the script. Here is my output for now:
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 (http://ubuntuforums.org/showthread.php?t=1736409) and http://ubuntuforums.org/showthread.php?t=1719851&page=6 (http://ubuntuforums.org/showthread.php?t=1719851&page=6)).
Once again thanks for the feedback you have given so far.
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.
Quote from: jediAgain, 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.
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 (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!
Great news superwow and thank you all who assisted and developed an incredible installation scenario and fix
Fantastc superwow! Glad things got worked out for you.
Good job superwow! Way to stick with it. Glad you got it installed finally. Hopefully all this will help another user in the future!
Quote from: lwfitz on February 09, 2014, 05:36:19 AM
Quote from: jediAgain, 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:
#find the swap partition
TARGETSWAP=`fdisk -l | grep swap | awk '{print $1}' | cut -d "/" -f3`On a gpt-system, the output will be this:
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:
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.
Wow, my mistake. Thanks for the correction ew
Sorry posted after I noticed it was locked. Post removed...
Perhaps I should be taking a break...
Unlocked... It had to have been some mistake that it was locked in the first place
Maybe it was a sign....... ??? ???
Now I wonder what Jedi posted!
^ It wasn't pretty... and said a whole lot! ::)
Oh boy, thats what I figured...... I love you Jedi :D
My guess is he said what I wanted too?
@ew that confirms at least part of my install experience. When selecting Install (without swap) the installer would go through the steps of installing (although it would never boot). When selecting Install with Swap, nothing would happen.
So, what I wound up doing was use a tool from the Ubuntu peoples, which worked. I have a philosophical issue using Ubuntu tools though because 1) their CLA and licensing is contradictory to many FOSS principles and good old Debian, the community driven distro, 2) some of their corporate practices. (Interesting topic which is apparently being hammered out over on the systemd/upstart thread: my vote.... systemd ... I agree with all the upstart-detractors. For the record though, I am not a Canonical hater: they contribute a good deal, just, also tend to hijack and brainwash ...)
Are you are saying I could accomplish the install without using Boot-Repair, the Ubuntu tool? I can tell part of Boot-Repair is actually just bootinfoscript, but I just don't know the rest of the magic to get the install to work without using their tool. What's the remaining part?
First of all superwow, very nice job getting it installed! That is an achievment, no matter how you ended up doing so. Kudos on a great job, and way to stick with it. No wonder your IT dept. likes you so well! After 30 years in the industry, I wish all my users had been just like you!
This was found in my notes from quite a while back. (maybe a year?)
The choice basically boils down to this:
If using GRUB legacy as the bootloader, one must use MBR.
To dual-boot with Windows (both 32-bit and 64-bit) using Legacy BIOS, one must use MBR.
To dual-boot Windows 64-bit using UEFI instead of BIOS, one must use GPT.
If none of the above apply, choose freely between GPT and MBR. Since GPT is more modern, it is recommended in this case.
It is recommended to always use GPT for UEFI boot as some UEFI firmwares do not allow UEFI-MBR boot. This is critical to take note of!
I believe this was something I found on the Arch-Wiki site...
@ew! If you bothered to read any of the posts in their entirety, you would have observed the following;
Quote from: jedi
snip;
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"!
snip;
By the way, in all the reading I've done and from personal experience, GPT is the best partitioning scheme 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.
snip;
Linux should have no problems dual booting with Windows, so this is indeed puzzling.
snip;
After the user stated his aprx. knowledge level with Linux, I decided the best course of action was to do as I posted. I stand by those posts. This is not the first time you've "trolled" here, (ew) and as a Moderator on this site I will not tolerate any more of it! It is absurd and not the place for it. If you want to point out errors in a post, be courteous and PM whoever is making the error so it can be cleared up without trying to sound like your the "end all, be all" guru of Linux. Your not! None of us here claim to be...
Calling someone out as a liar,
Quote from: ew
Not true. I have no issues installing VSIDO on gpt-disks.
helps no one and is insulting to the extreme.
As to Grub2 installing to an EFI partition, maybe so, maybe not, depending on your level of expertise and resolve. Definitely not for the faint of heart, or the inexperienced user, which is why this statement was also in one of the above posts;
Quote from: jedi
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.
Typically this EFI partition is "hidden" from the user, and even with the 'right' tools, can be difficult to work with. For the record, I've never heard of Grub(2) even knowing what EFI is, much less booting a hidden FAT32 partition! I'm no guru so I'll admit I'm not familiar with this. For it to boot an EFI partition it has to be grub-efi-amd64. That has always been my understanding, and until shown otherwise, I'd not tell someone differently. Grub-pc and Grub-efi-amd64 are two different beasts all together. Apples and Oranges. As to installing "swap" to a GPT partitioned disk, never happen! Period. Indeed, Grub-Legacy will not even see a GPT partitioned drive.
Again, in the future should you decide to be so good as to help a user here, that would be great! Don't come in contradicting posts after they've been resolved. As I said, if one of us makes a mistake trying to help someone, or our information is patently wrong, a simple PM to the user (the one trying to help) to help them correct their information, would be a kindness to the one giving their time to help someone troubleshoot an issue. It is not our policy to try to purposefully hose someones computer.
Thank-you,
jedi
Here is my take on this...
Several people involved with several means of resolving it and then documenting it...
So far it looks as if superwow, lwfitz, ew and jedi have all defeated uefi!
This is what I want to see!
^ Thats what really matters!
I should also note that my post wasnt completely clear on some points that were clear in my head....... but apparently nobody can read my mind. I am quite clear that VSIDO, or Linux in general, will install on both MBR and GPT.
The point of my post was that if he wanted to dual boot Windows 7/VSIDO on that machine using legacy boot (NOT UEFI) and install with the VSIDO installer then my experience is that a format and change to MBR would be necessary.
That is strictly my experience with the three UEFI boards that I am currently installed on. Nothing more. And lets be 100% clear, I have no doubt that I will post something else in the future that and then Ill find out I was mistaken :D
Now back on topic...... Maybe someone ( hint... hint... ew...) could take the time to creat a howto for setting up EFI boot..... just an idea ;D
^ Most excellent idea!
I think Jedi should be very careful "calling me out as a liar", just because he`s probably not been able to install Vsido to a gpt-disk himself. I have done it, and it`s no problem at all. I did it the first time a long time ago by a workaround where I "fooled" the installer, and I`ve done it now, by fixing the installer, so that I don`t need to workaround it anymore. But, remember, I said to a gpt-disk, I didn`t say that I installed it to efi-boot. As there is no need to efi-boot just because there is a excisting efi-partition. A gpt-disk has the capability to bios-boot, and if Jedi isn`t aware of that, he should educate himself. EFI depends on GPT, but GPT doesn`t depend on EFI.
Superwow is confirming my claim that the non-swap installer completes the installation to a gpt-disk, but it wouldn`t boot for him. Well, that could be because he doesn`t have a bios-boot partition. This partition isn`t possible to create during the install, but I`ve got this partition from other installs that lets me create it. Read about the partition here: http://askubuntu.com/questions/132843/why-do-i-need-to-create-a-bios-grub-partition-when-i-install-12-04 (http://askubuntu.com/questions/132843/why-do-i-need-to-create-a-bios-grub-partition-when-i-install-12-04)
As to why the swap-installer fails on the initial hdd-detection is as I said before, because fdisk doesn`t support gpt. The installer needs to use blkid instead. But simply replacing "fdisk -l" with "blkid" will give a uotput that leads to swap not being properly automounted in FSTAB. As the output will be "sda x:" instead of just "sda x" Therfore a little modifying of this line in the swap installer is needed:
#find the swap partition
TARGETSWAP=`fdisk -l | grep swap | awk '{print $1}' | cut -d "/" -f3`
should be changed to:
#find the swap partition
TARGETSWAP=`blkid | grep swap | awk '{print $1}' | cut -d ":" -f1 | cut -d "/" -f3`
Finally. I never lie. And I don`t appreciate Jedi "calling me out as a liar" or make outrageous claims about me throlling, just because I disagree with him. I`m 100% correct, and I have no issues installing VSIDO to a gpt-disk. Jedi is a little to full of himself, and that`s ok when he can back it up by knowledge or skills, but sorry to say that it`s not the case in this topic, and I guess that`s what bugs him. Someone knowing more about something than he does.
Here is another Debian-distro that installs on GPT. Both the swap and non-swap installer works fine with GPT. How I know? I`ve created and tested the ISO myself, and if I make it work right ootb and Jedi doesn`t, then he clearly has to do something wrong. Because I`m no linux-guru and if I can make it work, then anyone that`s at a medium skill-level should be able to do the same. It`s a Crunchbang/Sid-mod. 64-bit. Try it.
https://copy.com/CskeNfZiU74z (https://copy.com/CskeNfZiU74z)
^ Do you not know how to PM? I am disturbed by this need you have to attack jedi in superwow's thread (and every time you post here) it is pathetic
I am going to allow jedi to handle this and your special needs
Topic is now locked. VasyOne please feel free to override me but I don't see this moving forward in any way that might be helpful.
So much for civilized and tolerable forum behavior from this fella. Pathetic is exactly right. Trolling is obviously an enchanting past-time for this guy. Nothing here that needs any further handling.
Another post of that nature and tone, and I think it is quite obvious what will happen. A PM has been sent to him, and hopefully this kind of vitriol from this user can be avoided in public posting areas in the future.
Thanks guys...