Big delay during boot

[vilu]

My conclusion too, 970 PRO after fresh install - no delay anymore.

 

[c-o-pr]

Everything I've seen about problems with slow boot on NVMe (specifically Samsung) are about a Trim feature regression: basically that Monterey and Trim get all squidgy. But the reports of are anecdotal. While many hack details are anecdotal, in this case the "fix" is particularly suspect. By doing a full re-install you might expect Trim state to be reset for entire volume as a matter of course, whereby the installation may not cause the Trim regression to be aggravated, and/or installs are expected to take a long time (many minutes). So sure if OS SSD garbage collection is reset by installation, you might expect boot times to be normal after installation...

But after the drive is exercised for a while, will you end up back at the same regression?

This thread might not be on the right track? IOW making the problem go away could be only temporary. ...Or maybe I'm missing something...

Back in old timey days of Mac there used to be jokes and disdain about Windows users and how they had so little confidence in their systems that the most common trouble-shooting approach was "nuke and pave". Around time of Intel Mac in 2006, MacOS started to become cryptic, error-prone and unreliable, more like Windows, and nuke-and-pave became part of Mac user parlance. With this thread my thought is "look at Mac now". A whole thread that seems clueless just wiping and reinstalling on new hardware where Apple engineering itself precludes even making a proper device backup. Truly the end of an era.

 

[theruck]

i am ordering a SN750 to test

replaced for SN750 (not SN750 SE) and boot time back to 24s instead of previous 6 minutes

so i am keeping the WD and selling the samsung 960 EVO

 

[theruck]

Swapped-out my Samsung 960 EVO for a WD SN750 SE NVMe (500GB), and boot time is back to normal now, running Monterey 12.0.1. BTW, another M.2 slot in my Hack is still occupied by a Samsung 970 EVO Plus with Windows 11 on it, but its presence alone has no impact on Mac boot time.

it has impact on boot time only if the Samsung drive contains apfs filesystem. Otherwise there is no need for the process to do the trim

 

[FormerUser-400995]

Everything I've seen about problems with slow boot on NVMe (specifically Samsung) are about a Trim feature regression: basically that Monterey and Trim get all squidgy. But the reports of are anecdotal. While many hack details are anecdotal, in this case the "fix" is particularly suspect. By doing a full re-install you might expect Trim state to be reset for entire volume as a matter of course, whereby the installation may not cause the Trim regression to be aggravated, and/or installs are expected to take a long time (many minutes). So sure if OS SSD garbage collection is reset by installation, you might expect boot times to be normal after installation...

But after the drive is exercised for a while, will you end up back at the same regression?

This thread might not be on the right track? IOW making the problem go away could be only temporary. ...Or maybe I'm missing something...

Back in old timey days of Mac there used to be jokes and disdain about Windows users and how they had so little confidence in their systems that the most common trouble-shooting approach was "nuke and pave". Around time of Intel Mac in 2006, MacOS started to become cryptic, error-prone and unreliable, more like Windows, and nuke-and-pave became part of Mac user parlance. With this thread my thought is "look at Mac now". A whole thread that seems clueless just wiping and reinstalling on new hardware where Apple engineering itself precludes even making a proper device backup. Truly the end of an era.

The frequent premise of if I can't see it, then everyone else is probably wrong; also known as the NIMBY (Not In My Backyard) syndrome; seems rampant, at times.

 

[kentval]

I have no way of knowing if this is associated with the 970 issue, but Monterey has its share of serious problems:

Some Older Macs Reportedly Bricked After Installing macOS Monterey

macOS Monterey, released last week as the latest version of macOS, is bricking older Mac computers, rendering them unusable and unable to even turn...

www.macrumors.com

Think I'll wait and see if a solution shows up here later... (yeah: I have a 970...)

 

[FormerUser-400995]

Some Older Macs Reportedly Bricked After Installing macOS Monterey

macOS Monterey, released last week as the latest version of macOS, is bricking older Mac computers, rendering them unusable and unable to even turn...

www.macrumors.com

Seems to be happening across quite a range of different Macs.

Interesting to note the apparent lack of these issues on non-standard hardware, though.

 

[kentval]

Seems to be happening across quite a range of different Macs.

Interesting to note the apparent lack of these issues on non-standard hardware, though.

Good point. Obviously Monterey is NRPT (Not Ready for Prime Time.)

 

[kentval]

Good point. Obviously Monterey is NRPT (Not Ready for Prime Time.)

Just to close the circle, it (the bricking) was a problem with T2 firmware and Apple has today (11/5/21) released a fix, apparently embedded in the latest Monterey download.

 

[FormerUser-400995]

Just to close the circle, it (the bricking) was a problem with T2 firmware and Apple has today (11/5/21) released a fix, apparently embedded in the latest Monterey download.

So, the issue would have been specific to a selection of real Mac systems, and only became evident when upgrading to Monterey. This explains the lack of similar reports from Hackintosh communities.