G-RAID Shuttle 8 causes reboot when connected via Thunderbolt on macOS Sequoia 15.5

Question

G-RAID Shuttle 8 causes reboot when connected via Thunderbolt on macOS Sequoia 15.5

Hi,

I’m experiencing a serious issue when connecting a G-RAID Shuttle 8 (96 TB) to my MacBook Pro M1 Max running macOS Sequoia 15.5.

When I connect the drive via a direct Thunderbolt 4 port, the system immediately crashes and reboots. I’ve tested with different certified Thunderbolt cables, but the issue persists.

Interestingly, when I connect the same unit through the Thunderbolt port of my Studio Display, the drive works — but macOS shows it as connected via USB, not Thunderbolt. So the unit is clearly functional, but Thunderbolt is not working as expected on the direct Mac ports.

In Safe Mode, the drive works via Thunderbolt without crashing, and the manufacturer’s support team confirmed the unit is not faulty. They suspect a macOS/Thunderbolt compatibility issue.

I’ll try testing the drive on a different Mac, but I need to work on this machine.

Has anyone encountered this kind of behavior on Sequoia 15.5?

Any ideas on how to force proper Thunderbolt behavior or debug this crash?

Thanks in advance for any help!

MacBook Pro 16″, macOS 15.5

Posted on Jul 23, 2025 8:48 AM

Reply

Answer 1

Jul 23, 2025 8:53 AM in response to danielemolineris

danielemolineris wrote:

In Safe Mode, the drive works via Thunderbolt without crashing, and the manufacturer’s support team confirmed the unit is not faulty. They suspect a macOS/Thunderbolt compatibility issue.

If it works properly in Safe Mode, that means the issue is not with macOS but rather with a 3rd party extension that is installed on that system.

Reply

Answer 2

Jul 23, 2025 11:11 PM in response to danielemolineris

Update:

I tested the G-RAID Shuttle 8 on another Mac (Intel-based, also running Sequoia 15.5), and it works perfectly without needing any drivers — so the issue seems specific to Apple Silicon + Thunderbolt + Sequoia 15.5.

Driver is installed and system extension is allowed via Recovery Mode.

At this point it seems like a Thunderbolt + kernel extension conflict under standard startup on Apple Silicon.

Any suggestions on how to trace the conflict?

Thanks again!

Reply

Answer 3

dsm363

Level 1

20 points

Aug 4, 2025 7:37 PM in response to danielemolineris

I'm having this same issue but with a M4 Max Mac Studio and a G-RAID Shuttle 4. Apple says it's likely the G-RAID and SanDisk think it's Apple.

The G-RAID is plugged directly into the Thunderbolt port on the back of the Mac. I turned off putting the display to sleep and so far, the computer hasn't rebooted on its own.

Reply

Answer 4

Jul 23, 2025 11:12 PM in response to neuroanatomist

Thanks for your reply! That’s exactly what I’m starting to suspect too.

I’ve already tried disabling most login items and background apps, but the issue still occurs.

Next step will probably be a clean macOS install to rule out any third-party kernel extensions or system modifications.

If you know of any tools or methods to detect which extension might be conflicting with Thunderbolt during normal boot, I’d really appreciate any suggestions!

Reply

Answer 5

dsm363

Level 1

20 points

Aug 5, 2025 6:09 AM in response to dsm363

My Apple Studio display was scheduled to sleep after 8 hours before. Now the screen saver is on all the time. 16 hours later the Mac is still working. Hasn't rebooted yet. So I'll call Apple back. Not sure why the monitor sleeping would cause this though since there is nothing plugged into the ports on the monitor.

Reply