problems with amlabel/amcheck

I had amanda up and running only to discover that the machine acting as host didn't have enough HD capacity to run Amanda smoothly. The project layed low for several weeks until I got hold of a new and bigger machine.

Installed RedHat 9.0 on it and installed amanda and mtx

started configuring everything as I remember doing it the last time, but now I've run into problems (So I obviously couldn't remember it :-)

a mtx -f /dev/sg2 status gives me the following:

# mtx -f /dev/sg2 status
Storage Changer /dev/sg2:1 Drives, 19 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
      Storage Element 1:Full :VolumeTag=000001L1
      Storage Element 2:Full :VolumeTag=000002L1
      Storage Element 3:Full :VolumeTag=000003L1
      Storage Element 4:Full :VolumeTag=000004L1
      Storage Element 5:Full :VolumeTag=000005L1
      Storage Element 6:Full :VolumeTag=000006L1
      Storage Element 7:Full :VolumeTag=000007L1
      Storage Element 8:Full :VolumeTag=000008L1
      Storage Element 9:Full :VolumeTag=000009L1
      Storage Element 10:Full :VolumeTag=000010L1
      Storage Element 11:Full :VolumeTag=000011L1
      Storage Element 12:Full :VolumeTag=000012L1
      Storage Element 13:Empty:VolumeTag=
      Storage Element 14:Empty:VolumeTag=
      Storage Element 15:Empty:VolumeTag=
      Storage Element 16:Empty:VolumeTag=
      Storage Element 17:Empty:VolumeTag=
      Storage Element 18:Full :VolumeTag=
      Storage Element 19:Empty:VolumeTag=

I can load and unload tapes with mtx -f /dev/sg2 load/unload without problems.

My amanda.conf looks like this:

#
# amanda.conf - configurtaion file for backup routines at Videlity A/S.
# Augmented from the sample amanda.conf provided by CS.UMD.EDU
#
# This amanda.conf should be placed in /etc/amanda/BackUp/amanda.conf

org "BackUp" # Name of BackUp scheme

mailto "root" # report status to this adress
dumpuser "root" # The user who should run the backup

inparallel 4 # maximum dumpers that will run in parallel
netusage 600 Kbps # maximum usage of LAN in KB per sec

dumpcycle 7 days                             # Number of days in a dump cycle
runspercycle 5 days                          # number of dumb runs in each cycle
tapecycle 12 tapes                           # number of tapes in rotation

bumpsize 20 Mb                               # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1                                   # minimum days in each level
bumpmult 4                                   # threshold = bumbsize * bumpmult(level-1)

etimeout 300 # number of seconds per filesystem for estimates

runtapes 1                                   # number of tapes to be used in a single run of amdump
tpchanger "chg-zd-mtx"                       # the tape-changer glue script
tapedev "/dev/nst0"                          # the no-rewind tape device used
changerfile "/var/lib/amanda/BackUp/changer.conf" # path to changer.conf
changerdev "/dev/sg2"                        # the changer device used

tapetype ultrium1 # what kind of tape is used (see below for tapetypes)
labelstr "^VidelityBackUp[0-9][0-9]*$" # label constraint regex: all tapes must match

#
# Next part defines the holding disks which is the part of the harddisk amanda uses to store
# data from a client still not written to tape.
#

holdingdisk hd1 {
    comment "primary holding disk"
    directory "/backup"                      # where the holding disk is
    use -30 Mb                               # use all but 30 Mb on the holding disk
}

infofile "/var/lib/amanda/BackUp/curinfo"    # database filename
logdir   "/var/lib/amanda/BackUp"            # log directory
indexdir "/var/lib/amanda/BackUp/index"      # index directory

runtapes 1                                   # number of tapes to be used in a single run of amdump
tpchanger "chg-zd-mtx"                       # the tape-changer glue script
tapedev "/dev/nst0"                          # the no-rewind tape device used
changerfile "/var/lib/amanda/BackUp/changer" # path to changer.conf
changerdev "/dev/sg2"                        # the changer device used

tapetype ultrium1 # what kind of tape is used (see below for tapetypes)
labelstr "^VidelityBackUp[0-9][0-9]*$" # label constraint regex: all tapes must match

#
# Next part defines the holding disks which is the part of the harddisk amanda uses to store
# data from a client still not written to tape.
#

infofile "/var/lib/amanda/BackUp/curinfo"    # database filename
logdir   "/var/lib/amanda/BackUp"            # log directory
indexdir "/var/lib/amanda/BackUp/index"      # index directory

# tapetypes

define tapetype ultrium1 {
    comment "Ultrium1 tapes for Dell PowerVault 128T"
    length 103911 mbytes
    filemark 524 kbytes
    speed 2158 kps
}

define dumptype normal_backup {
    compress NONE
    index yes
    maxdumps 5
    program "GNUTAR"
    record yes
}

define dumptype client_compression {
normal_backup
compress client fast
}

My changer.conf placed at "/var/lib/amanda/BackUp/changer.conf" looks like this:

firstslot=1
lastslot=19
cleanslot=18

AUTOCLEAN=0
autocleancount=99999

havereader=1

offlinestatus=1

OFFLINE_BEFORE_UNLOAD=0

All this taken from the old machine which was working, now to the problems:

amcheck BackUp gives:

Amanda Tape Server Host Check
-----------------------------
Holding disk /backup: 163180648 KB disk space available, using 163149928 KB
amcheck-server: could not get changer info: cannot determine first slot

#./chg-zd-mtx -info displays:
<none> changerfile must be specified in amanda.conf

amlabel reports:

# amlabel BackUp VidelityBackUp01
amlabel: could not load slot "current": cannot determine first slot

Do anyone have a clue where I have forgotten something?

/Mikkel