2ndary HD not mounting as executable so Steam for Linux can't use it

[claydoh]

You still may need to chown the contents to your user. Also if you haven't, check Steam's settings to see that the full path to the library matches the full path on your system. just in case.

[steve7233]

I got it to mount but Steam still complains. The library needs to be mounted on a file system with execute permission. I tried going old school to get it to work however I think it was just the lUID and GID values that were bad. This is the line in fstab that got it mounted.
/dev/sdb2 /media/steve7233/Steam\040for\040Linux ext4 rw,relatime,, 0 2
Of course it still needs work to get Steam to use it.

[steve7233]

This might be a clue.
steve7233@steve7233-EP45-UD3P:~$ sudo mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.
steve7233@steve7233-EP45-UD3P:~$ dmesg | tail
[ 1373.485913] EXT4-fs (sdb2): Unrecognized mount option "uid=1000" or missing value
steve7233@steve7233-EP45-UD3P:~$

[steve7233]

As a test I just tried the following command. sudo mount -t ext4 /dev/sdb2 /mnt
That seems to work.

[steve7233]

Unfortunately I already noticed and tried that.

[claydoh]

I am betting that the problem is that I forgot to have the OP [I]create the actual mount point[/I]


sudo mkdir -p "/media/steve7233/Steam for Linux"

[steve7233]

I was just pointing that out in case some noob read this thread and decided to unset his x permission on all his folders. Could happen!

I queried drive type and suggested fstab mounting some time ago but it appears the OP wasn't interested in replying or my comment wasn't helpful.

I believe the correct way to represent a space in fstab is \040 , in html %20, in bash "\ " without the quotes.

Or maybe the OP just missed your comment.

The # /040 is used in fstab to indicate the spaces so that's not the problem. Like I suggested. Maybe its due to my hard drives tech. being so old. Perhaps its one or more of the options. When kubuntu 15.04 boots up it always shows some error messages. It says assuming something caching, two other messages show up then the kdm splash screen appears and it finishes the boot. Maybe it doesn’t interpret the drive correctly but seems to get it booted eventually.

[oshunluvr]

I was just pointing that out in case some noob read this thread and decided to unset his x permission on all his folders. Could happen!

I queried drive type and suggested fstab mounting some time ago but it appears the OP wasn't interested in replying or my comment wasn't helpful.

I believe the correct way to represent a space in fstab is \040 , in html %20, in bash "\ " without the quotes.

[claydoh]

Point of clarity here; the executable bit for folders must be set before the folder can be opened. They're not "executable" in the sense that a program is, but execution on a folder is the permission to enter it.

I think the OP has that set correctly already on the directory, assuming this perpetual noob is reading it right

The error message Steam is kicking out seems to be the general one you get with any permission problem.

Do you think it would be ok to mount the partition using defaults, then chown things to the user? Also, is the formatting of the path correct for one with spaces in the name?

Sent from my HTC6435LVW using Tapatalk

[oshunluvr]

Folders are not executable, but files can be.

Point of clarity here; the executable bit for folders must be set before the folder can be opened. They're not "executable" in the sense that a program is, but execution on a folder is the permission to enter it.

[steve7233]

I was able to use nano to comment out the mount that you told me to add. I am able to boot now. Now we just need to figure out what mistake you told me to do. Probably a bad option my drive are old tech. Maybe what you thought doesn’t work for these drives.

[steve7233]

It seems when trying to mount the drive this thread is about, the log file says the mount failed due to wrong file system, bad option, bad superblock on /dev/sdb2.

[steve7233]

While looking in the log I found a line that says in red "ACPI PCC probe failed." What does that mean?

[steve7233]

I had to use my Amazon Kindle to reply.

[steve7233]

Great now the whole system is broken! It boots to emegency mode. I just copy and pasted your instructions to bash.