NCP Mount Fails

[jkress]

NOES2
SLES10SP3
ParaVirtualized on SLES11SP1

In yast2 software the NCP modules show as being installed.

NCPMOUNT fails -- no such device in mount (2)

Performing cat /proc/filesystems does not return NCPFS.

Same command works on other servers and show NCPFS in the cat list.

This is a new install, and I am close to blowing it away and do another
install from scratch.

Any ideas?

Thanks,
JoeK

[Bob-O-Rama]

Hi,

Is this OES 2, +SP1, +SP2, ? What is the version, etc. for the system hosting the volumes you are trying to mount?

/proc/filesystems does not necessarily represent reality on an OES2 server.

The best way to confirm ncpfs is available is ensure the kernel module is loaded:

modprobe -l ncp*

It should report that ncpfs.ko is loaded. What specific mount command line are you using ( or fstab entry as the case may be ).

The most common issue I have encountered is, ahem, not reading man ncpmount - leading to forgetting the use of -A and -S simultaneously as indicated. It should be something like...

mkdir /mnt/heapostuff
ncpmount -S BOBLAND -A bobland.xxxxxxxxxx.edu -V HEAPOSTUFF -U .bob.admin -P xxxxxxxxx /mnt/heapostuff

But start by consulting the man pages, and ensuring the basics are covered: the mount point exists, the proper addresses, volume are being specified, ... if you still have issues, please provide the details and the actual command line used. Also do an nslookup on the dns name of the remote server.

-- Bob

[jkress]

Thanks for the response. Resolved by reinstalling the server.

"Bob-O-Rama" <Bob-O-Rama@no-mx.forums.novell.com> wrote in message
news:Bob-O-Rama.4xm5hz@no-mx.forums.novell.com...
>
> Hi,
>
> Is this OES 2, +SP1, +SP2, ? What is the version, etc. for the
> system hosting the volumes you are trying to mount?
>
> /proc/filesystems does not necessarily represent reality on an OES2
> server.
>
> The best way to confirm ncpfs is available is ensure the kernel module
> is loaded:
>
> modprobe -l ncp*
>
> It should report that ncpfs.ko is loaded. What specific mount command
> line are you using ( or fstab entry as the case may be ).
>
> The most common issue I have encountered is, ahem, not reading *man
> ncpmount* - leading to forgetting the use of -A and -S simultaneously as
> indicated. It should be something like...
>
> mkdir /mnt/heapostuff
> ncpmount -S BOBLAND -A bobland.xxxxxxxxxx.edu -V HEAPOSTUFF -U
> bob.admin -P xxxxxxxxx /mnt/heapostuff
>
> But start by consulting the man pages, and ensuring the basics are
> covered: the mount point exists, the proper addresses, volume are being
> specified, ... if you still have issues, please provide the details and
> the actual command line used. Also do an nslookup on the dns name of
> the remote server.
>
> -- Bob
>
>
> --
> Bob Mahar -- Novell Knowledge Partner
> Do you do what you do at a .EDU? http://novell.com/ttp
> "Programming is like teaching a jellyfish to build a house."
> More Bob: 'Twitter' (http://twitter.com/BobMahar) 'Blog'
> (http://blog.trafficshaper.com) 'Vimeo' (http://vimeo.com/boborama) <--
> Click And Be Amazed!
> ------------------------------------------------------------------------
> Bob-O-Rama's Profile: http://forums.novell.com/member.php?userid=5269
> View this thread: http://forums.novell.com/showthread.php?t=442523
>
>

[Bob-O-Rama]

Sure, take the easy way out. 😉

Any thoughts as to what landed you in this situation in the first place?

-- Bob

[jdofaz]

Bob-O-Rama;2124631 wrote:


modprobe -l ncp*

Hadn't even considered a kernel module problem, I had updated the kernel without getting around to restarting, solved this error for me.

Thanks!