- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Tru64UNIX v4.0f writing a disklabel to a drive con...
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
тАО07-22-2004 03:11 AM
тАО07-22-2004 03:11 AM
Tru64UNIX v4.0f writing a disklabel to a drive connected to a KZPCC - /dev/rri0c
I have a Tru64UNIX v4.0F with a KZPCC single port controller. I have installed the latest patch kit, and NHD CD. I can see the controller and disk drives from Tru64UNIX. I now want to write a disk label. When I do this, I get an "Unrecognised component type" message.
I have looked in the disktab file, and there is no ri device listed. How do I do this ?
With regards
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 05:09 AM
тАО07-22-2004 05:09 AM
Re: Tru64UNIX v4.0f writing a disklabel to a drive connected to a KZPCC - /dev/rri0c
If using this information installation should work without a problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 05:58 PM
тАО07-22-2004 05:58 PM
Re: Tru64UNIX v4.0f writing a disklabel to a drive connected to a KZPCC - /dev/rri0c
This is a KZPCC-AC rev D01, firmware - CQ16.
I can see it from Tru64UNIX, and have followed the documentation, but the documentation does not seem to go as far as the writing of the disklabel.
I can see the RAID controller, and disk drives from Tru64UNIX.
Regards
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 07:02 PM
тАО07-22-2004 07:02 PM
Re: Tru64UNIX v4.0f writing a disklabel to a drive connected to a KZPCC - /dev/rri0c
Is this the syntax that you used ?:
# disklabel -rw ri0 rixx
/etc/disktab has been abandonned long agoo as repository for disk geometry. /etc/ddr.dbase and /etc/ddr.dbase have been introduced to play this role.
The kernel config file should contain at least 2 lines with the following syntax:
(slotnumber may vary)
bus i2o0 at pci2001 slot 4
controller i2o_bs0 at i2o0 slot 18
The file /etc/i2o_bs.db and i20_bs.db.bak are the keepers of the "ri" device numbering. If you find that it is ilogical, you may delete it and a reboot will recreate the file with the numbering starting a "0".(Don't do this if the bootdisk is on the KZPCC)
See also "man ri"
Have fun,
Johan.
_JB_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 08:32 PM
тАО07-22-2004 08:32 PM
Re: Tru64UNIX v4.0f writing a disklabel to a drive connected to a KZPCC - /dev/rri0c
So after checking the supported option list and the controller will be supported it is the next step to verify proper setup on s "unit" (storage) side.