From: Vincent, Jean-marc (jean-marc.vincent@hp.com)
Date: Thu Jun 19 2003 - 09:07:32 EDT
I received the call from customer concerning an AdvFS problem with root_domain.
At the time of the system boot, while the system tried to mount the root filesystem, he got the following error:
msfs_mount: The mount device does not match the linked device.
Check linked device in / etc. / fdmns / domain
msfs_mount: Setting root device name to root_device RW
In fact, the system has suffered multiple upgrades (notably from V4 to V5)/full reinstallation (without erasing the variable bootdef_dev), what has the effect of preserving the former SCSI old naming convention (i.e: rzNX instead of dskNX).
The link in /etc/fdmns/root_domain pointed to a device of type /dev/rz0a.
The customer wanted to suppress the former SCSI old naming convention (rzNX) and to use definitively the new one (dskNX). The links in /etc/fdmns/*/ were thus reappointed so as to use the new naming convention (i.e: in /etc/fdmns/root_domain: dsk0a - > /dev/disk/dsk0a instead of rz0a - > /dev/rz0a).
This is what generated the error message at the time of the system boot.
In fact, the problem results from the fact that when we choose to preserve the former SCSI old naming convention, the procedures of upgrade and installation introduce the parameter setting of the variable hwc_boot_old to the value of 1 into the subsystem hwc. It is necessary for the secondary boot (osf_boot) to know how to open, in read-only mode, the root device (/dev/rzNX or /dev/disk/dskNX) before loading vmunix.
So, it was /dev/rz0a which was opened by the secondary boot (osf_boot) and there was incoherence with the link in /etc/fdmns/root_domain (/dev/disk/dsk0a).
By modifying the variable hwc_boot_old to the value of 0 in the subsystem hwc (or by removing the line hwc_boot_old from the subsystem hwc in the file /etc/sysconfigtab, what is the same: the value by default being 0), the problem was resolved.
This problem seems only for the standalone systems. The former SCSI old naming convention is not valid within a cluster.
Jean-Marc
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:23 EDT