Amanda-Users

Re: /dev/sg4 no such device

2003-06-20 12:33:27
Subject: Re: /dev/sg4 no such device
From: Gene Heskett <gene.heskett AT verizon DOT net>
To: tom.brown AT goodtechnology DOT com
Date: Fri, 20 Jun 2003 12:30:51 -0400
On Friday 20 June 2003 12:06, Tom Brown wrote:
>> Has that kernel been recompiled to 'scan all luns'?
>
>it was yes - and it is now running on 2.4.28

Since the newest 2.4 series kernel is 2.4.21 I''l assume thats a typu 
<G>
>>>dmesg says
>>
>> There should be a few more lines below the above clip that show
>> what st* devices were assigned.  From the above, I'd guess the
>> changer device is now /dev/sg3 maybe.  Experiment a bit, using
>> mtx, and use whichever device mtx can use to control the robotics.
>>
>> Those extra lines in dmesg should look a bit like this:
>> ----
>> st: Version 20020805, bufsize 32768, wrt 30720, max init. bufs 4,
>> s/g segs 16
>> Attached scsi tape st0 at scsi0, channel 0, id 1, lun 0
>> ~~~~~~~~~~~~~~~~~~~^^^~~~~^^^^^~~~~~~~~~~^~~~~~^~~~~~~^
>> Attached scsi generic sg1 at scsi0, channel 0, id 1, lun 1,  type
>> 8
>> ~~~~~~~~~~~~~~~~~~~~~~^^^~~~~~~~~~~~~~~~~~~~^~~~~~^~~~~~~^~~~^^^^^
>>^
>
>they are...
>
>scsi0:A:0:0: Tagged Queuing enabled.  Depth 253
>scsi0:A:1:0: Tagged Queuing enabled.  Depth 253
>scsi0:A:2:0: Tagged Queuing enabled.  Depth 253
>st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4,
> s/g segs 16 Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0
>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
>Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
>SCSI device sda: 17850000 512-byte hdwr sectors (9139 MB)
>Partition check:
> sda: sda1 sda2 sda3 sda4 < sda5 >
>SCSI device sdb: 35843670 512-byte hdwr sectors (18352 MB)
> sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 >
>SCSI device sdc: 35843670 512-byte hdwr sectors (18352 MB)
> sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 >
>Attached scsi generic sg4 at scsi0, channel 0, id 4, lun 0,  type 8

Thats the line.  And I see that a "scan all luns" isn't required for 
that changer, its actually on a seperate address from the drive 
proper.

>i recompiled again and now it works - it was on /dev/sg4... must
> have been a bad build perhaps

We call those "snilmerg", hint, spell it backwards...

Great, glad you got it working.

>$ mtx -f /dev/sg4 status
>  Storage Changer /dev/sg4:1 Drives, 9 Slots ( 0 Import/Export )
>Data Transfer Element 0:Full (Storage Element 2 Loaded):VolumeTag =
>      Storage Element 1:Full :VolumeTag=
>      Storage Element 2:Empty:VolumeTag=
>      Storage Element 3:Full :VolumeTag=
>      Storage Element 4:Full :VolumeTag=
>      Storage Element 5:Full :VolumeTag=
>      Storage Element 6:Full :VolumeTag=
>      Storage Element 7:Full :VolumeTag=
>      Storage Element 8:Empty:VolumeTag=
>      Storage Element 9:Empty:VolumeTag=
>
>Tom

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


<Prev in Thread] Current Thread [Next in Thread>