<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>linux.dev.scsi Google Group</title>
  <link>http://groups.google.com/group/linux.dev.scsi</link>
  <description></description>
  <language>en</language>
  <item>
  <title>Linux and bad SCSI HD: can I force mount a partition?</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/bfaf5c90a55ffd45/131a04b289c9bc45?show_docid=131a04b289c9bc45</link>
  <description>
  Hello, &lt;br&gt; Copy the whole hd to another disk or an ftp server. This makes sure that &lt;br&gt; another disk failure won&#39;t destroy any more data. If you know the exact &lt;br&gt; start/end of the partition, you can mount it using something like this: &lt;br&gt; losetup -o start_position_in_bytes /dev/loopX image &lt;br&gt; mount /dev/loopX /mnt &lt;br&gt; regards
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/bfaf5c90a55ffd45/131a04b289c9bc45?show_docid=131a04b289c9bc45</guid>
  <author>
  wolfgang_.fisc...@freenet.de
  (Wolfgang Fischer)
  </author>
  <pubDate>Fri, 08 Aug 2003 08:25:13 UT
</pubDate>
  </item>
  <item>
  <title>how to create /dev/sdc ?</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/4d05818963e29fd0/cc65790489baeeb2?show_docid=cc65790489baeeb2</link>
  <description>
  RS wrote: &lt;br&gt; Two ways: &lt;br&gt; 1) cd /dev; ./MAKEDEV sdc &lt;br&gt; man MAKEDEV for more info. For instance &amp;quot;./MAKEDEV -S sdc&amp;quot;, will show you &lt;br&gt; what it will do without actually doing it. &lt;br&gt; 2) mknod -m 0660 /dev/sdc b 8 32 &lt;br&gt; chown root.root /dev/sdc &lt;br&gt; (I actually got the above from running MAKEDEV with the -S option).
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/4d05818963e29fd0/cc65790489baeeb2?show_docid=cc65790489baeeb2</guid>
  <author>
  renr...@yahoo.com
  (V. Turner)
  </author>
  <pubDate>Fri, 08 Aug 2003 05:20:45 UT
</pubDate>
  </item>
  <item>
  <title>how to create /dev/sdc ?</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/4d05818963e29fd0/7ef9364d655fcce2?show_docid=7ef9364d655fcce2</link>
  <description>
  Hi, there, &lt;br&gt; I accidentally deleted /dev/sdc. &lt;br&gt; Would someone please tell me how to create it back. &lt;br&gt; Is it by using &#39;mknod&#39;? What would be the MAJOR and MINOR &lt;br&gt; be? I think the type is 8. &lt;br&gt; Thanks in advance! &lt;br&gt; Roger &lt;br&gt; email: rs...@bigmailbox.net
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/4d05818963e29fd0/7ef9364d655fcce2?show_docid=7ef9364d655fcce2</guid>
  <author>
  noem...@nospam.com
  (RS)
  </author>
  <pubDate>Fri, 08 Aug 2003 04:38:37 UT
</pubDate>
  </item>
  <item>
  <title>Linux and bad SCSI HD: can I force mount a partition?</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/bfaf5c90a55ffd45/89d2bbe6e0d14abb?show_docid=89d2bbe6e0d14abb</link>
  <description>
  Hi, there, &lt;br&gt; I have this SCSI HD which developed a problem. It seems that &lt;br&gt; sector 0 of the HD turned bad. &lt;br&gt; When my Redhat Linux 7.3 boot up, I got this message:
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/bfaf5c90a55ffd45/89d2bbe6e0d14abb?show_docid=89d2bbe6e0d14abb</guid>
  <author>
  noem...@nospam.com
  (RS)
  </author>
  <pubDate>Fri, 08 Aug 2003 03:45:56 UT
</pubDate>
  </item>
  <item>
  <title>Will a LVD drive work with the NCR 53c876 controller?</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/505d984964d6713f/e296817d6916afbc?show_docid=e296817d6916afbc</link>
  <description>
  I have a 53c876-based controller with 68-pin cables and I need to &lt;br&gt; replace a drive. Is the 68-pin connector all I need to worry about and &lt;br&gt; current-generation drives will work fine, or do I need to find an old &lt;br&gt; non-LVD 68-pin drive? &lt;br&gt; I really hope the new U160 and U320 drives are drop-in compatible. I &lt;br&gt; am, of course, aware that they won&#39;t run at full speed...
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/505d984964d6713f/e296817d6916afbc?show_docid=e296817d6916afbc</guid>
  <author>
  jo...@aproposretail.com
  (John Hardin)
  </author>
  <pubDate>Wed, 06 Aug 2003 16:39:34 UT
</pubDate>
  </item>
  <item>
  <title>cdrom broken?</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/516669fc9bcc3c22/5c9eccf29331ecc7?show_docid=5c9eccf29331ecc7</link>
  <description>
  Hi! &lt;br&gt; Trying to copy the first (audio-) cd of the year ended with xcdroast`s &lt;br&gt; failure message: &lt;br&gt; cdda2wav: Input/output error. ReadStandard10: scsi sendcmd: cmd timeout &lt;br&gt; after 0.294 (300) s &lt;br&gt; CDB: 28 00 00 00 00 2E 00 00 32 00 &lt;br&gt; resid: 102400 &lt;br&gt; cmd finished after 0.294s timeout 300s &lt;br&gt; a few hundred times. &lt;br&gt; This is the according syslog entry:
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/516669fc9bcc3c22/5c9eccf29331ecc7?show_docid=5c9eccf29331ecc7</guid>
  <author>
  rotoploo...@freenet.de
  (Tim Boneko)
  </author>
  <pubDate>Fri, 03 Jan 2003 12:42:29 UT
</pubDate>
  </item>
  <item>
  <title>UPDATE: scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/f29904e772fc3666?show_docid=f29904e772fc3666</link>
  <description>
  Hey, you can&#39;t have everything!! ;-)
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/f29904e772fc3666?show_docid=f29904e772fc3666</guid>
  <author>
  j...@kona.homeip.net
  (Jason Adams)
  </author>
  <pubDate>Wed, 11 Dec 2002 03:55:15 UT
</pubDate>
  </item>
  <item>
  <title>UPDATE: scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/82c899ee1f36af89?show_docid=82c899ee1f36af89</link>
  <description>
  &amp;lt;snip&amp;gt; &lt;br&gt; &lt;p&gt;Unfortunately, my joy was short lived. sane has decided to seg fault &lt;br&gt; without fail again. &lt;br&gt; David
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/82c899ee1f36af89?show_docid=82c899ee1f36af89</guid>
  <author>
  dko...@kosmosisland.com
  (David Koski)
  </author>
  <pubDate>Wed, 11 Dec 2002 00:37:34 UT
</pubDate>
  </item>
  <item>
  <title>UPDATE: scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/c417c86ec337bea0?show_docid=c417c86ec337bea0</link>
  <description>
  JP, &lt;br&gt; I too have had 7.1 on the same hardware without problems. Even 8.0, but &lt;br&gt; with 8.1 I have to have the following boot options: &lt;br&gt; ide=nodma apm=off acpi=off &lt;br&gt; Add to that: &lt;br&gt; max_scsi_luns=1 &lt;br&gt; ..to make my scanner work. But it works great now--no device repeats in &lt;br&gt; the device list, no segmentation faults. Correction on my
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/c417c86ec337bea0?show_docid=c417c86ec337bea0</guid>
  <author>
  dko...@kosmosisland.com
  (David Koski)
  </author>
  <pubDate>Tue, 10 Dec 2002 18:05:46 UT
</pubDate>
  </item>
  <item>
  <title>UPDATE: scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/eacebd0550f31651?show_docid=eacebd0550f31651</link>
  <description>
  David, &lt;br&gt; I have the exact same problem with my scanner(microtec E6) on SuSe8 &lt;br&gt; but on the very same system,Suse 7.1 did not have this problem..Go &lt;br&gt; Figure.. &lt;br&gt; Goodluck, &lt;br&gt; JP
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/eacebd0550f31651?show_docid=eacebd0550f31651</guid>
  <author>
  jolp...@hotmail.com
  (jolphil)
  </author>
  <pubDate>Tue, 10 Dec 2002 14:24:58 UT
</pubDate>
  </item>
  <item>
  <title>UPDATE: scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/9bd0fcaa9519959b?show_docid=9bd0fcaa9519959b</link>
  <description>
  Right on! Now my scanner works perfectly with &amp;quot;Segmentation faults&amp;quot; too! &lt;br&gt; Thanks, &lt;br&gt; David Koski &lt;br&gt; da...@KosmosIsland.com
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/9bd0fcaa9519959b?show_docid=9bd0fcaa9519959b</guid>
  <author>
  dko...@kosmosisland.com
  (David Koski)
  </author>
  <pubDate>Tue, 10 Dec 2002 10:05:19 UT
</pubDate>
  </item>
  <item>
  <title>UPDATE: scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/442a50107ec122cf?show_docid=442a50107ec122cf</link>
  <description>
  This article in the SuSE knowledge base refers to cdburners, but &lt;br&gt; it might work for scanners too..... &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://sdb.suse.de/en/sdb/html/max_scsi_luns.html&quot;&gt;[link]&lt;/a&gt;
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/442a50107ec122cf?show_docid=442a50107ec122cf</guid>
  <author>
  j...@kona.homeip.net
  (Jason Adams)
  </author>
  <pubDate>Tue, 10 Dec 2002 06:38:35 UT
</pubDate>
  </item>
  <item>
  <title>UPDATE: scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/3eb34136a9031429?show_docid=3eb34136a9031429</link>
  <description>
  More info; /proc/scsi/scsi shows that the duplicate scanner devices are &lt;br&gt; assigned unique LUNs: &lt;br&gt; Attached devices: &lt;br&gt; Host: scsi0 Channel: 00 Id: 00 Lun: 00 &lt;br&gt; Vendor: IBM Model: DDYS-T18350N Rev: SA2A &lt;br&gt; Type: Direct-Access ANSI SCSI revision: 03 &lt;br&gt; Host: scsi0 Channel: 00 Id: 01 Lun: 00
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/3eb34136a9031429?show_docid=3eb34136a9031429</guid>
  <author>
  dko...@kosmosisland.com
  (David Koski)
  </author>
  <pubDate>Mon, 09 Dec 2002 02:22:45 UT
</pubDate>
  </item>
  <item>
  <title>scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/53046a81379f1135?show_docid=53046a81379f1135</link>
  <description>
  &amp;lt;snip&amp;gt; &lt;br&gt; Yes, and yes. It is the only device on the BusLogic, and it is terminated &lt;br&gt; at the scanner. &lt;br&gt; Thanks, &lt;br&gt; David
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/53046a81379f1135?show_docid=53046a81379f1135</guid>
  <author>
  dko...@kosmosisland.com
  (David Koski)
  </author>
  <pubDate>Sun, 08 Dec 2002 20:20:55 UT
</pubDate>
  </item>
  <item>
  <title>scanner repeated in device list</title>
  <link>http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/0e3b698bb3fb8ebb?show_docid=0e3b698bb3fb8ebb</link>
  <description>
  Is the scanner the last device in the external chain and is it &lt;br&gt; terminated properly? If you have another terminator, I&#39;d suggest trying &lt;br&gt; to swap them. I didn&#39;t have this problem, but my SCSI scanner had misc &lt;br&gt; problems until I put a new terminator on it.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/linux.dev.scsi/browse_thread/thread/867584235fde251c/0e3b698bb3fb8ebb?show_docid=0e3b698bb3fb8ebb</guid>
  <author>
  walthar...@mindspring.com
  (Walt Harris)
  </author>
  <pubDate>Sun, 08 Dec 2002 15:20:23 UT
</pubDate>
  </item>
  </channel>
</rss>
