[Info-vax] Odd BACKUP error: unsupported file structure !

[JF Mezei]

An update to my problem...

I was away last week, so I didnt get to do much work.


It was confirmed to be by a real/former VMS engineer that the VMS IDE
driver does not log errors, so having an error count of 0 did not mean
the disk was healthy.

I am extreely disapointed that Digital would produce Alphas with disk
drivers that did not log errors.

I may take this IDE drive and plug it into an old mac and run the disk
utility to test it out.



I tried to copy the allin1 software which was on that drive to the
healthy system disk. Allin1 crashed or said that a premature end of file
was encountered (although ana/image discovered 0 errors). So I am in the
process of installing it from scratch and will move config files from
older backups (those don't change much) once it is installed. A pain to
do since my remaining use of A1 is to port data/documents to another
platform.

So it looks like data corruption had truly begun on the drive.


last resort would be to run the VAX version on SIMH or fire up my
remaining VAXstation 3100 to extract the data. (I have good backups of
that data).


Here is a question:

> $ show dev dqb0/full
> 
> Disk $11$DQB0: (CHAIN), device type Maxtor 53073H6, is online, file-oriented
>     device, shareable, served to cluster via MSCP Server, error logging is
>     enabled.
> 
>     Error count                    0    Operations completed                223
>     Owner process                 ""    Owner UIC                      [SYSTEM]
>     Owner process ID        00000000    Dev Prot            S:RWPL,O:RWPL,G:R,W
>     Reference count                1    Default buffer size                 512
>     Total blocks            58633344    Sectors per track                    87
>     Total cylinders             7659    Tracks per cylinder                  88
>     Allocation class              11
> 
> $ mount/foreign dqb0:
> %MOUNT-F-DEVALLOC, device already allocated to another user


Of the owner process ID is blank, why would the system think the define
has been allocated to another user ?