Tag: Ubuntu

Categories
User Guides exacqVision Server Categories Products

Installing exacqVision Software on 64-bit Ubuntu

Description

Instructions for installing exacqVision Server and Client on 64-bit Ubuntu varies based on the Ubuntu version.

Product 

  • exacqVision Client
  • exacqVision Server
  • exacqVision Web Service
  • Ubuntu Linux

Solution

Download the following files depending on which software you are installing, then follow the instructions below for either 12.04, 14.04, 16.04, 18.04, 20.04 or 22.04.

Software Downloads

exacqVision Server

exacqVision Client

exacqVision Web Service

Dependencies – Only needed for 12.04, 14.04 and 16.04.

IMPORTANT: Installers will list the version number within the file name. In the steps below, use the version number in the downloaded file name in place of the text <version>
Example: exacqVisionServer_23.06.1.0_x64.deb

<br>

Ubuntu 22.04 (Jammy Jellyfish):

Installing exacqVision Server in 64-bit Ubuntu 22.04

  1. Install the Server deb file with:
    sudo dpkg -i exacqVisionServer_&lt;version&gt;_x64.deb
    Note: Follow the prompts. You may see a message regarding dependency problems. Fix dependency issues by running (requires internet access):
    sudo apt install -f

Installing exacqVision Client in 64-bit Ubuntu 22.04

  1. Install the Client deb file with:
    sudo dpkg -i exacqVisionClient_&lt;version&gt;_x64.deb

Installing exacqVision Web Service in 64-bit Ubuntu 22.04

  1. Install the Web Service deb file with:
    sudo dpkg -i exacqVisionWebService_&lt;version&gt;_x64.deb
    Note: Follow the prompts. You may see a message regarding dependency problems. Fix dependency issues by running (requires internet access):
    sudo apt install -f
    <br>

Ubuntu 20.04 (Focal Fossa):

Installing exacqVision Server in 64-bit Ubuntu 20.04

  1. Install the Server deb file with:
    sudo dpkg -i exacqVisionServer_&lt;version&gt;_x64.deb
    Note: Follow the prompts. You may see a message regarding dependency problems. Fix dependency issues by running (requires internet access):
    sudo apt install -f

Installing exacqVision Client in 64-bit Ubuntu 20.04

  1. Install the Client deb file with:
    sudo dpkg -i exacqVisionClient_&lt;version&gt;_x64.deb

Installing exacqVision Web Service in 64-bit Ubuntu 20.04

  1. Install the Web Service deb file with:
    sudo dpkg -i exacqVisionWebService_&lt;version&gt;_x64.deb
    Note: Follow the prompts. You may see a message regarding dependency problems. Fix dependency issues by running (requires internet access):
    sudo apt install -f
    <br>

Ubuntu 18.04 (Bionic Beaver):

Installing exacqVision Server in 64-bit Ubuntu 18.04

  1. Install the Server deb file with:
    sudo dpkg -i exacqVisionServer_&lt;version&gt;_x64.deb
    Note: Follow the prompts. You may see a message regarding dependency problems. Fix dependency issues by running (requires internet access):
    sudo apt install -f

Installing exacqVision Client in 64-bit Ubuntu 18.04

  1. Install the Client deb file with:
    sudo dpkg -i exacqVisionClient_&lt;version&gt;_x64.deb

Installing exacqVision Web Service in 64-bit Ubuntu 18.04

  1. Install the Web Service deb file with:
    sudo dpkg -i exacqVisionWebService_&lt;version&gt;_x64.deb
    Note: Follow the prompts. You may see a message regarding dependency problems. Fix dependency issues by running (requires internet access):
    sudo apt install -f
    <br>

Ubuntu 16.04 (Xenial Xerus):

Installing exacqVision Server in 64-bit Ubuntu 16.04

  1. Install the dependency package using the following command:
    sudo dpkg -i exacqVisionServerRC-deps.deb
  2. Install the Server deb file with:
    sudo dpkg -i exacqVisionServer_&lt;version&gt;_x64.deb
  3. Note: Follow the prompts. You will see a message that some packages are missing. Select ‘OK’ and continue. Fix new dependency issues by re-running:
    sudo apt install -f

Installing exacqVision Client in 64-bit Ubuntu 16.04

  1. If desired, install hardware decompression dependencies with:
    sudo apt-get install i965-va-driver:i386 libva-x11-1:i386
  2. Install the Client deb file with:
    sudo dpkg -i exacqVisionClient_&lt;version&gt;_x64.deb
    Note: You may see a message regarding dependency problems. Fix dependency issues by running (requires internet access): sudo apt install -f
  3. Reboot

Installing exacqVision Web Service in 64-bit Ubuntu 16.04

  1. Install dependencies with:
    sudo apt-get install libc6:i386 libstdc++6:i386 zlib1g:i386 libexpat1:i386
  2. Install the Web Service deb file with:
    sudo dpkg -i exacqVisionWebService_&lt;version&gt;_x64.deb
    <br>

Ubuntu 14.04 (Trusty Tahr):

Installing exacqVision Server in 64-bit Ubuntu 14.04

Note: If installing exacqVision Server 6.9.36 or earlier, you must first execute the following command before completing the installation procedure:
sudo apt-get install libgtk2-perl

  1. Ensure that your dpkg is configured to allow installation of 32-bit packages; otherwise, you will see an error message similar to “wrong architecture i386.” To verify, execute the following command:
    sudo dpkg --print-foreign-architectures
    If you do not see “i386” execute the following commands:
    sudo dpkg --add-architecture i386
    sudo apt-get update
  2. Install the dependency package using the following command:
    sudo dpkg -i exacqVisionServerRC-deps.deb
  3. Install the Server deb file with:
    sudo dpkg -i exacqVisionServer_&lt;version&gt;_x64.deb
    <br>

Ubuntu 12.04 (Precise Pangolin):

Installing exacqVision Server and in 64-bit Ubuntu 12.04

  1. Ensure that your dpkg is configured to allow installation of 32-bit packages; otherwise, you will see an error message similar to “wrong architecture i386.” To verify, execute the following command:
    sudo dpkg --print-foreign-architectures
    If you do not see “i386” execute the following commands:
    sudo dpkg --add-architecture i386
    sudo apt-get update
  2. Install the dependency package using the following command:
    sudo dpkg -i exacqVisionServerRC-deps.deb
  3. Install the Server deb file with:
    sudo dpkg -i exacqVisionServer_&lt;version&gt;_x64.deb
  4. You will encounter the following known dependency error:
  5. To fix this error, execute the following command:
    sudo apt-get install libdaemon0:i386
    After the libdaemon0 package successfully completes installation, the exacqVision Server package will automatically install.

<br>

Categories
Knowledge Support Support exacqVision Client exacqVision Server Categories Products

exacqVision Client and Server version 5.10 and Later Cannot be Installed on Ubuntu 6.06

Beginning with version 5.10, exacqVision Client and exacqVision Server cannot be installed on Ubuntu 6.06. An error message will appear during installation indicating that “Dependency is not satisfiable.”<br>

Categories
Knowledge Support Support Categories Products exacqVision Hardware

exacqVision Drives Incorrectly Marked as Read Only in Ubuntu Linux

If a hard drive in an Ubuntu Linux-based exacqVision system has an error in its file system, it could be marked as read only. This could cause a failure in the process of storing recorded video.

Starting with version 4.9, exacqVision detects whether a drive is read only. To determine whether a hard drive is read only in exacqVision 4.8 and earlier, try to save a temporary file to it by entering sudo touch /mnt/edvr/2/temp.file in a Terminal window (where “/mnt/edvr/2” is the name of the drive). If this command fails, the drive is read only. Alternatively, you can enter cat /proc/mounts and look for “ro” in the result.

To remount drives and change them to read-write, enter sudo mount -a.

<br>

exacqVision-Drives-Incorrectly-Marked-as-Read-Only-in-Ubuntu-Linux.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Bad Package Quality Error when Installing exacqVision Software on Ubuntu 11.04

Exacq recommends installing exacqVision software on Ubuntu 10.04 because of its extensive testing within the Ubuntu community and its status as a Long Term Support version.

However, if you try to install exacqVision Client and exacqVision Server software version 4.5 and older, exacqVision Web Service, or Enterprise Health Manager on a Ubuntu 11.04 system, the new Ubuntu Software Center installer displays a false error message indicating a “package of bad quality.” This error can be ignored. Changes in exacqVision version 4.6 prevent this message from being displayed.

<br>

Bad-Package-Quality-Error-when-Installing-exacqVision-Software-on-Ubuntu-11.04.pdf
Categories
Knowledge Support Support exacqVision Server Categories exacqVision Hardware Products

Changing the Automatic Login User in Linux (Legacy)

To change the automatic login user in Linux, complete the steps provided for your Linux version.

<br>

Ubuntu 18.04 and higher

On systems built by Exacq with Ubuntu version 18.04 and higher, the ability to use the operating system to configure automatic logins has been removed as a security measure.

You may, however, utilize the Exacq Kiosk User software to create kiosk user accounts and select whether or not a kiosk user account will automatically login.

See also: Setting up the Kiosk User for ExacqVision Systems

Ubuntu 16.04

  1. Log out of the User account.
  2. Log in as an Admin.
  3. From the upper-right corner, click the computer icon from the menu bar.
  4. Select System Settings from the menu.
  5. In the Settings window that appears, select Users.
  6. Select Unlock. Enter the admin password when prompted.
  7. Highlight the user account you wish to automatically login.
  8. Toggle the Automatic Login switch for the user account.
  9. Close the User Accounts window.
  10. Restart the system to test the new automatic login.

Ubuntu 14.04

  1. Log out of the User account.
  2. Log in as an Admin.
  3. From the upper-left corner, open the Applications menu.
  4. Expand the System Tools option from the menu.
  5. Expand the Administration menu, then select User Accounts.
  6. Select Unlock. Enter the admin password when prompted.
  7. Highlight the user account you wish to automatically login.
  8. Toggle the Automatic Login switch for the user account.
  9. Close the User Accounts window.
  10. Restart the system to test the new automatic login.

Ubuntu 12.04

  1. Log out of the User account.
  2. Log in as an Admin.
  3. From the upper-left corner, open the Applications menu.
  4. Expand the System Tools option from the menu.
  5. Select System Settings.
  6. In the System Settings window, select User Accounts.
  7. Select Unlock. Enter the admin password when prompted.
  8. Highlight the user account you wish to automatically login.
  9. Toggle the Automatic Login switch for the user account.
  10. Close the User Accounts window.
  11. Restart the system to test the new automatic login.

Ubuntu 10.04

  1. Log out of the User account.
  2. Log in as an Admin.
  3. In the upper-left corner, select System from the menu bar.
  4. Select Administration from the menu.
  5. Select Login Screen from the menu.
  6. Select Unlock. Enter the admin password when prompted.
  7. Select Log In As and then select the desired user from the drop-down list.
  8. Click Close.
  9. Restart the system to test the new automatic login.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Adding/Configuring Locales on Ubuntu Linux

For Ubuntu, adding a new locale (language) is a two-step process. First, determine the UTF8-encoded locale name, then generate the UTF8-encoded locale.

<br>

Determine Locale Name

Open a command line window and type:

less /user/share/i18n/SUPPORTED

This will list all of the locales Ubuntu supports. Scroll down to find the one that matches the ISO 639-1/ISO 3369-1 language codes of the language you are wanting to add.

Please be aware that some of the locales will not have a suffix (look closely – there is no period (‘.’) between the xx_YY language code and the following characters). Others will have a suffix of ‘.UTF-8.’ Still others will have suffixes like ‘@euro’ and ‘.EUC-KR.’ For ExacqVision, you must use the locale with the ‘UTF-8’ suffix.

For example, Irish in Ireland has these three locales:

...
ga_IE.UTF-8 UTF-8
ga_IE ISO-8859-1
ga_IE@euro ISO-8859-15
...

The first one has a ‘UTF-8’ suffix and should be used. The second and third ones do not have the ‘UTF-8’ suffix and should NOT be used.

<br>

Generate Locale

Since we’ve now determined the proper locale to generate, head back to the command prompt and type (once for each locale you wish to generate):

sudo locale-gen ga_IE.UTF-8

To actually trigger Ubuntu to generate the locale(s), type:

sudo dpkg-reconfigure locales

To verify that the locale(s) were generated, type:

locale -a

<br>

Change the Locale

For any given run of any program

Also, you may run the exacqVision Client from the command line preceded by an env setting. For example:

env LANG=es_CL.utf8 /usr/local/exacq/client/edvrclient

will cause the exacqVision Client to run with the Chilean Spanish translation.

<br>

Permanently

To change the locale, you may change the entire operating system by going to System->Administration->Language Support and changing the default language dropdown. This will require a reboot.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

How do I monitor Disk I/O?

Disk I/O (input/output) plays a crucial role in how you experience the exacqVision software. If disks are unable to handle the amount of data being written to them, you could see reliability issues.

To help pinpoint the source of these issues on your server, use the following steps as a guide based on your system operating system.

<br><br>

Linux (Ubuntu)

How to view I/O wait

Ubuntu, and most versions of Linux, come with the ‘top’ command already installed.

Press CTRL+ALT+T to open a Terminal window and enter ‘top’ by typing top and pressing Enter.

Towards the top-left, find the row that shows ‘%Cpu(s)’ and follow this line over to the right. The ‘wa’ statistic here reports the percentage of time the CPU is waiting for disk I/O to finish.

You may exit ‘top’ by pressing ‘q’.

I/O wait is an indicator to look further. This is where tools such as ‘iotop’ can help determine which processes have high I/O percentages.

How to find the causes of high I/O wait times

The ‘iotop’ command does not come pre-installed with Ubuntu, so you will probably need to install it.

When connected to the internet, enter the following commands to install ‘iotop’.

sudo apt-get update
sudo apt-get install iotop

You will probably need to run ‘iotop’ with elevated privileges using the sudo command, so enter sudo iotop.

The top left and right sections display the overall read and write throughput.

Below this, ‘iotop’ displays a live updating list of processes and their individual read and write I/O values.

The column you are most concerned with is that of ‘IO’. This column reports the percentage of time the process on that row was performing I/O against its total processing time.

Let’s say it takes approximately 1 second to write 200 MB to disk. You’ve issued a Save command to write 160 MB to file, which took 800ms, then your I/O wait time would be 80%.

Many systems today have multiple cores. Use Terminal again to enter the following command cat /proc/cpuinfo and find the number of Cores. You may need to scroll up a bit to find this.

Calculate 1/# of Cores.

If your wait time percent is regularly near or above this amount, your CPU is spending a lot of time waiting for disks to catch up, and thus slowing your system.

<br><br>

Windows

Monitoring disk I/O with Performance Monitor

Windows packages a tool called Performance Monitor (perfmon.exe) on it’s operating system. Open this application by clicking on the Windows (Start) icon on the toolbar and typing “Performance Monitor,” then click to open it.

from the left-hand navigation panel, expand ‘Monitoring Tools’ and select ‘Performance Monitor.’

The monitor panel will usually be very empty by default, so you will need to add the specific counters you wish to monitor.

Click the green ‘Add’ button from the toolbar above the main panel.

Beneath ‘Available Counters,’ scroll to find ‘PhysicalDisk’ and expand it. The statistics you will be interested in are:

  • ‘% Disk Time’
  • ‘% Idle Time’
  • ‘Current Disk Queue Length’
  • ‘Disk Reads/sec’
  • ‘Disk Writes/sec’

When you highlight each of these, the below panel allows you to select individual drives, ‘All Instances’, or ‘_Total’. Total will sum all activity between multiple instances, whereas selecting ‘All Instances’ adds them all individually to your displayed data. On your NVR you will probably only be concerned with the recording disk(s).

After selecting each counter and the instances below, be sure to click the ‘Add>>’ button below to move it to the ‘Added counters’ panel on the right.

NOTE: If your system is utilizing RAID or you have partitions spanning multiple disks in a JBOD configuration you can also monitor these using statistics found under ‘LogicalDisk,’ which provides statistics for partitions rather than physical disks.

Before moving on, you may also wish to expand ‘Processor’ from the ‘Available counters’ panel and add:

  • ‘% Idle Time’

When you have finished adding all your counters, click the ‘OK’ button.

By default the Performance Monitor displays a graph, but this can be difficult to read with many counters added at once, nor does it display the current values well. From the toolbar, use the ‘Display Type’ icon to cycle through the type options with each click, or use the drop-down arrow beside it to select ‘Report.’

You are no able to monitor the live disk I/O values and processor time.

The figure you will be most concerned with is the ‘% Disk Time.’ You could also choose to display the ‘% Disk Read Time’ and ‘% Disk Write Time,’ but by using ‘% Disk Time, this is the sum of both reading and writing, so the total I/O for that disk.

Many systems today have multiple cores. Press CTRL+SHIFT+Esc to open Windows Task Manager, then click on the ‘Performance’ tab to find the number of cores on your system. This example from a Windows 10 machine shows 6 cores.

Calculate 1/# of Cores.

If your idle time percent is regularly near or above this amount, then your CPU is spending a lot of time waiting for disks to catch up, and thus slowing your system. I/O wait is merely and indicator to look further.

Adding the ‘Available MBytes’ instance from the ‘Memory’ counter in Performance Monitor will show you if a large amount of memory is being consumed while data is waiting to be written to disk. The ‘Current Disk Queue Length’ instance from the ‘PhysicalDisk’ counter will help display how many operations are in the disk queue waiting to be completed.

Finally, you may search under ‘Process’ for ‘IO Data Bytes/sec’ for the ‘exacqd’ instance to display the amount of ‘IO Bytes’ the Exacq application is performing. High processor idle time, high % Disk Time, combined with high memory usage can point to a disk I/O bottleneck on the system.

<br><br>

Factors that can affect I/O

  • Average I/O performance per disk
    Higher Read/Write speeds mean more data transactions per second.
  • RAID Arrays
    Having several disks in an array increases I/O transactions.
  • RAID Factor
    While RAID factors are varied to provide a number of levels to mitigate the possibility of data loss through fault-tolerance, the RAID factor can determine if more read/write transactions are necessary for each operation. For example, all other things being equal, RAID 5 has better I/O performance than RAID 6 due to the additional parity required by RAID 6.


<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

How do I change the listening port number for exacqVision Server?

By default, the exacqVision Client communicates with exacqVision Servers on port 22609. If your network does not allow port 22609, or if you need to forward the port on multiple exacqVision systems, you can change the exacqVision Server’s listening port number. To do this, complete steps detailed on this page.

NOTE: The exacqVision Default Ports article states that 22610 is reserved for interprocess communication. This is true when using the default client to server port set to 22609. If this is changed to a port other than 22609, the reserved port becomes your chosen port number plus one.
Example: If you change 22609 to 2350, the reserved port becomes 2351.<br><br>

Windows 11, 10, 8, 7, Vista, XP

  1. Log into the system hosting the exacqVision Server application.<br><br>
  2. Exit all exacqVision software.<br><br>
  3. Highlight the exacqVision Server service listed, and Stop the ExacqVision Server service, in one of three ways:
    • Press the ‘Stop’ icon from the toolbar.
    • Click the ‘Stop’ link from the left-hand side.
    • Right-click the service name and select ‘Stop’.

      Note: Leave the Services window open, as you will need to restart the service later.<br><br>
  4. Open the Notepad application. Search for the application from the Windows Start menu, right-click and choose to ‘Run as Administrator’.
    <br><br>
  5. Use Notepad to Open the following file:
    C:\Program Files\exacqVision\Server\streampi.xml<br>
    If you are using a 32-bit installation, select Program Files (x86) instead of Program Files.<br>
    NOTE: In the Open file dialogue, you will likely need to change the file type field from ‘Text Documents (*.txt)’ to All Files (*.*)’ to see file types of other extensions.

    <br><br>
  6. In the streampi.xml file, scroll down until you find the line which states: <Port value="22609" />.

    Change the number to the port you want to use between the quotation marks (” “). Do NOT use port 22610 since this is reserved. The following example changes the port number to ‘11111’.
    <br><br>
  7. After changing the port number, open the File menu, select Save, and close the editor window.<br><br>
  8. Restart the exacqVision Server Service by clicking ‘Start’ button, link or from the right-click menu, in the Services window that you opened earlier. You should now be able to connect using the new port number.<br><br>
  9. In the exacqVision Client, make sure the port number on the ‘Add Systems’ page matches the new port number.
    NOTE: The exacqVision Web Service is also a client of the exacqVision Server. Therefore, if using the exacqVision Web Service you may also be required to change the connecting port in the exacqVision Web Service Configuration.<br><br>

Ubuntu 20.04, 18.04, 16.04, 14.04, 12.04, 10.04

  1. Log into the system hosting the exacqVision Server application.<br><br>
  2. Exit all exacqVision software.<br><br>
  3. Open a Terminal command prompt by pressing CTRL+ALT+T

    NOTE: Depending on system settings, your Terminal window may appear with different colors than pictured.<br><br>
  4. Stop the exacqVision Server by entering one of the following commands:
    • sudo service edvrserver stop
    • sudo /etc/init.d/edvrserver stop

      NOTE: The sudo command elevates your system privileges in order to edit this file. Your system may prompt you for an administrator password. Enter this password if prompted. Linux systems do not display any characters when entering passwords in the CLI.

      NOTE: On some systems you may see output that reads:
      sudo: unable to resolve host <hostname>
      Ignore this message if seen.<br><br>
  5. You may use your preferred Linux editing tool, but in our example we will be using ‘gedit’.

    Use gedit to open the streampi.xml file containing the settings for the exacqVision Server by entering:
    sudo gedit /usr/local/exacq/server/streampi.xml<br><br>
  6. Locate the line which states: <Port value:"22609" />

    Change the number to the port you want to use between the quotation marks (” “). Do NOT use port 22610 since this is reserved. The following example changes the port number to ‘11111’.
    <br><br>
  7. Click ‘Save’ to commit your changes and close the editor window. <br><br>
  8. Returning to the Terminal prompt, enter one of the following commands to restart the exacqVision Server:
    • sudo service edvrserver start
    • sudo /etc/init.d/edvrserver start<br><br>
  9. In the exacqVision Client, make sure the port number on the ‘Add Systems’ page matches the new port number.

    NOTE: The exacqVision Web Service is also a client of the exacqVision Server. Therefore, if using the exacqVision Web Service you may also be required to change the connecting port in the exacqVision Web Service Configuration.

<br>

Categories
Categories exacqVision Webservice Products

Can ExacqVision Server run on Linux?

Yes, ExacqVision Server has been tested on the following:

  • Ubuntu 22.04 (64-bit)
  • Ubuntu 20.04 (64-bit)
  • Ubuntu 18.04 (64-bit)
  • Ubuntu 16.04 (64-bit)
  • Ubuntu 14.04 (64-bit or 32-bit with PAE1)
  • Ubuntu 12.04 (32-bit with PAE1)2
  • Ubuntu 10.04 (32-bit with PAE1)2

Version numbers are listed as YY.MM.

ExacqVision supports Ubuntu LTS releases only. Canonical provides LTS releases every two years. Long Term Support (LTS) lasts for a period of 10 years after release. ExacqVision will provide support for future LTS releases of Ubuntu as they become available.<br>

  1. PAE stands for Physical Address Extension, which allows 32-bit systems to use more than 4GB of memory.
  2. These versions are no longer receiving security updates from Canonical. At the end of long term support, future Exacq software releases will not be tested on these versions.

<br>

Categories
Knowledge Support Support Categories exacqVision Webservice Products

iSCSI on Ubuntu

Retrieved From HowtoForge

<br>

Setting Up The Initiator

Install the initiator:

sudo apt-get install open-iscsi

<br>

Next we open /etc/iscsi/iscsid.conf…

sudo nano /etc/iscsi/iscsid.conf

… and set node.startup to automatic:

<br>

Then we restart the initiator:

sudo /etc/init.d/open-iscsi restart

<br>

Now we connect to the target (server2) and check what storage devices it has to offer:

sudo iscsiadm -m discovery -t st -p IP_Address_of_ISCSI_Server

server1:~# iscsiadm -m discovery -t st -p 192.168.0.101
192.168.0.101:3260,1 iqn.2001-04.com.example:storage.lun1
server1:~#

<br>

sudo iscsiadm -m node

<br>

server1:~# iscsiadm -m node
192.168.0.101:3260,1 iqn.2001-04.com.example:storage.lun1
server1:~#

<br>

The settings for the storage device iqn.2001-04.com.example:storage.lun1 on 192.168.0.101:3260,1 are stored in the file /etc/iscsi/nodes/iqn.2001-04.com.example:storage.lun1/192.168.0.101,3260,1/default.

<br>

We need to set the username and password for the target in that file; instead of editing that file manually, we can use the iscsiadm command to do this for us:

sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --op=update --name node.session.auth.authmethod --value=CHAP
sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --op=update --name node.session.auth.username --value=iSCSI_username
sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --op=update --name node.session.auth.password --value=iSCSI_password

<br>

Now we can log in, either by running…

sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --login

server1:~# iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --login
Logging in to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260]
Login to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260]: successful
server1:~#

<br>

… or by restarting the initiator:

sudo /etc/init.d/open-iscsi restart

<br>

(If you want to log out, you can run iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --logout)

<br>

If your iSCSI device has already been formated, and contains data, please skip to Mounting your drive.

<br>

Continue on ONLY if your device is being set up for the first time, or you instructed to do so by tech support.

<br>

In the output of

<br>

sudo fdisk -l

<br>

you should now find a new hard drive (/dev/sdb in this example); that’s our iSCSI storage device:

<br>

server1:~# fdisk -l

Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00031334

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        3749    30113811   83  Linux
/dev/sda2            3750        3916     1341427+   5  Extended
/dev/sda5            3750        3916     1341396   82  Linux swap / Solaris

Disk /dev/sdb: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table
server1:~#

<br>

To use that device, we must format it (replace /dev/sdX with the value obtained from the last command):

<br>

sudo fdisk /dev/sdX

<br>

server1:~# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x882944df.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won’t be recoverable.

<br>

The number of cylinders for this disk is set to 20480.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

<br>

Command (m for help): <– m
Command action
   a   toggle a bootable flag
   b   edit bsd disklabel
   c   toggle the dos compatibility flag
   d   delete a partition
   l   list known partition types
   m   print this menu
   n   add a new partition
   o   create a new empty DOS partition table
   p   print the partition table
   q   quit without saving changes
   s   create a new empty Sun disklabel
   t   change a partition’s system id
   u   change display/entry units
   v   verify the partition table
   w   write table to disk and exit
   x   extra functionality (experts only)

<br>

Command (m for help): <– n
Command action
   e   extended
   p   primary partition (1-4)
<– p
Partition number (1-4): <– 1
First cylinder (1-20480, default 1): <– ENTER
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-20480, default 20480): <– ENTER
Using default value 20480

<br>

Command (m for help): <– t
Selected partition 1
Hex code (type L to list codes): <– L

<br>

0  Empty           1e  Hidden W95 FAT1 80  Old Minix       be  Solaris boot
 1  FAT12           24  NEC DOS         81  Minix / old Lin bf  Solaris
 2  XENIX root      39  Plan 9          82  Linux swap / So c1  DRDOS/sec (FAT-
 3  XENIX usr       3c  PartitionMagic  83  Linux           c4  DRDOS/sec (FAT-
 4  FAT16 <32M      40  Venix 80286     84  OS/2 hidden C:  c6  DRDOS/sec (FAT-
 5  Extended        41  PPC PReP Boot   85  Linux extended  c7  Syrinx
 6  FAT16           42  SFS             86  NTFS volume set da  Non-FS data
 7  HPFS/NTFS       4d  QNX4.x          87  NTFS volume set db  CP/M / CTOS / .
 8  AIX             4e  QNX4.x 2nd part 88  Linux plaintext de  Dell Utility
 9  AIX bootable    4f  QNX4.x 3rd part 8e  Linux LVM       df  BootIt
 a  OS/2 Boot Manag 50  OnTrack DM      93  Amoeba          e1  DOS access
 b  W95 FAT32       51  OnTrack DM6 Aux 94  Amoeba BBT      e3  DOS R/O
 c  W95 FAT32 (LBA) 52  CP/M            9f  BSD/OS          e4  SpeedStor
 e  W95 FAT16 (LBA) 53  OnTrack DM6 Aux a0  IBM Thinkpad hi eb  BeOS fs
 f  W95 Ext'd (LBA) 54  OnTrackDM6      a5  FreeBSD         ee  EFI GPT
10  OPUS            55  EZ-Drive        a6  OpenBSD         ef  EFI (FAT-12/16/
11  Hidden FAT12    56  Golden Bow      a7  NeXTSTEP        f0  Linux/PA-RISC b
12  Compaq diagnost 5c  Priam Edisk     a8  Darwin UFS      f1  SpeedStor
14  Hidden FAT16 <3 61  SpeedStor       a9  NetBSD          f4  SpeedStor
16  Hidden FAT16    63  GNU HURD or Sys ab  Darwin boot     f2  DOS secondary
17  Hidden HPFS/NTF 64  Novell Netware  b7  BSDI fs         fd  Linux raid auto
18  AST SmartSleep  65  Novell Netware  b8  BSDI swap       fe  LANstep
1b  Hidden W95 FAT3 70  DiskSecure Mult bb  Boot Wizard hid ff  BBT
1c  Hidden W95 FAT3 75  PC/IX
Hex code (type L to list codes): <-- 83

<br>

Command (m for help): <– w
The partition table has been altered!

<br>

Calling ioctl() to re-read partition table.
Syncing disks.
server1:~#

<br>

Afterwards, the output of

<br>

sudo fdisk -l

<br>

should look as follows:

<br>

server1:~# fdisk -l

<br>

Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00031334

<br>

 Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        3749    30113811   83  Linux
/dev/sda2            3750        3916     1341427+   5  Extended
/dev/sda5            3750        3916     1341396   82  Linux swap / Solaris

<br>

Disk /dev/sdb: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x882944df

<br>

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       20480    20971504   83  Linux
server1:~#

<br>

Now we create a filesystem on /dev/sdb1…

<br>

sudo mkfs.ext3 /dev/sdX1

<br>

Issue the following command, and make note of the largest number listed< /p>

<br>

ls /mnt/edvr/

<br>

server1:~# ls /mnt/edvr
0 1
server1:~#

<br>

Mount the drive with the command below, substituting Y with the the largest number returned from the previous command + 1 (2 in our example)

<br>

sudo mount /dev/sdX1 /mnt/edvr/2

<br>

You should now see the new device in the outputs of…

sudo mount

<br>

server1:~# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sdX1 on /mnt/edvr/2 type ext3 (rw)
server1:~#

<br>

… and

<br>

sudo df -h

<br>

server1:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1              29G  685M   27G   3% /
tmpfs                 253M     0  253M   0% /lib/init/rw
udev                   10M   88K   10M   1% /dev
tmpfs                 253M     0  253M   0% /dev/shm
/dev/sdX1              20G  173M   19G   1% /mnt/edvr/Y

<br>

server1:~#

You can unmount it like this:

<br>

sudo umount /mnt/edvr/Y

<br>

To have the device mounted automatically at boot time, e.g. in the directory /storage, we create that directory…

<br>

mkdir /storage

<br>

… and add the following line to /etc/fstab:

<br>

sudo nano /etc/fstab

<br>

For test purposes, you can now reboot the system:

<br>

sudo reboot

<br>

After the reboot, the device should be mounted:

<br>

sudo mount

<br>

server1:~# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sdX1 on /mnt/edvr/Y type ext3 (rw,_netdev)
server1:~#

<br>

df -h server1:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1              29G  685M   27G   3% /
tmpfs                 253M     0  253M   0% /lib/init/rw
udev                   10M   88K   10M   1% /dev
tmpfs                 253M     0  253M   0% /dev/shm
/dev/sdX1              20G  173M   19G   1% /mnt/edvr/Y

<br>