Solaris

Hi techies,

I am pretty new to Solaris. So the qstn might be a silly one.

I had a local disk with Solaris installed.
I have done ufsdump to a SAN disk and after that s3 and s7 slices are giving the following error : "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY."

I had the following slices defined in the local disk.
s0 - root
s1 - swap
s3 - globaldevices
s7 - /export/home

When I partitioned the SAN disks, it did not allow me to give the "globaldevices" and "/export/home" tags. Instead I had to give "var" and "home" respectively.

After ufsdump, I set the SAN disk as boot-device and rebooted the machine.
Root and swap comes up fine. But s3 and s7 gives the above error.
I think I am missing the mounting part in /etc/vfstab.
My current /etc/vfstab file looks like :

Code:

#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
#
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/dsk/c7t5001438004C69F4Bd4s1        -       -       swap    -       no
-
/dev/dsk/c7t5001438004C69F4Bd4s0        /dev/rdsk/c7t5001438004C69F4Bd4s0
/       ufs     1       no      -
/dev/dsk/c7t5001438004C69F4Bd4s7        /dev/rdsk/c7t5001438004C69F4Bd4s7
/export/home    ufs     2       yes     -
/dev/dsk/c7t5001438004C69F4Bd4s3        /dev/rdsk/c7t5001438004C69F4Bd4s3
/globaldevices  ufs     2       yes     -
swap    -       /tmp    tmpfs   -       yes     -

Please let me know what mistake I am making here.

Thanking in advance,
Manu

it looks like your vfstab might be correct.

boot into single user mode via the OBP with boot -s and run:

fsck -F ufs /dev/rdsk/c7t5001438004C69F4Bd4s3


fsck -F ufs /dev/rdsk/c7t5001438004C69F4Bd4s7

you said you think you might be missing the mount part? looks like you have your mount points correct based on what you labeled them? are the directories created for /globaldevices and /export/home

as an aside, that is one crazy long dev tree path, but im sure thats the SAN

another option is to boot to the cdrom and do the fsck there. Is this on a Sparc machine or Intel?

After booting the system in single user mode,

You can unmount the filesystem(s) and try fsck corrupted filesystem(s)

you can also check for the /var/adm/messages for more information.

Thanks Joe,

I got the solution accidentally.
As I doubted, it was a mount issue only.

The mount points "/globaldevices" and "/export/home" were already defined for local disk.
But once I unmounted those from local disk and mounted on the SAN disk, everything was perfect.

Regards,
Manu

you are welcome...one thing i have learned is to not over think anything