- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- volume daemon is not accessible!
Operating System - Tru64 Unix
1748234
Members
3339
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО12-22-2003 03:31 AM
тАО12-22-2003 03:31 AM
I make LSM in my workstation,but seem to fail
# scu show edt
CAM Equipment Device Table (EDT) Information:
Device: RZ1CF-CF Bus: 0, Target: 0, Lun: 0, Type: Direct Access
Device: VIKING II 4.5SCA Bus: 0, Target: 2, Lun: 0, Type: Direct Access
Device: RRD46 Bus: 0, Target: 4, Lun: 0, Type: Read-Only Direct Access
#disklabel -rw -t advfs rz2
#voldisksetup -i -v rz2
!voldisk -F -f init rz2 type=sliced puboffset=16
volume daemon is not accessible
#
# scu show edt
CAM Equipment Device Table (EDT) Information:
Device: RZ1CF-CF Bus: 0, Target: 0, Lun: 0, Type: Direct Access
Device: VIKING II 4.5SCA Bus: 0, Target: 2, Lun: 0, Type: Direct Access
Device: RRD46 Bus: 0, Target: 4, Lun: 0, Type: Read-Only Direct Access
#disklabel -rw -t advfs rz2
#voldisksetup -i -v rz2
!voldisk -F -f init rz2 type=sliced puboffset=16
volume daemon is not accessible
#
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 04:57 AM
тАО12-22-2003 04:57 AM
Re: volume daemon is not accessible!
Hi,
assuming, you have 4.0X, look here:
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/AQ3NCETE/TITLE.HTM
greetings,
Michael
assuming, you have 4.0X, look here:
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/AQ3NCETE/TITLE.HTM
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-23-2003 04:20 AM
тАО12-23-2003 04:20 AM
Solution
Prior to V4.x you will see this message when a user is trying to execute an LSM command and they are not the superuser. With V4.x the message is more obvious: "You are not privileged to run volprint".
Please check if vold is still running as a process. If not use the following commands:
1. add "pseudo-device lsm_ted 0"
"pseudo-device lsm 1"
into your kernel parameter file and rebuild kernel. Reboot kernel afterwards
2. check lsm license with
# lmf list |grep LSM-OA
output must be:
LSM-OA active unlimited
3. check if vold is running:
# ps waux |grep vold
if not running, use #/sbin/vold to start the vold daemon.
4. zero disklabel of disk which will be used by LSM!!
5. # volsetup rz2
there are different ways and commands to create volumes (e.g. volassist make vol01 10m etc.)
have a look into the documentation and be sure you understand the concept and the lsm objects prior to "play around".
Please check if vold is still running as a process. If not use the following commands:
1. add "pseudo-device lsm_ted 0"
"pseudo-device lsm 1"
into your kernel parameter file and rebuild kernel. Reboot kernel afterwards
2. check lsm license with
# lmf list |grep LSM-OA
output must be:
LSM-OA active unlimited
3. check if vold is running:
# ps waux |grep vold
if not running, use #/sbin/vold to start the vold daemon.
4. zero disklabel of disk which will be used by LSM!!
5. # volsetup rz2
there are different ways and commands to create volumes (e.g. volassist make vol01 10m etc.)
have a look into the documentation and be sure you understand the concept and the lsm objects prior to "play around".
Help() { FirstReadManual(urgently); Go_to_it;; }
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP