Steam fails to recognize the second hard drive in Pop_OS environment.
Steam fails to recognize the second hard drive in Pop_OS environment.
I've been working nonstop on my keyboard, trying to get Steam to recognize my gamedrive. After setting up Steam initially, I was able to install my games, but once I rebooted my computer, accessing them became impossible. The drive is located in my home folder, and I always verify its presence before launching Steam. When adding a new library location via the file browser and navigating to my home directory, the drive doesn't show up. I've reinstalled Steam, updated my operating system, and restarted my PC multiple times without success. Any Linux assistance would be helpful? Note: I switched from Steam to a .deb install from the official site after using the pop_shop method.
The drive is positioned precisely at the designated location. You can simply add a folder that resides on the mounted drive and your system will handle it. Placing it in your home might feel unusual, but mounting it at /mnt/hdd works fine. The file system should be compatible; Steam often encounters problems with ZFS.
The settings are configured with specific privileges. Your account receives complete access to the storage device. The Steam library viewer recognizes the directory and successfully loads it. Adding the item proceeds without issues.
User has read/write access and can use the drive without issues except for this issue with Steam.
The Steam file browser doesn’t recognize the drive folder. In /home/kmilo all folders are visible except the drive. In the OS file browser, the drive shows up correctly when navigating to the same location.
I’m unable to add it because it isn’t listed.
Flatpack can be tricky to work with. It forces you to attach the drive to another place inside the app's root folder, which is why I stopped using it. The short version: mount your source folder to a target folder in ~/.var/app/com.valvesoftware.Steam with a bind option.
You're experiencing the same issue again, and both uninstalling and reinstalling through the terminal haven't resolved it. You've also attempted a drive format, but that didn't help either.
I know this is a 6 month old thread but I can't figure this out. Also, I'm entirely new to pop os (debian, ubuntu, etc). I use solus as my daily driver so the deb command prompts are all new to me. If anyone has a dumbed down, noob answer for me, I'd greatly appreciate it!
The system organizes data in a specific way. Steam Linux doesn’t support NTFS drives directly; it mainly accepts ext4, and I’ve worked with Btrfs and LVM successfully before. The drive is mounted using a file manager automatically, but Steam often struggles due to permission restrictions. You might need to remount it to see if the problem persists. Disconnect the drive, set up a new folder in your user directory as the mount point, and use the `lsblk` command to find the correct partition ID (SDxx for SATA, nvmexnxpx for NVMe). Use that ID when mounting with the command: `sudo mount /dev/{blockID} ~/mountpoint`. Ensure you use the partition ID, not the entire drive. After mounting, add the drive to Steam’s configuration file via fstab for automatic boot mounting. If this fixes it, consider adding it to UUID instead of block ID for better stability.