<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: device path for device in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426627#M14969</link>
    <description>I dont think there is any particular device path for external tape.&lt;BR /&gt;&lt;BR /&gt;If the controleur is seen and the tape is correctly attached it should be pick-up by the kernel and/or by the build in loadable modules &lt;BR /&gt;&lt;BR /&gt;This is usualy logged in /var/log/messages and can be found with dmesg &lt;BR /&gt;&lt;BR /&gt;Could you tell us more about your setup, lsmod extract of dmesg or boot log would help&lt;BR /&gt;&lt;BR /&gt;J-P</description>
    <pubDate>Sat, 20 Nov 2004 06:55:10 GMT</pubDate>
    <dc:creator>Huc_1</dc:creator>
    <dc:date>2004-11-20T06:55:10Z</dc:date>
    <item>
      <title>device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426626#M14968</link>
      <description>I have connected a new external tape device to my server , in another server , I use the device path /dev/st0 for the internal device , but I can't use the same device path for the new external tape device now , are they different for internal and external device ? if yes, what is the device path for external device ? thx in advance.</description>
      <pubDate>Sat, 20 Nov 2004 00:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426626#M14968</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-11-20T00:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426627#M14969</link>
      <description>I dont think there is any particular device path for external tape.&lt;BR /&gt;&lt;BR /&gt;If the controleur is seen and the tape is correctly attached it should be pick-up by the kernel and/or by the build in loadable modules &lt;BR /&gt;&lt;BR /&gt;This is usualy logged in /var/log/messages and can be found with dmesg &lt;BR /&gt;&lt;BR /&gt;Could you tell us more about your setup, lsmod extract of dmesg or boot log would help&lt;BR /&gt;&lt;BR /&gt;J-P</description>
      <pubDate>Sat, 20 Nov 2004 06:55:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426627#M14969</guid>
      <dc:creator>Huc_1</dc:creator>
      <dc:date>2004-11-20T06:55:10Z</dc:date>
    </item>
    <item>
      <title>Re: device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426628#M14970</link>
      <description>attach the lsmod and dmesg log , please help to advise what is the device path .. thx in advance.</description>
      <pubDate>Sun, 21 Nov 2004 22:27:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426628#M14970</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-11-21T22:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426629#M14971</link>
      <description>dmesg.txt</description>
      <pubDate>Sun, 21 Nov 2004 22:29:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426629#M14971</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-11-21T22:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426630#M14972</link>
      <description>lsmod.txt</description>
      <pubDate>Sun, 21 Nov 2004 22:31:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426630#M14972</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-11-21T22:31:29Z</dc:date>
    </item>
    <item>
      <title>Re: device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426631#M14973</link>
      <description>Ok.  I take it this 'dmesg' is from before the tape drive was attached.&lt;BR /&gt;&lt;BR /&gt;It looks as if the tape drive hasn't been detected at this point.&lt;BR /&gt;&lt;BR /&gt;At the very least, you need to get the SCSI controller to re-read it's attached ID's (I'm unsure how to do that with your controller.  A reboot will do it).&lt;BR /&gt;&lt;BR /&gt;For the moment though, does '/proc/scsi/scsi' list a 'SEQUENTIAL-ACCESS' device along with the 'DIRECT-ACCESS' and 'Processor' devices?&lt;BR /&gt;&lt;BR /&gt;If it does, then you can probably get away with 'modprobe st' ('st' being the driver module that drives tape drives in Linux).&lt;BR /&gt;&lt;BR /&gt;If not, reboot, try again.</description>
      <pubDate>Mon, 22 Nov 2004 00:48:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426631#M14973</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-11-22T00:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426632#M14974</link>
      <description>the below is my vi /proc/scsi/scsi , could help to analyse. thx in adance&lt;BR /&gt;&lt;BR /&gt;Attached devices: &lt;BR /&gt;Host: scsi0 Channel: 00 Id: 00 Lun: 00&lt;BR /&gt;  Vendor: IBM      Model: SERVERAID        Rev: 1.00&lt;BR /&gt;  Type:   Direct-Access                    ANSI SCSI revision: 02&lt;BR /&gt;Host: scsi0 Channel: 00 Id: 15 Lun: 00&lt;BR /&gt;  Vendor: IBM      Model: SERVERAID        Rev: 1.00&lt;BR /&gt;  Type:   Processor                        ANSI SCSI revision: 02&lt;BR /&gt;Host: scsi0 Channel: 01 Id: 08 Lun: 00&lt;BR /&gt;  Vendor: IBM      Model: 32P0032a S320  1 Rev: 1   &lt;BR /&gt;  Type:   Processor                        ANSI SCSI revision: 02</description>
      <pubDate>Mon, 22 Nov 2004 02:25:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426632#M14974</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-11-22T02:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: device path for device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426633#M14975</link>
      <description>Last time that I have problem with tape device using  RAID CTL  was hard :) &lt;BR /&gt;this documents may be help you:&lt;BR /&gt;&lt;A href="http://linuxbg.com/how_to/Tape_CCISS/Tape_scsi.txt" target="_blank"&gt;http://linuxbg.com/how_to/Tape_CCISS/Tape_scsi.txt&lt;/A&gt;&lt;BR /&gt;You must read kernel doc for your RAID CTL.&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Nov 2004 03:07:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/device-path-for-device/m-p/3426633#M14975</guid>
      <dc:creator>Ivajlo Yanakiev</dc:creator>
      <dc:date>2004-11-22T03:07:33Z</dc:date>
    </item>
  </channel>
</rss>

