Hello Community,
I haven’t found any similar problem in this forum, so I’m posting a dedicated topic.
As the title indicates, my MacBookPro 8,2 (late 2011) w/ MacOS Sierra crashes every time I connect my G-Drive 2 TB to it.
Here are the details :
Product: G-DRIVE 2 TB - 2010 (if I remember well)
Formatted in HFS+ not journaled
Mac OS System crash:
Tests:
1) On MacBook 5,2 (mid-2009) with OS X El Capitan, no app running
a. Drive connected on Mac Firewire port (FW port #1 on drive) : after 1 min, crash. Drive does not appear in finder, but just before crash appears in DiskUtility
b. Drive connected on Mac Firewire port (FW port #2 on drive) : after 1 min, crash. Drive does not appear in finder, but just before crash appears in DiskUtility
c. Drive connected on Mac USB port : after 1 min, crash. Drive does not appear in finder, but just before crash appears in DiskUtility
2) On MacBook Pro 8,1 (Late 2011) with MacOS Sierra (10.12.1), no app running
a. Drive connected on Mac Firewire port (FW port #1 on drive) : after 1 min, crash. Drive does not appear in finder, but just before crash appears in DiskUtility
b. Drive connected on Mac Firewire port (FW port #2 on drive) : after 1 min, crash. Drive does not appear in finder, but just before crash appears in DiskUtility
c. Drive connected on Mac USB port : after 1 min, crash. Drive does not appear in finder, but just before crash appears in DiskUtility
d. Drive connected on Thunderbolt port through Kanex Thunderbolt to eSata & USB 3 adapter. Drive connected on eSata port: after 1 min, crash. Drive does not appear in finder, but just before crash appears in DiskUtility
Beginning of MacOS Error report for 1)a: “panic(cpu 0 caller 0xffffff801bcf427a): “hfs: extendbtree: fcb 0xffffff80301a8500 has eof 0xb0e5000 not a multiple of 0x2000 (trim 0)\n”@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3248.60.11/bsd/hfs/hfs_btreeio.c:542”
Comments:
- Drive is correctly mounted on Windows 10 and content readable thanks to HFS drivers (from Mac BootCamp).
- Drive is correctly mounted in read/write on Raspberry Pi B+ Raspbian vXXXX.
- Not tested with Paragon drivers on Windows.
As I’ve been using this G-Drive nearly exclusively on my Raspberry Pi B+, it might be due to obsolete HFS(+) drivers on Raspbian (Debian-based) that could have caused some corruption of fundamental reference tables/sectors for MacOS specifically. MacOS would be more strict in the way it mounts HFS+ volumes.
Thanks for your help!
