Hello all
We have an Alpha server 2100A with DU4.0E
Last friday I had the tape driver changed. It looks like the driver works
OK, the backups went fine.
But another problem occured:
When I restarted the server one partition didn't mount. The other partition
of the same disk mounted without problem so it doesn't seem like a physical
disk crash.
In the log files from Friday I found this:
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #510 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #509 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #508 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #507 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #506 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #505 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #504 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #503 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: pg #502 is bad; truncating log
>Sep 17 13:47:32 torun vmunix: advfs_logger: can't find log end
When I try to mount the partiton with mount -a I get the same message in
the console window. I also get this message in the DECterm:
>bs_bfdmn_activate:can't open domain ftx log, tag=Oxfffffff7 0xO
>E_CANT_FIND_LOG_END (-1077) PC_dmn#PC_fs on /PC: I/O error
Is there anyone out there who can give me a clue?
I have called the support but since I know I get fast answers from you guys
I try this way too.
I would be very grateful for all help
Kindly
Neta Hedberg
-------------------------
Neta Hedberg SIGIT AB
Tel 0980-70028
neta.hedberg_at_sigit.se
-------------------------
Received on Mon Sep 20 1999 - 10:12:37 NZST