You are not logged in.
I'm using GPT partitioning and recently it came to it that the system had updated several packages, including GRUB, Linux kernel. I also installed Fedora 17, which is now gone. It has created an additional 2 MB partition with a bios_grub flag. I deleted it since it was creating a conflict in the partition table with incorrectly set sectors and etc.
Since the installation of Fedora 17, ArchLinux stopped booting via UEFI - "no OS found" type of BIOS error. I tried to create new EFI records with efibootmgr, but those don't work just as well. Lastly, I tried to boot UEFI shell from a USB drive and everything was working, but it could not open any filesystems on disk, only on the USB.
Before that, I was booting it as EFIstub, meaning no GRUB or etc. involved, straight to the vmlinuz-linux.efi...
It doesn't seem to be a kernel problem, since I can successfully boot the system via GRUB command line booted with UEFI from a USB. The problem however seems to be in partitioning or something like that.
What could be the problem and how do I solve it?
gdisk output:
ernestas ~ $ sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1250263728 sectors, 596.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 61C6803E-72D9-4733-A013-90F50584B576
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1250263694
Partitions will be aligned on 2048-sector boundaries
Total free space is 131693 sectors (64.3 MiB)
Number Start (sector) End (sector) Size Code Name
1 206848 309247 50.0 MiB 8300 Linux filesystem
3 1229780992 1250181119 9.7 GiB 0700 Linux filesystem
4 2048 206847 100.0 MiB EF00 Microsoft basic data
5 38066176 1229766655 568.2 GiB 8300 Linux filesystem
6 17672192 38057983 9.7 GiB 8300 Linux filesystem
7 323584 17661951 8.3 GiB 8200
ernestas ~ $ (since I am not installing ArchLinux, I thought this forum would be the best choice)
Offline
Solved the problem by reinstalling the whole OS.
Offline