-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find the ESP! #16
Comments
I'll need the output of the following commands:
|
This is my separate windows HDD.
This is Arch Linux
|
This part of the output presents a problem:
The "parttype" property's value is correct (c12a7328-f81f-11d2-ba4b-00a0c93ec93b) as well as the "fstype" property's value (vfat) but the value of the "mountpoint" property is null, apparently. |
This part is Windows ESP. My refind ESP is on /dev/sdb1 and it is mounted for sure as well as present in fstab. I tried to mount my windows efi partition and here is the output
I also tried to swap SATA cables to make Linux drive appear as /dev/sda so /dev/sda1 is a Linux ESP and it didn't help. Result was the same without Windows ESP - Could not find the ESP. And with mounted Windows ESP only these lines changed:
Also i tried to umount all Windows NTFS partitions that i had and it still couldn't find the ESP |
Well, I don't know exactly why, in your case, lsblk reports the /dev/sdb ESP's mountpoint as null. That is a problem because I cannot access anything related to rEFInd that way (its config file, primarily). Having more than one ESP is definitely problematic, imho. I've not dabbled with supporting such a setup, unfortunately. I also have Windows installed alongside Linux (installed after Windows) but only one ESP (with rEFInd installed on it, of course). Can you access the ESP partition (the one on /dev/sdb/) while your Linux system is running (by using a file manager, for instance)? EDIT: I see that your /boot and ESP are one and the same partition, judging by this part of the output:
If so, you technically do not have a separate /boot, from the perspective of this tool as I suppose your kernel and microcode images are located on it. Your / partition is mounted as /btrfs, which is also pretty interesting. You have quite an exotic setup, I have to say. I'd have to think about exactly how to implement support for this particular scenario - the "fstype" property's value is correct, the partition itself is obviously mounted but the "parttype" property's value (its type's GUID) is not the one I expect, per specification . |
Also, I'd like to see findmnt's output, as well: Thank you in advance. |
I unplugged my Windows drive SATA cable and problem is still here. So it seems to me that having more than one ESP has nothing to do with this. Gotta be that i messed up my Linux ESP. My install is fresh so it's ok to me to quickly fix this even if it would require to wipe and redo everything. Here is the output
|
Even this picture on the Wiki article is showing what is, essentially (assuming I'm interpreting it correctly), a two in one kind of partition (both ESP and /boot) so it must be a common enough setup, I guess. The most sensible approach, at this time, would be to allow the user to define the ESP partition's UUID in the config file. This should be an optional value which would be (if defined) taken for granted, so to speak. I can use that value to try and match the ESP directly from lsblk's output. What I still don't understand is where exactly are your kernel images located at? Do they reside on this ESP/boot hybrid (for lack of a better word) partition or are they somewhere else? EDIT: |
I though about that too. It would be nice if there was such an option in the config
|
So, it is a separate /boot partition and your kernel and microcode images do not reside on a Btrfs partition? Sure, I'll try to implement this feature during the following weekend. |
Yup, it's a vfat partition with microcode, kernel and refind on it mounted as /boot. |
I've just released an implementation of this proposed feature, tried it locally and I've been able to identify the ESP by setting its UUID in the config file. By default this new option (named "esp_uuid", first one listed in the file) is set to an empty UUID and thus ignored. You can try setting it to "ed31ab35-a36e-8341-b60e-40977b4e66c0" and hope for the best, I guess. In any case, please report back here with the results, when convenient. |
I set esp_uuid and after that the stanzas started to generate, became bootable and everything works as expected. Thanks for the great work on this must-have tool! |
That's just great, I'm glad it finally worked out for you! |
Not sure what i should include here besides this. ESP is mounted for sure
Feel free to ask any info about my setup
The text was updated successfully, but these errors were encountered: