- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SAM problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2001 09:58 AM
11-12-2001 09:58 AM
SAM problems
I'm trying to create a new volume group using SAM. I started SAM fine, and kicked off the create volume group.
I looked in /var/sam/log/samlog and found nothing special. Except for one vgimport -P command which exited with code 1.
The disc I'm trying to create volume on is on a NIKE20 disk array.
I installed patch PHCO_23876 on my 11.00 O/S.
Any clues as to what is going on?
Thank!
Josee...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2001 10:03 AM
11-12-2001 10:03 AM
Re: SAM problems
do a diskinfo /dev/dsk/cXtYd0
after you get the device file for the lun 0 of the nike 20.
You will probably see the lun0 twice. once on tX and tY corresponding to the SPA and SPB.
The nike has a curious note about autotrespass.
You could try it from command line also.. to get a more verbose output.
See: here for more on the nike:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x417edfe5920fd5118fef0090279cd0f9,00.html
Later,
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2001 10:04 AM
11-12-2001 10:04 AM
Re: SAM problems
Try
Creating Volume Group and Logical Volumes
pvcreate /dev/rdsk/cXtXd0 - For each disk
mkdir /dev/vgname
mknod /dev/vgname/group c 64 0x0#0000
vgcreate /dev/vgname /dev/dsk/cXtXd0
To create new logical volumes
lvcreate -n lv## /dev/vgname - Create a zero sized logical volume,
lvextend -l <# 4MB extents> /dev/vgname/lv## /dev/dsk/cXtXd0 - Make lv's size you want
To create and mount a new filesystem (make sure to get blksize from DBA)
mkdir /mntpoint
newfs -F vxfs -b
mount /dev/vgname/lvol_ /mntpoint
Add entry to /etc/fstab
/dev/vgname/lvol_ /mntpoint vxfs rw,suid,delaylog,detainlog 0 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2001 10:14 AM
11-12-2001 10:14 AM
Re: SAM problems
To identify the problem, go in the manual route.
ioscan -nkCdisk
and note the disks which you want to be in the new VG
If there are any pvlinks (two pv paths to the same disk), make a note of that too.
pvcreate
mkdir /dev/vgname
mknod /dev/vgname/group c 64 0xx0000
vgcreate
{options can be pv limit, extent size etc. or you can not specify anything).
See how this works. I suspect the problem is more to
with the recognition of disks.
-raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2001 02:59 PM
11-12-2001 02:59 PM
Re: SAM problems
Try to create the vg manually,
Do a ioscan -fnC disk to check whether the disk is sensed properly with the device as claimed.
ioscan -fnC disk
Now proceed to creating a VG,
pvcreate -f /dev/rdsk/cxtydz
mkdir /dev/vg_name
mknod /dev/vg_name/group c 64 0x0n0000
(n=1,2,3,.... and is unique
do a ll /dev/*/group to check the n is unique)
vgcreate /dev/vg_name /dev/dsk/cxtydz
Do a pvcreate and vgextend for any other disk you want to add to this vg. Now do a lvcreate to create a new lv on this disk,
lvcreate -L lv_size_MB -n lv_name /dev/vg_name
Now create a filesystem on this lv,
newfs -F vxfs -o largefiles /dev/dsk/rlv_name
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2001 03:24 PM
11-19-2001 03:24 PM
Re: SAM problems
I haven't not yet isolated the issue due to lack of time but am lucky that the array in not critical for me at this time.
Something for me to play with on rainy days.
Thanks again!
Josee...