#GLOBALSAN AND XTARGET SOFTWARE#

There is nothing wrong with that, but this is larger than 1024,Īnd could in certain setups cause problems with:ġ) software that runs at boot time (e.g., old versions of LILO)Ģ) booting and partitioning software from other OSs The number of cylinders for this disk is set to 1878738. fdisk /dev/sdbĭevice contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabelīuilding a new DOS disklabel with disk identifier 0x75450acd.Ĭhanges will remain in memory only, until you decide to write them.Īfter that, of course, the previous content won't be recoverable. Units = cylinders of 2048 * 512 = 1048576 bytesĭisk /dev/sdb doesn't contain a valid partition configure this disk. Setup a Physical Device for LVM fdisk -lĭisk /dev/sda: 29.9 GB, 29999759360 bytesĢ55 heads, 63 sectors/track, 3647 cylinders

Make sure to reboot at this point to device mapper can be loaded into the kernel and properly setup.

#GLOBALSAN AND XTARGET INSTALL#

Install LVMįirst I need the lvm stuff installed apt-get install lvm2 But it still ** that it happens at all.This HOWTO is on Ubuntu but should be very similar for Fedora, or Slackware based Linux boxen. Usually this behavior happens during idle times (the reason for the auto logout I think), so there is no harm done to the data. For 16s the volume was inaccessible, so that OSX declared it as ejected. 3:36:12 the iscsi app logged in again and re-established the connection. The access-log say that 3:35:56 the backup luns was logged out. the server complains that there was a disconnet on the 20th 3:36am. It automatically logs out the iscsi user after some time and the re-login from the Globalsan app sometimes takes too long, so that OSX detects a hard disconnect.

But I do still get disconnecting errors on my server, because of some weird behavior of the Qnap. I did not get a GLO warning from the Globalsan software yet, which is a good sign. And I did re-enable the HD sleep function in the Qnap box. I did reinstall the iscsi luns using instant alloction (witch is block access I think). If so, is there a way to prevent the Qnap from automatically logging out after some idle time? Thanks for your support, Tim Maybe the OS detects the login before the GlobalSAN app, so that I sometimes get the disconnection error message. Sometimes the time gap is short (see yourself in the log), sometimes it takes longer. If the Qnap logs out after a while for some reason, probably the GlobalSAN logs back in after a short time. Are these logouts/logins initiated by the Qnap? Why is that? The GlobalSAN support says that they never logout the device from their software. Strangely the targets logout and back in a few times every day. Is anybody else using GlobalSAN with a Qnap box? If so are there any problems? I started the iSCSI logging on the Qnap box and I get inormation only (no errors).

#GLOBALSAN AND XTARGET UPDATE#

They asked for the full price for an update so I went with GlobalSAN which is way cheaper. I never had any issues with that combination.

#GLOBALSAN AND XTARGET MAC#

Before I updated my Mac Mini it ran under 10.9 with the Xtend SAN software. They say it's not related to GlobalSAN but to the QNAP box. So I created a ticket with SNS support and they tried to find the error. Sometimes I get an error window telling me that either files or backup was not disconnected properly. I created 2 targets (backup and files), no ACLs. The target is a QNAP TS-659 with FW 4.2.6. Latest GlobalSAN iSCSI initiator is installed (5.3.1.555). Hi there, I have a Mac Mini server running under Sierra.

Globalsan and xtarget