akfromnyc wrote:
At this point, I’m not inclined to try running anything off the internal drives. I’m currently booting from an external USB SSD (Samsung T7), and performance is generally good. The only intermittent issues I’m seeing—occasional freezes and a kernel panic—appear to stem from low-level interaction with the failed internal NVMe SSD, rather than the external drive itself. I’ve attached two short excerpts from a recent kernel panic log that show the NVMe timeout directly.
FYI, if you have any external Thunderbolt connected NVMe SSDs, they will show up as "nvme" in the Kernel Panics.
Given that, my working assumption is that if the internal SSD could somehow be taken fully out of the equation (or effectively neutralized), the external boot experience would likely be stable enough that I wouldn’t need to pursue an internal HDD → SSD upgrade.
I would perform a simple erase of the internal SSD so you get rid of any macOS boot files so the system firmware doesn't have to spend much time checking the SSD for bootable volumes which will minimize the chances of the internal SSD causing a problem.
I would also configure macOS to prevent mounting the internal SSD automatically during the boot process. You can use the instructions in the following article....you may need to change "hfs" to "apfs" in Step #8 if you erase the internal SSD with the APFS file system. This will further minimize macOS trying to access that internal SSD.
Prevent a volume from mounting at startup - Apple Community
If you still get the "nvme" related Kernel Panics even by doing both of these things and you do not have a Thunderbolt SSD connected which could be the source of the panics, then the only other options are to try resetting the SSD (I will need to write those instructions, just let me know), physically remove the internal SSD, or retire & recycle the computer.
I take your point on the HDD as well—especially the “High Fly Writes” attribute—which does suggest it’s not in great shape either. That reinforces my hesitation to rebuild the Fusion Drive or rely on either internal disk going forward. At this stage, I’m more focused on isolating the source of instability than trying to rehabilitate the internal drives.
I don't recall seeing any HD exceeding the manufacturer's lifetime expectations for High Fly Writes. This HD seems to have allowed for only 100 High Fly Writes.
According to the SMART wikipedia page, here is a description of High Fly Writes:
HDD manufacturers implement a flying height sensor that attempts to provide additional protections for write operations by detecting when a recording head is flying outside its normal operating range. If an unsafe fly height condition is encountered, the write process is stopped, and the information is rewritten or reallocated to a safe region of the hard drive. This attribute indicates the count of these errors detected over the lifetime of the drive.
This feature is implemented in most modern Seagate drives[3] and some of Western Digital's drives, beginning with the WD Enterprise WDE18300 and WDE9180 Ultra2 SCSI hard drives, and will be included on all future WD Enterprise products.[56]