Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone!
Some days before I tried to install android X86 6.0 to a 8GB partition. I the installer, I selected to edit my partitions and selected gpt. I made a partition to install it. I didn't nailed it, and when trying to boot back to Deepin (my primary OS), BIOS showed me the boot menu, I don't knew why. I selected to boot into my hard drive, but after 3 seconds I was back to the boot menu. I guess I mixed up gpt with... something else? I tried to use boot repair, but this shows up all the time:
Code:
Filesystem repair requires to unmount partitions. Please close all your programs. Then close this window.
And is quite annoying, because it comes up again after half a munite. I tried closing all my programs, but that didn't help.
I managed to make Boot-repair work in some way, but it says that the EFI partition was deleted, and now I have to create one at the start of the disk, but windows is there in ntfs and can't be moved.
Android really belongs in a virtual machine anyway. I know that won't help you right now, but for the future... As for your current problem, I've never really used any Ubuntu, and I've never used UEFI, so I'm little help otherwise.
Actually I tried to install it in Virtualbox, but the mouse was recognized as touch by Android, so there wasn't any mouse pointer. Actually I think that my HDD hoax happened when installing Android X86, because at the partition management tool I selected GPT. Also Deepin 15 is now based on Debian, looks like the moderator did wrong and added the Ubuntu icon. Anyway, if you don't know much about UEFI it's OK, after all no one knows everything . But if you could ask somebody else to help me, that would realy realy help!
For one, VirtualBox has mouse settings you could try changing. Also, how would you feel about a reinstall? I can't see what's going on there, and how your partitions are, and exactly what's corrupted, so you could try a reinstall and see what the installer tries to do in the way of partitioning.
Well, I think anyone can see that I don't know much about vbox :| ... But, I tried installing Lubuntu in free space, and I got this error:
Quote:
The attempt to mount a file system with type vfat in SCSI1 (0,0,0), partition #5 (sda) at /boot/efi failed.
You may resume partitioning from the partitioning menu.
Also, that link of pastebin I provided (http://paste.ubuntu.com/14543926/) says it all (I think) about my HDD and my partitions, it was generated by boot-repair.
Are you able to boot anything now from the hard drive? Your boot repair script shows you are using MBR and that windows 7 is installed using MBR. My understanding is that if you use GPT with windows, you must use UEFI. If you use UEFI, you need a FAT32 partition for EFI at the beginning of the drive. You don't have that which means your systems (windows and Deepin) where not using UEFI/GPT. Selecting GPT with Android was a mistake.
Your output shows Grub in the MBR of sda with correct boot entries for Deepin and windows. At the top of the output, it shows sda5 (Deepin) as an ext4 filesystem, just below that it also shows sda5 as EFI System partition. It shows also that sda3 is a BIOS boot partition which is used with Linux systems using GPT. Have you tried the recommendation at the bottom of the boot repair? I don't use UEFI/GPT so I'm not sure how you would resovle these problems. The link below, under General Principles explains some of the reasons your are having problems.
cd /media
sudo mkdir sda5
sudo mount /dev/sda5 sda5
sudo chroot sda5
su alex
[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
And the output is:
Code:
Legacy boot on HDD
which is bacause there is no /sys/firmware/efi folder in there. Which means I have legacy boot (I guess). But I mixed things up. OMG, can somebody help me?
The info in the boot repair output shows you are using or were using MBR which is what the output you posted from that command indicates. You should not have selected GPT for Android because windows needs UEFI with GPT, at least from everything I've read. You don't want to create an EFI partition, that will complicate things even further. I don't use UEFI myself but I would suggest you turn off anything relating to UEFI in the BIOS and review the information at the link I posted earlier.
To boot a gpt disk in an mbr situation need a partition flagged as bios_grub. The partition doesn't need to be very large, an unformated 2mb parition will work. The partition is where grub-install --force /dev/sda will install the mbr boot code on the gpt disk that the mbr bios can find.
Last edited by colorpurple21859; 01-17-2016 at 09:34 PM.
just run grub-install --force /dev/sda grub will find the 2mb partition. If you get the no efi partition error then grub-install --force --target=i386-pc /dev/sda
Last edited by colorpurple21859; 01-18-2016 at 12:30 PM.
you most likely have grub-efi installed instead of grub-pc, which IMO would indicate that lubuntu was installed in efi mode.
Quote:
I managed to make Boot-repair work in some way, but it says that the EFI partition was deleted, and now I have to create one at the start of the disk, but windows is there in ntfs and can't be moved
I don't think the efi partition has to be first on the hard drive, hard to say since every computer manufacture efi-boot-bios is different. you could try efi mode again if you have room somewhere to create a 200-300mb efi partition, or apt-get install grub-pc to continue on with trying to boot in mbr-bios mode, however I think with apt-get install grub-pc grub-efi will be uninstalled.
Last edited by colorpurple21859; 01-18-2016 at 01:32 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.