NSS volume not visible

With NOWS 2.5 i have NSS installed and created DATA NSS
volume on second disc ( other than system )
Volume is activated, mounted, can be fully managed via iManager
or NRM, but admin or user logged via Novell Client ( 4.91 sp5 )
cannot see this volume. Volume SYS ( linux ext3 via NCP ) also not.
In eDirectory all OK - SYS, DATA, NSS admin object.
What is bad ?
Thanks for any tips.

May be Novell should setup a WIKI for SBS with option for public submission
of Tips or How-to (ofcourse this should be vetted before actually
publishing)
"KBOYLE" <[email protected]> wrote in message
news:[email protected]...
>
> toho;1931182 Wrote:
>> NCP is exactly for that: accessing your NCP volumes, it should
>> definitely work.
>> Do you see any messages in the system logfile? Any error message on the
>> client? Do you see the server and the tree in your network neighborhood?
>>
>> And Kevin,
>>
>> > NOWS SBE was designed to access NSS using Samba and not the Novell
>> Client
>>
>> Why not? I don-t see any hassles using NSS and the Novell client
>> together on an SBE-box and it-s a much easier setup (at least at the
>> server side) than messing around with all that Samba stuff. Create your
>> NSS volume(s), install the client on the workstation, assign rights, map
>> your folders and your set.
>> Especially for those coming over from NW this should be a lot easier to
>> handle than dealing with Samba.
>>
>>
>> Dirk
> I don't disagree Dirk. The target market for NOWS SBE are -new- small
> business customers with little or no Linux experience. If they are new
> customers, they probably don't have much Novell experience - NetWare or
> otherwise. Perhaps this is why so little emphasis is placed on the
> Novell Client.
>
> The standard scripted install is not very flexible. Samba is listed as
> a prerequisite to installing NSS and the documentation explains (IMO,
> poorly) how to access NSS files via Samba. My experience has been the
> more I deviate from the recommended configuration, the more likely I am
> to encounter issues.
>
> NOWS SBE is also the upgrade path from Novell SBS but there is precious
> little in the NOWS SBE documentation that discusses migration. There is
> little mention of the Novell Client other than a warning if you intend
> to deploy it to use the one supplied with NOWS SBE to minimize issues.
> So, how NOWS SBE is best deployed and managed would seem to depend a lot
> on whether or not you have any previous Novell experience and whether
> you are willing to deal with any issues you may encounter when deviating
> from the documented way of doing things.
>
>
> --
> Kevin Boyle
> ------------------------------------------------------------------------
> KBOYLE's Profile: http://forums.novell.com/member.php?userid=19359
> View this thread: http://forums.novell.com/showthread.php?t=401066
>

Similar Messages

Mac OS 9 AFP file sharing volume not visible under Mac OS 10.5

An old blue-white PowerMac G3 running Mac OS 9.2.2 with file sharing on is not visible on the network for a MacBook Pro running Mac OS X 10.5.5. – However, a PowerBook G4 with Mac OS X 10.4.11 perfectly shows the G3.
Connecting to the G3 works on the new MacBook Pro with OS X 10.5 if I use the server's IP-address (afp://xxx.xxx.xxx.xxx) but does not work if I use the server's name (afp://<servername>).
All other shares on the network are visible for both the MacBook Pro running OS X 10.5 and the PowerBook G4 running OS X 10.4.
Why does the MacBook Pro with Mac OS X 10.5.5 not show the G3?
Why can't I connect to the G3 using its AFP name?

I think this is because there is no AppleTalk on Leopard.
Ah, I stand corrected........
Go to SystemPreferences > Network
Select your connection in the left column. Advanced > AppleTalk
Enable AppleTalk for your connection.
sp
Message was edited by: brainslice

Volumes not visible in disk utility

Hi All
I'm running an X-RAID and just updated all the disks to 250GB in all fourteen slots. Then I made two new RAID 5 arrays, one on each side, using RAID Admin 1.5.1. All lights are green and the arrays seem fine, only they do not show up in disk utility or any other disk software like Disk Warrior. Nothing shows. I read somewhere that I might need to disable the LUN masking but the new RAID Admin won't let me do this as far as I can see.
It's running OS 10.4.11 on a Mactel 2x2.66Ghz 8GB Ram

Did you upgrade the firmware to 1.5.1? If you didn't, then LUN masking is in place but RAID Admin will not let you turn it off. If you upgrade the firmware to 1.5.1 then there should be no LUN masking since 1.5.1 dropped support for it.
You can download and run RAID Admin 1.5. This version supports LUN masking and should allow you to turn it off.
If your firmware has been upgraded to 1.5.1 then something funky might be happening. You might want to downgrade the firmware to 1.5, then check LUN masking, and then upgrade back to 1.5.1 after it is turned off.

Not enough space on nss-volume

Hello,
system: 3node sles10.3 + oes2sp3
nss-volume
Some of our users (Windows 7 + NC Client) report that they want to copy some files to their nss-share, it says not enough space.
The same when we wanted to copy files from the linux-console (cp) -> not enough space on device.
We definitely have enough space on the volume and there are also no quotas set.
Can anyone help?
thx,
hugo

Originally Posted by susehoush
Hello,
system: 3node sles10.3 + oes2sp3
nss-volume
Some of our users (Windows 7 + NC Client) report that they want to copy some files to their nss-share, it says not enough space.
The same when we wanted to copy files from the linux-console (cp) -> not enough space on device.
We definitely have enough space on the volume and there are also no quotas set.
Can anyone help?
thx,
hugo
Some users? So others can write to that volume?
If not, have you maybe set a volume space restriction in nssmu on the properties of the volume? & what's the output of the console command 'df -h' and 'nsscon /spaceinfo'?
Cheers,
Willem

Rsync not copying NSS volumes

I have two OES 11 servers. Trying to rsync between NSS volumes. I
run this command on the source server:
rsync -av /media/nss/VOL1/PROJECTS/* 192.168.1.39:projects
It prompts me for the password. I enter the password and it appears
to be copying files. But nothing shows up on the destination server.
Is there something special about OES or NSS volumes that I have to set
to get this to work?
Thanks,
Ken

Originally Posted by ketter
On Wed, 30 May 2012 22:46:01 GMT, ataubman
<[email protected]> wrote:
>
>Good, that'll save me mentioning that you've posted in a NetWare forum,
>not OES!
LOL! Yesterday was one of those days! Not quite a Monday, but still.
I saw OES and didn't read the rest of the line in my newsreader.
Thanks for not pointing out my mistake in front of the whole class.
Ken
Can you tell me where I can download a copy of rsync for netware 6.5?

Hp dv6 volume scroll not visible

hello ,,,,
i have hp dv6 1350 us notebook ....the volume scroll is not visible on my monitor the volume working but not visible plz help
This question was solved.
View Solution.

Hi,
Download and reinstall HP MediaSmart SmartMenu on the following link - note that you must have at least one other MediaSmart application already installed.
HP MediaSmart SmartMenu.
After the reinstallation has completed, restart the notebook.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

After Update, cannot delete files from nss volumes

Not sure if this is the same problem caused by the SLES11 upgrade, but after running all the upgrades on an OES11 system, I can see all the nss volumes of the upgraded servers from workstations using the Novell client, and I can copy or create files on these volumes. However, I cannot delete any files, they disappear from the workstation windows explorer when they are "deleted", but an f5 promptly shows the files are still there. I can go into the server as root, and delete the files under Linux with no problems, so this part is working OK.
I am running Novell 11.1 patch 1, and this problem has only been noticeable after the update installation.
I have supervisor rights to the volumes and files, and if I additionally set all the other file rights, I am still unable to delete the files.
Anyone got any ideas?
Cheers.
ChasR

Originally Posted by chas
Not sure if this is the same problem caused by the SLES11 upgrade, but after running all the upgrades on an OES11 system, I can see all the nss volumes of the upgraded servers from workstations using the Novell client, and I can copy or create files on these volumes. However, I cannot delete any files, they disappear from the workstation windows explorer when they are "deleted", but an f5 promptly shows the files are still there. I can go into the server as root, and delete the files under Linux with no problems, so this part is working OK.
I am running Novell 11.1 patch 1, and this problem has only been noticeable after the update installation.
I have supervisor rights to the volumes and files, and if I additionally set all the other file rights, I am still unable to delete the files.
Anyone got any ideas?
Cheers.
ChasR
I had a similar problem at updating with SP3 on SP4. It was similar, that permission ERASE is not applied to all trustees working through ncp in spite of the fact that it was available.
Has solved a problem that has redefined this permission for trustees on all catalogues.

Access forbidden when Apache is trying to use NSS volume

I'm helping a customer migrate from an OES2 SBE server to an OES2 Linux server running under VMware. The new server is up and seems to be running fine and I've migrated all of the data over, but not using the Migration Tools as I could not get them to work. (That's another thread in the forums. Could that problem be related to this problem???).
Anyway, on their old server they run Apache for their public web site and it's default directory is on an NSS volume. It's configured in default-server.conf and it works fine. There are no virtual servers configured in Apache
On the new server, I've duplicated every setting I can find in Apache and every permission in the file system to match exactly with the old server. However, all I can get from Apache is an "Error 403: You don't have permission to access the requested directory. There is either no index document or the directory is read-protected."
If I move the web folder off of the NSS volume and adjust default-server.conf, it serves the pages up just fine. So, I'm pretty sure it's NSS permissions related. The wwwrun user and www group are pre-existing in the Tree and the old server is using them and they appear to be LUM enabled. There's a Unix Workstation object in the tree for the new server, so I'm assuming it's LUM enabled. From what very little I understand about LUM, it appears to be working but I wouldn't bet much on that. I also tried configuring Apache to use a virtual host instead of the default-server and that didn't help either.
I've found several other threads and TIDS on the topic and tried them all but nothing worked. I'm at the end of my knowledge!
-Farren

farren wrote:
>
> I'm helping a customer migrate from an OES2 SBE server to an OES2 Linux
> server running under VMware. The new server is up and seems to be
> running fine and I've migrated all of the data over, but not using the
> Migration Tools as I could not get them to work. (That's another thread
> in the forums. Could that problem be related to this problem???).
>
> Anyway, on their old server they run Apache for their public web site
> and it's default directory is on an NSS volume. It's configured in
> default-server.conf and it works fine. There are no virtual servers
> configured in Apache
>
> On the new server, I've duplicated every setting I can find in Apache
> and every permission in the file system to match exactly with the old
> server. However, all I can get from Apache is an "Error 403: You don't
> have permission to access the requested directory. There is either no
> index document or the directory is read-protected."
>
> If I move the web folder off of the NSS volume and adjust
> default-server.conf, it serves the pages up just fine. So, I'm pretty
> sure it's NSS permissions related. The wwwrun user and www group are
> pre-existing in the Tree and the old server is using them and they
> appear to be LUM enabled. There's a Unix Workstation object in the tree
> for the new server, so I'm assuming it's LUM enabled. From what very
> little I understand about LUM, it appears to be working but I wouldn't
> bet much on that. I also tried configuring Apache to use a virtual host
> instead of the default-server and that didn't help either.
>
> I've found several other threads and TIDS on the topic and tried them
> all but nothing worked. I'm at the end of my knowledge!
>
> -Farren
>
>
Did you give rights to wwwrun to the volume?

My new folders are not visible in Finder

New folders (generated by a application, SABNZB+, that runs in the background as a web service) will only show up in Finder once I have run a search in Finder and are not visible before. I have tried a disk repair and a permissions rebuild.
Any ideas anyone?

Yes they do, no problems there.
I am starting to believe it might have to do with the fact that the folders are created by an unarchiver that reassembles files after they are downloaded from my newsgroup. The strange thing is that there never used to be a problem, it started somewhere around the second update to mountain lion. But it could also be a new version of the application SABNzb+, I am not sure.
What is also weird is this: I can find the folder when doing a search in Finder, then open the folder, all files are there and the folder is then visible normally.
Edit: The files are reassembled by the unarchiver on the main Macintosh HD, then moved to a different volume and deleted from the originating volume.

Commvault issue with JobResults on NSS volume

Hi all, we see an issue with Commvault 9R2 (sp10) using a Linux i-data agent client on OES2SP3 x64 backing up (clustered) NSS volumes. For speed we, this case, do not want to use a NSS i-data agent, so we just leverage the Linux i-data agent.
The issue is that if we use the Linux i-data agent and the jobresults directory is also hosted on the same NSS volume that's being backed up we get an error on failures.cvf
"Could not open failures file [/media/nss/LBAPOA/galaxy/JobResults/2/268/Failures.cvf] error number [19, No such device]. The backup would continue but this would affect the ability of reattempting the failed file backup during next incremental backup. A full backup is recommended to back up all files. Check the following: 1. The account this product uses has permissions to the product's install directory. 2. Sufficient disk space is available for the Job Results directory. If the problem persists, please upload log files from CommServe, MediaAgent and Client and contact your vendor's support hotline with the job ID of the failed job."
If we (for testing only) move only the jobresult directory to an ext3 volume we do not see the issue.
Has someone seen (and hopefully fixed) this issue before? My guess it's a Commvault issue, but just before we open a SR with them I would like to now if there's a good guess to solve this:)

sveld,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Vibe file repository on NSS volume?

Has anyone figured out how to set up Vibe to use a file repository on an NSS volume? Or how to change to file repository location post install?
I made the mistake of specifying /media/nss/VOL1/teaming as my file repository during the initial installation and now either need to change the location or make it work as is.
I'd be willing to remove Vibe completely and start again if someone knows a way to proceed with that.

We moved our content from a local disk to the NAS. I'm looking at my notes, here are the steps we used:
- Setup NAS share and copied archivestore and filerepository folders from current repository to NAS share.
- Gave the user teaming was setup as full rights to the files (we are using Linux) and change ownership to match if needed.
- Run the installer and choose reconfigure. In my notes I have written to modify the path to the repository in the install.xml file. I'm not sure if that was a necessary step.
- Do a full re-index.
I'm not sure if this is the best or most efficient way to do it, but it worked for us.
Tom

Mavericks disk not visible from Windows 7 Bootcamp

Mavericks disk is not visible under Windows 7 Bootcamp. Every other drive in the machine and everything else on the network shows up. Any ideas?

CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 760EBA5D-A4B0-49CD-B1BA-087764922062
    =========================================================
    Name:         Untitled
    Status:       Online
    Size:         2999733223424 B (3.0 TB)
    Free Space:   0 B (0 B)
    |
    +-< Physical Volume 5A04D434-DEAC-4D83-ACDB-0EE9BFE6E686
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk2s2
    |   Status:   Online
    |   Size:     2999733223424 B (3.0 TB)
    |
    +-> Logical Volume Family 762D431D-888C-489A-854C-F2151D121F99
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume 96DD2E04-244F-4559-9C89-2DAE309B4994
            Disk:                  disk4
            Status:                Online
            Size (Total):          2999414448128 B (3.0 TB)
            Conversion Progress:   -none-
            Revertible:            No
            LV Name:               Thurgood
            Volume Name:           Thurgood
            Content Hint:          Apple_HFS

XSAN Lun not visible

Hello,
Hello I have XSAN with 4 MacPro's. Two of them are MDC and two clients. Suddenly the volumes disappeared from one of the clients. I checked on one of the mdc and the volumes were visible but in Xsan admin there was a message No visible luns. I turned off all computers and turned on just one of the mdc. Immediately i get a message that the system see some volumes that are not readable and offer me to initiliaze them. Xsan admin no does not see any luns and no volumes are mounted. The LUN are visible in disk utility.
OS version 10.8.5
Two RAID systems with 2 LUN's each.
Qlogic fc switch
Can you help? What is going on?

Hey there,
We once expanded a 4 drive raid 5 to a 7 drive (rebuilt it) and had a similar issue with xsan... what we did:
1) reboot all the machines connected to the xsan one by one, making sure at least one metadata controller stays online at all times
2) on one of the machines, do the following:
cd /Library/Filesystem/Xsan/bin
sudo ./cvlabel -l (to list the lun in question)
sudo ./cvlavel -u "the LUN in question" (without the quotes)
This should totally strip the LUN of any xsan labels and show now appear back in the LUN paine and you should be able to label it to it's full capacity

Use OES2SP3 NSS Volume on a OES11SPx Server

Hello all
We have a couple of virtual OES2SP3 servers which we plan to replace with OES11SPx servers (on several remote sites).
Now we had the idea to mount the existing OES2SP3 NSS volume (own vmdk disk) with all the data on it to the new OES11SPx server.
With this procedure we would not need to migrate the data to the new server and would save some time.
Does anyone have experiences with such a action?
The NSS volume contains GW and a usual folder structure.
Thank you for your feedback and suggestions.
Best regards
Beat

Originally Posted by bschwegl
Hello all
We have a couple of virtual OES2SP3 servers which we plan to replace with OES11SPx servers (on several remote sites).
Now we had the idea to mount the existing OES2SP3 NSS volume (own vmdk disk) with all the data on it to the new OES11SPx server.
With this procedure we would not need to migrate the data to the new server and would save some time.
Does anyone have experiences with such a action?
The NSS volume contains GW and a usual folder structure.
Thank you for your feedback and suggestions.
Best regards
Beat
Works fine.
The gotcha's that I'm aware of:
When you power off the OES2 VM, and "remove the disk", and then you attach it to the OES11 VM, I don't believe it MOVES the actual VMDK file or directory structure.
In other words:
OES2 VM used DATASTORE1 and the directory was like \oes2-vm\oes2-vm.vmdk
OES11 would show it like:
DATASTORE1\oes2-vm\oes2-vm.vmdk
So if/when you decomission the OES2 box, you do NOT want to do a "delete from disk" as it will whack the vmdk and directory and your OES11 box will lose the volume.
I am unsure if a storage vmotion would work (if you have the paid VMware) or if you will have to power off the VM's and manually move the datastructures around. If going from esx host to esxi host, it can be time consuming.
If all the servers are using the one esxi host, then I imagine a simple rename, etc. would suffice (ie, power off the VM's, manually browse the datastore, change the directory name, or move it into the OES11 one, etc.)
But yes, what you want to do works and I've done it many times before.
Disconnect the disk from the OES2 box, reconnect it to the OES11 box, rescan for LUNs. I don't remember if a server reboot is needed, but I always like to do that. Otherwise I think you'll have to manually run nssmu to mount the volume, etc.
Obviously if it's Groupwise you'll need to adjust any config files if you used UNC paths for stuff, along with IP addresses (ie, change the IP of the POA/MTA, rebuild the databases, etc.)
--Kevin

Invalid descriptor error when trying to access nss volums

Hi everyone,
sorry for my english, when some users try to access shared nss volumes they get this error " invalid descriptor", but other folders are accessible at the same level.
users are on windows 7 and the last novell client.
thanks

On 23/06/2014 16:06, skaii wrote:
> sorry for my english, when some users try to access shared nss volumes
> they get this error " invalid descriptor", but other folders are
> accessible at the same level.
>
> users are on windows 7 and the last novell client.
Since you reference Novell Client I'm thinking that you're not using
Novell's Dynamic File Services product[1] which is what this forum is
for. If that is the case then you should repost in a more appropriate
forum, depending on whether you're using Open Enterprise Server (OES) or
NetWare.
HTH.
[1] http://www.novell.com/products/dynamic-file-services/
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

NSS volume not visible

Similar Messages

Maybe you are looking for