03-05-2008 08:25 AM
Hi,
On SF Basic 5.0 for Solaris 10 x86, I get the following message when attempting to encapsulate or add/initialize disks with vxdiskadm despite having 2 free partitions, free unpartitioned space, a valid slice 2 (backup slice) showing total disk space on both drives:
These disk devices do not appear to be valid. The disks may not be
formatted (format(1M)), may have corrupted VTOCs, the device files
for the disks may be missing or invalid, or the devices may be turned-off
or detached from the system. These disks will be ignored.
Output format: [Device_Name,Disk_Access_Name]
[c0t1d0,c0t1d0s2] [c1t0d0,c1t0d0s2]
I’m able to successfully fdisk the secondary drive, partition, newfs, and mount it as a UFS file system.
Does anyone have any suggestions on what might be causing this condition? Any help would be greatly appreciated.
Thanks in advance,
Cary
04-09-2008 06:03 AM
04-16-2008 06:58 AM
04-17-2008 09:40 AM
Hello
I too came across the same problem when i was using x86 Sol 10 in a vmware session. It turned out that it was more of a Solaris problem than a Vxvm issue in that one instance of Solaris was 08/07 (would not work with vxvm) the other was 11/06 and that worked fine. As I was only using this setup to practice for my exam I was not too worried about which release of Solaris I used.
As of yet I have not managed to get Storage Foundation 5.0 to work with Solaris release 08/07.
04-18-2008 02:12 AM
04-18-2008 06:29 PM
04-21-2008 12:32 AM
04-21-2008 02:17 AM
07-25-2008 12:53 AM
FYI
I have 2 servers running SF5.0 Basic on Solaris10 x64 today. I sent a question to Veritas Support regarding "Solaris x64 not supported with SF5.0" as it says on their website but also the fact that they have SF5.0 for Sol10 x64 available for download. I got the answer (05-27-2008) that both SF Basic 5.0 and SF Basic 4.1 for Sol10 x64 platform are available now for download and support.
There are no MPs available for SF5.0 on Sol10 x86 today just a few RPs like
VRTSvxfs 5.0_x86: Rolling Patch for File System 5.0
I had some problems with vxconfigd. It kept stopping and occasionally caused some panic crashes for the server.
Symantec has a RP regarding this issue but only available through request at the time I had the problem
VM 5.0_x64_RP1_HF1: RP1 for Volume Manager 5.0 on 5.10_x86
This RP solved the problem.
07-25-2008 01:00 AM
Sorry...forgot about the disk issue.
Try "sliced" format instead. It solved the problem for me. Since its just the local disks it shouldn't matter to much that you choose "sliced" instead of "cds".