first. i have been googleing for five days straight stopping to sleep 4-6hours a day,eat once a day and smoke before i break something don’t just tell me to google it
second. this post will be created over several hours on multiple devices i apologize but its been a long week and my patience is very low
the problem:
upgraded my steam deck from the 64gb emmc poop to a sabrent 1tb 2230 monster and game mode/steam cannot see the partition i made after mounting.
the things i have already tried in no particular order more may be added as i remember:
re-installed the os with recovery image from valve every time it super borks (differently every time). 10-15 times now.
following this self compiled guide on how to set up drives so game mode can see them (that currently works for usb hard drive)(it was written in a way meant only to be seen by me don’t take anything in it personally its at me)
theoretically disabling the sudo password(yaya i know why people are afraid of that don’t yell at me for it) (i am ONLY putting this is as reference to what i have done and will remove it if asked by mods)
([deck@steamdeck ~]$ echo “%wheel ALL=(ALL) NOPASSWD:ALL” | sudo tee /etc/sudoers.d/wheel >/dev/null)
(it also still asks for sudo password to mount the drive)
It can be frustrating facing a issue then having to try and resort at hacking the problem to just get things to work. considering how steamos is structured (A/B versioned, Read only etc) I’d highly suggest working out the problem of a clean working deployment using the recovery image rather then going into the weeds with workarounds that may end up being unstable or problematic in the future.
Can you elaborate on how the recovery image deployments “super bork”
not really it never seams to break the same twice and we are 15 - 20 re-installs later
and hi-stress(omg why does my main gaming pc not work)= low memory
yes i main a steam deck for pc gameing
i can say flatpaks are always borked in the in the process. i just sorted out how to fix that (now need to write myself a guide on THAT poop show)
and because of how i figured That Problem out when i updated game mode it refuses to boot now
(actualy going to do a cleaner full re-image instead of the re-install witch im super not happy about)
(loss of data is unacceptable in my view)
but i can (if i remember)tell yall how it borks this time
i could like sortof do a more “play by play” if yall want
but i dont want to get in trouble for spamming short tidbits with poop tons of pictures
(2 picture limit for new users {i totaly get it by the way this in NOT a complaint just a statement of fact})
ok thats an improvement flatpaks just seam to work this time so thats a start…theres a thing im not sayin cuz i dont want to jynx it will keep updating
well it seams to work now after full wipe/re-image and but i count this experience as a complete loss i never figured out what was wrong or how to fix it i literally learned nothing at all
Thanks for the update, and yeah, what a pain in the ass we can’t all learn what the issue was.
So many people got decks now, an you bet Thousands trying the sane thing, and A Bunch of them prolly also having whatever the issue was…
For what its worth, your notes look pretty solid, from an outsider looking in; I don’t have a deck, but it looks like a cool toy. Perhaps whatever is wrong with steamOS failing to mount without a password was the issue, but like you said, it never explained, so don’t know.
Oh well… Well done sticking with it and doing year another reimage/reinstall instead of yeeting the thing through the nearest window
