codezeroo wrote:
<New Report.log>
<DriveDX Report.log>
<Firstaid.log>
Thank you for your replies and suggestions. When erasing my SSD, I wipe it completely.
The SSD health report looks Ok. I was hoping it might have showed some errors.
Your First Aid report is showing a huge amount of overallocation warnings (too many to list even). I am not certain, but I think they may be related to the APFS Container which could definitely explain the performance issues.
So you did select the physical drive to erase and not just the Volume Group of "Macintosh HD" volume as I described in my last post? I'm only asking because it is very unusual to see First Aid errors on a clean install since that usually indicates a hardware issue of some sort.
If there are no external devices connected and the whole physical SSD was erased, then I believe you have some sort of hardware issue with this laptop.
You can try installing macOS to an external USB3 SSD and boot from the external SSD to compare results as this would likely tell us whether the internal SSD is the problem (physical SSD hardware or file system). It would be best to use the USB port on the right side of the laptop since that USB port is on the Logic Board.
Another experiment you can perform is to use the command line to try running the file system check by providing it with the option to override the default behavior so that it can attempt to repair those "overallocation" errors. You will need to do this while booted from Recovery Mode. You do need to make sure that you are booted into the Monterey installer when using Recovery Mode because you must use the most recent version of file system checker or bad things can happen. Also, make sure the physical drive has the device identifier "disk0".
Command to use if booted into Recovery Mode (make sure "Reinstall Monterey" is shown so that the file check utility will be the most recent version):
fsck_apfs -o /dev/rdisk0s2
That " -o " section is a hyphen followed by a lower case letter "Oh". With the "rdisk0s2" portion, that is the number zero.
FYI, I only tried running the file system checker this way one time a long time ago, but I think this is all that is needed. I'm only offering it since you don't have any data to worry about since you've already erased the system.