Le 02.02.2014 23:27, berenger.morel@neutralite.org a écrit :
Le 02.02.2014 21:46, Tom H a écrit :On Tue, Jan 28, 2014 at 5:47 AM, <berenger.morel@neutralite.org> wrote:Le 28.01.2014 11:41, berenger.morel@neutralite.org a écrit : Sorry for incomplete message. Here is the full message:At my job, I have a computer on which I can choose the OS so, I installed my lovely debian there (with "some" problems to make it booting because of thisdamned EFI ) but would prefer to keep windows in dual boot. Windowspartition is still there, but grub does not seems to be able to notice it. I can do all tasks on the Debian system, but I need to retrieve some informations which were configured on windows, and keeping a dual boot seems a not so bad idea anyway, so do someone have any idea about what to do tofix that problem?Now some technical informations which could give (or not) some hints to helpme: The boot flag was on a NTFS partition sda1, 1GiB large.Windows itself was on a NTFS partition sda2, more than 300GiB large, but I have resized it through Debian installer to 93GiB ( should be enough for a system which will almost never be used, even if the system's name is windowsbtw ). After simple resizing, it was still able to work.There were 2 other partitions, one for windows recovery with NTFS, andanother one for HP tools with fat32. I have removed both of them.I now have a fat32 partition with EFI informations, mount point: /boot/efi,1.86GiB large on sda3, which is bootable.I have lot of other partitions for Debian: /, /usr, /var, swap, /tmp and/home. Lot of GiB there.The last partition is a FAT32 that I intend to keep to share data between windows and debian, on sd5, 61GiB large ( very large too, but consideringthe HD's size... I did not cared a lot about that ).Have you checked that "/boot/efi/EFI/Microsoft\Boot\bootmgfw.efi" exists? (It might be "Bootmgfw.efi".)I'm not at work currently, but I'll take a look tomorrow. However, I have already looked at what was in /boot and am pretty sure that I have no file or directory with microsoft or windows in their name ( lowercase, uppercase and all kinds of mixes ). I'll check anew to be sure anyway.
I only have a debian directory there: -------------------- root@...-P07-2:/boot/efi/EFI# ls debian --------------------
Have you tried to switch to "bootmgfw.efi" through your firmware?Which firmware?Running "efibootmgr" should display all the values that your firmwareknows about and the order in which they classified.I'll install this tool and check what it gives tomorrow, thanks.
It was already installed, finally. Here is the output of the command: -------------------- root@...-P07-2:/boot/efi/EFI# efibootmgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0001,0002,0003,0007,0008,0005,0006 Boot0000* debian Boot0001* DTO UEFI USB Floppy/CD Boot0002* DTO UEFI USB Hard Drive Boot0003* DTO UEFI ATAPI CD-ROM Drive Boot0005 DTO Legacy USB Floppy/CD Boot0006 Hard Drive Boot0007* IP4 Realtek PCIe GBE Family Controller Boot0008* IP6 Realtek PCIe GBE Family Controller --------------------No mention of any windows'efi file anywere. I just rechecked on the partition that I suspect to have it before my installation ( aka: sda1, a 1GB large partition containing a folder named "Boot" at root ) and no more luck. Sounds like all informations needed to boot windows lacks now... I guess I'll have to try to rebuild them, if possible, or... reinstall windows? I doubt I can: the restore files were on a partition that I had to delete to be able to create mines ( despite any good sense, they used the 4 primary partitions slots, when only one needed to be bootable! I wonder how could those people could say they are computer scientists, really! And it takes no more time to create secondary partition than primary ones... grrr! But at least I know why I will never go back to default installations for my personal uses. )...
Any idea?