Jonathan Kamens 86 47<p>As I previously discussed <<a href="https://federate.social/@jik/114803156348073466" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">federate.social/@jik/114803156</span><span class="invisible">348073466</span></a>>, I recently had to replace my <a href="https://federate.social/tags/SSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSD</span></a> on my primary <a href="https://federate.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> PC.<br>I ended up replacing it with this 1TB <a href="https://federate.social/tags/SanDisk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SanDisk</span></a> SSD: <a href="https://www.newegg.com/sandisk-ultra-3d-1tb/p/N82E16820173354" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">newegg.com/sandisk-ultra-3d-1t</span><span class="invisible">b/p/N82E16820173354</span></a><br>Shortly after installing it I started getting these kernel errors.<br>Replacing the cable and moving it to a different MB port didn't help.<br>Online research suggests the drive _may_ be faulty.<br>I've temporarily switched back to my HDD and asked the seller to replace the SSD. We'll see if that solves it!</p>