[Oxyd][0.16.1] Filesystem errorwhen generating a new world.

[Alphys_Hedge]

Hi! I downloaded 0.16.1 to try it out today and I can't seem to start a new world at all. Each time I click "Generate" it stalls for a couple seconds and gives me this notice:

Code: Select all

filesystem error: copy_file
"/media/seth/Games/factorio-0.16/temp/currently-playing/level.dat" to "/media/seth/Games/factorio-0.16/temp/currently-playing/level-init.dat" failed:
Function not implemented
[/media/seth/Games/factorio-0.16/temp/currently-playing/level.dat]
[/media/seth/Games/factorio-0.16/temp/currently-playing/level-init.dat]

I'm playing on Ubuntu Linux 14.04 LTS, Intel Celeron CPU w/ 4GB RAM. Not quite sure what's going wrong here; any help is appreciated!

EDIT: Apologies, It somehow slipped my mind to include a log file.

[Oxyd]

Hi. Is /media/seth/Games located on some kind of a network share or something? Could you post the output of the `mount` command? (Just `mount`, no arguments.)

[Alphys_Hedge]

Hi. Is /media/seth/Games located on some kind of a network share or something? Could you post the output of the `mount` command? (Just `mount`, no arguments.)

Thanks for replying! /media/seth/ is where my SD card is mounted currently.

`mount` command output:

Code: Select all

/dev/mmcblk0p1 on / type ext4 (rw,noatime,commit=600,data=ordered)
devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=1977672k,nr_inodes=494418,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shmfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
tmp on /tmp type tmpfs (rw,nosuid,nodev,relatime)
none on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=395880k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
run on /var/host/dbus type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
run on /var/host/shill type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
/dev/mapper/encstateful on /var/host/timezone type ext4 (rw,nosuid,nodev,noexec,noatime,discard,commit=600,data=ordered)
/dev/root on /lib/modules/4.4.79-11654-g7e0f59a105a1 type ext2 (ro,relatime,block_validity,barrier,user_xattr,acl)
run on /var/host/udev type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
run on /var/host/cras type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
run on /var/host/chrome type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
media on /var/host/media type tmpfs (rw,nosuid,nodev,noexec,relatime)
/home/.shadow/4cba90e7baf2b8d0d32e2122cfbd1ee18962c009/vault on /home/seth/Downloads type ecryptfs (rw,nosuid,nodev,relatime,ecryptfs_sig=18844a34a6e811c5,ecryptfs_fnek_sig=70945d8521d0589a,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs)
none on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime,gid=605,mode=750)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,noprefix)
tmpfs on /sys/class/drm type tmpfs (rw,nosuid,noexec,relatime,size=395880k,mode=755)
tmpfs on /dev/dri type tmpfs (rw,nosuid,noexec,relatime,size=395880k,mode=755)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sda1 on /media/seth type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)

I don't know if this helps in figuring out the problem, but I suppose I should mention I'm running Ubuntu 14.04 with crouton using a Chromebook.

[Oxyd]

Thanks for the information. Do you know if the SD card is formatted as FAT or NTFS? Also, could you show the output of `ls -l /media/seth/Games/factorio-0.16`?

[Alphys_Hedge]

Thanks for the information. Do you know if the SD card is formatted as FAT or NTFS? Also, could you show the output of `ls -l /media/seth/Games/factorio-0.16`?

The SD card is formatted as exFAT; here's the output of that command:

Code: Select all

(trusty)seth@localhost:~$ ls -l /media/seth/Games/factorio-0.16
total 2176
-rwxr-xr-x 1 root root   1526 Dec 15 10:46 achievements.dat
drwxr-xr-x 1 root root 131072 Dec 15 10:24 bin
drwxr-xr-x 1 root root 131072 Dec 15 10:35 config
-rwxr-xr-x 1 root root    998 Aug  7  2015 config-path.cfg
-rwxr-xr-x 1 root root 849177 Dec 15 10:35 crop-cache.dat
drwxr-xr-x 1 root root 131072 Dec 13 12:50 data
drwxr-xr-x 1 root root 131072 Dec 13 12:51 doc-html
-rwxr-xr-x 1 root root   4753 Dec 15 10:46 factorio-current.log
drwxr-xr-x 1 root root 131072 Dec 15 10:46 mods
-rwxr-xr-x 1 root root    666 Dec 15 10:46 player-data.json
drwxr-xr-x 1 root root 131072 Dec 15 10:36 temp
(trusty)seth@localhost:~$ 

I've run Factorio 0.14 & 0.15 on this same SD card before (still formatted as exFAT), so it confuses me as to why I'm having this error show up.

[Alphys_Hedge]

I recently got a new hard drive which I intended to format to ext4, and created a world in 0.16 seems to work on it!

So I guess the problem was the filesystem. Though it confuses me why 0.16 couldn't create a world on exFAT but 0.15 could, I'm glad I was able to resolve it.

[Oxyd]

Well, it's mounted as root and you (as non-root) have read-only permissions to it. It's more suspicious that it ever worked.

Either mounting it with your own user or with 777 permissions (umask=000) should resolve the issue. Or, indeed, getting a filesystem with actual support for permissions.

I'm going to call this not a bug since I don't see what we possibly could do about a read-only file owned by root.

[Alphys_Hedge]

Well, it's mounted as root and you (as non-root) have read-only permissions to it. It's more suspicious that it ever worked.

It had read-only permissions? That's odd, I've been using this card for at least 6 months now and I've been able to run multiple games and use it like it was my laptop's disk, I wonder how it could've possibly had read-only permissions lol

Nonetheless good to know this wasn't a bug but rather an issue on my end, I'm looking forward to playing 0.16 more soon

EDIT: I've been mounting it with `sudo mount -o exec` if you're wondering.

[Oxyd]

It had read-only permissions? That's odd, I've been using this card for at least 6 months now and I've been able to run multiple games and use it like it was my laptop's disk, I wonder how it could've possibly had read-only permissions lol

Well, that's what your ls output shows. All of the files are listed as “-rwxr-xr-x 1 root root”, which means read-write-execute for the owner (which is root) and read-execute (but not write) for everyone else.

EDIT: I've been mounting it with `sudo mount -o exec` if you're wondering.

You could try `sudo mount -o exec,umask=000` to give everyone read-write-execute permissions. Or `sudo mount -o exec,uid=$UID,gid=$GID` to make yourself the owner of all files on the card.