It should be noted that the way you listed the partitions misses the dual (A/B) install method that the deck uses. There are 2 identical size partitions for root, var, and EFI. When an update occurs. The system installs the new update on the inactive set of partitions and then tells the UEFI to use the other set on the next boot. That doesn’t matter too much for 512GB models like your’s, but the extra ~5.5GB for the redundant partition layout can be significant for 64GB models.
The df command only shows mounted devices and filesystems. You can use lsblk to show all block devices and their partitions. To format it more nicely to show the labels for each partition, you can use these options: lsblk -o name,mountpoint,partlabel,size.
This is the output from my deck without the microsd card:
![[Solved] Anyone know if those Samsung Miscro sd cards work well on the Steam Deck?](https://lemmy.world/pictrs/image/0faa80c4-5ec2-4113-8216-daf0f6b0d8c9.jpeg){kind=link}
It should be noted that the way you listed the partitions misses the dual (A/B) install method that the deck uses. There are 2 identical size partitions for root, var, and EFI. When an update occurs. The system installs the new update on the inactive set of partitions and then tells the UEFI to use the other set on the next boot. That doesn’t matter too much for 512GB models like your’s, but the extra ~5.5GB for the redundant partition layout can be significant for 64GB models.
I’ve used
df -hand that showed only this three partitions. I’ve only skipped the tmpfs mounts.The
dfcommand only shows mounted devices and filesystems. You can uselsblkto show all block devices and their partitions. To format it more nicely to show the labels for each partition, you can use these options:lsblk -o name,mountpoint,partlabel,size.This is the output from my deck without the microsd card: