I just installed ubuntu 12.04 using a different partition for the /boot (I don't know why exactly I did this, I remembered reading somewhere on the web about this). The thing is that after this operation, the grub is not showing at boot, so the computer is loaded directly into windows.
cfr wrote:So you have a combined EFI/boot partition? That is, you do have a separate /boot (separate from /) but it is identical to your EFI partition?Do you know if that set up can work? That is, can grub use a /boot which is formatted as fat 32?The usual set up, I think, is to mount the efi partition at /boot/efi.
When I buy laptop recently,it already install win7.
I remove D to install ubuntu 12.04 64 bits.
At first I only set partitions like this,and I don't change any other partitions related with win7:
swap 16GB
/ 150GB
But I got this message:
The partition table format in use on your disks normally requires you to create a separate partition for boot loader code.
I'm trying to install /boot in a RAID 1 using 3 TB disks. As the RAID partition do not let you manage partitions than more than 2 TB, CentOS automatically configures the partitions using GPT.
My current machine (HP Proliant ML110 G4) does not support EFI/GPT so it uses MBR to boot the system.
Post title explains it all, here is more info.
I have a server with 3 hard disks, here is the layout:
hard disk 1: /boot and swap partition (DEAD)
hard disk 2: raid1 member
hard disk 3: raid1 member
I installed the boot parition on a separate hard disk because I read somewhere that it was not advised to put the /boot partition inside a software RAID array (which is what I am currently u
So I recovered everything but the system doesn't even boot.Unless you have a separate boot partition, you also need to reinstall the bootloader if you want it to actually boot. Because simply restoring the files doesn't automatically mean that it's bootable.
Can we take a peek at your /etc/fstab ?I think you've the problem I had suspected was going on in that other thread. I think your boot partition is not mounted on /boot at the time you do the upgrade. This will cause the new modules to be installed in the libraries. The new kernel and initrd will be built, and installed to the /boot mount point. Unfortunately, if the b
I'm trying to install F17 on a new HP box with UEFI. My disk layout is
/boot/efi 256M EFI System Partition
2M BIOS Boot
/ 32G EXT4
/sl6 32G EXT4
/home 183G EXT4
On my first install the installer didn't demand a BIOS boot partition, after install it booted to a blank GRUB command line. On the next install it demanded a BIOS Boot partition.
I got a new DELL XPS 8500 with Windows 8. I understand that it has UEFI (as opposed to traditional boot-loading BIOS system).
I installed Ubuntu 12.04 (not realizing that it doesn't work as well with the secure-load/uefi system). I partitioned my solid state drive so Windows was on one partition, and Ubuntu would be on a new one (sdb7). This always worked with my PREVIOUS computer...
Email this page