- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Device File name appears as (null) to HWMGR
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
Discussions
Discussions
Forums
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
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
тАО04-24-2006 06:03 AM
тАО04-24-2006 06:03 AM
Device File name appears as (null) to HWMGR
disklabel: dsk5: No such file or directory
This is the response I get when trying to use disklabel in /devices/disk. I get the same results in /devices/ndisk. Both directories contain the files dsk0a-h through dsk4a-h.
Additional information: When I use HWMGR, the disk shows up, but the DEVICE FILE name is this: (null) My other disks show up as dsk0 - dsk4.
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 06:11 AM
тАО04-24-2006 06:11 AM
Re: Device File name appears as (null) to HWMGR
when you delete the device with hwmgr and do a scan, does that change anything?
A NULL means that there is no device behind that file anymore.
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 06:24 AM
тАО04-24-2006 06:24 AM
Re: Device File name appears as (null) to HWMGR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 07:38 AM
тАО04-24-2006 07:38 AM
Re: Device File name appears as (null) to HWMGR
hwmgr delete -id
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 07:55 AM
тАО04-24-2006 07:55 AM
Re: Device File name appears as (null) to HWMGR
hwmgr: Error unable to find subsystem name in command line.
No luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 04:40 PM
тАО04-24-2006 04:40 PM
Re: Device File name appears as (null) to HWMGR
Else try,
#/sbin/hwmgr -show scsi
Chk. the did (2nd column) corresponding to dsk5
then,
#/sbin/hwmgr -delete scsi -did
Hope this helps,
-Srinivas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 04:55 PM
тАО04-24-2006 04:55 PM
Re: Device File name appears as (null) to HWMGR
I had same problem tried everything but of no use then I removed the disk from array put put it again and problem solved.
Hope this wul solve ur problem
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 08:32 PM
тАО04-24-2006 08:32 PM
Re: Device File name appears as (null) to HWMGR
I happened to have dealt with a much similar sounding problem yesterday.
It was a little more complicated, as it was a cluster and the disk _seemed_ to work as an other cluster member was performing a distributed raw device service for it.
We had a 'null' and yet there were 2 path indicated and a BLT entries visible.
'hwmgr -show comp inconsisten' did also highlight that device ID.
We cleaned up using:
hwmgr -delete -d xxx
hwmgr -scan scsi
The device now re-appeared, with a fresh ID and a fresh dskXX name.
You can rename that with cfsmgr, but why bother for a new device, and for us we only flipped the softlink in /etc/fdmns/yyy_domain to point to the new disk file.
note 1...
We further cleaned up with: hwmgr -refresh component.
Note 2...
Consider hwmgr -scan component
Hth,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 10:13 PM
тАО04-24-2006 10:13 PM
Re: Device File name appears as (null) to HWMGR
Remember Tru64 now disks have "unique" id's
they are not mapped to a SCSI-slot anymore.
once unix has detected the disks you can move them around in the slots and theyremain operational (as long as you reboot the system first or send rescan de scsibus).
at boottime the system runs "dsfmgr -K" to create the special-files in /dev/disks.
so when at boottime the disk5 is not present there will not be any dsk5a-h special file.
so after "hwmgr -scan scsi" and "hwmgr -show scsi" the file name still is NULL then the disk is not in the system or the disk is
not functioning.
and dsfmgr -K or dsfmgr -F will not create any special files in /dev/disk.
Pieter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2006 02:24 AM
тАО04-25-2006 02:24 AM
Re: Device File name appears as (null) to HWMGR
My console log had this message on it: "hwc_user_cmd:framework error 60" "hwc_run_dsfmgr_cmd: cmd failure (frame=60), (subsys=0)"
As recommended by the system itself, I entered the following command: "/sbin/dn_setup -boot" to synchronize dsfmgr with kernel
Resulting messages were: "dsfmgr: NOTE: updating kernel basenames and old devnames for system at /" "dsfmgr:NOTE: creating device special files for system at /" "+dsk5a +dsk5a +dsk5b +dsk5b ... +dsk5h +dsk5h"
After this I did an hwmgr -scan scsi and an hwmgr -show scsi The device that had showed up as "(null)" previously now shows up as dsk5. On to the next staep, thanks to everyone for their suggestions.