Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
PS: perhaps take its drive out and FSCK it yourself... on linux live boot cd! its onboard linux kernel maybe messed up if it cant run a programmed command which i assume is to fix its own drive/check its own file system
I recommend against the advise meklin gave for this. No need for a new harddrive, but you do need a USB in all likelihood.
If it is just this error that shows it, then likely the init doesn't know what to do with this 'strange' fsck. In other words, fsck was probably moved during the update and the init config file didn't update.
This is very odd on Steam Deck because Steam Deck uses an immutable file system. In other words, its file system configs are handled by Valve. Basically something went wrong with updating the file system it seems.
What is also odd is that it doesn't restore a previous version of the OS.
Anyway, you may need to use an image of Steam OS to restore the file system. As you said @OP, you tried updating during 'bad internet' moments; it's possible something went wrong. You can fix it by downloading the OS image file, then making a bootable usb for your deck.
you can find instructions on how to do this here: https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3