| 2017-09-17 23:09:58 |
YannUbuntu |
description |
Boot-repair requests to create a bios-boot partition when there is already an empty EFI partition.
user.
The user had to manually create the EFI directory and everything became correct again.
Suggestion could boot-repair create the non-existent directory?
Other suggestion. Boot-repair requires the use of the first FAT32 partition with an ESP boot flag.
I think that imposing the storage of the ubuntu boot directory in the same partition as those of windows should not be systematic.
We should find a solution ...
Having the boot structure in another FAT32 partition has the following advantages:
1) Sometimes this partition can not be read by the bios. There is then double punishment. Neither windows, nor ubuntu can start.
2) Some ubuntu application tools initialize the ubuntu boot partition by forgetting that it also contains the windows boot structure that is destroyed
3) A constructor knows how to lock the windows boot partition in read mode. The installer of ubuntu is blocked and boot-repair also. It insists in removing the lock and launching a fsck that can not repair
4)It will happen one day that windows will make a partition not very vast and of which the available space will become insufficient to contain the files of boot of ubuntu which become more voluminous.
5) The space available in the deboot partition can become too small for windows to install new boot files He'll do some housework. Ubuntu boot files will not be spared |
Boot-repair requests to create a bios-boot partition when there is already an empty EFI partition.
user.
The user had to manually create the EFI directory and everything became correct again.
Suggestion could boot-repair create the non-existent directory? |
|
