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:
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 -h
and that showed only this three partitions. I’ve only skipped the tmpfs mounts.The
df
command only shows mounted devices and filesystems. You can uselsblk
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:
deck@steamdeck ~> lsblk -o name,mountpoint,partlabel,size NAME MOUNT PARTLABEL SIZE nvme0n1 476.9G ├─nvme0n1p1 esp 64M ├─nvme0n1p2 efi-A 32M ├─nvme0n1p3 efi-B 32M ├─nvme0n1p4 / rootfs-A 5G ├─nvme0n1p5 rootfs-B 5G ├─nvme0n1p6 /var var-A 256M ├─nvme0n1p7 var-B 256M └─nvme0n1p8 /home home 466.3G