On Mon, 2005-09-26 at 10:55 +0200, Arno Lehmann wrote: > Hello, > > On 25.09.2005 14:39, Erik P. Olsen wrote: > > > I am still in the testing phase and I get what seems to me to be a > > strange problem. The scenario is as follows: > > > > 1. Bacula daemons are started normally. > > 2. bconsole is started. > > 3. *run Client1 is issued. > > 4. Bacula sends "Intervention needed" message asking to mount Volume > > "Bacula02" on Storage Device "DDS-4" > > 5. Tape is ejected manually and true it was a wrong tape (not a bacula > > volume). > > 6. Volume "Bacula02" is inserted. > > 7. *mount storage=DDS-4 is not accepted and produce the following set of > > messages: > > > > *mount DDS-4 > > block.c:782 Read error at file:blk 0:0 on device /dev/nst0. > > ERR=Input/output error. > > block.c:782 Read error at file:blk 0:0 on device /dev/nst0. > > ERR=Input/output error. > > 3902 Cannot mount Volume on Storage Device "/dev/nst0" because: > > Requested Volume "" on /dev/nst0 is not a Bacula labeled Volume, > > because: ERR=block.c:782 Read error at file:blk 0:0 on device /dev/nst0. > > ERR=Input/output error. > > 3905 Device /dev/nst0 open but no Bacula volume is mounted. > > If this is not a blank tape, try unmounting and remounting the Volume. > > > > Unmounting and remounting the volume does not change anything. Trying > > with another Bacula labeled volume follows the same scenario. Stopping > > and starting bacula doesn't change anything either. > > > > First of all I like to understand what bacula is trying to tell me with > > these messages. Secondly can a wrong tape (not a bacula volume) cause > > this sort of errors and are the volumes which bacula would not accept > > now unusable for bacula forever? > > With a proper tape drive, it's rather hard to render a tape definitely > unusable.* I meant unusable for restores. I am sure the tape i physically OK: > > I suspect that the tapes you insert are either not labeled by bacula or > you changed your tape block size settings in between. Maybe, but not by me. > > In both cases, the easiest solution is to use the label command on them. Yes, but then the contents are gone. I suspect that somewhere bacula has recorded the volume as being in error and therefore will not use it. Can that happen? > > If you are absolutely sure that they contain a bacula label, the program > btape is a good first start to find out what is wrong with the tapes, > although, in your case, he output you give above shows clearly that > bacula can't read a volume label off the tapes. > > In this case, I have used dd and od with good results - something like > 'dd if=/dev/nst0 count=1 bs=65536 | od -t x1c' and playing with block > sizes sometimes helped my find the block size on that tape. I'll check that and come back with what I find. I don't know the format of the bacula label but I assume it is the first file on the tape. > > Arno > > * Proper tape drive means "everything except DDS" :-) No worries, that > was partly a joke. The part which is not a joke worries me nevertheless. About a year ago I had a head crash at the same time as my tape drive decided to brake down. In order to recover the system I had to buy a new drive to read my backup tapes, so I am stuck with a fairly new tape drive that I wish was of another type :( > -- Regards, Erik P. Olsen
------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
