external Samsung T7 crashing both Macs (crash logs)

[JamesMay82]

just gone to plug in my T7 drive into 2015 MacBook Pro and it crashed. double checked in on 2014 iMac and it did the same.

here is the crash log - does it mean anything to anyone?

Edit - I was using usb to usb c cable on my older Macs and just tried it on my new machine which is m2 Studio via usb c to C cable and its also crashed that with the same code. I've had the drive a year or so but rarely use it but the fact it's crashing on all Macs must say the drive is dead? my T5 drive still works with the same cables so its def not a cable issue. If it is dead, I'm very lucky to have a back up of this drive.

panic(cpu 6 caller 0xffffff8015e32a4e): "jnl: do_jnl_io: curlen == 0, offset 0x3a7be00 len 0\n" @hfs_journal.c:353
Panicked task 0xffffff86b108cd40: 1 threads: pid 390: mount_hfs
Backtrace (CPU 6), panicked thread: 0xffffff9517202000, Frame : Return Address
0xffffffcb02ff30b0 : 0xffffff8014279a3d
0xffffffcb02ff3100 : 0xffffff80143dca26
0xffffffcb02ff3140 : 0xffffff80143cbd93
0xffffffcb02ff3190 : 0xffffff8014219a90
0xffffffcb02ff31b0 : 0xffffff8014279e0d
0xffffffcb02ff32d0 : 0xffffff80142795c6
0xffffffcb02ff3330 : 0xffffff8014b149d3
0xffffffcb02ff3420 : 0xffffff8015e32a4e
0xffffffcb02ff3490 : 0xffffff8015e338fe
0xffffffcb02ff35f0 : 0xffffff8015e6adc6
0xffffffcb02ff36b0 : 0xffffff8015e58b53
0xffffffcb02ff3800 : 0xffffff8015e51388
0xffffffcb02ff38a0 : 0xffffff8014529fd0
0xffffffcb02ff3b00 : 0xffffff801452b862
0xffffffcb02ff3f00 : 0xffffff801452b42e
0xffffffcb02ff3f40 : 0xffffff8014986aab
0xffffffcb02ff3fa0 : 0xffffff801421a256
      Kernel Extensions in backtrace:
         com.apple.filesystems.hfs.kext(583.100.10)[3AB0653D-B9CA-301E-8D1E-DA4ECB57B6D9]@0xffffff8015e1e000->0xffffff8015e7cfff
            dependency: com.apple.filesystems.hfs.encodings.kext(1)[1E25D938-506D-3AEC-B104-42C25963DCE0]@0xffffff8015e83000->0xffffff8015e84fff

Process name corresponding to current thread (0xffffff9517202000): mount_hfs

Mac OS version:
21G1974

Kernel version:
Darwin Kernel Version 21.6.0: Thu Nov  9 00:38:19 PST 2023; root:xnu-8020.240.18.705.10~1/RELEASE_X86_64
Kernel UUID: ABAADB03-E25C-33B4-B3E0-574627B92635
KernelCache slide: 0x0000000014000000
KernelCache base:  0xffffff8014200000
Kernel slide:      0x0000000014010000
Kernel text base:  0xffffff8014210000
__HIB  text base: 0xffffff8014100000
System model name: MacBookPro11,4 (Mac-06F11FD93F0323C5)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 26326476603
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000006212e2afa
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000008103c49e4 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff804889b000 - 0xffffffa04889b000
  . PGZ   : 0xffffff804889b000 - 0xffffff804a89c000
  . VM    : 0xffffff804a89c000 - 0xffffff851709b000
  . RO    : 0xffffff851709b000 - 0xffffff86b089b000
  . GEN0  : 0xffffff86b089b000 - 0xffffff8b7d09b000
  . GEN1  : 0xffffff8b7d09b000 - 0xffffff904989b000
  . GEN2  : 0xffffff904989b000 - 0xffffff951609b000
  . GEN3  : 0xffffff951609b000 - 0xffffff99e289b000
  . DATA  : 0xffffff99e289b000 - 0xffffffa04889b000
  Metadata: 0xffffffa048ffb000 - 0xffffffa068ffb000
  Bitmaps : 0xffffffa068ffb000 - 0xffffffa06effb000

last started kext at 20197396791: >driverkit.serial    6.0.0 (addr 0xffffff7fad4ae000, size 28672)
loaded kexts:
>AudioAUUC    1.70
>!APlatformEnabler    2.7.0d0
>AGPM    129
>X86PlatformShim    1.0.0
@filesystems.autofs    3.0
>!AUpstreamUserClient    3.6.9
>!AHDAHardwareConfigDriver    340.2
>!AHDA    340.2
>eficheck    1
>!A!IHD5000Graphics    18.0.8
>!AGraphicsDevicePolicy    6.5.7
>!ALPC    3.1
>AGDCBacklightControl    6.5.7
@AGDCPluginDisplayMetrics    6.5.7
>!ACameraInterface    7.9.1
>pmtelemetry    1
|IOUserEthernet    1.0.1
>usb.!UUserHCI    1
>!AHV    1
>!ADiskImages2    126.141.2
>!AMuxControl    6.5.7
>!ABacklight    180.8
>!AThunderboltIP    4.0.3
>!A!ISlowAdaptiveClocking    4.0.0
>!ASMCLMU    212
>!AFIVRDriver    4.1.0
>ACPI_SMC_PlatformPlugin    1.0.0
>!AMCCSControl    1.16
>!A!IFramebufferAzul    18.0.8
|SCSITaskUserClient    456.140.3
>!ATopCaseHIDEventDriver    5450.8
>!UTopCaseDriver    5450.8
>!UCardReader    533.120.2
>AirPort.BrcmNIC    1400.1.1
>!AAHCIPort    351.100.4
>!AFileSystemDriver    3.0.1
@filesystems.tmpfs    1
@filesystems.lifs    1
@filesystems.apfs    1934.141.2
@filesystems.hfs.kext    583.100.10
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
@private.KextAudit    1.0
>!ASmartBatteryManager    161.0.0
>!AACPIButtons    6.1
>!ARTC    2.0.1
>!AHPET    1.8
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    402
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
@Dont_Steal_Mac_OS_X    7.0.0
@kec.!AEncryptedArchive    1
>driverkit.serial    6.0.0
|IOSerial!F    11
@kext.triggers    1.0
>!UAudio    416.2
>!AAudioClockLibs    140.1
>DspFuncLib    340.2
@kext.OSvKernDSPLib    529
>!ASMBusPCI    1.0.14d1
>!AHDA!C    340.2
|IOHDA!F    340.2
|IOAudio!F    340.2
@vecLib.kext    1.2.0
|IO!BSerialManager    9.0.0
|IO!BPacketLogger    9.0.0
|IO!BHost!CUSBTransport    9.0.0
|IO!BHost!CUARTTransport    9.0.0
|IO!BHost!CTransport    9.0.0
>IO!BHost!CPCIeTransport    9.0.0
|IOAVB!F    1040.6
@plugin.IOgPTPPlugin    1040.3
|IOEthernetAVB!C    1.1.0
|CSR!BHost!CUSBTransport    9.0.0
|Broadcom!BHost!CUSBTransport    9.0.0
|Broadcom!B20703USBTransport    9.0.0
>!AIPAppender    1.0
>!AGraphicsControl    6.5.7
@!AGPUWrangler    6.5.7
>!ABacklightExpert    1.1.0
|IONDRVSupport    597
>!AThunderboltEDMSink    5.0.3
>!AThunderboltDPOutAdapter    8.5.1
|IOSlowAdaptiveClocking!F    1.0.0
>IOPlatformPluginLegacy    1.0.0
>X86PlatformPlugin    1.0.0
>IOPlatformPlugin!F    6.0.0d8
>!ASMBus!C    1.0.18d1
|IOAccelerator!F2    462.9
@!AGraphicsDeviceControl    6.5.7
|IOGraphics!F    597
>!AActuatorDriver    5460.1
>!AHS!BDriver    5450.8
>IO!BHIDDriver    9.0.0
>!AMultitouchDriver    5460.1
>!AInputDeviceSupport    5460.1
>!AHIDKeyboard    228.2
>usb.IOUSBHostHIDDevice    1.2
>usb.cdc    5.0.0
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
>!AThunderboltDPInAdapter    8.5.1
>!AThunderboltDPAdapter!F    8.5.1
>!AThunderboltPCIDownAdapter    4.1.1
>!AXsanScheme    3
>!AThunderboltNHI    7.2.81
|IOThunderbolt!F    9.3.3
|IOAHCIBlock!S    333.140.2
|IO80211!FLegacy    1200.12.2b1
|IOSkywalk!F    1.0
>mDNSOffloadUserClient    1.0.1b8
>corecapture    1.0.4
|IOAHCI!F    297
>!A!ILpssGspi    3.0.60
>usb.!UXHCIPCI    1.2
>usb.!UXHCI    1.2
>!ABSDKextStarter    3
|IOSurface    302.15
@filesystems.hfs.encodings.kext    1
>usb.!UHostPacketFilter    1.0
|IOUSB!F    900.4.2
>!AEFINVRAM    2.1
>!AEFIRuntime    2.1
|IOSMBus!F    1.1
|IOHID!F    2.0.0
|IOTimeSync!F    1040.3
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    9.0.0
|IOReport!F    47
$quarantine    4
$sandbox    300.0
[USER=381322]@Kext[/USER].!AMatch    1.0.0d1
|CoreAnalytics!F    1
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    533.120.2
|IOUSBMass!SDriver    210.120.3
|IOSCSIBlockCommandsDevice    456.140.3
|IO!S!F    2.1
|IOSCSIArchitectureModel!F    456.140.3
>!AMobileFileIntegrity    1.0.5
$!AImage4    4.2.0
@kext.CoreTrust    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!ACredentialManager    1.0
>KernelRelayHost    1
|IOUSBHost!F    1.2
>!UHostMergeProperties    1.2
>usb.!UCommon    1.0
>!ABusPower!C    1.0
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AACPIPlatform    6.1
>!ASMC    3.1.9
|IOPCI!F    2.9
|IOACPI!F    1.4
>watchdog    1
@kec.pthread    1
@kec.Libm    1
@kec.corecrypto    12.0

 

[Fishrrman]

Something to try:

Take the drive to the 2015 MBP or the 2014 iMac. Either one.

Shut that Mac down first.
Then, boot into "safe mode" (by holding down the shift key CONTINUOUSLY at boot).
Get logged in and into the finder.
NOW, connect the t7.

Does it still crash the Mac?
(safe mode boots up WITHOUT loading extensions)

 

[JamesMay82]

Something to try:

Take the drive to the 2015 MBP or the 2014 iMac. Either one.

Shut that Mac down first.
Then, boot into "safe mode" (by holding down the shift key CONTINUOUSLY at boot).
Get logged in and into the finder.
NOW, connect the t7.

Does it still crash the Mac?
(safe mode boots up WITHOUT loading extensions)

Thanks - I tried this and at the log in it says safe mode in top menu bar but once logged in the safe mode disappears from the top right, is that correct?

I just connected the drive and it crashed the computer again? are you thinking the drive is fine but its just some sort of glitch with software? its not working on my iPad either but at least its not crashing my iPad but its just showing solid blue light. I think the iPad was maybe the last thing I used it on when I was transferring files over.

Any other ideas? its very annoying as drive has only been used sparingly as is only a year old

 

[Fishrrman]

Do you have available a Windows computer, on which you could try the drive?
Just to see what happens?

I don't recall ever seeing a drive that would "crash the computer" when it was connected.
Plenty of drives that gave "this disk is unreadable".
But no outright "crashes"...

I'm wondering if there could be some kind of internal failure inside?
(I have a couple of t7 shields myself)

 

[JamesMay82]

Do you have available a Windows computer, on which you could try the drive?
Just to see what happens?

I don't recall ever seeing a drive that would "crash the computer" when it was connected.
Plenty of drives that gave "this disk is unreadable".
But no outright "crashes"...

I'm wondering if there could be some kind of internal failure inside?
(I have a couple of t7 shields myself)

unfortunately I don't but odd its happening on new and old Macs. I'm annoyed as it's fairly new. it literally pops up with the black screen saying it crashed and then restarts the second I connect the drive.

it never travels, it just sits in desk draw so I know its not had a drop.

 

[Fishrrman]

One more thing to try:
Different connecting cables.

 

[JamesMay82]

One more thing to try:
Different connecting cables.

sadly that also crashed it!

so bizare its just stopped working all of a sudden.

 

[eRondeau]

Wouldn't hurt to check if a Firmware Update is available for your T7. A few years ago I bought an external NVMe SSD enclosure that was unusable "out of the box" due to constant ejections. But a quick firmware update made it perfect and it's been working flawlessly for 3+ years now.

 

[FreakinEurekan]

What exactly is "Crashing" - is macOS itself halting (e.g. a Kernel Panic), or does macOS continue working but the disk doesn't mount?

If it's just the disk not mounting, open up Disk Utility and see if you can Erase it.

If the computer is completely shutting down, boot to Recovery (boot with Command-R) and open Disk Utility there, then plug in the T7 and see if you can erase it there.

 

[JamesMay82]

What exactly is "Crashing" - is macOS itself halting (e.g. a Kernel Panic), or does macOS continue working but the disk doesn't mount?

If it's just the disk not mounting, open up Disk Utility and see if you can Erase it.

If the computer is completely shutting down, boot to Recovery (boot with Command-R) and open Disk Utility there, then plug in the T7 and see if you can erase it there.

I went into recovery mode disk utility and then plugged in the drive and it crashed that. By crashed I mean the screen goes black and then restarts and it lets me see the crash log I posted in first message.

If I leave drive plugged in, once I then log into my user account it just crashes it again, restarts and repeats doing so till I unplug the drive.

I was using this drive at Christmas time so utterly bizarre its just stopped working. My T5 drive is fine and I've used 3 different cables on 4 different Macs.

The drive is barely a year old with minimal use.

any other ideas?

 

[JamesMay82]

Wouldn't hurt to check if a Firmware Update is available for your T7. A few years ago I bought an external NVMe SSD enclosure that was unusable "out of the box" due to constant ejections. But a quick firmware update made it perfect and it's been working flawlessly for 3+ years now.

yeah I can't keep the Mac switched on to do any of that. it just instantly restarts my machines every time.

 

[Fishrrman]

I'm wondering if there's an internal short or something along that line.

Again, I'll suggest you try it on a PC if possible. Perhaps at a computer repair shop?

If it still crashes the PC -- as well as any Mac to which it's attached -- I'm going to GUESS that there's not going to be much hope for it. No way to "repair" anything "inside" it.

 

[JamesMay82]

I'm wondering if there's an internal short or something along that line.

Again, I'll suggest you try it on a PC if possible. Perhaps at a computer repair shop?

If it still crashes the PC -- as well as any Mac to which it's attached -- I'm going to GUESS that there's not going to be much hope for it. No way to "repair" anything "inside" it.

Good news!

I tried it on my PS5 and that let me reformat it. now plugged into Mac and its let me re format it to APFS and its working like it should!

Thanks for your help!

but the million dollar question is can I/should I trust it! any ideas what could of gone wrong with it. the last thing I did with it was copy 800 gigs of video files to my iPad and then I've not used it since. maybe some issue that the iPad caused?

 

[chrfr]

Good news!

I tried it on my PS5 and that let me reformat it. now plugged into Mac and its let me re format it to APFS and its working like it should!

Thanks for your help!

but the million dollar question is can I/should I trust it! any ideas what could of gone wrong with it. the last thing I did with it was copy 800 gigs of video files to my iPad and then I've not used it since. maybe some issue that the iPad caused?

Now that you have the disks in a state where they don't panic the Macs, download and install the Samsung external SSD software and check the disks for firmware updates. That app installer is found on this page: Tool & Software Download | Samsung Semiconductor USA and there is a specific one for the T7 series disks.

 

[G46&Fbnth5]

It happened the same thing to me, immediately after using the drive (Samsung T9 in my case) with an iPad. Luckily I was able to repair it and retrieve all the data with a Windows PC.

 

[JamesMay82]

It happened the same thing to me, immediately after using the drive (Samsung T9 in my case) with an iPad. Luckily I was able to repair it and retrieve all the data with a Windows PC.

ah so the iPad's the culprit! that makes me feel a bit better about using the drive again.. will just keep it Mac only.

 

[Snoeckie99]

I have the exact same problem!! I use my T7 for backing up recent photos from my iPad and Mac (after a while I'll transfer them to a bigger external HDD). I also partitioned it as a Time Machine drive for my Mac.

On a random forum from years ago, someone said partitioning an external drive for Time Machine gave problems for him. I'm unsure of the onset of problems with my drive, but my Mac crashes fully as soon as I plug the drive in. I hope I'm able to recover the data as it has photos of recent shoots I've not backed up to any other drive 😬 hoping my friends windows laptop will save me 🤞

@JamesMay82 was your T7 also used for Time Machine?
thanks in advance!

My setup:
- Samsung T7
- MacBook Pro 2015
- iPad Pro 11 inch 3e Gen

 

[JamesMay82]

I have the exact same problem!! I use my T7 for backing up recent photos from my iPad and Mac (after a while I'll transfer them to a bigger external HDD). I also partitioned it as a Time Machine drive for my Mac.

On a random forum from years ago, someone said partitioning an external drive for Time Machine gave problems for him. I'm unsure of the onset of problems with my drive, but my Mac crashes fully as soon as I plug the drive in. I hope I'm able to recover the data as it has photos of recent shoots I've not backed up to any other drive 😬 hoping my friends windows laptop will save me 🤞

@JamesMay82 was your T7 also used for Time Machine?
thanks in advance!

My setup:
- Samsung T7
- MacBook Pro 2015
- iPad Pro 11 inch 3e Gen

No i just used mine for a manual back up and moving larger files between machines. Ive put my issues down to the iPad maybe corrupting something on the drive as that was the last time it worked before I plugged it back into my Mac.

The only device it worked on was my ps5 which I used to wipe it so maybe you can use that to access files on there.. or maybe try a windows machine?

 

[Snoeckie99]

Okay I’m so happy I found a solution online that worked after a lot of hours of frustration
A recurring thing i read was that the ‘auto mounting’ of the drive on MacOS is part of the problem, I’m not a computer guy but I thing it means something like the Mac instantly wants to check, read and write on the connected drive. Thus by disabling ‘auto mount’ and just ‘reading’ the drive, you’re able to access all the data.
The problem seems to occur to people using it on both an iPad-Mac, randomly in time (I’ve been using this drive for 2 years).

How I was able to back up everything using the Mac that kept crashing after plugging in the external SSD:
(I suggest to read the whole thing first before trying it immediately)

• A program called Disk Arbitrator (Site to download the App)
  • This app wouldn’t open because of a safety feature “Cannot be opened because the developer cannot be verified”, I did however trust the app at my own risk since other people used it on other forums.
  • This app blocks ‘Auto-Mount’ and gives you two options: ‘Block mounts’ and ‘Read-only’
  • If you have the same problem when trying to open the app. Go to System Preferences-> Security & Privacy -> General Tab -> click the Lock icon and enter your Mac login -> You should see the blocked app and be able to allow it (More info here - Methode 4) -> Start the app
• So now the app should be open and display: ☑️ Activated Mode: Read-only
• Time to plug in the external drive
  • From here you should be able to access all the files

Since I wanted to back up this drive to an other drive, I plugged in the other drive before starting the Disk Arbitrator application. By doing this, you still allow it to write on this drive. After launching the app followed by plugging in the problematic drive, this one won’t be writable.

I’ll be happy to help if anyone has a problem with this method
Or help other people if you have an easier method.

Good Luck, hope this works for everyone and saves you from losing files.
A note to myself, a back up on only one drive is equal to no back up at all. Gotta back up to more drives