- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- FC Tape Drive for Redhat V4
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2007 03:46 PM
06-13-2007 03:46 PM
In tru64 I would use
# hwmgr -scan scsi
Is there an equivalent function in redhat linux?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2007 07:04 PM
06-13-2007 07:04 PM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2007 07:04 PM
06-13-2007 07:04 PM
Re: FC Tape Drive for Redhat V4
first you need to know your fibre-HBA.
$ lspci | grep -i fibre
the (re)load the apropriate driver:
e.g. lpfc or qla2200v6 or ...
$DRVR=lpfc
$ #modprobe -r $DRVR # remove driver
$ modprobe $DRVR # load driver
then check if you see your tape(s):
$cat /proc/scsi/scsi
Then check Tape status:
$ mt -f /dev/st0 status
rgds
HGH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2007 07:08 PM
06-13-2007 07:08 PM
Re: FC Tape Drive for Redhat V4
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/as-s390/RELEASE-NOTES-U3-s390-en.html
Support for fabric rediscovery through sysfs is now available in Red Hat Enterprise Linux 4 Update 3. For the Qlogic (qla2xxx) and Emulex (lpfc) Fibre Channel HBA drivers, run the following commands to perform redisocvery and rescan for new storage:
echo "1" > /sys/class/fc_host/hostXYZ/issue_lip
echo "- - -" > /sys/class/scsi_host/hostXYZ/scan
In some Fibre Channel configurations, an operating system will automatically detect the addition of a new target device while the system is running. In other configurations, it is necessary to issue the following command to detect a new target device:
echo 1 > /sys/class/fc_host/hostn/issue_lip
Where hostn corresponds to the appropriate adapter.
When a new Logical Unit is created on a particular target, a command such as the following is required to detect and configure it:
echo "b t l" > /sys/class/scsi_host/hostn/scan
Where b is the bus, t is the target, and l is the LUN to be scanned on hostn.
Wild cards can also be used, such as the following example:
echo "- - -" > /sys/class/scsi_host/host2/scan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2007 06:17 PM
06-14-2007 06:17 PM
Re: FC Tape Drive for Redhat V4
like i said, in my case all is detected at boot (no need for extra drivers or tools), which can be checked easily with dmesg.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2007 06:14 PM
06-20-2007 06:14 PM
Re: FC Tape Drive for Redhat V4
I have scanned the scsi device and can see the changer and (i think) tape drive in /proc/scsi/scsi. All good. But still no /dev/st0 or /dev/rmt# or /dev/changer.
Do I need to reboot the server for these changes to take effect?
Thanks in advance.
Graham
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2007 06:36 PM
06-20-2007 06:36 PM
Re: FC Tape Drive for Redhat V4
check if "st" kernel module is loaded:
$ lsmod | grep -w st
# if not loaded (re)load it:
($ rmmod st )
$ modprobe st
What do you see in /proc/scsi/scsi?
(try attached script).
rgds
HGH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2007 06:41 PM
06-20-2007 06:41 PM
Re: FC Tape Drive for Redhat V4
[root@dcpbl01 ~]# modprobe st
[root@dcpbl01 ~]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: HSV200 Rev: 6000
Type: RAID ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 00 Lun: 01
Vendor: HP Model: HSV200 Rev: 6000
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 00 Lun: 02
Vendor: HP Model: HSV200 Rev: 6000
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: HP Model: HSV200 Rev: 6000
Type: RAID ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: HSV200 Rev: 6000
Type: RAID ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: HP Model: HSV200 Rev: 6000
Type: RAID ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 02 Lun: 02
Vendor: COMPAQ Model: MSL5000 Series Rev: 0518
Type: Medium Changer ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 05
Vendor: HP Model: NS E1200-160 Rev: 568c
Type: RAID ANSI SCSI revision: 04
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2007 07:10 PM
06-20-2007 07:10 PM
Re: FC Tape Drive for Redhat V4
does the script from my last post show a device file for your changer?
can you give the output of:
$ ls -l /sys/bus/scsi/devices/0:0:2:2/
rgds
HGH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2007 08:38 PM
06-21-2007 08:38 PM
Re: FC Tape Drive for Redhat V4
You might need to add the following line to /etc/modules.conf
options scsi_mod max_scsi_luns=128
and rebuild your kernel.
Take a look at the following RedHat article:
http://kbase.redhat.com/faq/FAQ_43_2706.shtm
Hope this helps,
Regards,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2007 11:47 AM
06-24-2007 11:47 AM
Re: FC Tape Drive for Redhat V4
[root@dcpbl01 0:0:2:2]# ls -l /sys/bus/scsi/devices/0:0:2:2
lrwxrwxrwx 1 root root 0 Jun 25 09:44 /sys/bus/scsi/devices/0:0:2:2 -> ../../../devices/pci0000:00/0000:00:02.0/0000:03:00.0/0000:04:03.0/host0/target0:0:2/0:0:2:2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2007 07:44 PM
06-24-2007 07:44 PM
Re: FC Tape Drive for Redhat V4
can you give the output of:
$ ls -l /sys/bus/scsi/devices/0:0:2:2/*
With "*" (sorry it was lost in copy'n paste)
Have you tried my script? Does it show some tapes?
rgds
HGH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2007 12:53 PM
06-25-2007 12:53 PM
Re: FC Tape Drive for Redhat V4
--w------- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/delete
-rw-r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/detach_state
-r--r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/device_blocked
-rw-r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/dump
lrwxrwxrwx 1 root root 0 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/generic -> ../../../../../../../../class/scsi_generic/sg6
-r--r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/model
-rw-r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/queue_depth
--w------- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/rescan
-r--r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/rev
-r--r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/scsi_level
-rw-r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/state
-rw-r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/timeout
-r--r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/type
-r--r--r-- 1 root root 4096 Jun 26 10:52 /sys/bus/scsi/devices/0:0:2:2/vendor
/sys/bus/scsi/devices/0:0:2:2/power:
total 0
-rw-r--r-- 1 root root 4096 Jun 26 10:52 state
[root@dcpbl01 0:0:2:2]#