Ubuntu :: Connecting To QNAP ISCSI Target
Nov 8, 2010connecting to my QNAP iSCSI target from Ubuntu (10.04). I've followed the instructions in the QNAP manual, but I something goes wrong when I need to list the nodes. When I enter
[Code]....
connecting to my QNAP iSCSI target from Ubuntu (10.04). I've followed the instructions in the QNAP manual, but I something goes wrong when I need to list the nodes. When I enter
[Code]....
I want to run ISCSI target on CentOS. Both "scsi-target-utils" and "iscsi-target" can be used.
They seem to have the same function.
Is there any significant difference between them, on performance or stability?
I've been trying to figure out how to set up a partition on my CentOS serve r as an iscsi target, so I can access it from another CentOS client.I've been reading the manuals and various pages on the web, and nothing is very clear. I just want to be able to create a partition on my server, define it as a target, and then have my client initiator mount it.
View 2 Replies View Relatedi have installed centOS5. i want to configure iscsitarget. i know that iscsi target is built-in in centOS5. how can i use iscsiadm utility to configure iscsi target. please describe in detailed.
1.) i want to make 4 drives (4Drives OR 4LUNs)in iscsi target each with 5GB space.
2.) please describe and highlight where we mention disk space(5GB)
I want to install iscsi-target package in opensuse 11.1.
Step 1:
linux-7bvl:~ # zypper search iscsitarget
Loading repository data...
[code]....
I have an Intel NIC supporting iSCSI boot.I successfully installed Karmic Server 64-bit on the iSCSI target.But it won't boot from it.It looks like it can't mount the iSCSI target:
Code:
Gave up waiting for root device. Common problems: ...
and it drops me to a BusyBox shell.
[code]....
was able to install iSCSI target via yum, configured a couple of target LUNs, in fact all the same steps that worked on Fedora 10 appeared identical. However, when I try to start the service the following happens.
[root@Server01 ~]# service iscsi-target start
Starting iSCSI target service: FATAL: Error inserting crc32c_intel (/lib/modules/2.6.29.4-167.fc11.i686.PAE/kernel/arch/x86/crypto/crc32c-intel.ko): No such device
[code]...
I am trying to install iscsi-target on centos 5.4 i386. When I go into the iscsi-target directory and type make I get the following error:
[root@cluster-storage iscsitarget-1.4.19]# make
cc: /lib/modules/2.6.18-164.el5/build/include/linux/version.h: Datei oder Verzeichnis nicht gefunden
cc: keine Eingabedateien
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -le: unary operator expected
/bin/sh: line 0: [: -lt: unary operator expected
make -C usr
make[1]: Entering directory `/opt/iscsitarget-1.4.19/usr' .....
make: *** [kernel] Fehler 2
iSCSI Server, can I change the default port 3260 to other port ?
View 1 Replies View RelatedI have never done this before but stood up a new Debian (testing) x64 system. It only has 146GB available for RAID1 so I created a 500GB iSCSI LUN on my NAS device on the network and am really confused how I can attach my Debian to the iSCSI LUN I created. Right now the OS is installed all locally on the machine but I would like the iSCSI LUN to be the /home directory for mail storage. Is this possible or do I need to mount the LUN to a newly created folder / mount point that is locally attached?
View 1 Replies View RelatedQnaps run on Atom: is it possible to install Ubuntu server at all? I like them being small and easy on the power drain, but I'd rather have my OS of choice.
View 3 Replies View RelatedI'm having issues copying files from a USB attached HDD (formatted by the NAS to EXT3) over to a NAS device. First some background info (maybe relevant or may not be): I upgraded the HDD in my NAS and now I'm unable to copy the files over from the old HDD while plugged into the NAS. Also tried copying over from windows 7 (64 & 32 bit) as well as an XP machine using EXT2FDS & IFS resulting in perpetual re-booting of all three machines.As a result of that I got a brainwave to try copying the files over from a bootable Linux DVD (Unbuntu 11.04) to the Nas over the network. I am in Unbuntu now but I am having problems copying to the NAS. It seems to work when I select individual files but when I select afolder/folders/sub folders to copy over an "error while copying" dialog box appears appears. For example: in "Show More Details" here is the copied text from an error: "Error stating file '/media/f0745264-c91b-4528-9fe3-e3469cdb13cc/Public/MANUALS/oliver_manual_99_99GM_tractors_O_7_1956.pdf': Input/output error"
View 2 Replies View RelatedI have a QNAP 219P which has an ARM processor. I want to run SPLUNK, the SNMP/Polling management program on it (not that crazy for a small business server I wouldn't have thought).
Anyway, I can download SPLUNK in the following forms:
splunk-4.1.5-85165.i386.rpm
splunk-4.1.5-85165-linux-2.6-intel.deb
splunk-4.1.5-85165-Linux-i686.tgz
splunk-4.1.5-85165-linux-2.6-x86_64.rpm
splunk-4.1.5-85165-linux-2.6-amd64.deb
splunk-4.1.5-85165-Linux-x86_64.tgz
When I use Nautilus to copy files to my NAS-disk they end up with owner "root" and I cannot edit them. If I copy them back to my PC they have owner <username> and are editable.
My fstab is: //10.0.0.20/Qmultimedia /media/Mmedia cifs credentials=/root/.smbcreds,directio,iocharset=utf8,noacl,noperm,rw, nobootwait 0 0
Of course I want my Mmedia mount on the NAS to behave like another disk on my PC; i.e. owner should be <username> and the files should be editable.
What I am trying to do is edit the link target to force ip=xxxx.xxx.xxx string at end. I have a software program which access 4 different servers running the software but with different configs. In xp I can copy links and modify as above to correctly force the program to the various servers.
I have read the various how tos on hard vs sym links which I get. Playing around with hardlinks and sysmlinks (the examples I find) does not seem to be what I need. Feel like this is pretty basic stuff but I am a bit stumped.
I just installed Ubuntu 9.10 and its great. However when I connect to the internet at home it shows that the connection has been established but I still cant connect to the internet. My flatmates are all able to connect. However, I am able to connect from work both wirelessly and through an ethernet cable.
View 2 Replies View RelatedI have an iSCSI target on my Ubuntu 10.04 LTS server that is giving me access to 3 x 2TB volumes. I am using LVM to create 1 big volume and using it as a place for my backup software to write to. Upon initial setup I tested to see if the connection would still be there after a reboot, and it was. After going through the trouble of configuring my backup software (ZManda) and doing a few very large backups I had to reboot my SAN (OpenFiler) for hardware reasons. I took my server down while performing the maintenance and brought it back up only after the SAN work was done. Now, the LVM volume is listed as "not found" when booting.
Using iscsiadm I can see the target but LVM doesn't know of any volumes that exist using those targets. I need to get it back up and running and then troubleshoot the reboot issue.
I'm running 10.04 64-bit diskless on ESXi, installed as a minimal virtual machine. I want this server to access an iSCSI drive. The machine can view the iSCSI shares with iscsiadm, and can even log into the drive. When I do an iSCSI login, this appears in /var/log/messages:
Aug 17 11:08:21 ubuntutest kernel: [1123295.329972] scsi4 : iSCSI Initiator over TCP/IP
So, it appears that open-iSCSI is working correctly. But no new /dev/sd* nodes appear, and nothing new appears in /dev/disk/by-path. I'd expect to see /dev/disk/by-path/ip-XXXXXXXXX. fdisk -l shows nothing but the boot drive. My guess is that the "minimal kernel" doesn't include some necessary module or driver.
I am currently wanting to connect to an NAS unit that I have. I have installed open-iSCSI and have made the following changes to the iscsi_conf file:
Quote:
# To set a CHAP username and password for initiator
# authentication by the target(s), uncomment the following lines:
node.session.auth.username = "user"
node.session.auth.password = "12 digit pass"
[Code].....
My goal is to get the iSCSI initiator to connect after a reboot. Mounting after connecting I am sure this will be another challenge.
On windows I installed the iscsi initiator which tells me my pc id. Then I take that id and put it in my storage which automatically gives me my extra disk. How can I find out the id assigned to my ubuntu pc?
View 1 Replies View RelatedI have used open-iscsi for a couple of years on fedora and oracle linux, but since I use ubuntu for my desktop, web servers and mysql servers I thought I would be nice to do so on our new MySQL-server which should be connected to our Qlogic SAN. The installation went well after figuring out how to put two network cards on the same network, which seems to be the Qlogic way to do multipath. But I cannot make open-iscsi to log on automatically after reboot. Is there something different with open-iscsi on ubuntu?
Everything works if I logon and do:
iscsiadm -m node -l
multipath -v2
And then mount the volumes but if I try to put them in my fstab like:
/dev/MySQLdata/data/var/lib/mysql/ext4_netdev1 2
/dev/MySQLbackup/backup/var/mysqlbackupext4_netdev1 2
I seem to get logged into the NetApp filer fine - it shows the session, but I don't get a device. And don't panic - the system is CentOS 5.4, but the system is named OpenVMS (don't ask . . . ) iscsiadm shows me logged into the NetApp and the session is up.
[Code]....
iscsi-client OS: SLES10SP3i586I configured this sles10sp3 box an iscsi-client via YaST (yast2 iscsi-client), but 'lsscsi' or 'fdisk -l' doesnt show any iscsi-disk
# rcopen-iscsi restart
Closing all iSCSI connections: Logging out of session [sid: 1, target: iqn.2010-03.com.ibm:sn.135026430, portal: 192.168.0.1,3260]
[code]....
I'm trying to increase the size of an iSCSI device. On the LUN side, the provision size has been expanded already. I expanded the size of this device from 15GB to 30GB.
I then rescanned the devices:
[root@ps-dev-nfs ~]# iscsiadm -m node --targetname iqn.2001-05.com.equallogic:0-8a0906-db7938c02-c6a994bda8a4a773-ps-dev-nfs -R
Rescanning session [sid: 1, target: iqn.2001-05.com.equallogic:0-8a0906-db7938c02-c6a994bda8a4a773-ps-dev-nfs, portal: 10.3.2.10,3260]
[Code].....
want to create a iSCSI connection which mounts /home directory to a share on my NAS via iSCSI. Does anyone know if this is possible on a RHEL 5.4 machine? I am building the server from scratch and then creating the iSCSI mount point in /etc/fstab. After the /home directory is mounted on the mail server, I will copy all the mailboxes over to the /home directory via iSCSI.
View 4 Replies View RelatedI have an iSCSI device that is large, ~17TB usable, and I've created an XFS file system at the device level. I mount the device no problem and am able to touch and remove files without issue. I start my application and within about 5-10 minutes I start seeing the following entries appear in /var/log/messages
[Code]...
Does anyone have any good articles on mounting a Ubuntu volume as an iSCSI share on a windows box? Originally I was just going to use a SAMBA share but it turns out samba has issues with my lan security. So I thought since all I really want to do is create the share on my backup server that an iSCSI device would do. Been using the following article with limited success... [URL]
View 2 Replies View RelatedI'm trying to jump Ubuntu Server 10.04.1 x86_64 on an HP DL360 G5. After loading the modules for install, I'm greeted with an iSCSI prompt that cannot be bypassed. Hitting Finish brings me right back to the same iSCSI prompt.The issue seems to be identical to y kickseed file is as follows:
Code:
#platform=x86, AMD64, or Intel EM64T
# System authorization information
[code]....
I'm wanting to run 10.10 server from a root disk located on an iSCSI server. My server is FreeBSD 8 running isc-dhcpd and is sharing out a 20GB iSCSI disk. I've run the server install CD (currently testing in VMWare), and it finds the iSCSI share without a problem. I'm able to install the OS just fine, but the problems start when I try to boot the installation. I'm booting off a gPXE iso until I can get PXE chain-loading figured out. My DHCP config looks as such:
Code:
host mm-iscsi
{
hardware ethernet 00:50:56:3f:3f:bf;
fixed-address 10.50.3.245;
[Code]....
I'm trying to make a fresh install of Ubuntu 10.10 Server 64bit but is stuck with the Partitioning Disk part and Ubuntu 10.04 LTS provides the same error. The installation wizard gives me a menu:
!! Partitioning disks
This menu allows you to configure iSCSI volumes
iSCSI configuration actions
[code].....