Is your steam library on a NTFS filesystem?
I have a similar problem on Arch that is only affected when the library is on a NTFS filesystem.
There was an update for steam on Dec 12 that fixed ZFS drives. Which is when the NTFS issue started to show up.
I use ext4
try again tomorrow
Also try and verify other games and see if they pass. Most of the games on my NTFS drive will download and be playable (except CS:GO which is getting the same issue as you), but all of them will fail verification.
The games that do pass verification (including CS:GO) are installed on a BTRFS filesystem.
I have the same issue as @sixsupersonic. With how the WD Black² hybrid drive works, I could format the SSD partition to ext4 but had to keep the HDD partition NTFS. Hoping this issue gets fixed soon.
Switching filesystems from ntfs to ext4 resolved this for me on Debian Sid. Smaller games were fine on NTFS, but CSGO and Dota 2 would fail repeatedly.
@kendase3 What are these "smaller games?" All of the games I have on the NTFS drive fail verification, big or small.
"Papers, Please" downloaded and passed verification, though I didn't try to launch it. I believe I tried Teleglitch as well and that downloaded without issue. I never explicitly verified files after the download in either case, but neither resulted in a 'download corrupt' as would happen repeatedly in the case of Dota and CSGO after each download reached 100%.
The smallest game I have "Uplink (42MB)" failed verification, but successfully downloads and is playable.
I can't play Dota 2, it's an external hard-drive, but with EXT4. I tried everything, even clearing download Three times.
Do you guys have steam library in an encrypted home folder?
My main steam library is sitting on an separate NTFS (no encryption) partition that I share with Windows 10.
The games that don't work on the NTFS partition are on my root/home Arch Linux BTRFS partition (no encryption).
The NTFS Library will always fail verification, but the games will download, run, and update with the only exception being CS:GO, which fails to download.
I don't know if this is of any use, but here is my NTFS-3G mount options
"noatime,defaults,windows_names,big_writes"
Any progress on this?
Please let us know if fix is in next update
Trying to install now on ext4 (before in ntfs ) wait for news
I wish Valve was less secretive about their progress on issues like this. They're obviously giving it attention, since they're closing duplicates, but they're not telling us what they're doing about it, and where they are in terms of fixing it. Whether they've reproduced the error, what caused it, etc. We basically know nothing until the fix is finally released to the public, god knows when
3 weeks and not even as much as a response from Valve. I've seen open source projects with much smaller budgets (or none at all) and fewer maintainers which respond faster than you guys do
Apparently after the update they fixed
Is anyone else experiencing this issue with the steam beta client? (CS:GO / Dota 2 on NTFS or F2FS)
Just tested it out. Still experiencing the issue. CS:GO won't work due to the corrupted update files (when on NTFS).
Tested with dota 2 on Steam Beta. Still the same issue
Now the games won't finish downloading to my NTFS library (CORRUPT UPDATE FILES). Same issue as CS:GO and Dota 2, but affecting all games I tried to download to a NTFS library.
Resolved after update
Hello @Rxon7, I'm not aware of a specific fix that went in for this issue. What update are you referring to?
Yeah, I haven't got any updates on Steam since my last test on 3 days ago and tested this one again and it's still broken.
Yes, please reopen this issue
@kisak-valve If you don't mind me asking, and this is more of a technical detail, but shouldn't Steam and pretty much every program on Linux be file-system agnostic? Why would you need to specifically add support for ZFS, or why would support on a certain filesystem suddenly break?
@Rxon7, I see what happened here, the original issue is about download corruption when pausing and resuming a download on ext4 which appeared at about the same time as the NTFS issue, and these two issues got accidentally combined. Glad to hear your ext4 issue is resolved. Now what to do now that the majority of the issue report is about NTFS.
@SethDusek, you may want to skim over #4670, where this was recently discussed.
Okay, I have decided the original issue report should take priority, let's continue tracking the NTFS issue on the newly created #4800.
@kisak-valve I'm sorry. I do not speak English
ext4 === Perfect
NTFS === broke
This issue still has not been fixed. I'm still having this problem.
Still not a single response from Valve. I cannot play any games right now on my Linux machine. The issue still persists.
It really bugs me that most people have game libraries of over 2000 USD worth, yet they fail to respond to major issues like this. Get your shit together valve, I'm a paying customer.
The problem is still here. I copied my TF2 files from Windows to Linux (to a different folder on the same NTFS partition) and tried to launch it using Steam. Steam downloads ~22 MB worth of Linux libraries, then shows me the "corrupt update files" error (file: /host/Steam_Linux/steamapps/downloading/440/bin/bsppack.so) over and over.
Trying to verify game files ends up with Steam removing the entire goddamn folder with TF2 game files and redownloading them all over again. So annoying...
I can also confirm that this is still a problem. I'm on Manjaro (Arch) Linux and my library is on a NTFS HDD. Can't download/install CS:GO.
Still a problem. At random times CSGO crashes out and complains about invalid PAK files, it's a different file each time. I perform a file validation and it fixes the issue for 5 minutes and then when I join a game after about 5-10 minutes it crashes out again with the same error, different PAK file.
Issue not solved yet, I have two game libraries, one on a ext4 drive and another on a ntfs drive, having dota installed in ext4 and still the update files are being downloaded on the ntfs drive so I get this Issue (maybe it picks the ntfs drive because of more available space). Pretty annoying still.
my issue was apparently caused by a bad stick of ram, so I would recommend testing that
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
After leaving the night downloading back to the outset
Steps for reproducing this issue: