Im having an issue with rEFInd that is more of a nuisance than an actual problem. I have a Mid 2012 Macbook Pro, I have a triple boot set up with OS X Yosemite, Ubuntu 14.04, and windows 8.1. They all seem to be working fine as far as loading up but the problem is when I start the computer. The rEFInd boot menu does not pop up on its own, I have to hit a key on the keyboard for it to display. Soon as I hit the key 3 errors will flash on a black screen for as brief second then it will go to the rEFInd boot menu and all is well from there. the errors that are displayed are:
"Error: Volume corrupt while scanning the \ directory"
"Error: Volume corrupt while scanning the EFI directory"
"Error: Volume corrupt while scanning the boot directory"
If im not mistaken I installed ubuntu fist and windows last, after the ubuntu install, the rEFInd menu was working like it should but it was after the windows installation where I believe the rEFInd menu stop loading on its own and I start having the above problem. Does anybody know what could be causing this and what i can do to fix it?
Im just hoping I dont have to start all over from scratch and reinstall everything to fix this. But this small issue is really bothering me!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
try installing refind to the root drive with 'install.sh --notesp'
I found with my macbook pro 4,1 A1260 that the same thing happens (no refind boot menu) if refind is installed to the esp volume.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would not advise re-installing rEFInd to the root drive, particularly with Yosemite. Instead, I recommend disabling the Windows "Fast Startup" feature:
Given that the problem began after installing Windows 8.1, my suspicion is that this "feature" of Windows is causing corruption on one or more partitions (perhaps the ESP, perhaps a FAT or HFS+ shared-data partition). If I'm right, disabling "Fast Startup" should fix the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Im having an issue with rEFInd that is more of a nuisance than an actual problem. I have a Mid 2012 Macbook Pro, I have a triple boot set up with OS X Yosemite, Ubuntu 14.04, and windows 8.1. They all seem to be working fine as far as loading up but the problem is when I start the computer. The rEFInd boot menu does not pop up on its own, I have to hit a key on the keyboard for it to display. Soon as I hit the key 3 errors will flash on a black screen for as brief second then it will go to the rEFInd boot menu and all is well from there. the errors that are displayed are:
"Error: Volume corrupt while scanning the \ directory"
"Error: Volume corrupt while scanning the EFI directory"
"Error: Volume corrupt while scanning the boot directory"
If im not mistaken I installed ubuntu fist and windows last, after the ubuntu install, the rEFInd menu was working like it should but it was after the windows installation where I believe the rEFInd menu stop loading on its own and I start having the above problem. Does anybody know what could be causing this and what i can do to fix it?
Im just hoping I dont have to start all over from scratch and reinstall everything to fix this. But this small issue is really bothering me!
try installing refind to the root drive with 'install.sh --notesp'
I found with my macbook pro 4,1 A1260 that the same thing happens (no refind boot menu) if refind is installed to the esp volume.
I would not advise re-installing rEFInd to the root drive, particularly with Yosemite. Instead, I recommend disabling the Windows "Fast Startup" feature:
http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html
Given that the problem began after installing Windows 8.1, my suspicion is that this "feature" of Windows is causing corruption on one or more partitions (perhaps the ESP, perhaps a FAT or HFS+ shared-data partition). If I'm right, disabling "Fast Startup" should fix the problem.