<?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: Proliant DL 380 hot-plug tape drive with SUSE Linux in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436290#M15224</link>
    <description>Thanks for the rescue attempt. &lt;BR /&gt;&lt;BR /&gt;On a hunch, I ejected the tape which we had used with a previous Linux version, rebooted the server and inserted a fresh tape (AIT-100). When I tried a typical command (mt -f /dev/st0 status), the tape showed. I then TAR'd and restored a directory, and everything went swimmingly. Since I a relative newbie at Linux, it was very satisfying, because this tape backup issue has frustrated our program to bring up a bunch of Linux servers. Thanks again&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 07 Dec 2004 13:23:06 GMT</pubDate>
    <dc:creator>Dale McPherson_1</dc:creator>
    <dc:date>2004-12-07T13:23:06Z</dc:date>
    <item>
      <title>Proliant DL 380 hot-plug tape drive with SUSE Linux</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436286#M15220</link>
      <description>We were able to get DL-380 hot plug tape drive working with RedHat 8 distro, using "enage scisi" info in cciss.txt document.&lt;BR /&gt;We recently upgraded server to SUSE Linux Enterprise Server Version 9, and can't access the tape drive even though we're using the same scsi engage command. &lt;BR /&gt;&lt;BR /&gt;Running dmseg provides following output:&lt;BR /&gt;cciss0: No device changes detected.&lt;BR /&gt;cciss0: No appropriate SCSI device detected, SCSI subsystem not engaged.&lt;BR /&gt;&lt;BR /&gt;The hot-plug AIT tape drive still shows a power light and will accept or eject tapes.&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Dec 2004 14:12:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436286#M15220</guid>
      <dc:creator>Dale McPherson_1</dc:creator>
      <dc:date>2004-12-03T14:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 380 hot-plug tape drive with SUSE Linux</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436287#M15221</link>
      <description>I unfortunately don't have access to a SUSE machine, but my guess would be that the kernel setting called 'CONFIG_CISS_SCSI_TAPE' is not set.&lt;BR /&gt;&lt;BR /&gt;This setting tells the driver/kernel that the RAID controller is capable of taking a hot-plug tape drive.&lt;BR /&gt;&lt;BR /&gt;On RH machines, this is enabled by default.  I don't know about SUSE machines.&lt;BR /&gt;&lt;BR /&gt;Without the kernel's ".config" file, I'm unsure how to test whether this setting is on or off however.</description>
      <pubDate>Fri, 03 Dec 2004 17:10:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436287#M15221</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-12-03T17:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 380 hot-plug tape drive with SUSE Linux</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436288#M15222</link>
      <description>I generated a config file readout with:&lt;BR /&gt;zcat /proc/config.gz &amp;gt; config.txt and the&lt;BR /&gt;CONFIG_CISS_SCSI_TAPE parameter was set to 'Y'.&lt;BR /&gt;&lt;BR /&gt;Is that is a valid way of finding the kernel configuration?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 05 Dec 2004 17:16:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436288#M15222</guid>
      <dc:creator>Dale McPherson_1</dc:creator>
      <dc:date>2004-12-05T17:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 380 hot-plug tape drive with SUSE Linux</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436289#M15223</link>
      <description>It's not a method I was aware of, and can't find an equivlanet on any of my redhat or fedora boxes, so do not know.</description>
      <pubDate>Sun, 05 Dec 2004 20:24:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436289#M15223</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-12-05T20:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 380 hot-plug tape drive with SUSE Linux</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436290#M15224</link>
      <description>Thanks for the rescue attempt. &lt;BR /&gt;&lt;BR /&gt;On a hunch, I ejected the tape which we had used with a previous Linux version, rebooted the server and inserted a fresh tape (AIT-100). When I tried a typical command (mt -f /dev/st0 status), the tape showed. I then TAR'd and restored a directory, and everything went swimmingly. Since I a relative newbie at Linux, it was very satisfying, because this tape backup issue has frustrated our program to bring up a bunch of Linux servers. Thanks again&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Dec 2004 13:23:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-dl-380-hot-plug-tape-drive-with-suse-linux/m-p/3436290#M15224</guid>
      <dc:creator>Dale McPherson_1</dc:creator>
      <dc:date>2004-12-07T13:23:06Z</dc:date>
    </item>
  </channel>
</rss>

