![]() On the plus side: I can access the Windows data partition ( /dev/sda2) from within Antergos without any problems. I still cannot boot into Windows, nor can I see the HDD0 in the BIOS to select a. However, the initial problem still persists. dev/sda3: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS ", sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, hidden sectors 975034368, dos < 4.0 BootSector (0x80), FAT (1Y bit by descriptor) NTFS, sectors/track 63, sectors 1736703, $MFT start cluster 72362, $MFTMirror start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial number XXXXXXXXXY dev/sda2: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS ", sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, hidden sectors 34816, dos < 4.0 BootSector (0x80), FAT (1Y bit by descriptor) NTFS, sectors/track 63, sectors 974999354, $MFT start cluster 786432, $MFTMirror start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial number XXXXXXXXXX This seemed to fix the "Invalid partition table", as it is now reported as follows: /dev/sda: DOS/MBR boot sector partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors Grub-install -target=x86_64-efi -efi-directory=/boot/efi -bootloader-id=Antergos-grubĪnd in the BIOS, I added the HDD0/Antergos-grub/./something.efi to boot from.Īfter this, I was able to boot into Antergos but somewhere along the way I apparently screwed up my Windows boot settings.Īs mentioned above, Windows Boot Manager fails and the system then defaults to Antergos' GRUB.Ī quick file -sL /dev/sda* showed an "Invalid partition table" on /dev/sda which I tried to fix with dd if=/usr/lib/syslinux/bios/mbr.bin of=/dev/sda. Mount /dev/mapper/AntergosVG-AntergosRoot /mnt/ However, there seems to be a known problem with Antergos installs, which I fixed by following a blog post describing a near-identical issue with the following steps to fix the boot issue: cryptsetup luksOpen /dev/nvme0n1p3 luks 19.4 ISO, if that even matters) on HDD0/nvme0n1, LUKS-encrypted, with GRUB also on nvme0n1. ![]() ![]() Then I installed Antergos (hence the arch-linux tag, I hope that's ok. All went well, several reboots & update-cycles later I was still able to boot into the Windows partition. efi file to set as a secure boot option ("Select an UEFI file as trusted for executing").Īdditionally, Windows Boot Manager points to the wrong HDD (in boot selection: "Windows Boot Manager (Samsung SSD 970 PRO 512GB)") - or at least I think so, I did not pay attention to this when I set up the Windows system initially.įirst, I installed and configured Windows on HDD1 with default partitioning etc. My problem is, that I cannot boot into Windows anymore (selecting the Windows Boot Manager from the boot selection screen defaults to the Antergos GRUB) and I cannot see HDD1 in the BIOS anymore to choose an. HDD1 | sda | Samsung SSD 850 EVO 500GB | Windows 10 (non-BitLocker) ![]() HDD layout HDD0 | nvme0n1 | Samsung SSD 970 PRO 512GB | Antergos 19.4 (LUKS) I recently re-did my system setup, having two separate SSDs because Windows usually tries to screw Linux installations up if it's on the same physical disk. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |