External hfs formated disk access denied via terminal mount command?

sudo mount -t hfs /dev/disk2s2/Volumes/Seagate2TSL/

sudo mount -uw -t hfs /dev/disk2s2/Volumes/Seagate2TSL/

sudo mount -uw -t hfs, local, nosuid, journaled, noowners /dev/disk2s2/Volumes/Seagate2TSL/

Do you have a space between disk2s2 and /Volumes? Because what you posted above does not have a space.

The 'mount' command wants a directory to mount on top of, so does /Volumes/Seagate2TSL exist?

You could also try

sudo diskutil mount /dev/disk2s2

Or

sudo diskutil mount -mountpoint /Volumes/Seagate2TSL /dev/disk2s2

sudo mount -t hfs /dev/disk2s2 /Volumes/Seagate2TSL I get 'resource busy' as answer.

This is from 'man mount'

[EBUSY]

Another process currently holds a reference to dir.

That implies that something else is current using /Volumes/Seagate2TSL.

Does

sudo /bin/ls -laeO@ /Volumes/Seagate2TSL

Does this give you useful information?

Is ownership enabled on the external volume?

Select the mounted drive in the Finder, then Finder -> File -> Get Info and look at the bottom for "[_] Ignore ownership on this volume". Is it checked or unchecked? If you check it, does it change anything on the volume?

NOTE: Some of the stuff I'm suggesting, is just wild guesses.

PS: is there a course/book/online resource for someone like myself who wants to learn some command line stuff (other than just trying to figure out the manual)? TIA

Google "os x command line books"

For generic command line usage, books on 'bash' which is the name of the command line shell that reads you keyboard, finds the program/command you specified, and launch it. You can find books on 'bash' in may book stores (might even be able to find Learning OS X Unix in a bookstore), and then get a beverage in the bookstore cafe and browse to get a feel if you like how the author words things.

Or you can get job working with Unix back in the '80s and learn how much you do not know yet by the 2016's 🙂

There are also various web sites that will give you overviews of things in the Unix side of the house.

The Terminal just passes your keyboard input the shell or program/command running, and displays what it returned. In other words the Terminal is just a human input/output device. The shell gives you a prompt, read what you enter, tries to find a program in PATH that matches the name of the first word on the command line. PATH is a list of directories to search. Typical directories are /bin, /usr/bin, /usr/local/bin, $HOME/bin, but the list can be much longer, it all depends on whether you have added to the search list. Once the program is started it reads its command line and does what the arguments and options tell it. Unix shells all have a scripting language that allows you to write simple (or rather complex) scripts, putting them in a file and allowing you to invoke the script just like any other command/program. Unix shells also allow piping the output from one command into another command to be processed. chaining commands together via pipes is very common in Unix. The classic example is something like

ls | grep fred

where you are using the general regular expression processor (grep) to select output from the input based on a regular expression string 'fred' is a rather simple string to look for, but it can be much more complex.

And of course you can create scripts that are processed by other scripting tools, such as awk, perl, python, etc... (lots of scripting languages out there).

It does appear that root can access the volume via 'sudo'

sudo this

sudo that

sudo etc...

should give you access to most of the data. If you have another copy (as in a backup of this data), you could experiment with changing permissions and ownership, but DO NOT start this if it is the only copy of the data, because if something goes wrong you could loose it.

If you have another drive you could create a clean file system and try moving what you really need over via 'sudo cp -R from to'

If you have Carbon Copy Cloner, it runs as root, and should be able to move data, but CCC may also transfer all the ownership and permissions which seem to be annoying you.

I do not know what else to tell you about getting control of this external disk. I've exhausted all my tricks.

First off I tried several Commands and ultimately what worked was stopping fsck_hfs in activity monitor. Something so simple, a little time & effort from the Genuine Genius of Google and these forums helped so much. So to all on here helping one another I say THANK YOU!

If your just looking for a Fix, stopping the fsck_hfs fixed all my issues.

<Edited by Host>