Linux Newbie here...running Ubuntu 14.04 LTS

Downloaded a couple of binaries/executables to the Downloads directory. ./command runs just fine but copying the binaries to /bin or /usr/bin says permission denied. I used chmol

After digging a bit more, realized that my FS is being mounted as read only!. Not sure why. /etc/fstab says UUID=8559f1a0-60e0-47e4-922d-9175f282fa8a / ext4 errors=remount-ro 0 1

Something is not right with the filesystem and I am not sure how to fix it.

Thanks
Raj

So is the copy to /bin where the error is or when you try to run them after copying them?

The first would be because you need to be root.

The second would normally be because you do not have access to the file in the directory

1 members found this post helpful.

What does the command mount say?

1 members found this post helpful.

The errors are after I copy the command to the /bin directory as a su. What is not apparent to me is why some commands/programs pre-installed run but the one I downloaded (docker-machine) doesn't and throws the permission denied error. That's when I ran into the ro option set on the drive!

When I run "mount -o remount, rw /", it looks like it succeeds (no errors) but then when I run just "mount" again, I see that the root partition on sda5 is still set to noexec ro.
So, I ended up using the took disk? to see if things can be fixed using a GUI tool (since I am a veteran Windows guy), that made things worse as it completely got the mount points messed up.
Long story short, re-installed Ubuntu and then ran mount again only to realize the ro flag is still set. Switched to su mode and ran mount to remount with rw permissions and now it seems to be sticking.

All this started because I was trying to run docker-machine to provision some docker containers on Azure.

Now, I have docker-machine running locally and trying to work my way through the labyrinth that is Linux

This
Means that if an error occurs on that drive during the mounting process, it will remount it in read only mode so you can continue to use the system. If your system keeps booting up in read only mode, you might want to take a look at your log files to see what error is causing it. There could be a corruption on the drive and the system is trying to protect itself.

http://ubuntuforums.org/showthread.php?t=845912