|
Re: chg-scsi: "got signal 11" on amcheck
2003-05-14 10:17:27
On Tue May 13 2003 06:04, Toralf Lund wrote:
>> On Mon May 12 2003 14:26, Toralf Lund wrote:
>> >Did anyone find a way around this
>> >
>> >amcheck-server: fatal slot <error>: <error> could not read
>> > result from "/usr/freeware/libexec/chg-scsi" (got signal 11)
>>
>> Here, that would be /usr/local/libexec/chg-scsi. OS diffs no
>> doubt...
>
>I'm using SGI IRIX.
Humm, so we need IRIX experts here. Not guilty.
I used to consider myself a bit of an expert on IRIX, actually, but now I
hardly ever work on the systems anymore, so I've forgotten much I what I
used to know... We do still have an SGI file server, as you have gathered
by now, but most of the time it Just Works, so I don't need to touch it a
lot...
[ ... ]
>[ ... ]
>I've now created a new config based on yours - I changed
> changerdev to "/dev/scsi/sc2d1l0" and dev to "/dev/nrtape", and
> replaced "/usr/local" with "/usr/freeware", but left everything
> else unchanged. I still get the same behaviour with this setup.
> Here is the output from various chg-scsi commands:
>
># /usr/freeware/libexec/chg-scsi -info
>0 4 1 0
># /usr/freeware/libexec/chg-scsi -slot 0
>Segmentation fault (core dumped)
># /usr/freeware/libexec/chg-scsi -slot 1
>Segmentation fault (core dumped)
># /usr/freeware/libexec/chg-scsi -scan
>name /dev/scsi/sc2d1l0 Changer
>Count 1
># /usr/freeware/libexec/chg-scsi -eject
>1 /dev/nrtape
>
>Notice that the tape appears to be changed correctly at the point
> where it dumps core. I also tried to debug a bit to find out what
> was going on, but wasn't very successful; the debugger simply got
> very confused and didn't really tell me anything. I've run the
> commands as super user and "amanda", with the same results.
I think you've got to have a chew of Kentucky Twist going in order
to properly decode some of that swahili from dbg! Red Man just
won't cut it. ;-)
Right ;-)
>I've now also built and installed mtx, though, so maybe I'll just
> use chg-mtx or chg-zd-mtx...
Going back to the signal 11, thats often indicative of a hardware
problem, as in a bad memory location here on a linux box. Has that
been checked? Also cabling issues, terminations and such could
play a part I'd imagine.
Hmmm. The only thing I could think of that might cause trouble is a SCSI
cable chain that's somewhat on the long side (we're talking about a
pre-LVD controller, here.) I don't see any other indications of problems
with the setup, though...
Anyhow, I don't think I'll spend more time on chg-scsi, but rather use
chg-zd-mtx, which seems to work just fine.
Where is the IRIX expert when you need him?
--
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.
|
|
|
