Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
Showing results for 
Search instead for 
Did you mean: 

dsfmgr verification error

Bengt Svensen
Occasional Visitor

dsfmgr verification error

I'm trying to clone a 5.1B system and when I boot dsfmgr gives the following error message:

Dev Nodes:
ERROR: wrong ldev: /dev/rdisk/dsk23a is: 5600000 sb: 5100500
ERROR: wrong cdev: /dev/rdisk/dsk23a is: 5600000 sb: 130020b
ERROR: wrong ldev: /dev/rdisk/dsk20b is: 5600001 sb: 5100541
ERROR: wrong cdev: /dev/rdisk/dsk20b is: 5600001 sb: 130021d
Errors: 4

I get this message after I run
dn_setup -init
dsfmgr -K
to recreate all device files.

The only difference between the 2 systems is three additional disks on the new system that aren't on the old system. Any hints/tips on where to start looking?
Ralf Puchner
Honored Contributor

Re: dsfmgr verification error

Cloning is unsupported in this way, use the official cloning tool. Moving a disk from one system to another will only work if the two systems are totally identically, means same slots, same devices, same firmware etc.

see also

or use search function next time.

Help() { FirstReadManual(urgently); Go_to_it;; }
Bengt Svensen
Occasional Visitor

Re: dsfmgr verification error

Perhaps you can theorize on dfsmgr then....In addition to dfsc.* and dsfl.*, what other files does dsfmgr interact with to build it's information on the major/minor numbers?
Johan Brusche
Honored Contributor

Re: dsfmgr verification error

The following system files contain static or dynamic information that is used to configure the device into the kernel. You should not edit these files manually even if they are ASCII text files. Some files might be Context Dependent Symbolic Links. If the links are accidentally broken, the files might not be usable in a clustered environment until the links are re-created.

/etc/ddr_dbase - The DDR (device dynamic recognition) device information database. The contents of this file is compiled into the binary file/etc/ddr.db, which is used by the system to obtain device information.

/etc/dec_devsw_db - This is a binary database owned by the kernel dev switch code. This database keeps track of the driver major numbers and driver switch entries.

/etc/disktab - This file specifies the disk geometry and partition layout tables. This file is useful for identifying disk device names and certain disk device attributes.

/etc/dvrdevtab - This file specifies the database name and the mapping of driver names to special file handlers.

/etc/gen_databases - A text file that contains the information required to convert a database name to a database file location and a database handler.

/etc/dec_hw_db - This is a binary database that contains hardware persistence information. Generally, this refers to hardware such as buses or controllers.

/etc/dec_hwc_ldb - This is a binary database that contains information on hardware components that are local to a cluster member.

/etc/dec_hwc_cdb - This is a binary database that contains information on hardware components that are shared by all members of a cluster. Hardware components with unique cluster names or mapped dev_t are stored in this database.

/etc/dec_scsi_db - This is a binary database owned by SCSI/CAM. It stores the world-wide identifier (WWID) of SCSI devices and enables CAM to track all SCSI devices that are known to the system.

/etc/dec_unid_db - This is a binary database that stores the preceding highest hardware identifier (HWID) assigned to a hardware component. This database is used to generate the next HWID to be assigned to a newly-installed hardware component.

Helpful informationen about the device-special database are located in /etc/dfsc.dat and /etc/dfsl.dat
(Don't edit this file!)

To check the device-data-base with hardware-database use the "dsfmgr -v" command
Additional with option "-F" you are able to fix some differences between both.

Command to build a new HW-DB on a single system
boot -fl s


rm /etc/dec*
rm /etc/dfsc*
rm /etc/dc*
cd /cluster/members/member/dev/; ./MAKEDEV std
rm /cluster/members/member/etc/dfsl*
rm /cluster/members/member/.Booted
cd /devices; rm -rf disk rdisk tape ntape cport dmapi changer

init 0
boot -fl s

dn_setup -init
dsfmgr -K
dsfmgr -v # optionally -vF
hwmgr show scsi


Have fun....
__ Johan.