Big delay during boot

[tedyun]

Good to hear. What were you using before as your boot drive?

Samsung 970 EVO Plus, 2 TB. Changed it out for WD SN750, 2 TB. I'll probably move my Windows Boot Drive to the Samsung now.

 

[FormerUser-400995]

The NVME 970 Samsung which i just did the basic update to Monterey on. I have too much stuff on this drive to consider a fresh install. Monterey actually seems quite crisp and fast once it boots.

Actually, I was responding to @tedyun - but, this may be of interest to you, if you don't already know about the TRIM issue on those drives.

 

[FormerUser-400995]

Samsung 970 EVO Plus, 2 TB. Changed it out for WD SN750, 2 TB. I'll probably move my Windows Boot Drive to the Samsung now.

Probably a good idea. Or, even better, as storage - somewhere to keep all those wav files, or movies, or unmentionables.

 

[theruck]

I have the similar problem on my Samsung NVME 970 Pro, which was Big Sur updated to Monterey. Also noted this on a Samsung SSD 860 Pro on which I run High Sierra so I can use some 32 bit programs and curiously enough also with my Sandisk Ultra usb install disc for Big Sur. This is via Disc Utility in Monterey and all these drives had their EFI created in earlier versions of OSX. I then formatted another USB install disc using Monterey as a Monterey Install disc and DU saw no issues with my EFI. It seemed to boot up the install program in about a minute which is probably normal for an install disc. There was a time lag in Big Sur around the point of ignoring kextcache but not nearly as long as the current lag. I just wonder if there has been a change in the EFI partition that Monterey and perhaps older vesrsions of Big Sur were looking for and hence the delay. In previous versions of OSX DU saw no problems with these drives or their EFI's. Perhaps explains why clean installs presumably using a USB with Monterey have no problems regardless the brand of NVME.

its not a problem really
anyway if you want to solve it just delete and recreate the partition
backup the EFI folder first of course

 

[FormerUser-400995]

its not a problem really
anyway if you want to solve it just delete and recreate the partition
backup the EFI folder first of course

Unfortunately, that won't necessarily solve the TRIM issue for very long. I initially thought the same as you do, however, the underlying problem will still exist, and can exhibit the same symptoms again after a period of time.

 

[tpark]

its not a problem really
anyway if you want to solve it just delete and recreate the partition
backup the EFI folder first of course

Not sure how to safely do this and did it fix your DM errors in your case and did it look after the slow boot issue. If I clone my Monterey NVME to another brand will I not still have the defective EFI.

 

[FormerUser-400995]

Not sure how to safely do this and did it fix your DM errors in your case and did it look after the slow boot issue. If I clone my Monterey NVME to another brand will I not still have the defective EFI.

This may be of interest; posted by @flytiger :-

"Samsung 960/970 Evo/Pro suffered from slow boot in Monterey is caused by TRIM issue. There is no report of upgrading firmware to solve the issue. The fresh install on those drives may temporary suppress the symptom of slow boot, however, the issue may re-surface after substantial usage due to broke TRIM implementation between macOs and the NMVe."

 

[tedyun]

This may be of interest; posted by @flytiger :-

"Samsung 960/970 Evo/Pro suffered from slow boot in Monterey is caused by TRIM issue. There is no report of upgrading firmware to solve the issue. The fresh install on those drives may temporary suppress the symptom of slow boot, however, the issue may re-surface after substantial usage due to broke TRIM implementation between macOs and the NMVe."

@macntosh - the Buyer's Guide for the SSDs should probably be updated. I went off of this when originally choosing my NVMe. I wonder who we contact to raise these concerns.

 

[FormerUser-400995]

@macntosh - the Buyer's Guide for the SSDs should probably be updated. I went off of this when originally choosing my NVMe. I wonder who we contact to raise these concerns.

I should think someone with administrative access to the site would be best, or failing that, at least one of the moderators.

It's probably a good idea to warn people of the issue, I agree, especially considering that it's been [6?] months, without any joy. Or, at least, promote the Working fine with TRIM category until a solution is found; or until the next churn of product releases.

If vit9696 and crew found this TRIM bug, you can bet your butt that the respective manufacturers knew about it too [my opinion only]. They probably considered it low risk, and shipped anyway. No big surprise there.

Poor consolation, but at least those who bought one of the affected drives should have a valid warranty claim, IMHO.

 

[UtterDisbelief]

@macntosh - the Buyer's Guide for the SSDs should probably be updated. I went off of this when originally choosing my NVMe. I wonder who we contact to raise these concerns.

Two ways -

1) Very bottom of the webpage, links for: "Home Activity Rules Contact Us Contribute".

2) Or in the forum: Site Suggestions.