- USE OMNIDISKSWEEPER INSTALL
- USE OMNIDISKSWEEPER PRO
- USE OMNIDISKSWEEPER SOFTWARE
- USE OMNIDISKSWEEPER FREE
This allows a user to easily find the largest files on a drive and is great for clearing up free space (such as when preparing to migrate to a smaller solid state drive). However, in Mac Geek Gab 355, listener Joe found that it doesn’t always show everything. OmniDiskSweeper scans the files and folders of your Mac’s hard drive and displays a list, in order of file size, of the contents of your drive. Just make sure to have a backup of all your data before attempting any of those workarounds.Long time Mac Geek Gab listeners know that using OmniDiskSweeper is a fantastic (free!) way to find out what files are taking up all your precious hard drive or SSD space.
I've never tried any of those "fixes" so the links are the best I can do there unless another contributor with more experience chimes in here with more specific instructions. It is possible recovery mode may not be using the discrete GPU so this could be misleading or the GPU issue decided to just work at that particular time (that is always a problem trying to troubleshoot an intermittent issue).Ĭheck out the links I provided in my previous post to force the laptop to use the Intel GPU instead as that can allow you to continue using the laptop if you do not need the capabilities of the discrete GPU.
USE OMNIDISKSWEEPER SOFTWARE
If this works without an issue, then it may indicate a software issue. You could try booting into Internet Recovery Mode using Command + Option + R which will bypass the local recovery mode which could have issues.
USE OMNIDISKSWEEPER INSTALL
You can always perform a clean install of macOS or a restore from a previous backup to confirm though. I don't see Omni DiskSweeper causing a hardware failure with the GPU (a software issue maybe). I really do think it is just a coincidence by the description of the issue. I highly doubt this is the case, but there is always a slight possibility. I believe I have used Omni DiskSweeper with "sudo" before and I had no issues, although a bug or accidental deletion could have unforeseen consequences. Any help would be great, because I’m not sure if this happen again in the 24-48 hrs. Did the terminal command Sudo damage my GPU or cause havoc on the logic board? If its working perfectly fine(for now) was there ever an issue with the GPU in the first place. I forgot to mention that I used target disk mode with a MacBook air and the hard drive was perfectly fine. I woke up to attempt to turn the computer on and the computer(albeit with a slight graphical issue in the boot(strange line), booted up successfully and now the MacBook’s desktop and everything else looks fine.
I kept trying to fix the MacBook until I gave up at about 4am in the morning. The two that really stood out were ConfigureInterests - nElements <= 0! Failed to configure interests and IO80211Controller::addSubscription() Failed to addSubscription for group Chip subgroup.
USE OMNIDISKSWEEPER PRO
I then went to verbose or single user mode(one of the two) and I saw too significant failures in the code(I am not a pro and I looked up the meanings of the code). I then consulted Apple who told me to go through the same procedures to no avail. The test passed successfully, but I continued to have problems. I used SMC NVPRAM resets, attempted recovery mode/disk utility but ended up with a dark blue screen, safe mode, and even tried the Apple Hardware Test. The screen was flickering, turning different colors, discoloration, graphics all over the place, and within twenty minutes the computer was stuck on the boot screen. Within seconds, my computer’s graphics went haywire. I saw others used this same command and had the same cryptic message, but everything was fine. After putting in the command I got a strange message: OCCCrashCatcher: Not enabling crash catching since we're connected to a tty (and thus presumably in gdb). I read that many were successful using the software with the terminal command: sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper. I was cleaning out my early MacBook pro 2011 i7 2.2 and decided to use Omni Disksweeeper. It seems to be working, now but who knows.