GRUB can`t see my second Xubuntu partition
Hello, i hope i created this thread in good place
I have 2 linux Xubuntu 14.04 partitions GRUB shows only one partition, i cannot switch user to the second partition too, but file manager sees it right. In GParted it looks like this: http://s23.postimg.org/igpp2j1jf/Scr...5_19_08_53.png the bigger dev/sda/1 partition is my old one which i want to boot with GRUB and use it and /dev/sda/6 is new which i need to remove But i cannot do this because GRUB doesn`t see /dev/sda/1, so what can i do? My GRUB version is 2.02~beta2-9ubuntu1, i tried to update it with sudo update-grub but no effects. Thanks for your effort |
Try running: sudo os-prober and watch the output for an entry for sda1 then run sudo update-grub. If that doesn't work, google bootinfoscript and go to the site and download and run it then post the output, a results.txt file here.
|
http://ubuntu.pl/forum/viewtopic.php?f=127&t=177301
this is the same thread on other forum, please take look on the codes because the rest is in another language Now my goal is to login to bigger partition and re-install there grub since it`s installed using terminal in new partition but i cannot do this because it can`t connect to the internet by sda1 in terminal |
have you tried chroot from the second install to fix the first install?
|
first install is ok, the problem is that i want to login to first install (dev/sda1) using terminal and re-install GRUB but cannot do this because internet does not work when i use terminal and login within.
Code:
root@kek-G41M-ES2L:/# apt-get install --reinstall grub-pc |
You are able to boot the Xubuntu on sda6 but cannot boot the Xubuntu on sda1, correct? The reason you can't boot the system on sda1 is because you don't have any Grub files on that partition. Since both systems are Xubuntu 14.04, you can simplify the process by simply copying all the files from sda6 /boot/ to the /boot directory on sda1.
Once you have done that and while still booted into sda6, run: sudo update-grub and/or sudo os-prober If you see output for sda1, reboot and you should see an option to boot sda1, select that and if it boots, open a terminal and run: sudo update-grub then since you want to use sda1, run: sudo grub-install /dev/sda while booted into the system on sda1. This should work but it is not a standard method and would only work since you are running two identical systems. |
Thanks, now i know what`s going on
http://s23.postimg.org/igpp2j1jf/Scr...5_19_08_53.png So it llooks like this: I copied boot files and now GRUB shows two options one is Xubuntu and one is Xubuntu /dev/sda1 But both are starting the same profile so i guess i need to change /dev/sda1 mounting point since now it doesn`t has one and do something with `/` mounting point in /dev/sda6. But how can i do it safely? |
The first thing I would do, assuming you are able to boot the Xubuntu on sda6 and what you actually want is to use sda1, is to boot to sda6 which you can do, then create a mount point for sda1 then mount sda1:
Code:
sudo mkdir /mnt/sda1 Code:
sudo mount /dev/sda1 /mnt/sda1 Quote:
|
i`m very sorry i edited post while you was answering
Now when i did sudo mkdir and sudo mount sda1 has mounting point in Code:
/media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a, /mnt/sda1 |
After booting the Xubuntu on sda6, you copied the /boot/grub files to sda1. Is that correct? Did you verify that there was a kernel (vmlinuz file) on sda1 as well as an initrd file there in the boot directory?
Quote:
When you select the entry for sda1, can you boot it? Quote:
Code:
sudo mount /dev/sda1 /mnt/sda1 You could also simply reinstall Grub to sda1 but if you do not have a kernel and initrd, that won't help. The Grub files are also in /usr/lib/grub/i386-pc on Xubuntu on either install and you could probably use the chroot method suggested above to install Grub on sda1 and then run sudo update-grub. Using the chroot method is a little more complicated and is explained at the link below: https://help.ubuntu.com/community/Gr...ing#via_ChRoot I guess the important question now is, can you boot sda1? |
Yes files in /dev/sda1 boot folder are the same like in /dev/sda6 and i did update GRUB.
I have two options in GRUB but whatever i choose it loads ``kek`` profile which is /dev/sda6 now when i did Code:
sudo mkdir /mnt/sda1 Code:
sudo mount /dev/sda1 /mnt/sda1 Code:
/media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a, /mnt/sda1 And this is what i get when i click on these two devices in file manager: http://postimg.org/gallery/36q458sw/ This is the full story: /dev/sda1 was my only system partition which i used at usually and everything was working fine next day i turned on my computer and GRUB doesn`t loaded, it was showing Code:
/boot/grub/i386-pc/normal. mod not found And after it i was only able to boot new /dev/sda6 partition and it looks like it simply changed mounting point as seen in GParted. Would changing /dev/sda1 to mounting point `/` and /dev/sda6 to another solve problem? |
Open the file manager and go to: /media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a
Look in the /boot directory and verify that you have a grub directory. Also check to see if the other grub files are there. You show the links to the vmlinux and initrd files in the root of sda1 so verify that these files are under the /boot directory here. Also, verify that the normal.mod file is there, probably under /boot/grub/i386-pc directory. If the files are there run from your bootable Xubuntu on sda6: sudo os-prober - watch the output then run: sudo update-grub - again, watch the output. You should see an entry for sda1 if all the correct files have been verified to be on sda1. After doing this, re-boot the computer and look for an entry for sda1. If the update-grub added an sda1 entry, it should be there and boot. I don't know what happened to your normal.mod file but it won't boot without it. Quote:
|
I already did that and checked files before and one GRUB option is Xubuntu, second is Xubuntu /dev/sda/1.
Both are loading the same (new) profile Code:
kek@kek-G41M-ES2L:~$ sudo os-prober |
The os-prober output in your last post shows an entry for sda1 is detected. What happens when you move the arrow key down to that entry on the boot menu to select and hit Enter? Does it boot? So you have checked sda1 and you have the /boot/grub and i386-pc directories with the vmlinuz and initrd files, correct. Is there a normal.mod file in i386-pc?
Quote:
/media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a and delete the grub.cfg file there then do chroot as shown below. F first from a terminal run: df -h to see if /media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a is mounted. If it is, unmount it and run: Code:
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i //media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a$i; done Code:
sudo chroot /media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a The standard method of reinstalling grub, specifically for your partition is below. This installs Grub to the master boot record pointing to the Grub files on sda1. If you are missing a vmlinuz or initrd file it won't work. The problem with this is that if it fails, your machine is un-bootable. If you still have the installation medium you can re-install to sda6 with a similar command by replacing the UUID below for sda with the correct UUID for sda6: Quote:
|
Yes as i said i already checked these files and normal.mod is there.
Grub.cfg is in Code:
/media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a/boot/grub/ Code:
kek@kek-G41M-ES2L:~$ df -h Code:
kek@kek-G41M-ES2L:~$ for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i //media/kek/90f4d874-9e8d-44f1-92a1-1db889e0476a$i; done so i dont know if im ready to do next steps |
All times are GMT -5. The time now is 08:15 AM. |