Steam Hardware

23392 readers

277 users here now

A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Controller] - Steam Controller related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.

These are not enforced, but they are encouraged.

Rules:

Follow the rules of Sopuli
Posts must be related to Steam Hardware or Steam OS in an obvious way.
No piracy, there are other communities for that.
Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
This is a place of civil discussion, no trolling.
Have fun.

Link to our Matrix Space

founded 5 years ago

MODERATORS

Moxvallix@sopuli.xyz

Fubarberry@sopuli.xyz

Note about issues upgrading Steam Machine SSD (Solved) (sopuli.xyz)

submitted 1 week ago by user_6282638282@sopuli.xyz to c/steamdeck@sopuli.xyz

5 comments fedilink hide all child comments

I received my 512GB Steam Machine yesterday and immediately attempted to follow the standard instructions for upgrading storage: replace the physical drive and then run the SteamOS recovery image from a USB drive.

That method failed, the script for reimaging failed when mkfs couldn't do ... something. The error was a little ambiguous and searching yielded no obvious solutions.

I'll include the various search terms here in case it helps someone find it later: "discarding device blocks" stuck "mkfs input/output error"

Note the 2TB NVMe I installed had a Bazzite install on it, but I'd expect the script to handle that. Even deleting all the partitions manually in KDE Partition Manager (included in the recovery image) didn't help. But you may not have an issue with a truly fresh drive. I reinstalled the original 512 drive and proceeded to setup the device and install some games.

What DID work is to use a Rescuezilla image to clone the OG drive onto the 2TB while the OG drive was installed in the SM and the 2TB in a USB enclosure. With 400GB of game data, it took around 15m. Then using Gparted in Rescuezilla, I increased the size of the final partition to use up all the remaining space.

Be sure to use the front USB-A ports, they are 3.2.

This is the video guide I used: https://m.youtube.com/watch?v=jCxJYtE5ONE

Now I can play games instead of just installing them!

you are viewing a single comment's thread
view the rest of the comments

[–] Fubarberry@sopuli.xyz 3 points 1 week ago (1 children)

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 points 1 week ago (1 children)

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 1 points 1 week ago* (last edited 1 week 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 to do it that way.