SEO

I'm having some trouble reading from my backup tapes. When I try to
run 'restore -i' it times out and after 3 attempts resets the SCSI
bus. After that I get 'mt: /dev/rst0: Input/output error' trying to
access the drive through mt and restore or dump don't do any better.
The only way I know to clear the problem is to reboot the machine.
That's not a good option so what I want to know is, how can I
clear/reset/re-initalize/whatever the SCSI bus without rebooting? I'm
running OpenBSD 3.2 which I know I should update but I'm reluctant to
do so until I trust my backups. It's a VXA-1 internal packet tape
drive. Ecrix has a VXATool for diagnostics but it's not built for
OpenBSD so I can't tell if tell if the drive is the problem. Anyone
knows a way to make it work or find a something that does the same
thing?

Here's a copy of /var/run/dmesg.boot:

cat /var/run/dmesg.boot
16 function 2 "VIA VT83C572 USB" rev 0x80: irq 10
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: vendor 0x0000 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
"VIA VT6202 USB 2.0" rev 0x82 at pci0 dev 16 function 3 not configured
pcib0 at pci0 dev 17 function 0 vendor "VIA", unknown product 0x3177
rev 0x00
pciide0 at pci0 dev 17 function 1 "VIA VT82C571 IDE" rev 0x06: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <TEAC, CD-552E, T016> SCSI0 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
auvia0 at pci0 dev 17 function 5 "VIA VT8233 AC97 Audio" rev 0x50: irq
10
ac97: codec id 0x414c4720 (Avance Logic <20>)
ac97: codec features 20 bit DAC, 18 bit ADC, Realtek 3D
audio0 at auvia0
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask 9c40 netmask 9c40 ttymask 9cc2
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
iop0: configuring...
ioprbs0 at iop0 tid 522: <ADAPTEC, RAID-5, 370L> direct access, fixed
scsibus2 at ioprbs0: 1 targets
sd0 at scsibus2 targ 0 lun 0: <I2O, Container #00, > SCSI2 0/direct
fixed
sd0: 117288MB, 14952 cyl, 255 head, 63 sec, 512 bytes/sec, 240205824
sec total
device (class 0x80) at iop0 tid 8 not configured
device (class 0x80) at iop0 tid 9 not configured
device (class 0x80) at iop0 tid 10 not configured
device (class 0x80) at iop0 tid 11 not configured
dkcsum: sd0 matched BIOS disk 80
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
uhub0: port error, restarting port 1
uhub0: port error, restarting port 2
uhub1: port error, restarting port 1
uhub1: port error, restarting port 2
uhub2: port error, restarting port 1
uhub2: port error, restarting port 2
st0(adw0:0:0): timed out
st0(adw0:0:0): timed out
st0(adw0:0:0): Check Condition on opcode 0x8
SENSE KEY: Media Error
INFO FIELD: 32768
ASC/ASCQ: Unrecovered Read Error
st0(adw0:0:0): Check Condition on opcode 0x0
SENSE KEY: Not Ready
ASC/ASCQ: Medium Not Present
st0(adw0:0:0): Check Condition on opcode 0x8
SENSE KEY: Blank Check
INFO FIELD: 32768
ASC/ASCQ: End-Of-Data Detected
st0(adw0:0:0): Check Condition on opcode 0x8
SENSE KEY: Blank Check
INFO FIELD: 32768
ASC/ASCQ: End-Of-Data Detected
st0(adw0:0:0): Check Condition on opcode 0x8
SENSE KEY: Blank Check
INFO FIELD: 32768
ASC/ASCQ: End-Of-Data Detected
st0(adw0:0:0): Check Condition on opcode 0x1b
SENSE KEY: Media Error
ASC/ASCQ: No Additional Sense Information
st0(adw0:0:0): timed out
st0(adw0:0:0): timed out
st0(adw0:0:0): timed out AGAIN. Resetting SCSI Bus
syncing disks... done
shutting down iop devices... done.
rebooting...
OpenBSD 3.2-stable (ATALK) #3: Tue Oct 7 22:47:21 EDT 2003
kit@hades.kithalsted.com:/usr/src/sys/arch/i386/compile/ATALK
cpu0: AMD K7 (Athlon) ("AuthenticAMD" 686-class) 1.80 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SYS,MTRR,P GE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SIMD
real mem = 536391680 (523820K)
avail mem = 491794432 (480268K)
using 4278 buffers containing 26923008 bytes (26292K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 09/11/02, BIOS32 rev. 0 @
0xfdad0
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev. 2.1 @ 0xf0000/0x10000
pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xf7f30/208 (11 entries)
pcibios0: no compatible PCI ICU found: ICU vendor 0x1106 product
0x3177
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc0000/0xa800 0xca800/0x4000 0xd2800/0x6000!
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8366 Host-PCI" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8366 PCI-AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Nvidia Vanta" rev 0x15
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
adw0 at pci0 dev 5 function 0 "Advansys ABP-940UW" rev 0x00: irq 11
scsibus0 at adw0: 16 targets
adw0: target 0 using 8 bit 10.0 MHz 15 REQ/ACK offset xfers
st0 at scsibus0 targ 0 lun 0: <ECRIX, VXA-1 V219191B, 0001> SCSI2
1/sequential removable
st0: density code 0x80, 1024-byte blocks, write-enabled
ppb1 at pci0 dev 7 function 0 "DPT PCI-PCI bridge" rev 0x02
pci2 at ppb1 bus 2
iop0 at pci0 dev 7 function 1 "DPT SmartRAID (I2O)" rev 0x02: I2O
adapter <ADAPTEC 2400A>
iop0: interrupting at irq 10
nge0 at pci0 dev 10 function 0 "NS DP83820 1/10/100/1000" rev 0x00:
irq 12: address: 00:50:ba:38:ed:d8
nsgphy0 at nge0 phy 1: DP83861 10/100/1000 media interface, rev. 2
uhci0 at pci0 dev 16 function 0 "VIA VT83C572 USB" rev 0x80: irq 11
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: vendor 0x0000 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 16 function 1 "VIA VT83C572 USB" rev 0x80: irq 12
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: vendor 0x0000 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 16 function 2 "VIA VT83C572 USB" rev 0x80: irq 10
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: vendor 0x0000 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
"VIA VT6202 USB 2.0" rev 0x82 at pci0 dev 16 function 3 not configured
pcib0 at pci0 dev 17 function 0 vendor "VIA", unknown product 0x3177
rev 0x00
pciide0 at pci0 dev 17 function 1 "VIA VT82C571 IDE" rev 0x06: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <TEAC, CD-552E, T016> SCSI0 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
auvia0 at pci0 dev 17 function 5 "VIA VT8233 AC97 Audio" rev 0x50: irq
10
ac97: codec id 0x414c4720 (Avance Logic <20>)
ac97: codec features 20 bit DAC, 18 bit ADC, Realtek 3D
audio0 at auvia0
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask 9c40 netmask 9c40 ttymask 9cc2
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
iop0: configuring...
ioprbs0 at iop0 tid 522: <ADAPTEC, RAID-5, 370L> direct access, fixed
scsibus2 at ioprbs0: 1 targets
sd0 at scsibus2 targ 0 lun 0: <I2O, Container #00, > SCSI2 0/direct
fixed
sd0: 117288MB, 14952 cyl, 255 head, 63 sec, 512 bytes/sec, 240205824
sec total
device (class 0x80) at iop0 tid 8 not configured
device (class 0x80) at iop0 tid 9 not configured
device (class 0x80) at iop0 tid 10 not configured
device (class 0x80) at iop0 tid 11 not configured
dkcsum: sd0 matched BIOS disk 80
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
uhub0: port error, restarting port 1
uhub0: port error, giving up port 1
uhub0: port error, restarting port 2
uhub0: port error, giving up port 2
uhub1: port error, restarting port 1
uhub1: port error, giving up port 1
uhub1: port error, restarting port 2
uhub1: port error, giving up port 2
uhub2: port error, restarting port 1
uhub2: port error, giving up port 1
uhub2: port error, restarting port 2
uhub2: port error, giving up port 2

In article <bac833fe.0312170822.39055b64@posting.google.com >,
asumoactingbig <asumoactingbig@yahoo.com> wrote:
>I'm having some trouble reading from my backup tapes. When I try to
>run 'restore -i' it times out and after 3 attempts resets the SCSI
>bus. After that I get 'mt: /dev/rst0: Input/output error' trying to
>access the drive through mt and restore or dump don't do any better.
>The only way I know to clear the problem is to reboot the machine.
>That's not a good option so what I want to know is, how can I
>clear/reset/re-initalize/whatever the SCSI bus without rebooting? I'm
>running OpenBSD 3.2 which I know I should update but I'm reluctant to
>do so until I trust my backups. It's a VXA-1 internal packet tape
>drive. Ecrix has a VXATool for diagnostics but it's not built for
>OpenBSD so I can't tell if tell if the drive is the problem. Anyone
>knows a way to make it work or find a something that does the same
>thing?

Just for clarity, there are more switches used with interactive
restore than just 'restore -i'. Exactly what command are you using?

Exactly what command did you use to write the backup tapes?

Did you specify a blocksize when writing the backup tapes? While it
is sometimes true that restore can determine the blocksize of the
tape it is reading, it is more often the case that it can not.
(after the era of 9-track tapes). It is always safer to specify a
blocksize to restore.

carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst@ucsd.edu

> Just for clarity, there are more switches used with interactive
> restore than just 'restore -i'. Exactly what command are you using?
>
> Exactly what command did you use to write the backup tapes?
>
> Did you specify a blocksize when writing the backup tapes? While it
> is sometimes true that restore can determine the blocksize of the
> tape it is reading, it is more often the case that it can not.
> (after the era of 9-track tapes). It is always safer to specify a
> blocksize to restore.

restore -i is the command I was using. According to the restore man
page it should be cool to call it with only that flag. Is that not
so? I was trying to restore a couple specific files.

To write the backups I used:
/sbin/dump -0a -f /dev/nrst0 /myfolder/filestodump

I think I can do without the -a flag.

If I didn't specify the blocksize when I did the dump, how do I know
what blocksize to call restore with?

asumoactingbig <asumoactingbig@yahoo.com> wrote:
> I'm having some trouble reading from my backup tapes. When I try to
> run 'restore -i' it times out and after 3 attempts resets the SCSI
> bus...

An annecdote-- I was having vaguely simliar problems. I couldn't
restore critical data from tape. In my case, I would get a tape read
error, a bunch of mysterious SCSI stuff went into dmesg, and the SCSI
bus locked up. Even though I used the -y flag to ignore the error, I
couldn't get restore to continue. After trying many unlikely
remedies, I booted into single user mode. restore worked flawlessly.

Maybe it was just luck, but it's worth a shot.

Good luck,

- Eric

In article <bac833fe.0312181102.57acf149@posting.google.com >,
asumoactingbig <asumoactingbig@yahoo.com> wrote:
>> Just for clarity, there are more switches used with interactive
>> restore than just 'restore -i'. Exactly what command are you using?
>>
>> Exactly what command did you use to write the backup tapes?
>>
>
>restore -i is the command I was using. According to the restore man
>page it should be cool to call it with only that flag. Is that not
>so? I was trying to restore a couple specific files.
>
>To write the backups I used:
>/sbin/dump -0a -f /dev/nrst0 /myfolder/filestodump
>
>I think I can do without the -a flag.
>
>If I didn't specify the blocksize when I did the dump, how do I know
>what blocksize to call restore with?

OK, default blocksize is default blocksize.

You specified the tape device "-f /dev/nrst0" when doing the dump,
think about also needing to specify the tape device when doing the
restore? Perhaps your invocation of the program is waiting forever
to read from a non-existent tape drive.

Read down toward the end of the man.page where it (probably) discusses
the default tape drive that is attempted if nothing is specified.

carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst@ucsd.edu

> >restore -i is the command I was using. According to the restore man
> >page it should be cool to call it with only that flag. Is that not
> >so? I was trying to restore a couple specific files.
> >
> >To write the backups I used:
> >/sbin/dump -0a -f /dev/nrst0 /myfolder/filestodump
> >
>
> You specified the tape device "-f /dev/nrst0" when doing the dump,
> think about also needing to specify the tape device when doing the
> restore? Perhaps your invocation of the program is waiting forever
> to read from a non-existent tape drive.
>
> Read down toward the end of the man.page where it (probably) discusses
> the default tape drive that is attempted if nothing is specified.
>
> carl

From the OpenBSD 3.2 restore man page:
/dev/rst0 the default tape drive

I'm pretty sure I'm calling restore OK. I just don't know why it
fails, retries, and resets the SCSI bus in a way that I can't clear
without a reboot.

It's probably worth mentioning that the hardware setup isn't new.
It's been running for awhile without incident.