syscl Posted January 3, 2017 Share Posted January 3, 2017 Here's why rc scripts are starting to change since r3961 http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2332320 I can't download the r3961's shutdown script: the file isn't here anymore. But I saw the discussion: for FileVault2, we need to dump NVRAM to EFI/ instead of /. Theoretically, pairing with the touched version of 20.mount_ESP.local, my version of script can successfully dump NVRAM to EFI every time. Show me the rc.shutdown.logs after several reboot... syscl Link to comment Share on other sites More sharing options...
cjfly Posted January 3, 2017 Share Posted January 3, 2017 @gujiangjiang @tluck @Sherlock @Slice Try the latest 80.save_nvram_plist.local, improvements use mount_hfs instead of mount -t hfs to mount hfs EFI use @tluck's suggestion if there's no Clover under EFI, return if root volume and EFI are on the same disk, nvram.plist should be either in / or EFI/ Note: This script will write nvram.plist to all the EFI which contains Clover syscl_save_nvram.zip Good luck, syscl dear syscl, I can confirm this one work flawlessly! Thanks a ton! here is the result, I reboot 4 times and the result is the same as below v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local ^_^ 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 I can't download the r3961's shutdown script: the file isn't here anymore. But I saw the discussion: for FileVault2, we need to dump NVRAM to EFI/ instead of /. Theoretically, pairing with the touched version of 20.mount_ESP.local, my version of script can successfully dump NVRAM to EFI every time. Show me the rc.shutdown.logs after several reboot... syscl r3961 rc script https://sourceforge.net/p/cloverefiboot/code/3963/tree//CloverPackage/CloverV2/rcScripts/etc/rc.shutdown.d/80.save_nvram_plist.local Theoretically, pairing with the touched version of 20.mount_ESP.local, my version of script can successfully dump NVRAM to EFI every time. does it mean to have nvram file both in ESP and root? i have only nvram.plist file in root. Theoretically we have nvram both ESP and root to use FileVault2. right? my ESP status v1.1 © 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: / EmuVariable is present dump nvram >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ i don't understand nvram now exactly. anyway is my status no problem now to use FileVault2? sorry my english. Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 r3961 rc script https://sourceforge.net/p/cloverefiboot/code/3963/tree//CloverPackage/CloverV2/rcScripts/etc/rc.shutdown.d/80.save_nvram_plist.local Theoretically, pairing with the touched version of 20.mount_ESP.local, my version of script can successfully dump NVRAM to EFI every time. does it mean to have nvram file both in ESP and root? i have only nvram.plist file in root. Theoretically we have nvram both ESP and root to use FileVault2. right? my ESP status 스크린샷 2017-01-04 오전 3.38.47.png 스크린샷 2017-01-04 오전 3.39.40.png i don't understand nvram now exactly. anyway is my status no problem now to use FileVault2? sorry my english. Not a problem. 1) Install my version of 20.mount.ESP.local in /etc/rc.boot.d, then reboot This script will make msdosfs.kext load, then you will see nvram.plist save in EFI/ In my laptop, I reboot my computer 2 times and do not mount any EFI: syscls-MacBook:~ syscl$ ls / Applications etc EFI-Backups home Library installer.failurerequests Network net System private Users sbin Volumes tmp bin usr cores var dev syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log Password: v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/syscl.startup.log msdos and exfat forceload (c) syscl/lighting/Yating Zhou Wait for your feedback, syscl Link to comment Share on other sites More sharing options...
tluck Posted January 3, 2017 Share Posted January 3, 2017 with new scripts from today - 1 time fail to write to EFI out of about 10 reboots. Target was / once. - hmm. should it just not write to / ever? versus have one in /EFI and randomly one in / ? i haven't looked at the code to see which file EmuVar reads in case of one in /ESP and / Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 with new scripts from today - 1 time fail to write to EFI out of about 10 reboots. Target was / once. - hmm. should it just not write to / ever? versus have one in /EFI and randomly one in / ? i haven't looked at the code to see which file EmuVar reads in case of one in /ESP and / Not randomly write to / and EFI/, but it depends on if msdosfs.kext will be loaded or not. I have already added force msdosfs.kext load in the 20.mount.ESP.local, but if you sleep your laptop, system will automatically unload msdosfs.kext, that's the reason why you saw my script write NVRAM to / There's two solutions(IMO) till now: 1. use hfs for EFI, since hfs will always present 2. use sleepwatcher to load the msdosfs.kext after waking from sleep I will try to figure out better solution if there exists... BTW, @tluck, could you test your .apdisk with the latest script? I've already added detection for Clover folder. Remove nvram.plist in you .apdisk then see if my script will dump NVRAM to it or not. Thanks, syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 Not a problem. 1) Install my version of 20.mount.ESP.local in /etc/rc.boot.d, then reboot This script will make msdosfs.kext load, then you will see nvram.plist save in EFI/ In my laptop, I reboot my computer 2 times and do not mount any EFI: syscls-MacBook:~ syscl$ ls / Applications etc EFI-Backups home Library installer.failurerequests Network net System private Users sbin Volumes tmp bin usr cores var dev syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log Password: v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/syscl.startup.log msdos and exfat forceload (c) syscl/lighting/Yating Zhou Wait for your feedback, syscl still i dont have nvram.plist in ESP. previous rc script is no problem about this. add. strange. previous rc script suddenly can't generate nvram.plist in ESP. i didn't touch other. Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 still i dont have nvram.plist in ESP. previous rc script is no problem about this. add. strange. previous rc script suddenly can't generate nvram.plist in ESP. i didn't touch other. Please try this one: 80.save_nvram_plist.local.zip Could you post this information as well? kextstat |grep -i 'msdos' syscl Link to comment Share on other sites More sharing options...
tluck Posted January 3, 2017 Share Posted January 3, 2017 ah right. on time to / for me EFI must be FAT32 so another solutions must be found a logoutHook maybe a choice. and yes - it avoided the non CLOVER disk $ ls -l /Volumes/E* /Volumes/ESP: total 19 drwxrwxrwx 1 tluck staff 1024 Dec 28 09:29 EFI drwxrwxrwx 1 tluck staff 1024 Dec 31 11:59 EFI-Backup drwxrwxrwx 1 tluck staff 512 Dec 15 2015 NU -rwxrwxrwx 1 tluck staff 7091 Jan 3 13:54 nvram.plist /Volumes/ESP-1: total 16 drwxrwxrwx 1 tluck staff 512 Jan 2 18:13 EFI drwxrwxrwx 1 tluck staff 512 Jan 2 18:13 EFI-Backup -rwxrwxrwx 1 tluck staff 7091 Jan 3 13:54 nvram.plist /Volumes/ESP-2: 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 Please try this one: 80.save_nvram_plist.local.zip Could you post this information as well? kextstat |grep -i 'msdos' syscl Supreme-MBP:~ supreme$ kextstat |grep -i 'msdos' 129 1 0xffffff7f80f80000 0xf000 0xf000 com.apple.filesystems.msdosfs (1.10) F8B8D309-C01A-32AD-B769-8822D9B4593B <7 5 4 1> Supreme-MBP:~ supreme$ strange. to clear status and refine issue, i reinstalled r3974 latest clover pkg. and i confirmed nvram.plist in ESP and root. and remove both nvram.plist files. and replace your rc script and ESP mount script. reboot. i can see only nvram file in root. there is no nvram.plist in ESP. reboot 2times and 3times still same. Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log Password: Found EFI disk0s1 Target path: / EmuVariable is present dump nvram >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ log shown no problem. but still not shown nvram.plist in ESP. r3974 rc script perfectly generate nvram.plist file in ESP. your script has something problem. Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 strange. to clear status and refine issue, i reinstalled r3974 latest clover pkg. and i confirmed nvram.plist in ESP and root. and remove both nvram.plist files. and replace your rc script and ESP mount script. reboot. i can see only nvram file in root. there is no nvram.plist in ESP. reboot 2times and 3times still same. r3974 rc script perfectly generate nvram.plist file in ESP. your script has something problem. The first time you saw r3974's script that generated nvram.plist in ESP is because: - Install 3974's package will mount ESP, that will let system load msdosfs.kext successfully then it will dump to both ESP and / (Install Clover --> Mount ESP require --> load msdosfs.kext --> script successfully dump ESP to /) It's very possible that msdosfs or exfat failed to load on your macOS. To confirm, please run sudo kextload /System/Library/Extensions/msdosfs.kext sudo kextload /System/Library/Extensions/exfat.kext Then reboot to see if this solve your problem. syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 The first time you saw r3974's script that generated nvram.plist in ESP is because: - Install 3974's package will mount ESP, that will let system load msdosfs.kext successfully then it will dump to both ESP and / (Install Clover --> Mount ESP require --> load msdosfs.kext --> script successfully dump ESP to /) It's very possible that msdosfs or exfat failed to load on your macOS. To confirm, please run sudo kextload /System/Library/Extensions/msdosfs.kext sudo kextload /System/Library/Extensions/exfat.kext Then reboot to see if this solve your problem. syscl my steps. 1. reinstall clover r3974 pkg 2. boot, remove nvram file in ESP and root. 3. replace your script(RC,ESP script) 4. reboot, confirmed in ESP, there is no nvram.plist file. 5. run sudo kextload /System/Library/Extensions/msdosfs.kext sudo kextload /System/Library/Extensions/exfat.kext 6. reboot. 7. still no nvram file in ESP. Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 my steps. 1. reinstall clover r3974 pkg 2. boot, remove nvram file in ESP and root. 3. replace your script(RC,ESP script) 4. reboot, confirmed in ESP, there is no nvram.plist file. 5. run sudo kextload /System/Library/Extensions/msdosfs.kext sudo kextload /System/Library/Extensions/exfat.kext 6. reboot. 7. still no nvram file in ESP. I will send you a test version in private message to see what's wrong in your situation. Edited: I cannot send test version in private message, thus I place here, please give me the output of rc.shutdown.logs testversion.zip syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 I will send you a test version in private message to see what's wrong in your situation. Edited: I cannot send test version in private message, thus I place here, please give me the output of rc.shutdown.logs testversion.zip syscl test version report. we don't need to reboot to check rc script work or not it's very easy Supreme-MBP:~ supreme$ sudo chown 0:0 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo chmod 755 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local /etc/rc.shutdown.d/80.save_nvram_plist.local: line 144: syntax error near unexpected token `>' /etc/rc.shutdown.d/80.save_nvram_plist.local: line 144: ` mount_hfs "${gDevRepo}" "${gAssignMountPoint}" &>>${gNvramLogPath} && RETURN_VAL=${kBASHReturnSuccess} || RETURN_VAL=${kBASHReturnFailure}' Supreme-MBP:~ supreme$ your test version log above. your latest rc script(not test version) i don't see nvram.plist in ESP. i can see only make nvram.plist in root. you can see what i said. try your laptop. because of this reason(only exist nvram in root), brightness load work like old script. Supreme-MBP:~ supreme$ sudo chown 0:0 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo chmod 755 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ r3974 rc script log. and i can see nvram.plist in ESP. Supreme-MBP:~ supreme$ sudo chown 0:0 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo chmod 755 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local NVRAM saved to '/Volumes/EFI/nvram.plist' [disk0s1] Supreme-MBP:~ supreme$ Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 test version report. we don't need to reboot to check rc script work or not it's very easy your test version log above. your latest rc script(not test version) i don't see nvram.plist in ESP. r3974 rc script log. and i can see nvram.plist in ESP. Please try this one with reboot testversion2.zip syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 Please try this one with reboot testversion2.zip syscl testversion2 has critical bug. in ESP, all files is gone. i have to recovery EFI folder files. no need reboot. first test your script in your laptop. and see script behavior Supreme-MBP:~ supreme$ sudo chown 0:0 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo chmod 755 /etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 testversion2 has critical bug. in ESP, all files is gone. i have to recovery EFI folder files. no need reboot. first test your script in your laptop. and see script behavior I double that your EFI has problem, like I mentioned in previous post: my script will not mount damage EFI... testversion3.zip As you mentioned, I re download the 1.1 script then run in terminal syscls-MacBook:~ syscl$ sudo cp /Users/syscl/Downloads/syscl_save_nvram/test/80.save_nvram_plist.local /etc/rc.shutdown.d/80.save_nvram_plist.local Password: syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ And this Last login: Tue Jan 3 14:42:28 on ttys000 syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local Password: Sorry, try again. Password: syscls-MacBook:~ syscl$ sudo rm /Library/Logs/CloverEFI/rc.shutdown.log syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ ls / |grep -i 'plist' syscls-MacBook:~ syscl$ ls /Volumes/EFI01/EFI/ |grep -i 'plist' syscls-MacBook:~ syscl$ ls /Volumes/EFI01/ |grep -i 'plist' nvram.plist syscls-MacBook:~ syscl$ syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 I double that your EFI has problem, like I mentioned in previous post: my script will not mount damage EFI... testversion3.zip As you mentioned, I re download the 1.1 script then run in terminal syscls-MacBook:~ syscl$ sudo cp /Users/syscl/Downloads/syscl_save_nvram/test/80.save_nvram_plist.local /etc/rc.shutdown.d/80.save_nvram_plist.local Password: syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ And this Last login: Tue Jan 3 14:42:28 on ttys000 syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local Password: Sorry, try again. Password: syscls-MacBook:~ syscl$ sudo rm /Library/Logs/CloverEFI/rc.shutdown.log syscls-MacBook:~ syscl$ sudo /Users/syscl/Downloads/syscl_save_nvram/80.save_nvram_plist.local syscls-MacBook:~ syscl$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram syscls-MacBook:~ syscl$ ls / |grep -i 'plist' syscls-MacBook:~ syscl$ ls /Volumes/EFI01/EFI/ |grep -i 'plist' syscls-MacBook:~ syscl$ ls /Volumes/EFI01/ |grep -i 'plist' nvram.plist syscls-MacBook:~ syscl$ syscl Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log Password: v1.1 © 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 umount: disk0s1: not currently mounted umount: /Volumes/EFI01: not currently mounted kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/msdosfs.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/msdosfs.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/msdosfs.kext - (libkern/kext) function disabled. /System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) function disabled. mount_msdos: msdos filesystem is not available mount_hfs: Invalid argument kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/exfat.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/exfat.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/exfat.kext - (libkern/kext) function disabled. /System/Library/Extensions/exfat.kext failed to load - (libkern/kext) function disabled. mount_exfat: exfat filesystem is not available >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo kextload /System/Library/Extensions/msdosfs.kext Supreme-MBP:~ supreme$ sudo kextload /System/Library/Extensions/exfat.kext Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 © 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 umount: disk0s1: not currently mounted umount: /Volumes/EFI01: not currently mounted kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/msdosfs.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/msdosfs.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/msdosfs.kext - (libkern/kext) function disabled. /System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) function disabled. mount_msdos: msdos filesystem is not available mount_hfs: Invalid argument kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/exfat.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/exfat.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/exfat.kext - (libkern/kext) function disabled. /System/Library/Extensions/exfat.kext failed to load - (libkern/kext) function disabled. mount_exfat: exfat filesystem is not available >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ here. i didn't any sleep mode, just reboot and check. Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 @Sherlock Now you know why kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/msdosfs.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/msdosfs.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/msdosfs.kext - (libkern/kext) function disabled. /System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) function disabled. mount_msdos: msdos filesystem is not available mount_hfs: Invalid argument kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/exfat.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/exfat.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/exfat.kext - (libkern/kext) function disabled. /System/Library/Extensions/exfat.kext failed to load - (libkern/kext) function disabled. mount_exfat: exfat filesystem is not available >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo kextload /System/Library/Extensions/msdosfs.kext Supreme-MBP:~ supreme$ sudo kextload /System/Library/Extensions/exfat.kext Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 © 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 umount: disk0s1: not currently mounted umount: /Volumes/EFI01: not currently mounted kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/msdosfs.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/msdosfs.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/msdosfs.kext - (libkern/kext) function disabled. /System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) function disabled. mount_msdos: msdos filesystem is not available mount_hfs: Invalid argument kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/exfat.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/exfat.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/exfat.kext - (libkern/kext) function disabled. /System/Library/Extensions/exfat.kext failed to load - (libkern/kext) function disabled. mount_exfat: exfat filesystem is not available The same problem as I previous posted. Here's the log information after I reboot my laptop In second time, you forget to run my script, you just manually load two kext, that's not correct operation. syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 @Sherlock Now you know why kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/msdosfs.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/msdosfs.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/msdosfs.kext - (libkern/kext) function disabled. /System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) function disabled. mount_msdos: msdos filesystem is not available mount_hfs: Invalid argument kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/exfat.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/exfat.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/exfat.kext - (libkern/kext) function disabled. /System/Library/Extensions/exfat.kext failed to load - (libkern/kext) function disabled. mount_exfat: exfat filesystem is not available >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local Supreme-MBP:~ supreme$ sudo kextload /System/Library/Extensions/msdosfs.kext Supreme-MBP:~ supreme$ sudo kextload /System/Library/Extensions/exfat.kext Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 © 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 umount: disk0s1: not currently mounted umount: /Volumes/EFI01: not currently mounted kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/msdosfs.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/msdosfs.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/msdosfs.kext - (libkern/kext) function disabled. /System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) function disabled. mount_msdos: msdos filesystem is not available mount_hfs: Invalid argument kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/exfat.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/exfat.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/exfat.kext - (libkern/kext) function disabled. /System/Library/Extensions/exfat.kext failed to load - (libkern/kext) function disabled. mount_exfat: exfat filesystem is not available The same problem as I previous posted. Here's the log information after I reboot my laptop Snip20170103_1.png In second time, you forget to run my script, you just manually load two kext, that's not correct operation. syscl ^[[ASupreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log Password: v1.1 © 2017 syscl/lighting/Yating Zhou 130 0 0xffffff7f83627000 0xe000 0xe000 com.apple.filesystems.exfat (1.4) D6D15BC4-BF6A-3A77-A20C-DC2FF777C165 <7kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext '/System/Library/Extensions/msdosfs.kext' kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Libkern.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Unsupported.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/Mach.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/System.kext/PlugIns/BSDKernel.kext" kext signature failure override allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext "/System/Library/Extensions/msdosfs.kext" (kernel) Kext loading is disabled. Failed to load /System/Library/Extensions/msdosfs.kext - (libkern/kext) function disabled. /System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) function disabled. mount_msdos: msdos filesystem is not available mount_hfs: Invalid argument mount_exfat: /dev/disk0s1 on /Volumes/EFI01: Invalid argument >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local et path: /Volumes/EFI01 EmuVariable is present dump nvram Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/syscl.startup.log msdos and exfat forceload © syscl/lighting/Yating Zhou Supreme-MBP:~ supreme$ forgot run your script? what is that? i just tested before like old script and other script in clover discussion thread. replace and give permission. and reboot. already your ESP script has echo "msdos and exfat forceload © syscl/lighting/Yating Zhou" >/Library/Logs/CloverEFI/syscl.startup.log kextload /System/Library/Extensions/msdosfs.kext >>/Library/Logs/CloverEFI/syscl.startup.log kextload /System/Library/Extensions/exfat.kext >>/Library/Logs/CloverEFI/syscl.startup.log i don't touch anything. where is wrong? strange. give me instrunction in detail. Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 forgot run your script? what is that? i just tested before like old script and other script in clover discussion thread. replace and give permission. and reboot. already your ESP script has i don't touch anything. where is wrong? strange. give me instrunction in detail. It's very clear that msdosfs and exfat.kext on your laptop don't load correctly. The only thing we need to do is figure out what's wrong with your computer. Give me the result of this sudo cat /Library/Logs/CloverEFI/syscl.startup.log syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 It's very clear that msdosfs and exfat.kext on your laptop don't load correctly. The only thing we need to do is figure out what's wrong with your computer. Give me the result of this sudo cat /Library/Logs/CloverEFI/syscl.startup.log syscl after use kext utility Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/syscl.startup.log Password: msdos and exfat forceload © syscl/lighting/Yating Zhou Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log v1.1 © 2017 syscl/lighting/Yating Zhou 129 1 0xffffff7f80f80000 0xf000 0xf000 com.apple.filesystems.msdosfs (1.10) F8B8D309-C01A-32AD-B769-8822D9B4593Bmount_msdos: /dev/disk0s1: Resource busy mount_hfs: Resource busy mount_exfat: /dev/disk0s1 on /Volumes/EFI01: Resource busy >> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local ounted umount: /Volumes/EFI01: not currently mounted mkdir: /Volumes/EFI01: File exists mount_hfs: error on mount(): error = -1. total 8 -rw-r--r-- 1 root wheel 2527 Jan 4 06:15 nvram.plist Target path: /Volumes/EFI01 EmuVariable is present dump nvram Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/syscl.startup.log msdos and exfat forceload © syscl/lighting/Yating Zhou Supreme-MBP:~ supreme$ still not shown nvram.plist in ESP Supreme-MBP:~ supreme$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *256.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Microsoft Basic Data Windows 7 110.0 GB disk0s2 3: Microsoft Basic Data Win Data 60.1 GB disk0s3 4: Apple_HFS Macintosh SSD 69.1 GB disk0s4 5: Apple_Boot Recovery HD 650.0 MB disk0s5 6: Apple_HFS Mac Data 16.0 GB disk0s6 Supreme-MBP:~ supreme$ also sometimes i have exprienced force reboot since use your script. Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 still not shown nvram.plist in ESP also sometimes i have exprienced force reboot since use your script. Notice this piece mount_msdos: /dev/disk0s1: Resource busy mount_hfs: Resource busy mount_exfat: /dev/disk0s1 on /Volumes/EFI01: Resource busy It's more clear now. My script and r3974's will try to mount EFI with 3 attempts. Let me say this clear: - Try to mount EFI with mount_msdos, if mount ok, then EFI must be msdos, otherwise EFI is exfat or HFS - Try to mount EFI with mount_exfat, if mount ok, then EFI must be exfat, otherwise EFI is HFS - Try to mount EFI with mount_hfs, if mount ok, then EFI must be HFS For example, you can see in my log: mount_hfs: Resource busy(or throw error) mount_exfat: Reource busy(or throw error) there's no mount_msdos error in my case. Why? Because mount_msdos will be silent if I mount my Fat32 EFI successfully. Now, turn to your problem, it's very clear that you have some other progress at this stage lock the EFI partition for doing some other stuff, all the three system calls(mount_msdos, mount_exfat, mount_hfs) have just to throw error, then my script return. We can add spin wait to wait the resource release the lock, but the problem is more like from your system/settings/softwares. This script will only be called at the shutdown stage, hence, no way to cause your system reboot during use. The only possible reason I think is you use kext utility to rebuild kernel cache, kext utility will touch msdos.kext and some other stuff, which make your system unstable during 20.mount.ESP.local load msdosfs.kext syscl Link to comment Share on other sites More sharing options...
Sherlocks Posted January 3, 2017 Share Posted January 3, 2017 Notice this piece mount_msdos: /dev/disk0s1: Resource busy mount_hfs: Resource busy mount_exfat: /dev/disk0s1 on /Volumes/EFI01: Resource busy It's more clear now. My script and r3974's will try to mount EFI with 3 attempts. Let me say this clear:- Try to mount EFI with mount_msdos, if mount ok, then EFI must be msdos, otherwise EFI is exfat or HFS - Try to mount EFI with mount_exfat, if mount ok, then EFI must be exfat, otherwise EFI is HFS - Try to mount EFI with mount_hfs, if mount ok, then EFI must be HFS For example, you can see in my log: mount_hfs: Resource busy(or throw error) mount_exfat: Reource busy(or throw error) there's no mount_msdos error in my case. Why? Because mount_msdos will be silent if I mount my Fat32 EFI successfully. Now, turn to your problem, it's very clear that you have some other progress at this stage lock the EFI partition for doing some other stuff, all the three system calls(mount_msdos, mount_exfat, mount_hfs) have just to throw error, then my script return. We can add spin wait to wait the resource release the lock, but the problem is more like from your system/settings/softwares. This script will only be called at the shutdown stage, hence, no way to cause your system reboot during use. The only possible reason I think is you use kext utility to rebuild kernel cache, kext utility will touch msdos.kext and some other stuff, which make your system unstable during 20.mount.ESP.local load msdosfs.kext syscl Okay. Once i return old script. old script is stable for me. Thank you. If you improve something, i will help you 나의 LG-F410S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
syscl Posted January 3, 2017 Share Posted January 3, 2017 Okay. Once i return old script. old script is stable for me. Thank you. If you improve something, i will help you 나의 LG-F410S 의 Tapatalk에서 보냄 Since you post this issue, I want to improve my script to solve your problem as well. I am happy you give so many useful information, give me some time... I will contact you to test new script. Anyway, the major issue is gone. BTW, it's very late in you Korea right? Better to have a rest then talk this later. Thanks, syscl 1 Link to comment Share on other sites More sharing options...
Recommended Posts