Comment on Note about issues upgrading Steam Machine SSD (Solved)
Fubarberry@sopuli.xyz 2 weeks ago
Thanks for sharing, hopefully it will help someone.
From reading on the issue, it may be a timeout during a large TRIM operation. With larger drives, you can have large scale TRIM operations fail for a couple reasons, but it mostly comes down to the volume of the requested consecutive operations being more than the NVME drive’s controller can handle in one go, or more than it can handle within the typical 30 second timeout window for these commands.
If it was this, you could either temporarily disable trim for the drive before running the install, or possibly tweak the mkfs commands in the install script to include the nodiscard option.
user_6282638282@sopuli.xyz 2 weeks ago
Interesting, and good to know. I couldn’t find any such information when searching.
I think the clone in place solution is superior in any case as the Rescuezilla image is a bit more mature than Valve’s “Arch with some scripts” recovery image. It also transfers installed games, and only needs the additional NVMe enclosure.
Fubarberry@sopuli.xyz 2 weeks ago
Yeah, when I upgraded my Deck’s m.2 drive to 1tb I used cloning as well, but it was mainly just because I didn’t want to reinstall all my games/emulators/plugins/etc. Definitely worked smoothly though.