ext4-formatted SSD causes problems since OpenCore-0.7.8

[windowless31]

 

Hello,

I have an ext4 formatted SSD in my PC. No Linux is installed there, there are KVM VMs on it.
This SSD wants to be initialized since OpenCore-0.7.8 in macOS-Monterey at every start.
The partitions where a Linux is installed are not recognized in Monterey and there is no message: "This volume cannot be read". This is how it should be.
How can I prevent that the ext4 disk wants to be initialized.

 

Sorry for my english and thank you

[Guest 5T33Z0]

You could add the ext4 driver to your EFI folder and config included in the OC Binary Data package and see if it change anything: https://github.com/acidanthera/OcBinaryData/tree/master/Drivers

And if it is present already, you could check what happens if you disable it.

[windowless31]

I had the ext4 driver active and with the driver disabled the same thing happens. With OpenCore 0.7.7 I do not have this behavior, I boot Linux via custom entries. In OpenCore 0.7.8 the direct Linux boot was integrated.
It is strange that it only affects the one ext4-SSD, the Linux partitions (Fedora and Arch) do not want to be initialized.

 

[Guest 5T33Z0]

@windowless31 Oka, then ma RestrictEvents does the trick: https://github.com/acidanthera/RestrictEvents

 

Among other things, it also disbales the "Uninitialized disk" warning

[windowless31]

@5T33Z0 I already use RestrictEvents, because of my CPU.
Sorry, I forgot to update my hardware. It's about an AlderLake system.
"Disabled uninitialized disk UI" does not work like that. Do I need to pass a bootarg with RestrictEvents?

 

Just found: diskread - disables uninitialized disk warning in Finder

I try out immediately.

Edited April 20, 2022 by windowless31

[windowless31]

@5T33Z0 the bootarg revpatch=diskread has solved the problem. Thank you very much for this.
My english is too bad, so I overread such hints, sorry