On Thu, November 16, 2006 11:40 am, Kern Sibbald said:
> 5. If the problem occurs again, be *much* more specific about what
> happened
> (with complete console and Job report output) and what commands you issued
> when.
OK, I tried to start from as close to ground zero as possible.
1) Powercycled the autochanger
2) When it was back up and in ready status, rebooted the tape host
3) Verified the changer and drive were seen in cat /proc/scsi/scsi
4) No errors in dmesg or /var/log/messages
5) Verified that bacula-fd, bacula-sd, and bacula-dir are all running
6) started bconsole
7) Per autochanger chapter, did:
*umount
Waited 1/2 hour while watching the console say nothing but "Connecting
to Storage daemon Autochanger at 10.10.0.8:9103 ..."
8) Aborted it with ctl-c
9) set debug to level 4
10) did umount again, and it did it within a few seconds
11) did update slots, and that completed quickly and showed:
*update slots
The defined Storage resources are:
1: File
2: Autochanger
Select Storage resource (1-2): 2
Connecting to Storage daemon Autochanger at 10.10.0.8:9103 ...
3306 Issuing autochanger "slots" command.
Device "Drive-1" has 8 slots.
Connecting to Storage daemon Autochanger at 10.10.0.8:9103 ...
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result: nothing loaded.
3306 Issuing autochanger "list" command.
Catalog record for Volume "MCL374L3" updated to reference slot 1.
Catalog record for Volume "MCL375L3" updated to reference slot 2.
Catalog record for Volume "MCL376L3" updated to reference slot 3.
Catalog record for Volume "MCL377L3" updated to reference slot 4.
Catalog record for Volume "MCL378L3" updated to reference slot 5.
Catalog record for Volume "MCL379L3" updated to reference slot 6.
Catalog record for Volume "MCL380L3" updated to reference slot 7.
Catalog record for Volume "CLN265L2" updated to reference slot 8.
Manual says to next do mount:
*mount
The defined Storage resources are:
1: File
2: Autochanger
Select Storage resource (1-2): 2
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result: nothing loaded.
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result: nothing loaded.
LONG DELAY HERE, like 15 minutes, then:
3902 Cannot mount Volume on Storage Device "Drive-1" (/dev/nst0) because:
Couldn't rewind device "Drive-1" (/dev/nst0): ERR=dev.c:678 Rewind error
on "Drive-1" (/dev/nst0). ERR=No medium found.
3905 Device "Drive-1" (/dev/nst0) open but no Bacula volume is mounted.
If this is not a blank tape, try unmounting and remounting the Volume.
True. There was no tape in the drive, all were in the magazine as a
result of the umount command. But why would it check it twice, both times
find the drive to be empty, then take 15 minutes trying to rewind a tape
that it had already determined twice was not in the drive?
So I issued the umount command:
*umount
The defined Storage resources are:
1: File
2: Autochanger
Select Storage resource (1-2): 2
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result is Slot 1.
3307 Issuing autochanger "unload slot 1, drive 0" command.
3002 Device "Drive-1" (/dev/nst0) unmounted.
Do you see why I am confused? Now it says there IS a tape in the drive,
and it is the one from slot 1... but it just failed to rewind the tape
that it determined wasn't in the drive but now thinks IS in the drive.
So I quit out of bconsole, and stopped the bacula daemons. Using mtx I
checked status and the tapes were all in the magazine. Using mtx I loaded
slot 3 into the drive and restarted bacula daemons and bconsole.
In bconsole, tried doing status on storage. It hung with the same
"Connecting to Storage daemon Autochanger at 10.10.0.8:9103 ..." message
for 10 minutes before I aborted it with ctl-c.
This was working yesterday. It did backups last night. I have modified
no config files, but now it seems to be unable to contact the sd unless
debug is set.
I am flummoxed and now going to lunch.
12) did "mount"
>
> Note, in general, if you unmount a drive, remove a volume from an
> autochanger,
> then remount the drive, Bacula just is not going to work. The manual
> explains why -- and Arno as well as others have explained why a number of
> times on this list.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
