Date: Thu, 4 Mar 1999 19:52:42 +0000 From: Nik Clayton <nik@nothing-going-on.demon.co.uk> To: questions@freebsd.org Cc: nclayton@lehman.com Subject: sd1(ncr0:1:0): error code 0, FAILURE Message-ID: <19990304195242.B671@catkin.nothing-going-on.org>
next in thread | raw e-mail | index | archive | help
Hi folks
[ cc'd to nclayton@lehman.com, I'd appreciate replys cc'd there as well,
thanks ]
The SCSI card in my FreeBSD box is recognised as;
ncr0 <ncr 53c875 fast20 wide scsi> rev 3 int a irq 10 on pci0:12:0
and had 1 disk attached to it (internal),
(ncr0:0:0): "QUANTUM XP32275W LXY4" type 0 fixed SCSI 2
sd0(ncr0:0:0): Direct-Access
sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled
sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 16)
2170MB (4445380 512 byte sectors)
and about 2 and a half months ago I added an additional SCSI disk, also
internal.
(ncr0:1:0): "SEAGATE ST34520W 1444" type 0 fixed SCSI 2
sd1(ncr0:1:0): Direct-Access
sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled
sd1(ncr0:1:0): 40.0 MB/s (50 ns, offset 15)
4340MB (8888924 512 byte sectors)
This disk has been working fine so far.
After buying a tape drive (external)
(ncr0:5:0): "SONY SDT-9000 0400" type 1 removable SCSI 2
st0(ncr0:5:0): Sequential-Access
st0(ncr0:5:0): 10.0 MB/s (100 ns, offset 15)
density code 0x13, 512-byte blocks, write-enabled
I've been trying to dump sd1 to tape.
I use all of sd1 for FreeBSD (cylinders 16-552 according to disklabel).
I've been trying to dump(8) this disk to the tape drive. It doesn't work.
First, to rule out some possible conflicts I
a) Booted single user, with just sd0s1a ("/") and sd1s1a ("/.0")
mounted, and the tape drive turned OFF, and ran
# dump -0 -a -f /dev/null /.0
Which runs to completion, and no errors.
b) As (a), but had the tape drive turned on when I booted, so it was
probed and discovered. Again, I dumped to /dev/null, and it ran to
completion, no errors.
c) As (a) and (b), with dumping various filesystems on sd0. All run
to completion.
d) Try and dump sd1 to the tape drive.
The command line was
# dump -0 -a -f /dev/nrst0 /.0
This works intermittently. Sometimes it runs straight through without
errors, other times I'll get a succession of messages like
Mar 4 00:17:27 catkin /kernel: st0(ncr0:5:0): error code 0
Mar 4 00:17:59 catkin /kernel: st0(ncr0:5:0): error code 0
Mar 4 01:27:27 catkin /kernel: sd1(ncr0:1:0): error code 0
Mar 4 01:27:27 catkin /kernel: , retries:3
Mar 4 01:27:39 catkin /kernel: sd1(ncr0:1:0): error code 0
Mar 4 01:27:39 catkin /kernel: , retries:1
Mar 4 01:27:51 catkin /kernel: sd1(ncr0:1:0): error code 0
Mar 4 01:27:51 catkin /kernel: , retries:4
Mar 4 01:28:03 catkin /kernel: sd1(ncr0:1:0): error code 0
Mar 4 01:28:03 catkin /kernel: , retries:2
Mar 4 01:28:15 catkin /kernel: sd1(ncr0:1:0): error code 0
Mar 4 01:28:15 catkin /kernel: , FAILURE
Mar 4 01:28:27 catkin /kernel: sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapp
ed commands attempted
Mar 4 01:28:27 catkin /kernel: , retries:3
and the dump fails. After these errors have appeared I'll then a succession
like
Mar 3 21:10:40 catkin /kernel: swap_pager: I/O error - pagein failed; blkno 135
04, size 16384, error 5
Mar 3 21:10:40 catkin /kernel: vm_fault: pager input (probably hardware) error,
PID 276 failure
Mar 3 21:10:40 catkin /kernel: pid 276 (xterm), uid 1001: exited on signal 11
Mar 3 21:10:52 catkin /kernel: sd1(ncr0:1:0): error code 0
Mar 3 21:10:52 catkin /kernel: , retries:3
Mar 3 21:11:00 catkin /kernel: swap_pager: indefinite wait buffer: device: 1321
05, blkno: 13712, size: 24576
Mar 3 21:11:00 catkin /kernel: swap_pager: indefinite wait buffer: device: 1321
05, blkno: 13240, size: 4096
Mar 3 21:11:00 catkin /kernel: swap_pager: indefinite wait buffer: device: 1321
05, blkno: 13056, size: 4096
Mar 3 21:11:00 catkin /kernel: swap_pager: indefinite wait buffer: device: 1321
05, blkno: 13768, size: 8192
e) Tried to do the dump, using Amanda 2.4.1 (from the ports tree).
This *always* fails within 30 seconds of running the command.
I've checked termination, and all seems good (sd0 terminated, sd1 not
terminated, st0 terminated, and the SCSI card auto-terminates, there are
no jumpers to set).
I thought it might be because sd1 is failing, but if that's the case, why
do dumps to /dev/null work without a hitch?
I'm going to try and get a replacement disk, and see if that fixes the
problem -- but I'm open to any suggestions people might have as to what
else could be causing this.
I'm running 2.2.8-stable, last rebuilt in the middle of January.
N
--
Bagel: The carbohydrate with the hole
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990304195242.B671>