# Error mounting NFS on SCO UNIX

**URL:** <https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952>\
**Category:** SCO\
**Created:** [March 24, 2022, 3:50pm UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952 "2022-03-24T15:50:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![antoniooctavio](https://community.unix.com/letter_avatar/antoniooctavio/32/6_22734026db12803ebb3e059622ac3534.png) [@antoniooctavio](https://community.unix.com/u/antoniooctavio)\
**Post date:** [March 24, 2022, 3:50pm UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/1 "2022-03-24T15:50:23Z")

</div>

I can't mount NFS.

SCO\_SV 3.2 5.0.6 i386

Code:

```plaintext
#mount -f nfs 192.168.X.XXX:/backup/sco /backup2

```

I get the response:

> mount: invalid fs type

---

<div class="post-metadata">

**Author:** ![Neo](https://community.unix.com/user_avatar/community.unix.com/neo/32/22838_2.png) [@Neo](https://community.unix.com/u/Neo)\
**Post date:** [March 24, 2022, 3:59pm UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/2 "2022-03-24T15:59:18Z")

</div>

Did you try "NFS" and not "nfs" ?

NFS is a valid filesystem type in SCO, nfs is not a valid fs type, at least according to the man page.

See, for example:

> **[mount(ADM)](http://osr600doc.sco.com/en/man/html.ADM/mount.ADM.html#mount_filesystem_types)**

### Note the filesystem is NFS (not nfs):

 ![Screen Shot 2022-03-24 at 10.41.51 PM](https://community.unix.com/uploads/default/original/3X/3/b/3b8ea9ff9da663cbf19acef627ae1718089963e2.png)

---

<div class="post-metadata">

**Author:** ![antoniooctavio](https://community.unix.com/letter_avatar/antoniooctavio/32/6_22734026db12803ebb3e059622ac3534.png) [@antoniooctavio](https://community.unix.com/u/antoniooctavio)\
**Post date:** [March 25, 2022, 11:28am UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/3 "2022-03-25T11:28:10Z")

</div>

```nohighlight
mount -f NFS oraculo:/mnt/hdb1/BACKUP/UNIX /nfs/mnt/hdb1/BACKUP/UNIX
mount: cannot mount /: Protocol not available (error 118)

```

---

<div class="post-metadata">

**Author:** ![Neo](https://community.unix.com/user_avatar/community.unix.com/neo/32/22838_2.png) [@Neo](https://community.unix.com/u/Neo)\
**Post date:** [March 25, 2022, 11:54am UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/4 "2022-03-25T11:54:22Z")

</div>

> [@antoniooctavio](#):
>
> mount: cannot mount /: Protocol not available (error 118)

@antoniooctavio

What does the error above mean?

_HINT: Experienced IT people alway Google error messages and try to understand what the error messages means and what others have done when they ran into the same error message in the past._

It is actually faster to Google error messages and search for "their meaning" than it is to ask others to tell us what the error message means, since we (believe-it-or-not) will simply cut-and-paste the error message into our browser and search Google just like you (should be doing).

Let us know what you find out! Thanks.

HTH

---

<div class="post-metadata">

**Author:** ![Neo](https://community.unix.com/user_avatar/community.unix.com/neo/32/22838_2.png) [@Neo](https://community.unix.com/u/Neo)\
**Post date:** [March 25, 2022, 1:19pm UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/5 "2022-03-25T13:19:35Z")

</div>

> [@antoniooctavio](#):
>
> mount: cannot mount /: Protocol not availabl

Also when you `mount`, you might try the `-v` flag to get more verbose information @antoniooctavio

Did you take the time to read the SCO man page for `mount` which I shared earlier?

Often, believe-it-or-not, reading the documentation for the commands we are having trouble with is very helpful 😉

You will notice that the SCO `mount` command (indeed most `mount` commands) have a flag to set to get more verbose output for debugging.

---

<div class="post-metadata">

**Author:** ![MadeInGermany](https://community.unix.com/letter_avatar/madeingermany/32/6_22734026db12803ebb3e059622ac3534.png) [@MadeInGermany](https://community.unix.com/u/MadeInGermany)\
**Post date:** [March 25, 2022, 1:39pm UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/6 "2022-03-25T13:39:52Z")

</div>

Did you purchase NFS at all?  
IIRC the tcp/ip base package is tcp/ip stack plus telnet - nothing else.

---

<div class="post-metadata">

**Author:** ![hicksd8](https://community.unix.com/letter_avatar/hicksd8/32/6_22734026db12803ebb3e059622ac3534.png) [@hicksd8](https://community.unix.com/u/hicksd8)\
**Post date:** [March 25, 2022, 2:13pm UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/7 "2022-03-25T14:13:25Z")

</div>

> [@antoniooctavio](#):
>
> mount: invalid fs type

To put it plainly, you are not providing anything like enough detail for us to have a fighting chance of helping you.

Firstly, as @MadeInGermany asked, is your system licensed for nfs?

Then, what and where is the nfs server you are trying to connect to? Is it on your LAN? What operating system is it? Is it a NAS box, if so, make/model?

Then, the big question given your error message, what filesystem type is on that nfs handle? Is it a Unix/Linux filesystem or a Windows filesystem, or what?

Also, many such nfs issues are caused by mis-matched nfs versions. The main versions in use these days are Version 2, Version 3 and Version 4, so you need to find out which versions both the nfs client and the nfs server are running. You might be able to put a command line switch on your mount command to tell it which version (2,3 or 4) to use that might solve the problem.

Please provide as much detail as you can whether you believe it relevant or not. Just hit us with all of it, that way you might get the help you need.

---

<div class="post-metadata">

**Author:** ![system](https://community.unix.com/uploads/default/original/2X/c/c7e9e16a595259edafe88615719d5c5dcda035c2.png) [@system](https://community.unix.com/u/system)\
**Post date:** [June 23, 2022, 2:13pm UTC](https://community.unix.com/t/error-mounting-nfs-on-sco-unix/385952/8 "2022-06-23T14:13:51Z")

</div>

Closed on June 23, 2022, 2:13pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
