Error loading domain in advfs, inconsistency detected.

[Jaggu_1]

I am having a problem loading a domain since this morning. My console log shows

ADVFS: Domain user1 not activated - inconsistency detected.
I used showfdmn user1 and the results show as follows

showfdmn user1

#ADVFS : Domain user1 not activated - inconsistency detected
showfdmn: unable to get info for domain 'domain1'
showfdmn: error = E_DOMAIN_NOT_ACTIVATED (-1067)
#"

I tried verify with both -f and -F and get the same error message as above. I used advscan -a and got listings of 3 domains including user1. I dont know whether this is a software problem or the actual disk has died. I have a lot of critical data I need to salvage if the disk is indeed dead.

I want to use fixfdmn but cannot find it in my advfs directory. I want to know all my options. Can someone also tell me how to place a service call for this problem.

Oh I have a 7 year old digital 600au personal workstation.

Thank you for all your help

[Michael Schulte zur Sur · Accepted solution]

Hi,

you probably have an old os version too because fixfdmn did not come out before 5.0.
Could you please post the output of the
advscan
any errors in messages related to disks
scu show edt
os version

thanks,

Michael

[Ivan Ferreira]

If you don't have fixfdmn, that should be in /sbin/advfs, then your best option is to delete and recreate the filesystem, then restore from a backup.

You can use the salvage utility to try to backup the data.

[Jaggu_1]

Here is the output of advscan -a

Scanning devices /dev/rrz16 /dev/rrz21
Found domains:
root_domain Domain ID:
Created:
Domain Volumes: 1
/etc/fdmns links: 1
Actual Partitions Found: rz16a
usr_domain Domain ID:
Created:
Domain Volumes: 1
/etc/fdmns links: 1
Actual Partitions Found: rz16g
user1_domain Domain ID:
Created:
Domain Volumes: 1
/etc/fdmns links: 1
Actual Partitions Found: rz21c

scu> show edt

CAM equipment device table(EDT) information
Device: CD-ROM Bus: 1, Target: 0,Lun: 0, Type: Read-Only Direct Access
Device: RZ2CC-KA Bus: 2, Target: 0, Lun: 0, Type: Direct Access
Device: ST39140W Bus: 2, Targer: 5, Lun: 0, Type: Direct Access
Device: TLZ10 Bus: 2, Target: 6, Lun: 0, Type: Sequential Access



uname -v returns 1091. I found out that this corresponds to Digital UNIX V4.0E (Rev 1091). This is the same from the boot messages.

Thanks for all your replies. I cannot do a file system remount because the backups I have are atleast 1 month old. We have a lot of new data that I dont want to lose.

[Ivan Ferreira]

If you cannot mount the fileset, use salvage to try to save the data. Like this:

salvage -F tar -f /path_to_file/filename.tar user1

Then use the tar command to restore filename.tar and see if the needed files was recovered.

[Han Pilmeyer]

It's the ST31940W disk that has the user1 domain (rz21c). I would like to see what the state of that disk is. Commands to check that would be:

file /dev/rrz21c
disklabel rz21c
dd if=/dev/rrz21c of=/dev/null bs=65536 \
count=1000

Your system is really old (V4.0E), so you don't have salvage. I think there was some other tool on V4, but I forgot the name (not nearly as useful as salvage unfortunately). However if you have a V5 CDROM somewhere, you could boot from that and try to salvage from there.The problem is that you need a lot of scratch space to recover the data and you don't appear to have any spare disks.

[Ivan Ferreira]

I have an OLD 4.0D Tru64, and it has the salvage command. So 4.0E should have it. To obtain your os version run:

sizer -v

Remember that salvage can recover data without mounting the domain/filesets.

[Jaggu_1]

Thank you all for your help. I did use salvage to retrieve 99% of my data. some of the data on the disk was corrupted. I got only file parts.

I am trying to find detailed instructions on installing a new scsi hard drive but couldnt get much help anywhere. I am new to Tru64 administration, so can you please help me with this final thing. Thanks a lot

[Michael Schulte zur Sur]

Hi,

you will find docs here:
http://h30097.www3.hp.com/docs/pub_page/doc_list.html
However the oldest is 4.0f
Have a look into system administration.
Have you still got the cdrom set for your alpha?
You may want to update 4.0F, where you get at least some support.

Michael