Jump to content

Vanilla Mojave Clover install stopped working recently


mattsnowboard
 Share

4 posts in this topic

Recommended Posts

I rebuilt a hackintosh this summer and a couple months ago it stopped working. Now when I boot it goes through some of the Clover verbose output, but then gets stuck. Some of the text is scrolling too quickly to read (and my phone can't focus to take a clear video). Near the end it starts saying:

 

> ru.usrsse3.SMCLightSensor did not stop (return code 0x5)

> ru.usrsse3.SMCLightSensor can't unload - module stop returned 0xdc008017

 

I'm not sure if that is an actual problem, or just the kexts are getting unloaded because something else is failing. I did try to disable SMCLightSensor when booting but it still fails to boot into OSX. After that it keeps printing "ATHR: unknown locale: 21", which it just always prints (and always has), likely just an issue with the Wi-Fi card I'm using.

 

Eventually (a few minutes later), I see some of the following messages:

 

>handle_encryption_rolling:5632: er: request granted[0].

>apfs_load_inode:4337: *** reset ino 1552716 size back to 23872 (from 24148)

>er_state_obj_get_for_recovery:4214: No ER state object for volume Recovery - rolling is not happening, nothing to recover.

>apfs_vfsop_mount:1536: mounted volume: Recovery

>disk2s3: device is not readable

>apfs_stop_bg_work:782: Volume Recovery is unmounting, stop any bg work

 

Some of these lines are repeated and the SMCLightSensor line happens again a few times.

 

As far as I know, nothing changed from when it was working until it stopped. It is able to boot fine into Windows. I was also able to boot into the Mojave installer from the USB drive I used, so worst case I may try reinstalling again. But if I can recover it (and understand what went wrong) that would be preferred (so it doesn't happen again). Is there something else I should try?

 

It was running Mojave 10.14.5

 

Clover v4961

boot options: -v dart=0 kext-dev-mode=1 keepsyms=1 nvda_drv=1

SIP: 0x3

Flags: 0x28

 

SMBIOS iMac13,2

 

Kexts:

SMCProcessor.kext 1.0.7

SMCLightSensor.kext 1

SMCBatteryManager.kext 1

Lilu.kext 1.3.8

USBPorts.kext 1.0

FakePCIID_XHCIMux.kext 1.3.15

FakePCIID.kext 1.3.15

WhateverGreen.kext 1.3.2

VirtualSMC.kext 1.0.7

SMCSuperIO.kext 1.0.7

IntelMausiEthernet.kext 2.5.0d0

AppleALC.kext 1.3.8

 

 

Hardware: i7-4770S Z87MX-D3H

Recently (when reinstalling) switched to AMD graphics Pulse Radeon RX580 8GB

 

Link to comment
Share on other sites

I think the culprit is 

 

disk2s3: device is not readable

Volume Recovery is unmounting, stop any bg work

 

seems apfs volume is failing. What puzzles me is why does it try to mount recovery instead of the os partition. Maybe there is a similar message about the OS partition? Your partitions should be like this: (in your case disk2 vs my case disk1)

 

1:                APFS Volume os                       113.2 GB    disk1s1
2:                APFS Volume Preboot                 45.2 MB    disk1s2
3:                APFS Volume Recovery                510.4 MB disk1s3

 

Can you try to explicitly boot Recovery Partition in Clover? There is a hotkey (see F1 clover help) to show hidden partitions.

 

Also can you check you are using ApfsDriverLoader.EFI in your EFI/drivers/uefi ?

 

A vector for testing would be putting the failing HD in an external enclosure and check it from another computer, you would need a OSX version 10.14+ for that, so APFS is supported.

 

Edited by rlp
Link to comment
Share on other sites

I think you are on the right track. I was also unable to boot into recovery, so I think something got messed up with that APFS volume.

 

I ended up just creating a new APFS volume and reinstalling there then copying everything from the old install during the OOBE setup. Seems to be working now.

 

Though I am able to access the old volume fine from the new install so I'm not sure what happened...

Link to comment
Share on other sites

Quote

 

Though I am able to access the old volume fine from the new install so I'm not sure what happened...


 

 

That's strange, wouldn't hurt to check it via terminal:

 

diskutil list


 

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *480.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         479.9 GB   disk0s2

You need to locate your APFS container, in my case /dev/disk0s2

then 

 

sudo fsck_apfs -n -l /dev/disk0s2

 

-n does not fix errors

-l allows to check a mounted filesystem

 

good luck !

Link to comment
Share on other sites

 Share

×
×
  • Create New...