planetwatt.com
Help and Support => Archives => wattOS R10 => Topic started by: berliner on October 18, 2016, 08:24:48 AM
-
I have tried it now 4 times.
When it comes to the installation of Grub, the installer crashes and says "installation of Grub in target failed".
The Toshiba Satellite Laptop is Uefi and I have Sparky Linux and 2 Mint-Distros installed on it. They all use the same installer as wattOS and it worked fine.
I selected sda as place for the grub -- it failed.
I selected sda1 as place for the grub, which is the Efi-boot-partition -- it failed.
I selected sda5 as place for the grub, which is the partition where the root of whatOS R10 is installed -- it failed. ( In Ubuntu wiki about installation they say that it is possible to install the grub into the PBR of the partition where the distro is installed (where the mount point / is) and the main distro which has it's grub in the Uefi-boot-partition must be updated , then the multi-boot-menu will let you select the new installed distro ). This failed too.
Now I have no clue how to install whatOS on my laptop. Maybe you can help ?
-
berliner, I know nothing about UEFI, so I can't really help...sorry. I do wonder though...
Biff said that if a user puts checkmarks on "Install updates" and "Install 3rd party software" during the installation, it can cause the installer to crash. The 3rd party software is already installed, and it's recommended to install updates after the installation.
So...just in case you have checked those two options, you might try it without putting the checkmarks on them.
This is just a wild guess on my part though.
-
Dan, I will try it.
I always check these boxes because it is recommended everywhere. I didn't know it is not recommended with whatOS.
Edit: Tried it but failed.
In the end, the laptop did not boot anymore. Strange messages appeared instead of the boot-menu.
Even the boot-repair live-usb-stick did not boot. The laptop did not boot from the harddrive nor from usb-stick.
While experimenting with boot options in the Bios, suddenly the boot-repair-live-distro loaded.
What a luck.
After it did it's normal automatic boot-repair routine, the laptop booted.
It even offered to boot whatOS R10, which was never installed properly.
No wonder that the booting is different from normal because it starts with messages running over the screen. Line after line and mostly it checks the lines with an "Ok".
I think it is listing all it is doing at boot.
Finally the login screen of whatOS appeared and the login worked.
What can I say ?
The grub-menu looks different from normal.
It shows Linux Mint Mate now which wasn't there before this mess. And strange enough, it does boot. Before the mess I had Mint Xfce installed which worked fine, now it is gone and Mate is there.
I have no clue what happened, everything is screwed up now.
Somehow I have the feeling, that I will wipe the harddrive and install one of the distros which have worked before on the laptop.
Distros like LMDE2 or MInt Xfce or Sparky.
Then later on, when maybe there is a new version of whatOS which hopefully will install, trying it then again with whatOS.
Good thing: I saved all my personal files before all the mess started to happen.
Sorry to say, but right now I am frustrated. Hours of installing and then the fear that booting is not possible anymore.
I must get rest to recover from this.
-
berliner,
I'm so sorry. You have my utmost apology for what you've experienced. I can only imagine what frustration you're feeling.
I've learned a lesson from this; in that, I will no longer offer advice in an area in which I'm unsure. Please forgive me if what I suggested is the cause of your problems.
-
Dan,
although I am not an expert, it is obvious to me that your advice did not cause the mess.
Why ?
Because I tried about 5 or 6 times to install , then listened to your advice and tried it about 3 or 4 times with different Bios settings.
The installer crashed each time when trying to install the grub to the efi-boot-partition.
Has absolutely nothing to do with your advice.
From what I have read in forums and wiki's it has to do with my laptop, with the Bios, with settings there, with the hardware etc.
I read the relevant Ubuntu-wiki tutorials and explanations about Uefi-boot and installation of Ubuntu distros.
On some Laptops like Acer, the user has to set exactly the opposite Bios options than other Laptops.
And they warn about damaging the uefi-partition and the grub there. It happens not only to me, it has happened to many users.
I am not able to find the cause in my case, but your advice was never the cause, you can trust me in this.
-
A new day.
I downloaded Lubuntu 16.10 , the brand new distro.
Used the mint-stick app on my PC in whatOS to copy the iso to the USB-stick.
Installed Lubuntu 16.10 on my laptop from that USB-stick ... no errors, no installer-crash.
I write this comment from my laptop Lubuntu 16.10 and am happy.
My guess: something in the whatOS R10 iso is broken which causes the crash of the installer on my laptop.
-
Thank you for the kind words and understanding berliner.
Again, I'm sorry for all of the trouble, but I'm glad you're able to use the computer again. :)
-
Flagged for Biff to look at as Owner of WattOS re ISO (moderators do not remove )
A new day.
I downloaded Lubuntu 16.10 , the brand new distro.
Used the mint-stick app on my PC in whatOS to copy the iso to the USB-stick.
Installed Lubuntu 16.10 on my laptop from that USB-stick ... no errors, no installer-crash.
I write this comment from my laptop Lubuntu 16.10 and am happy.
My guess: something in the whatOS R10 iso is broken which causes the crash of the installer on my laptop.
-
Thanks for flagging the thread.
Today I downloaded R10 anew, checked Md5 and put the iso on a live-usb-stick via multi-system.
The first installation on my laptop failed again.
This time I did not check the "download of third party software" and I didn't check the download of release something during installation.
I selected sda1 as target for the grub.
Installation of GRUB failed
The package grub-efi-amd64-signed could not be installed in target. Without the GRUB-bootloader the installed system will not boot
(not exactly this text, I translated it from german)
Next try:
I did not select "Other" in the installer but "install beside existing OS", so the installer has to find the efi-boot-partition by itself and install the grub2 there.
It failed again.
The error-message says:
Installation of GRUB failed
The package grub-efi-amd64-signed could not be installed in target. Without the GRUB-bootloader the installed system will not boot
After shutdown and removing of the live-usb-stick, the booting of the laptop brought the old grub-menu. I selected the Lubuntu 10.0 and there I put "sudo update-grub" into the terminal.
After restarting the laptop the 2 wattOS appeared in the grub-menu screen.
I selected the first one and wattOS started to load but it gave many messages on the screen ... the whole procedure what it loads and then "OK" in green.
But after that show the login-screen of wattOS appeared , of course the cursor did not work, so I had to unplug the usb-mouse and plug again, then the curser worked and I could login to wattOS.
Since wattOS R10 now is installed and there seems no solution for the problem, I would be interested in knowing how to stop the boot-show with all the messages on the screen.
I guess I have to tweak some settings somewhere in the root-files ?
-
# you can turn off the boot messages
# by editing the file /etc/default/grub
# make a copy BEFORE editing
# in terminal
cd /etc/default
less grub
# if there is a line that looks like:
GRUB_CMDLINE_LINUX_DEFAULT=""
# you will need to be root to edit it
sudo -s
<enter password>
# make a copy of grub
cp grub grub.bak
# edit grub (I use vi)
vi grub
# add "quiet" to the setting as:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
# save changes, exit vi, and update grub
update-grub
# then reboot
reboot
# did it work?
-
Thanks billwho.
In etc/default/grub the relevant line says:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"I removed the blank and the word "splash", saved it , updated grub and rebooted, but the boot messages are still there.
-
In the grub boot list (not the /etc/default/grub file):
what is the default system boot?
Is it WattOS or Lubuntu?
If Lubuntu then start Lubuntu and check its /etc/default/grub file.
It is not necessary to remove 'splash', only to have 'quiet' in the string.
If 'quiet' is not in the Lubuntu /etc/default/grub file, add and reboot.
It is the default system boot grub file that controls 'quiet' or noisy.
-
I don't know where to find the "boot list".
Default OS booting is Lubuntu because wattOS failed to install or update the grub into the Uefi-boot-partition.
According to your advice I checked the etc/default/grub in Lubuntu. As expected , it has the "quiet splash" written there, otherwise Lubuntu would show the boot-messages too, but it never did.
I made "sudo update-grub" in the Lubuntu, then restarted the laptop and selected wattOS to boot and now the boot-messages are gone.
I don't know why, but the problem with the boot-messages is solved now.
Thanks, billwho, for your help.
-
Since default OS booting is Lubuntu
That is where you needed to do the update-grub
And since Lubuntu's /etc/default/grub file was quiet
You now successfully quieted WattOS :)
-
berliner, please edit your thread title. Add solved to it. :)
-
blaze,
I don't consider the problem solved because the installer is not able to install the grub into the efi-boot-partition.
Something with the installer is wrong.
The Lubuntu 16.10 installer didn't fail to install the grub. Thus something in that installer is right which isn't right in the wattOS installer.
Ok, maybe I am wrong on this and the installer is ok but my laptop is the culprit, but why isn't it the culprit with Lubuntu ?
I have no answer for this.
-
Sorry, me being sloppy. :-[
-
Ok, this is quite a weird one. Just a couple of questions since I am very curious. I find the install process very fascinating, that is why I am asking. :)
berliner, in post #8 you say that you choose to install grub to sda1. Why? Grub normally should be installed to sda. Did you ever try to dd the iso to usb? (It is in my experience the best method.) Is it possible to turn off Uefi in BIOS and just use Legacy mode?
-
blaze,
the laptop has a Uefi boot partition on sda1.
Therefore I select sda1 as target for the grub2. Everywhere I read about uefi, it says that grub must be installed into the uefi-partition.
I let this rest now. I am too frustrated to invest more time into it.
Other distros installed without errors and I am using them.
-
Ok, thanks for the answer. :)
-
blaze,
I tried it again.
Made a new USB-live-stick with dd , installed it on my laptop and did not change anything, I let it install grub2 to sda as suggested by the installer.
Result ?
The installer crashed.
I give up on this and thank you for your help.
-
Thank you for trying once again berliner. Even if the result were :( Now I know that I have to read up a bit on this Uefi stuff.
-
blaze,
I went 1 step further in this mystery.
On the german ubuntuusers.wiki I found this article
https://wiki.ubuntuusers.de/EFI_USB-Stick/#ISO-entpacken (https://wiki.ubuntuusers.de/EFI_USB-Stick/#ISO-entpacken)
It describes how to create a live-usb-stick without using tools.
In short:
1. Format an USB-stick with vfat32
2. Download your desktop-amd64.iso
3. Unzip the iso into a folder
4. Select "show hidden files" in your file-manager (only on linux OS necessary)
5. Copy the whole content of the folder (point 3) to the USB-stick.
Ready.
Now the USB-stick can be used as live-system.
I did all as described, the USB-stick is booted in the laptop.
When I select "try osWatt10 without installing it", I am getting the following error-messages on my screen:
BusyBox v1.22.1 Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) mount: mounting /dev/loop0 on //filesystem.squashfs failed: No such device
Can not mount dev/loop0 (cdrom/casper/filesystem.squashfs) on //filesystem.squashfs
That is all.
The cursor blinks forever, nothing happens.
So I hope somebody understands that I will not use wattOS anymore. Cost me so much time, while other OS like Peppermint-7 or Lubuntu or Xubuntu or Linux Mint installed on exactly the same laptop without producing any errors or crashes.
-
I have flagged this with Biff and hopefully he should be able to get online soon and solve it for you
-
Thank you cheiron.
Since I am the only one with this problem, I have the impression that the problem is my laptop.
Something there with the harddrive, with the efi-partition, with the efi-bootmanager.
But then I think: Why does Lubuntu, Xubuntu, Peppermint-7 and Mint install without errors and only wattOS fails to install grub into the efi-partition ?
It is a mystery to me.
-
This is why i have flagged it to Biff, berliner!
As he makes the OS in person, he should be able to spot something the other members here that have tried to help possibly overlooked.
Please bear with us though, Biff has a manic work schedule and does try and get on as often as he can.
-
No problem, cheiron.
I have gone a bit further on this.
I decided to let the installer delete everything on the hard-drive of the laptop in order to only install the live-usb-OS.
In this case the installer is able to create the necessary efi-boot-partition by itself.
The installer grabs the whole harddrive and creates only 3 partitions.
sda1 the efi-system-partition where grub must be installed
sda2 the root-partition of the OS
sda3 swap-partition
1. Made a brand new wattOS R10 USB-live stick with dd
Result: Installer crashed as usual, was not able to install grub into efi-systempartition.
2. Made a custom-distro with Pinguybuilder from my Peppermint-7 OS installation on my PC and made a live custom-USB-stick from it and installed on my laptop.
Result: Installer crashed. Was not able to install grub.
3. Made a live-usb-stick from Peppermint-7 iso and installed it on my laptop.
Result: Runs through without error. Installed grub into efi-boot-partition. Perfect.
At this point it is obvious that something on wattOS R10-iso is broken.
Same error occurs with my custom-OS, built with Pinguybuilder.
Only the standard Peppermint-7 iso, downloaded from their website, installs without crash, without error.
Same applies to Lubuntu 16.10, to Xubuntu and Mint-distros. They all do not crash, they all install grub into the efi-partition.
Now I will rest until biff finds time.
-
same problem here installing R10 to my Lenovo YOGA3 I7 14" ...GRUB2 install crashed if I use my UEFI sda2 partition, same as I tried to install to sda...or trying to install to another USB stick
of course "berliner" ist right...all my other systems installed by stick ISO on YOGA3 are running perfect, like Ubuntu17 or Mint18 or LXLE or Manjaro17 well running at all...
I talked to "blaze" days before...hope somebody is a GURU here and online before XMAS...
happy holidays...dear friends(!) ;)
-
think...it's an unexpected christmas gift...did a test run using ubuntu boot repair stick/CD from YannUbuntu (https://sourceforge.net/projects/boot-repair-cd/) and tried my dead R10 WATT OS partition, ext4 ....and it really works perfect after doing. thousand thanks Santa(!) ::)
-
Why not install the WattOS R9 ? It is LTS and will be updated until 2019.
-
I am happy for you Ginnie ...
Microwatt resurrected my eeepc 1001px without problems... more light and more performant than manjaro i3 or sparkylinux openbox ...
-
Congratulations ginnie! :)