General NVMe Drive Problems (Fatal)

[pastrychef]

*OR* invest significantly less money in the same system you already own, running Linux (or BSD) coupled with KDE Plasma. What's that expression... More bounce to the ounce?!

Yeah... Windows is also an option but neither are what I want to use everyday.

 

[FormerUser-400995]

Yeah... Windows is also an option but neither are what I want to use everyday.

I'm fairly comfortable with most any OS, yet I still find fault with every one that I use. When someone asks which OS I favour, well, it's difficult to give an honest appraisal, without offending.

 

[pastrychef]

I'm fairly comfortable with most any OS, yet I still find fault with every one that I use. When someone asks which OS I favour, well, it's difficult to give an honest appraisal, without offending.

I use Linux and Windows when I must but my OS of choice is macOS.

 

[FormerUser-400995]

I use Linux and Windows when I must but my OS of choice is macOS.

What I like most about using multiple OS's is that nobody can call you a true fan boy.

 

[pastrychef]

What I like most about using multiple OS's is that nobody can call you a true fan boy.

People can call me what they like. I really don't care what they think. I know which OS I'm most comfortable with and which OS I know best and I'm not afraid to admit it.

I'm afraid of doing things in Windows because it has broken on me so many times. I'm a little more comfortable with Linux but there has been too many times where trying to fix things send me down rabbit holes that I couldn't get out of for days and sometimes still can't resolve problems.

 

[FormerUser-400995]

People can call me what they like. I really don't care what they think. I know which OS I'm most comfortable with and which OS I know best and I'm not afraid to admit it.

I'm afraid of doing things in Windows because it has broken on me so many times. I'm a little more comfortable with Linux but there has been too many times where trying to fix things send me down rabbit holes that I couldn't get out of for days and sometimes still can't resolve problems.

Don't get me started on Windows. I remember when I was much younger and my mother asked what I wasted for my birthday. I said, a cowboy outfit!! So, she offered to buy Microsoft for me.

I declined.

 

[c0c0p0ps]

There are several threads surrounding the Monterey/NVMe issues, and in particular the Samsung 970 EVO. I'd like to know if I clearly understand the issue with the 970.
1) The issue is ONLY long boot times because of TRIM. Once booted, the system runs fine. Is that correct?
2) TRIM still works on boot, even if the time is long, correct?
3) The 970 will NOT die, wiping out all the data, correct?

If that's all correct, then I'll test whether it's just Apple's implementation of TRIM, because I use Sensi from Cindori, which has its own Apple-approved TRIM code (as I understand it.)

Thanks!

As someone with a 2TB Sabrent Rocket Q4 and a 1TB Samsung 970 ECO, I am pretty interested in this as well. I also have the Sensei app from Cindori which as you say claims to use its own driver - In fact with trim enabled through a Clover patch although it shows under system profiler with a "Yes" next to trim, Sensei will actually recognise the system as NOT having trim enabled so clearly does something different to patching com.apple.iokit.IOAHCIBlockStorage!

 

[kentval]

2. TRIM is broken but to quote the official word the 970 EVO "can be used with TRIM disabled, at slower boot times, or as a data storage"

OK... here's why I ask about TRIM being "broken" (as in "does absolutely nothing at all") on the 970. What, exactly does that sentence above mean?

The original issue is here:

https://github.com/acidanthera/OpenCorePkg/blob/0.6.8/Docs/Configuration.tex#L2592-L2632

It says: " On several controllers, such as Samsung, where the deallocation process is relatively slow,
this timeout can be reached very quickly. (snip)

One way to workaround the problem is to increase the timeout to an extremely high value, which at the cost of slow boot times (extra minutes) will ensure that all the blocks are trimmed. "

IOW, at the cost of a slower boot time, TRIM will proceed correctly.

However here: https://github.com/dortania/bugtracker/issues/192 (which links to the original issue)

it describes various SSDs, saying "Working with TRIM broken (can be used with TRIM disabled, at slower boot times, or as a data storage): (snip) Samsung 970 Evo/Pro"

It appears to me that there is confusion stemming from a single comma [after 'disabled'], and thus how you read that sentence.

Sentence: Working with TRIM broken (can be used with TRIM disabled, at slower boot times, or as a data storage):

reading #1: can be used with TRIM disabled, (which will mean you have slower boot times) or as a data storage

(two possibilities: disabled or data)

reading #2: "can be (a) used with TRIM disabled, (b) at slower boot times, (c) or as a data storage

(three possibilites: disable, slow, data)

Reading one means "TRIM does nothing at all except slow you down" (IWO "TRIM is totally broken")
or
reading two means "you can disable TRIM, OR you can accept the slower boot times to get it to work, or you can use it just for data"

Reading number TWO matches the original description of the issue. Reading #1 does not match the original issue.

 

[pastrychef]

reading #2: "can be (a) used with TRIM disabled, (b) at slower boot times, (c) or as a data storage

(three possibilites: disable, slow, data)

I think this is correct.

 

[kentval]

I think this is correct.

Me too. Thanks!