NX Storage not being detected?

Answered
Follow
Avatar
Warren Welch

Hi there,

We had a node fail, and replaced the unit, restoring from backup.  So far all good.  Cameras, layouts, users, etc. all restored.

But, the second disk (/data1) [ext4] is not being detected.  Clearly something is there, a "/data1/HD Witness Media" folder appeared, and as a "*.tmp" file in it, but it's not showing up in the GUI.  

Any pointers as to how to get it to recognize the storage and start using it?  The services have been restarted, no help.

Thanks,
Warren

 

0

Comments

4 comments

Sort by Date Votes
  • Avatar
    Anderson Chang

    Hi Warren Welch,

    Here are some general rules for the Nx Server to recognize and utilize the disk:
    A. The available space on the disk must be at least larger than 10% of the largest disk (storage volume) on the system.
    B. The Nx Server application must have the privilege to access and write to the disk.

    According to your description, I assume you run the Nx Server application on an Ubuntu machine.
    Could you share the following information with us?
    1. How does the second disk connect to the Ubuntu machine? By SATA, USB, SMB, or others?
    2. Are there any files on the second disk? What are those files?
    3. File system info by lsblk or df
    4. The owner and privilege of the /data1 by ls

    Thank you.

    0
    Comment actions Permalink
  • Avatar
    Warren Welch

    Thanks for the reply.

    I think all of those are "okay" in terms of paramters.

    1.  Second disk is directly attached (VirtIO, SCSI).

    2. Other files?  No.  It's an empty disk specifically for this application.

    3.  df:-

    root@jrr-nswpmq-nxw02:~# df -kh
    Filesystem                   Size  Used Avail Use% Mounted on
    udev                         1.9G     0  1.9G   0% /dev
    tmpfs                        394M  1.1M  393M   1% /run
    /dev/mapper/vgmint-root       48G  9.8G   36G  22% /
    tmpfs                        2.0G     0  2.0G   0% /dev/shm
    tmpfs                        5.0M     0  5.0M   0% /run/lock
    tmpfs                        2.0G     0  2.0G   0% /sys/fs/cgroup
    /dev/sda1                    511M  4.0K  511M   1% /boot/efi
    /dev/mapper/nxdata1-lv_nxd1 1009G   24K  969G   1% /data1
    tmpfs                        394M  8.0K  394M   1% /run/user/121
    tmpfs                        394M  4.0K  394M   1% /run/user/1000

    lsblk:-

    root@jrr-nswpmq-nxw02:~# lsblk
    NAME                MAJ:MIN RM    SIZE RO TYPE MOUNTPOINT
    sda                   8:0    0     50G  0 disk
    ▒▒sda1                8:1    0    512M  0 part /boot/efi
    ▒▒sda2                8:2    0      1K  0 part
    ▒▒sda5                8:5    0   49.5G  0 part
      ▒▒vgmint-root     253:1    0   48.5G  0 lvm  /
      ▒▒vgmint-swap_1   253:2    0    976M  0 lvm  [SWAP]
    sdb                   8:16   0      1T  0 disk
    ▒▒sdb1                8:17   0   1024G  0 part
      ▒▒nxdata1-lv_nxd1 253:0    0 1023.1G  0 lvm  /data1
    sr0                  11:0    1   1024M  0 rom

    4.  Owner:-

    root@jrr-nswpmq-nxw02:~# ls -al /data1/
    total 28
    drwxr-xr-x  4 root root  4096 Jan  4 07:36  .
    drwxr-xr-x 20 root root  4096 Dec 29 08:50  ..
    drwxr-xr-x  2 root root  4096 Jan  4 08:04 'HD Witness Media'
    drwx------  2 root root 16384 Dec 29 08:50  lost+found

    Anything else?

     

     

    0
    Comment actions Permalink
  • Avatar
    Warren Welch

    Right, thanks for that.  I think I've got it sorted...

    So that first rule, the larger than 10% of the largest available was getting me...

    I'll take not of that.

    Now, I have a licensing issue cause I restored this.  How can I get these keys re-activated associated with the new hardware id?

    Thanks,
    Warrne

     

    0
    Comment actions Permalink
  • Avatar
    Anderson Chang
    • Edited

    Hi Warren Welch,

    I apologize that I did not explain the rule clearly, which might make you misunderstand the rule.

    A. The available space on the disk must be at least larger than 10% of the largest disk (storage volume) on the system.

    This mean, Nx Server will not allow recording to drives that are less than 10% the size of the largest drive in the system.
    If there are two drives on the system, let's say one is 12TB and the other is 1TB.
    1TB is lesser than 12TB × 10% = 1.2TB, the Nx Server will only use the 12TB drive for recording.

    On your machine, the nxdata1-lv_nxd1 is 1009GB, which is the largest drive and is more than 10 times larger than the /dev/sda1 and /dev/mapper/vgmint-root, so the Nx server should only take the nxdata1-lv_nxd1 for recording.
    Here is the support ARTICLE which describes more about how Nx Witness manages the storage.

     

    According to the information you provided, the owner of the /data1 is root, since the Nx Server application is run by the user networkoptix, it could only access and utilize the directory in which the networkoptix user has the read/write privileges.
    Therefore, please try to set the privileges of the folders for the networkoptix user.

     

    Also, please let us know which version of the Nx Witness you are currently running with.
    The latest Nx Witness version is 5.0.0.35745, if your Nx Witness is not running the latest version, you could first try to update the Nx Witness to the latest release.
     

    Thank you.
    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post