I get 2 lines of text when booting refind (exact same error twice)
Warning: Unable to scale icon from 0 x 0 to 128 x 128 from '.VolumeIcon.icns'
Looking at the logs, it seems to have trouble finding the icons for 2 of my volumes. I only have 2 entries showing and they work, so I don't know where the issue is occuring.
The icons for my other volumes work fine. It's find 10 volumes in total (I have a tripple boot with Windows, hackintosh and linux)
Everything else works and shows my entries, but the error is halting the boot process. I just have to hit a key to continue which is annoying.
How do I fix the custom volume not working? I've installed refind on 2 others P's with dual or tripple boot without issue so I don't know why it's only happening on this one.
Last edit: Darryl Miller 2024-09-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If it does, it has a continue_on_warning setting to show messages and then continue after a few seconds without needing to press a button. It also has a hidden_icons_ignore setting to completely ignore .VolumeIcon files. You can add one or both to your config file if it has the same problem.
More importantly though, is knowing whether it does or not.
Thanks
Last edit: dakanji 2024-09-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks @dakanji
I've copied the file to my refind EFI folder. I'm currently working from home so I'll reboot once I've finished work and let you know how I go.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Worked perfectly! No errors about .VolumeIcon files. I hadn't heard about refindplus before, but I'm sticking with this version now. Thanks for the advice @dakanji !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Right, the situation has some nuance. I have since been able to look at the code in the area to remind myself of what went in there (was away from my dev unit when I saw your post) and can see that RefindPlus takes a different approach to handling the fact that there is an issue with those files.
rEFInd is technically taking the more correct approach by informing users of the issue. RefindPlus on the other hand effectively decided the issue is trivial and just proceeds without saying anything (might be noted in the debug log ... will check later).
So, with RefindPlus, a user that actually wants to load these files may find that the files are not being loaded and information is not provided in an accessible manner as to what went wrong. The rationale behind the Refindplus approach is that the kind of person that would want these files would be well placed to figure things out quickly and that the overwhelming majority would be like you. Hence a decision that quietly ignoring the issue was ultimately most pragmatic was apparently made.
You now actually need to fix those zero-size files. They are Mac OS files and are used by a Mac's Start Manager. You can either try to find valid copies for your Mac OS versions online or alternatively, I think @joevt might have a script to create them and might be able to chime in.
Once the files ares fixed, rEFInd would also work without the warning messages.
Last edit: dakanji 2024-09-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did try tinkering with the mac OS icon files initially as it's obvious to me the problem is with my hackintosh boot. I also went looking in the icon folder for refind and didn't find any zero length files. However, my other 2 PC's also have an Opencore hackintosh bootloader and I have no problems with the icons on those systems. I do not have a customised icons for mac OS on the PC giving me the error, so I'm not sure why the VolumeIcon files are an issue only in this machine.
I think I might copy the refind config file/folders from one of the other PCs and see what happens.
Right, the situation has some nuance. I have since been able to look at the code in the area to remind myself of what went in there (was on away from dev unit when I saw your post) and can see that RefindPlus takes a different approach to handling the fact that there is an issue with your VolumeIcon files.
rEFInd is technically taking the more correct approach by informing users of the issue. RefindPlus on the other hand effectively decided the issue is trivial and just proceeds without saying anything (might be noted in the debug log ... will check later).
So, with RefindPlus, a user that wants to load these files may find that they are not being loaded and no information is provided on-screen as to what went wrong. The rationale behind the Refindplus approach is that the kind of person that would want these files would be well placed to figure things out quickly and that the overwhelming majority would be like you. Hence a decision that ignoring the issue was ultimately more user friendly was apparently made.
You now actually need to fix those zero-size files. They are Mac OS files and are used by a Mac's Start Manager. You can either try to find valid copies for your Mac OS versions online or alternatively, I think @joevthttps://sourceforge.net/u/joevt/profile/ might have a script to create them and might be able to chime in.
Good day Darryl. If it is any consolation I am no longer able to boot into Linux Mint from my 2018 Mac mini due to issues with icon files. I posted in the Linux Mint discussions but no one had an answer. I also emailed the creator of rEFInd. It is so frustrating that such a seemingly small thing like icons files should break this excellent bootloader. If I find a solution I will try to remember to post something here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get 2 lines of text when booting refind (exact same error twice)
Warning: Unable to scale icon from 0 x 0 to 128 x 128 from '.VolumeIcon.icns'
Looking at the logs, it seems to have trouble finding the icons for 2 of my volumes. I only have 2 entries showing and they work, so I don't know where the issue is occuring.
This is the text from the logs.
The icons for my other volumes work fine. It's find 10 volumes in total (I have a tripple boot with Windows, hackintosh and linux)
Everything else works and shows my entries, but the error is halting the boot process. I just have to hit a key to continue which is annoying.
How do I fix the custom volume not working? I've installed refind on 2 others P's with dual or tripple boot without issue so I don't know why it's only happening on this one.
Last edit: Darryl Miller 2024-09-05
@keys3429
Temporarily replace the rEFInd efi file with RefindPlus and see if you get the same outcome.
See here for how to: https://sf.net/p/refind/discussion/general/thread/4d2754f090/#5d5f
If it does, it has a
continue_on_warningsetting to show messages and then continue after a few seconds without needing to press a button. It also has ahidden_icons_ignoresetting to completely ignore.VolumeIconfiles. You can add one or both to your config file if it has the same problem.More importantly though, is knowing whether it does or not.
Thanks
Last edit: dakanji 2024-09-06
Thanks @dakanji
I've copied the file to my refind EFI folder. I'm currently working from home so I'll reboot once I've finished work and let you know how I go.
Worked perfectly! No errors about .VolumeIcon files. I hadn't heard about refindplus before, but I'm sticking with this version now. Thanks for the advice @dakanji !
Right, the situation has some nuance. I have since been able to look at the code in the area to remind myself of what went in there (was away from my dev unit when I saw your post) and can see that RefindPlus takes a different approach to handling the fact that there is an issue with those files.
rEFInd is technically taking the more
correctapproach by informing users of the issue. RefindPlus on the other hand effectively decided the issue is trivial and just proceeds without saying anything (might be noted in the debug log ... will check later).So, with RefindPlus, a user that actually wants to load these files may find that the files are not being loaded and information is not provided in an accessible manner as to what went wrong. The rationale behind the Refindplus approach is that the kind of person that would want these files would be well placed to figure things out quickly and that the overwhelming majority would be like you. Hence a decision that quietly ignoring the issue was ultimately most pragmatic was apparently made.
You now actually need to fix those zero-size files. They are Mac OS files and are used by a Mac's
Start Manager. You can either try to find valid copies for your Mac OS versions online or alternatively, I think @joevt might have a script to create them and might be able to chime in.Once the files ares fixed, rEFInd would also work without the warning messages.
Last edit: dakanji 2024-09-12
I did try tinkering with the mac OS icon files initially as it's obvious to me the problem is with my hackintosh boot. I also went looking in the icon folder for refind and didn't find any zero length files. However, my other 2 PC's also have an Opencore hackintosh bootloader and I have no problems with the icons on those systems. I do not have a customised icons for mac OS on the PC giving me the error, so I'm not sure why the VolumeIcon files are an issue only in this machine.
I think I might copy the refind config file/folders from one of the other PCs and see what happens.
From: discussion@refind.p.re.sourceforge.net discussion@refind.p.re.sourceforge.net on behalf of dakanji dakanji@users.sourceforge.net
Sent: Wednesday, 11 September 2024 7:05 PM
To: [refind:discussion] general@discussion.refind.p.re.sourceforge.net
Subject: [refind:discussion] Error message on boot
No errors about .VolumeIcon files
Right, the situation has some nuance. I have since been able to look at the code in the area to remind myself of what went in there (was on away from dev unit when I saw your post) and can see that RefindPlus takes a different approach to handling the fact that there is an issue with your VolumeIcon files.
rEFInd is technically taking the more correct approach by informing users of the issue. RefindPlus on the other hand effectively decided the issue is trivial and just proceeds without saying anything (might be noted in the debug log ... will check later).
So, with RefindPlus, a user that wants to load these files may find that they are not being loaded and no information is provided on-screen as to what went wrong. The rationale behind the Refindplus approach is that the kind of person that would want these files would be well placed to figure things out quickly and that the overwhelming majority would be like you. Hence a decision that ignoring the issue was ultimately more user friendly was apparently made.
You now actually need to fix those zero-size files. They are Mac OS files and are used by a Mac's Start Manager. You can either try to find valid copies for your Mac OS versions online or alternatively, I think @joevthttps://sourceforge.net/u/joevt/profile/ might have a script to create them and might be able to chime in.
Error message on boothttps://sourceforge.net/p/refind/discussion/general/thread/24ec0d27c9/?limit=50#997a
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/refind/discussion/general/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
You can google "VolumeIconUtil" . It might be able to find issues with .VolumeIcon.icns files.
Good day Darryl. If it is any consolation I am no longer able to boot into Linux Mint from my 2018 Mac mini due to issues with icon files. I posted in the Linux Mint discussions but no one had an answer. I also emailed the creator of rEFInd. It is so frustrating that such a seemingly small thing like icons files should break this excellent bootloader. If I find a solution I will try to remember to post something here.