Hello, i have followed standard instruction to instll mhvtl on centos 5.4 but this doesn't work, when i try to start the service i have this report:
/etc/init.d/mhvtl: line 310: modprobe: command not found
No kernel module loaded to feed these daemons.
The fact that 'modprobe: command not found' indicates you either do not have /sbin in your path, which is most likely because you are not attempting to start this as the superuser (root).
Did you compile and install the mhvtl kernel module ?
A few details on how you installed and what steps you performed will be useful in identifying what you missed or did incorrect.
- Did you install using the pre-compiled RPMS ?
- Did you download the source and build the kernel module ?
i compiled and installed the kernel source and when i launch "make " in /usr/src/redhat/SOURCE/..mhvtl-018/kernel i have this:
WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0401166) and 'check_x87'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc04012ef) and 'try_name'
i installed rpms and kernel source newly and now works :D, i need now to add this lib to tsm for testing purposes, my problem is that my tsm server is not on the same host of the library, how can i add the library to tsm?
i installed rpms and kernel source newly and now works :D,
Great news. I'm assuming the installation of the kernel source was the missing bit.
i need now to add this lib to tsm for testing purposes, my problem is that my tsm server is not on the same host of the library, how can i add the library to tsm?
OK, you need to search this forum for iSCSI configuration setup details.
I'm assuming your TSM server is on another type of operating system ?
If TSM is running on a version of Linux, make it easier for yourself and install the mhvtl s/w on the same box as TSM.
Several on the list has had success with SCST (SCST doesn't allow the SECURITY PROTOCOL IN / SECURITY PROTOCOL OUT op codes through - so you can't test out the native encryption).
I've had a lot of success with STGT.
I like it down to the following basic differences.
SCST - All in kernel space, so building custom kernel & modules is required.
- Potentially faster as it's all in kernel space.
- Programming errors will result in kernel panic/oops.
STGT - All in user space.
- Very easy to build.
- Any programming errors will result in a core dump.
Either SCSI Target will work and which one you use is just personal preference.
I have experienced similar with Windows 7 and it was at the end Windows firewall .. check closer if you see anything like Global Profile or such ... Also avoid target names with upper case letters in them as windows hate those also.