

- #Drobo dashboard cannot connect to ip address install
- #Drobo dashboard cannot connect to ip address windows
If you have multiple volumes on the target, you’ll see them all in GUI file manager.

All volumes on the Drobo were ‘visible’ in file manager.*note* I’d read that this Drobo didn’t support ext4 and after formatting the volume, I found that to be false.Ĭonfirm that you can write to it # touch /drobo/testfileĬheck the file system disk space usage. If it returns 1 aligned, you’re good to go.

2048s is a good choice for the starting sector.Ĭheck the disk alignment # parted /dev/sdb align-check optimal 1 Read this blog post and make the adjustments. Warning: The resulting partition is not properly aligned for best performance If by chance you get an error that reads: # parted -script /dev/sdb mklabel primary 0% 100% Run It again to create the primary partition # parted -script /dev/sdb mklabel msdos Run the parted command against the device to create a new disk label. # dmesg | tail Time to partition the device. If the login is successful, run the dmesg | tail command to see if the kernel sees the logical blocks. List out the /proc/partitions file to see the new disk. Once your volumes are discovered, you can login to them # iscsiadm -m node -T :1 -p 10.253.52.25 -login # iscsiadm -m discovery -t sendtargets -p 10.253.53.25 Use the iscsiadm command to discover the target. # cat /proc/partitionsĪdd the target name to /etc/iscsi/initiatorname.iscsi file, save and exit. Once you login to the iSCSI volume, a new one will appear and that’s the one we’ll format. List out the /proc/partitions file to see the devices that you have currently.
#Drobo dashboard cannot connect to ip address install
On the CentOS server, install the iscsi package # yum -y install iscsi-initiator-utils $ sudo yum install -y scsi-target-utils Configure the server I installed the iscsi initiator utilities. **note** your Drobo must be on the same subnet as your server. I also disabled SELinux on this test box. I did not enable CHAP, but it can be easily configured on the machine. Information you’ll need to connect to machine:
#Drobo dashboard cannot connect to ip address windows
(See Drobo Online User Guide) PreparationĪfter configuring the device’s IP and other settings via USB from my Windows desktop using Drobo Dashboard, I created a 1TB, unformatted volume. The Drobo and the host computer must be on the same subnet in order for this to work.
