I have a serious problem:
I had CentOS 6.3 and Win7 parallel working with refind 0.6.4
After a Win7 partition backup of the EFI and the Win7 partition (I know - stupid!) I only got Win7. I reinstalled refind 0.7 but it doesnt recognize my Linux installation, but it's still there!
I'm no expert in boot loaders and I hoped that refind would do the job on it's own. The boot folder on that partition is still there and the vmlinuz and so on are present there. Any idea how to get back access to my Linux?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are too many unknowns in your configuration for me to do more than make a wild guess. I recommend you run the Boot Info Script from a Linux emergency system and post a link to the RESULTS.txt file that it produces.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
okay so far I can't get the boot info script working for some reason but I got some progress. I copied the boot64.efi into some /EFI/redhat folder from the centos-live-system with the corresponding config file and it seems to be a grub-image. now I can select this boot64.efi in refind and I get some grub-menu which is obviously not proper configured as I used the config from the live system.
Can someone explain now, how to switch from here to the sda5 partition where my linux and the kernel inside the boot folder is laying? I could copy the vmlinuz and initramfs from there to the EFI partition but how can I switch then to the right partition?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In lieu of the Boot Info Script output, could you please post the complete list of files on the ESP with .efi filename extensions? For instance (from Linux), typing find /boot/efi -iname "*.efi" would do the trick. I'm not sure offhand what would get this information from Windows, though.
My suspicion is that you currently lack the driver file to access your Linux kernel on the Linux root (/) or /boot partition. If so, restoring it should fix the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys,
I have a serious problem:
I had CentOS 6.3 and Win7 parallel working with refind 0.6.4
After a Win7 partition backup of the EFI and the Win7 partition (I know - stupid!) I only got Win7. I reinstalled refind 0.7 but it doesnt recognize my Linux installation, but it's still there!
I'm no expert in boot loaders and I hoped that refind would do the job on it's own. The boot folder on that partition is still there and the vmlinuz and so on are present there. Any idea how to get back access to my Linux?
There are too many unknowns in your configuration for me to do more than make a wild guess. I recommend you run the Boot Info Script from a Linux emergency system and post a link to the
RESULTS.txtfile that it produces.okay so far I can't get the boot info script working for some reason but I got some progress. I copied the boot64.efi into some /EFI/redhat folder from the centos-live-system with the corresponding config file and it seems to be a grub-image. now I can select this boot64.efi in refind and I get some grub-menu which is obviously not proper configured as I used the config from the live system.
Can someone explain now, how to switch from here to the sda5 partition where my linux and the kernel inside the boot folder is laying? I could copy the vmlinuz and initramfs from there to the EFI partition but how can I switch then to the right partition?
In lieu of the Boot Info Script output, could you please post the complete list of files on the ESP with
.efifilename extensions? For instance (from Linux), typingfind /boot/efi -iname "*.efi"would do the trick. I'm not sure offhand what would get this information from Windows, though.My suspicion is that you currently lack the driver file to access your Linux kernel on the Linux root (
/) or/bootpartition. If so, restoring it should fix the problem.