Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
The Steam Deck sees that there is a 2.9 gb External Drive attached to it even without the micro SD being inserted. At this point I ran h2testw on the card, which tested fine at full capacity.
What fixed it for me was going to Desktop mode removing it there: Steam > Settings > Downloads > Library > Select the External Drive, click the 3 dots, Remove Drive.
In the Sep 22, 2022 OS beta update:
Maybe Valve's fixing it.
warning: Be careful with this...
Double check that `/dev/mmcblk0` is the block device for your microSD card
Then try to run `sudo dd if=/dev/zero of=/dev/mmcblk0 bs=512` which will write zeros to every block on the disk. This will nuke everything on the disk including any mangled partition table.
There is no progress indicator so it will just sit there until it finishes and will then return to the prompt.
Then retry to run f3probe.
It is very unlikely an actual defect. It is most likely a software issue with a mangled partition table, or it's a fraudulent microSD card that has a small amount of memory and has a firmware programed to report as a large amount of memory while looping writes as the disk is written to... which is what f3 {Fight Flash Fraud[fight-flash-fraud.readthedocs.io]) is testing for.
It is running now, will report back once it has completed. Your help is always appreciated Bro, thank you so much for it! My fingers are crossed, I'd love nothing more than to report back that my three cards are usable once again.
Do you happen to know approximately how long I might expect this to run? Just wondering, as it has been running about an hour at this point, but I know that it has typically taken the Minitool PW about 2.5-3 hours to partition/format these cards. Also, given the issues I have had with these cards, I am just making sure that if it is still running come morning, that it is OK to go ahead and kill it. I say this, as the Minitool PW took >12 hours to run a format for EXT4 on an 8TB USB drive, and it didn't even take, I tried it twice. I have set the Deck, albeit temporarily, to never allow the system to turn off or be put to sleep, as I don't want to sit here moving the mouse for hours to keep the system awake and running. Not sure this will work, first time invoking this, but the Deck does go to sleep rather regularly by default.
By the way, did you get your Deck? I'd love to hear your thoughts, I truly hope you are enjoying it as much as I enjoy mine. Such an impressive accomplishment by Valve in my opinion. For the past two months I have been learning something new, about the device and the OS, on a practically daily basis, and having a great time doing it.
How long it will take is dependent upon the size of the disk. The "bs=512" is telling the dd command to write in 512byte blocks (which is the physical block size for your microSD cards, so there won't be any over-run). As such it writes 512b and then flushes the buffer to disk, then repeats. You could speed it up by specifying a larger block size that is less than the available system memory so it writes more data into ram before flushing it to disk, however, that will result in an over-run at the end of the disk unless its a perfect devisor of your storage blocks (depends on the size of the disk).
From your post it looks like your using what is reporting as a 1TB microSD card so that will definitely take a while to complete. I'd just leave the Steam Deck plugged in while it does its thing. It definitely could take upwards of 16hr or more for a 1TB microSD card(probably should have noted that in my previous post).
Also, yes I did get my Steam Deck and have really been enjoying it. I've loaded up my emulation collection on a 1TB microSD card. I've been playing some DeadCells, just got the Ascent on Steam via my humble bundle sub so I'm going to load that up to play its new DLC, and mostly have been playing some of my favorite SNES, GameCube, and Wii U games. Currently playing through The Legend of Zelda: A Link to the Past again as its my favorite Zelda game as well as playing through the HD remake for The Legend of Zelda: The Wind Waker from the Wii U.
That is great, really glad you are enjoying it. I need to get some emulators on mine as well. I have a ton on my PC, though I haven't played with much newer than PS1, NDS, and PSP. I have a Wii U, and love the remake of Wind Waker on that system. Felt they could have done a lot more with Twilight Princess though. I see some have even been emulating BoTW, which I honestly believe is the greatest video game ever made. I have beaten it 2 times fully (350+ hours for each run, I love exploring that world), such an amazing experience. Before that I had well over 100 hours each in a couple of playthroughs of Twilight Princess. Don't know if you've played the remake of Link's Awakening on Switch, but it is a great little Zelda game in it's own right, and holds very accurate to the original, so much so that the original game guide book I had still works.
Yeah, I figured this could well be a long process for this 1TB card. It hasn't errored out or anything, which I will view as a positive thing to this point. I truly hope it works. I keep my Deck plugged in, have hardly used it as a handheld to this point, it is always docked. But, it still goes to sleep, after what seems like 10-15 minutes of inactivity by default, so I configured a special behavior in the power profile settings, and set it to never shut down the computer or let it go to sleep. I hope it works, as some of these options were clearly designed for use with a laptop and have no bearing on the Deck, I just hope this setting isn't one of them. I am good with it taking as long as needed, no rush, and time well spent if it allows my cards to be recovered.
Thank you again, for all your help, it always proves invaluable, cheers my friend!
Also, its a bit more complex but you can trigger the dd process to output how much data its written so you can see that it is progressing and effectively see how much it has left to go.
If you open another terminal you can use the `ps` command to find the process ID for your running dd process. If you do something like `sudo ps faux | grep dd` you should be able to see what the PID is for the "dd if=/dev/zero of=/dev/mmcblk0 bs=512" command you are running. Notate that PID and then in that 2nd terminal you can run a "watch" that will periodically refresh, or "watch" a command you tell it to.
So you can run sudo watch -n 120 "kill -USR1 $PID" where the $PID is the PID you find for the running dd command. The -n 120 tells the watch command to check the command in the quotes every 120 seconds (feel free to increase this to something longer like 5 - 10 minutes (specified in seconds) as each time it does this it is briefly interrupting the dd command which will slow it down slightly.
The "kill -USR1 $PID" is sending the "user defined signal 1" to the PID you specify which in the case of dd tells it to print a status to its standard output (STDOUT).
So for example if you do `sudo ps faux | grep dd` (that is a vertical pipe not an I or l, i.e. shift + the \ Key on most US keyboards) and find that your dd process is PID 4732 then you'd run:
sudo watch -n 120 "kill -USR1 4732"
Then you can switch back to the terminal that your dd is running in and you'll see that every 120 seconds it will spit out some output with its current status.
So, even with the power profile I had manually set (it's still set), the Deck still shut down over night. The command in the Konsole windows was still showing when I woke it up, but when I ran ps from another konsole it only listed the following:
(deck@steamdeck ~)$ ps
PID TTY TIME CMD
18118 pts/2 00:00:00 bash
18126 pts/2 00:00:00 ps
So, I simply used CTRL-C, and this is the output that was placed on the screen afterwards:
(deck@steamdeck ~)$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=512
[sudo] password for deck:
^C35255345+0 records in
35255345+0 records out
18050736640 bytes (18 GB, 17 GiB) copied, 34800.9 s, 519 kB/s
It ran for 4-5 hours before I went to sleep, so I know it at least ran that long, however, when I open it in Dolphin now, after having quit the process, all the files and directories that were present before are still present, it appears as if nothing has been run at all.
Go ahead and try to run the dd with a larger block size.
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=16M
that should speed it up quite a bit. I'm surprised that it is still showing the contents on the disk though since it showed it wrote 18GB at the start of the disk so it should have destroyed the partition table and the beginning of the filesystem so it shouldn't have been mountable.
Also what does the output for `sudo parted -l` show for you? (that is a lower case L) does it list the partition table for /dev/mmcblk0?
This is the output of that command. This is exactly the behavior that has been exhibited by all four cards with issues resulting from being used in the Deck, they show data, the directories still exist, but they disappear from the Steam Library as being installed. Then I am unable to partition, format, or change them in any way, no adding/deleting, they are just locked. No app, including KDE has been able to change the drives at all.
Anyhow, sorry for going on, here is the output of sudo parted -l:
Model: SD SN01T (sd/mmc)
Disk /dev/mmcblk0: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 67.1MB 1024GB 1024GB primary ext4
DD with a BS of 16M is currently running, we'll see if that, hopefully, makes a difference. Again, thank you very much for your help!
Some odd behavior, this is what the konsole window, that dd is currently running in, looks like, with just a solid white cursor block sitting below the password line:
(deck@steamdeck ~)$ sudo dd if=/dev/zero of=/dev/mmcblk0 bs=16M
[sudo] password for deck:
This is what the ps looks like:
(deck@steamdeck ~)$ ps
PID TTY TIME CMD
18118 pts/2 00:00:00 bash
18126 pts/2 00:00:00 ps
sudo ps | grep dd
where that | is a vertical pipe like the / and \ but stright up and down.