Video Screencast Help

vxdisk rm got ' Detected non-ascii character in name' error

Created: 07 Apr 2013 • Updated: 07 Apr 2013 | 3 comments
This issue has been solved. See solution.

Hi,

 

When I was trying to initial my new disk, I got the "auto:none DA record" error,  it was said is caused by the label type in this article:http://www.symantec.com/business/support/index?page=content&id=TECH192889.

 

But I checked the label in format command, and the label is EFI already, so I planned to rm the disk from vxdisk and rescan it, but I got a ‘Detected non-ascii character in name’ again.....

Could someone help me about this, thanks.

 

HBWHCG01:/etc/vx/bin/vxdisksetup -if emcpower0 format=sliced
VxVM vxdisksetup ERROR V-5-2-4006 Disk emcpower0 contains auto:none DA record emcpower0s2;
Disk cannot be reinitialized by vxdisksetup.

HBWHCG01:/var/adm# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
emcpower0s2  auto:none       -            -            online invalid

HBWHCG01:/var/adm# vxdisk rm emcpower0s2
VxVM vxdisk ERROR V-5-1-419 Bad name emcpower0s2: Detected non-ascii character in name. Name must contain ascii characters only.
HBWHCG01:/var/adm#

 

Operating Systems:

Comments 3 CommentsJump to latest comment

maxpaynebupt's picture

after a reboot............it recovered, I can delete the emcpower0s2  now..............

 

But the emcpower0s2 changed to emcpower0

 

really very weird......

SOLUTION
g_lee's picture

fyi:

For EFI disks, the daname does omit the slice, to reference whole disk due to the way the disk is formatted (eg: if you compare the emcpower devices in /dev/*dsk/emcpowerX* you'll notice the EFI disk should have a wd (whole disk) partition whereas the disks with SMI/non-EFI labels do not)

reference:

VxVM 5.1SP1 (Solaris) Administrator's Guide ( https://d1mj3xqaoh14j0.cloudfront.net/public/docum... ) -> Administering disks -> Disk devices (pp83-84)
--------------------
Operating system-based naming
In the OS-based naming scheme, all disk devices are named using the c#t#d#s# format.
The syntax of a device name is c#t#d#s#, where c# represents a controller on a host bus adapter, t# is the target controller ID, d# identifies a disk on the target controller, and s# represents a partition (or slice) on the disk.

Note: For non-EFI disks, the slice s2 represents the entire disk. For both EFI and non-EFI disks, the entire disk is implied if the slice is omitted from the device name.
--------------------

or https://sort.symantec.com/public/documents/sfha/5....

re: 'Detected non-ascii character in name’ / unable to remove the disk - did you rescan (in powerpath and then vxvm) after relabelling the disk?

Assuming it was same/similar issue to your previous post ( https://www-secure.symantec.com/connect/forums/lun... ) where the disk was being relabelled to <2TB so you had to relabel manually; it's possible this may have caused an issue where either ppath or vxvm was still pointing to the old/errored device so it wasn't picking up the device properly? It makes sense that a reboot would clear this since this would have cleared out the old device configuration. If it happens again, would try clearing old devices from the OS tree (devfsadm -Cv), rescanning powerpath and then vxvm to see if that picks up the disk correctly.

If this post has helped you, please vote or mark as solution