Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

vs40

macrumors member
Original poster
Jan 9, 2016
79
85
Hi folks!
After updating my MBA M1 to Sequoia 15.2 (24C101) I have very slow write speed on my external SSD(Samsung T7 Shield).
Write speed is slower than an old HDD.
I thought my drive is dying, but it has normal speed with Windows laptop and Samsung app shows good health status.
Any ideas?

SCR-20241217-olrl.png
 
You aren't the only one who has seen this problem.

I have two Samsung t7 "shield" drives (each 1tb) and they exhibit the problem.

Typically, when I first connect the drive, and try a speedtest on it (before doing anything else), it will offer up fast read speeds, but write speeds are TERRIBLE (as seen in the OP's post above). Both my drives are formatted HFS+.

Here's an "AJA System Test Lite" reading I just recorded while composing this reply:
AJA 1.jpg


There's SOMETHING -- whether it be in the drive's circuitry, or elsewhere -- that is failing to establish proper communication speeds with the Mac when first connected.

I happen to have an old copy of Drive Genius, and it offers "repair" and "rebuild" options for drives (the latter being a modest "directory rebuild", not sure?).

I opened DG3, and ran the rebuild option on the drive.
Here are the results:
===============
Repairing volume...
Checking Journaled HFS Plus volume.
The volume name is t7 Movie & TV Archive
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume t7 Movie & TV Archive appears to be OK.
Rebuilding volume...
Checking Journaled HFS Plus volume.
The volume name is t7 Movie & TV Archive
Checking extents overflow file.
Checking catalog file.
Rebuilding catalog B-tree.
Rechecking volume.
Checking Journaled HFS Plus volume.
The volume name is t7 Movie & TV Archive
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
Invalid volume file count
(It should be 1338 instead of 1316)
Invalid volume directory count
(It should be 271 instead of 270)
Invalid volume free block count
(It should be 106642522 instead of 106838533)
Volume header needs minor repair
Repairing volume.
Rechecking volume.
Checking Journaled HFS Plus volume.
The volume name is t7 Movie & TV Archive
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume t7 Movie & TV Archive was repaired successfully.
Verifying volume...
Checking Journaled HFS Plus volume.
The volume name is t7 Movie & TV Archive
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume t7 Movie & TV Archive appears to be OK.
===============

Note the following that was found:
"Invalid volume file count
(It should be 1338 instead of 1316)
Invalid volume directory count
(It should be 271 instead of 270)
Invalid volume free block count
(It should be 106642522 instead of 106838533)
Volume header needs minor repair
Repairing volume."

But... over the course of months... the problem will "be back" each time I connect the drive. The "fix" doesn't "stick".

HAVING SAID ALL THAT...
I've found that if you "plow through" -- that is, cancel and then restart the test several times -- the write speeds will suddenly "jump upwards" to where they SHOULD be.

Here's what happened if I stopped, and then restarted the AJA test 3 or 4 times:
AJA 2.jpg


Not sure if this matters with APFS formatted drives or not.
My other t7 has a single APFS partition on it, but it's not near at the moment.

My advice to the OP:
Try AJA System Test Lite (free)
or
Try Blackmagic Disk Speed Test.

If the initial write result is bad, stop and restart the test.
Repeat this about 4-5 times.
See if the write speeds suddenly "break through" and jump up to where they should be...
 
If the initial write result is bad, stop and restart the test.
Repeat this about 4-5 times.
See if the write speeds suddenly "break through" and jump up to where they should be...
You are right, after few iterations speeds are normal again, but it's not a solution for me.
I use my external drive for quick file download/transfer and I can't do those rituals every time to bring performance back.
According to some user-reports last macOS version with proper external drive behavior was Monterey.
If I don't find proper solution till weekend, I might downgrade from Sequoia.
 
You are right, after few iterations speeds are normal again, but it's not a solution for me.
I use my external drive for quick file download/transfer and I can't do those rituals every time to bring performance back.
According to some user-reports last macOS version with proper external drive behavior was Monterey.
If I don't find proper solution till weekend, I might downgrade from Sequoia.
I would at least start by installing Samsung Magician and checking the disk for firmware updates. I’m not clear if you did that step in Samsung app when you checked the drive already. I’d also suggest trying a different cable and also physically moving the drive somewhat to make sure you’re not getting some sort of interference.
What format are these drives? The errors in post 2 of the thread are typical of disks formatted as HFS+/MacOS Extended, and there’s really not any great reason to keep using that format anymore as it’s much less robust than APFS is.
 
I would at least start by installing Samsung Magician and checking the disk for firmware updates. I’m not clear if you did that step in Samsung app when you checked the drive already. I’d also suggest trying a different cable and also physically moving the drive somewhat to make sure you’re not getting some sort of interference.
All those steps are already done, but no results.

What format are these drives? The errors in post 2 of the thread are typical of disks formatted as HFS+/MacOS Extended
Post 2 is from another user, not from me.
All my drives are exFAT, because I need cross platform support.
And I have this problem only with MBA Sequoia.
 
OP wrote:
"According to some user-reports last macOS version with proper external drive behavior was Monterey.
If I don't find proper solution till weekend, I might downgrade from Sequoia."


I don't believe that the "OS version" has anything to do with the problem with the t7 SSDs.

All the tests I performed in reply 2 above were on a 2018 Mini (Intel) still running OS 10.14.6 "Mojave".

It's "in the drive" -- NOT the OS.

For this reason, I can no longer recommend Samsung t7 "shield" drives.
There's a problem with them that Samsung (to my knowledge) won't fix.

These days, I recommend the Crucial X9 (USB3.1 gen2). Offers up good speeds from the moment it's connected...

chrfr chimes in with:
"I would at least start by installing Samsung Magician"

UGH.
That's what I tried last night (on my 2021 MacBook Pro 14").
Awful, AWFUL software.

So then, I tried to remove it -- you can't get rid of it.
It put an icon into the dock that couldn't be removed through normal procedures.

I finally used EasyFind to locate all the pieces, and managed to delete them one-by-one.

Final thoughts on Samsung drives:
They're to be avoided.
I've seen many reports from forum members having trouble with Samsung drives, either the nvme format drives, or -- like now -- with the external SSDs.

I'll use other drives in the future...
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.