SF Basic 5.0 on Solaris 10 x86, vxdiskadm -> These disk devices do not appear to be valid.

[Cary]

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

[jgrimm01]

Hello Cary,

How many volumes are already created on the system?

Thanks,

J

[ngc604]

Hi,
I have the same problem adding a disk (c2d0):

- Veritas Storage Foundation Basic 5.0
- Solaris 10 x64

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c1d0 <DEFAULT cyl 9726 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0
       1. c2d0 <DEFAULT cyl 9726 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@1f,2/ide@1/cmdk@0,0
Specify disk (enter its number): 1
selecting c2d0

...cut...

...partition type
      Partition   Status    Type          Start   End   Length    %
      =========   ======    ============  =====   ===   ======   ===
          1       Active    Solaris2          1  9728    9728    100

partition> p
Current partition table (original):
Total disk cylinders available: 9726 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0 unassigned    wm       0               0         (0/0/0)            0
  1 unassigned    wm       0               0         (0/0/0)            0
  2     backup    wu       0 - 9725       74.50GB    (9726/0/0) 156248190
  3 unassigned    wm       0               0         (0/0/0)            0
  4 unassigned    wm       0               0         (0/0/0)            0
  5 unassigned    wm       0               0         (0/0/0)            0
  6 unassigned    wm       0               0         (0/0/0)            0
  7 unassigned    wm       0               0         (0/0/0)            0
  8       boot    wu       0 -    0        7.84MB    (1/0/0)        16065
  9 unassigned    wm       0               0         (0/0/0)            0

format> label
Ready to label disk, continue? y

# vxdctl enable

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto:none       -            -            online invalid
c2t0d0s2     auto:none       -            -            online invalid

# vxdiskadm
1      Add or initialize one or more disks
...cut
Select disk devices to add: [<pattern-list>,all,list,q,?] c2
  Here is the disk selected.  Output format: [Device_Name]

  c2t0d0

Continue operation? [y,n,q,?] (default: y) y

Which disk group [<group>,none,list,q,?] (default: none) TESTDG
Create a new group named TESTDG? [y,n,q,?] (default: y) y
Create the disk group as a CDS disk group? [y,n,q,?] (default: y) n
Use a default disk name for the disk? [y,n,q,?] (default: y) n
Add disk as a spare disk for TESTDG? [y,n,q,?] (default: n) n
Exclude disk from hot-relocation use? [y,n,q,?] (default: n) n

Add site tag to disk? [y,n,q,?] (default: n) n
  A new disk group will be created named TESTDG and the selected disks
  will be added to the disk group with disk names that you will specify
  interactively.

  c2t0d0

Continue with operation? [y,n,q,?] (default: y) y

  This disk device does not appear to be valid.  The disk may not be
  formatted (format(1M)), may have a corrupted VTOC, the device file
  for the disk may be missing or invalid, or the device may be turned-off
  or detached from the system.  This disk will be ignored.
  Output format: [Device_Name,Disk_Access_Name]

  [c2t0d0,c2t0d0s2]

???...
Any help would be greatly appreciated.

PS: I’m able to successfully newfs and mount it as a UFS file system.




Message Edited by ngc604 on 04-16-2008 07:03 AM

Message Edited by ngc604 on 04-16-2008 07:07 AM

[marinestu]

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.

[ngc604]

Hi marinestu,
tomorrow I install Solaris version 10 5/08 and I execute some test...

thanks

...to be continued

[springer]

Always with x86 make sure u apply mp1

but can u do following

/etc/vx/diag.d/vxdmpinq /dev/rdsk/c1t0d0s0  and same on the other disk and tell me if serial numbers are the same

[ngc604]

Hi springer,

8/7 and 5/8 don't work!

I have installed VM 5.0_x64_RP1: RP1 for Volume Manager 5.0 on 5.10_x86 (patch id 128060-02)
now I try the patch MP1...
...if I find the link in order to download the version for Solaris 10 5/8 x86 amd64

...
# ls /dev/rdsk
c0t0d0p0   c0t0d0s1   c0t0d0s15  c0t0d0s7   c1d0p3     c1d0s12    c1d0s4     c2d0p0     c2d0s1     c2d0s15    c2d0s7
c0t0d0p1   c0t0d0s10  c0t0d0s2   c0t0d0s8   c1d0p4     c1d0s13    c1d0s5     c2d0p1     c2d0s10    c2d0s2     c2d0s8
c0t0d0p2   c0t0d0s11  c0t0d0s3   c0t0d0s9   c1d0s0     c1d0s14    c1d0s6     c2d0p2     c2d0s11    c2d0s3     c2d0s9
c0t0d0p3   c0t0d0s12  c0t0d0s4   c1d0p0     c1d0s1     c1d0s15    c1d0s7     c2d0p3     c2d0s12    c2d0s4
c0t0d0p4   c0t0d0s13  c0t0d0s5   c1d0p1     c1d0s10    c1d0s2     c1d0s8     c2d0p4     c2d0s13    c2d0s5
c0t0d0s0   c0t0d0s14  c0t0d0s6   c1d0p2     c1d0s11    c1d0s3     c1d0s9     c2d0s0     c2d0s14    c2d0s6

# /etc/vx/diag.d/vxdmpinq c1d0s1 
ioctl failed: Inappropriate ioctl for device
VxVM vxdmpinq ERROR V-5-1-8853 /etc/vx/diag.d/vxdmpinq for /dev/rdsk/c1d0s1. ioctl failed., evpd 0 page code 0. Inappropriate ioctl for device

# /etc/vx/diag.d/vxdmpinq c2d0s1
ioctl failed: Inappropriate ioctl for device
VxVM vxdmpinq ERROR V-5-1-8853 /etc/vx/diag.d/vxdmpinq for /dev/rdsk/c2d0s1. ioctl failed., evpd 0 page code 0. Inappropriate ioctl for device



Message Edited by ngc604 on 04-21-2008 12:37 AM

[ngc604]

ops ...I have mistaken!

Is Storage Foundation Basic 5.0 available for Solaris x64?
No. Solaris x64 is not supported with Storage Foundation 5.0.
For Solaris x64 support, use Storage Foundation Basic 4.1.
(ent-sf_basic_5.0_technical_faq_01-2007.en-us.pdf)

...I try version 4.1 (sfbasic.4.1.00.0_phase2.x86.tar.gz)

sorry 

[Lord_of_TIburon]

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.  

[Lord_of_TIburon]

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".