![]() ![]() Whole bunch of these temp files trimmed from listing Using cacheBlockSize=32K cacheTotalBlock=32768 cacheSize=1048576K.Įxecuting fsck_hfs (version hfs-522.100.5).ĬheckCatalogBTree: fileCount = 421327, fileThread = 421326 #Updating openzfs on os x macIt would have been possible to also boot the system in rescue mode but the Mac I connected to via TDM was running a newer version of macOS and I was hoping that the tooling would be better able to deal with such an issue though fsck_hfs(8) bugs section states “ fsck_hfs is not able to fix some inconsistencies that it detects“, regardless. It would attempt to repair the file system 3 times, fail, and switch off.Ĭonnecting to another Mac via TDM, it was possible to mount the filesystem as read only and take a closer look. Since the filesystem had problems, the system would try to boot, the grey screen with the Apple logo would appear along with a progress bar which would move from left to right and then after some time the system would switch off.īooting the system in verbose mode by holding command + v showed that the system was running fsck on boot which is what the progress bar was an indicator for normally. Through doing this, the HFS+ journaled file system ended up with problems where fsck_hfs(8) was unable to fix the issue. The user was not aware of this issue and assumed whenever the system wouldn’t display anything on boot, it was the POST issue and would power cycle the system, hoping to strike it lucky. The system also had a failing Cinema Display which would work fine after a “cold” power cycle having removed the power connector from PSU and reattached, but would fail to wake from sleep if it had been left on. Luckily the issue was resolved by reseating things. ![]() ![]() The boot issue manifested itself as the system not POSTing and the fans spinning loudly. #Updating openzfs on os x proI was sitting in front of a Mac Pro which had previously suffered from boot issues due to the expansion boards holding the memory not making contact with the logic board properly. I think your best bet would probably be to try ALSOFT’s Disk Warrior if you need to fix this issue. Note: this post doesn’t provide a solution to address the “Incorrect number of thread records” file system issue but documents what I went through to see if I could when I faced it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |