This appendix explains some of the error messages that can occur while performing the procedures in this guide.
This section contains error messages that can occur during the conversion of a filesystem from EFS to XFS or when the system is rebooted after a conversion.
mountdir: Device busy
If umount reports that the root filesystem or any other filesystem is busy when you try to unmount it while in the miniroot, return to the Inst> prompt and follow this procedure to force inst to release files in the busy filesystem so that it can be unmounted:
Inst> quit
Building dynamic ELF inventory file for rqs(1) processing .. 100% Done.
Invoking rqs(1) on necessary dynamic ELF objects .. 100% Done.
Automatically reconfiguring the operating system.
Ready to restart the system. Restart? { (y)es, (n)o, (sh)ell, (h)elp }: no
Reinvoking software installation.
...
Inst Main Menu
...
Inst> admin
Administrative Commands Menu
...
Admin> umount -b /,/proc
Re-initializing installation history database
Reading installation history .. 100% Done.
Checking dependencies .. 100% Done.
|
mount: device on mountdir: Invalid argument
This message for a wide variety of problems. For example, this error message occurs if you try to mount a device that doesn't contain a valid filesystem.
WARNING: initial mount of root device 0x2000010 failed with errno 22 PANIC: vfs_mountroot: no root found
This panic at system startup is caused by a bad kernel. Some possible causes are:
eoe2.sw.xfs was not installed, but the root filesystem is an XFS filesystem.
eoe2.sw.efs was not installed, but the root filesystem is an EFS filesystem.
Conversion of a system disk with separate root and usr partitions from EFS to XFS was not performed correctly; /var wasn't linked to /usr/var, so kernel object files weren't found in /var/sysgen when the kernel was autoconfigured.
XFS dev 0xnnnnnnnn read error in file system meta-data. XFS dev 0xnnnnnnnn write error in file system meta-data.
These panics are caused by disk errors in filesystem metadata. 0xnnnnnnnn is the hexadecimal representation of the device that returned the error.
After getting this type of panic, you should:
Reboot the system and check the filesystems with xfs_check(1M) (see the section “Checking Filesystem Consistency” in Chapter 2).
Replace the disk that gives the errors if panics continue.
NOTICE: Start mounting filesystem: / NOTICE: Ending xFS recovery for filesystem: / (dev: 128/16) NOTICE: Start mounting filesystem: /vol1 NOTICE: Ending clean xFS mount for filesystem: /vol1
These messages, which occur during system startup, are normal and do not indicate that any error or problem has occurred.
/mountdir: Filesystem too large for device
This message is the result of mounting a disk partition that doesn't have an XFS filesystem on it, but it overlaps or has the same starting point as a disk partition that does have an XFS filesystem on it. For example, you see this error message if you make a filesystem on /dev/dsk/dks0d2s7, and then mount /dev/dsk/dks0d2s0.
mount: device on mountdir: Invalid argument
This message for a wide variety of problems. For example, this error message occurs if you try to mount a device that doesn't contain a valid filesystem.
The xlv_make(1M) reference page provides a complete listing of error messages from xlv_make and their causes. The xlv_make(1M) reference page is included in Appendix B in the printed version of this guide.
The xfs_check(1M) reference page provides a listing of error messages from xfs_check and describes them. The xfs_check(1M) reference page is included in Appendix B in the printed version of this guide.