CommandviewSDM

[Miles Denison]

A bit of background first. I have a va7410, and a ds2405. After a long while of strenuous use my va7410 up and died, so I would like to throw the disks in the 2405. This would mean reformatting the block size from 520, to 512.

After installing commandview in order to issue a JBODfmt, I'm getting errors when trying to use it: "launcher" yields "Error getting database reference from localhost", and "armdiscover" comes back with "Failed to obtain remote database interface to host: localhost"

I have gone into the commIpAddr.txt, and access.dat and changed the IPs to match my current configuration (192.168.0.110). I've also uninstalled/reinstalled commandview a few times now to no avail.

I can view the disks with an ioscan just fine.

Is there some small step that I've missed during the install?

Thanks for any help,
Miles.

[Torsten.]

Please check this too:

/opt/sanmgr/hostagent/config/access.dat

[Miles Denison]

as I mentioned above, I've checked access.dat and commIpAddr.txt already, and changed them both to 192.168.0.110.

[hvhari]

If you are planning to use the disks in DS2405 without the VA7410, then there is no need to use armdiscover / launcher. These commands will work only when you have access to Lun0 on VA7410 on the host. If VA7410 is dead, you can not use these commands.

You can connect the DS2405 directly to the host and use them as normal disks and configure using LVM.

[Miles Denison]

Ah. Well that would explain it.

In that case how would I go about reformatting those disks back to 512 block size? mediainit only works with a 512 size I believe.

[hvhari]

I belive, it formatting to 512k block size will be automatically taken care via the usual process of adding the disks to LVM. I personally does not have any setup like this to test now.

[Torsten.]

>> I belive, it formatting to 512k block size will be automatically taken care via the usual process of adding the disks to LVM


No.

You need command view SDM to do this.

Remove the product, remove the files and directories that are left in /opt/sanmgr/ and install again:

rm -fR /opt/sanmgr

rm -fR /etc/opt/sanmgr

rm -fR /var/opt/sanmgr

[Miles Denison]

Done, but again no change.

During the install procedure, when I am told to make sure that the correct services/daemons/scripts (technical term?) are running with ps "-ef |grep pfs" it only shows 4 of the 5 processes are running, "root 2592 2579 2 15:31:30 pts/tb 0:00 grep pfs" is not listed.

Could this have anything to do with the problem? I'm fairly new to the os.

[Torsten. · Accepted solution]

Normally the problem is always the wrong IP in the config files, but if you delete them, it cannot be the problem any longer.


Do you still get the same error message?


There is also a "wrong" kernel parameter possible, but the system will tell you during the installation (max_thread_proc I think).

[Miles Denison]

I've doubled the thread size from it's default. I've deleted the config files (access and commIpAddr), and when reinstalled played with the default configuration, wildcard, and a localhost address.

No luck yet.

Thanks for the help.