- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Blast from the past II: presenting a LUN to a 4.0F...
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
тАО01-10-2006 01:14 AM
тАО01-10-2006 01:14 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 01:25 AM
тАО01-10-2006 01:25 AM
Re: Blast from the past II: presenting a LUN to a 4.0F box
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 01:55 AM
тАО01-10-2006 01:55 AM
Re: Blast from the past II: presenting a LUN to a 4.0F box
Then use 'file' to see whether you can really see the device and disklabel to make is useable.
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 02:03 AM
тАО01-10-2006 02:03 AM
Re: Blast from the past II: presenting a LUN to a 4.0F box
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 02:10 AM
тАО01-10-2006 02:10 AM
Re: Blast from the past II: presenting a LUN to a 4.0F box
Calculate device name and make device file using MAKEDEV.
For example
BUS 4 ID 1 LUN 1
# cd /dev
# ./MAKEDEV rza33*
As Hein said check with file command did you create device file OK.
When you present LUN to TRU64 V4.0F box you also define which LUN will be assigned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 03:37 AM
тАО01-10-2006 03:37 AM
Re: Blast from the past II: presenting a LUN to a 4.0F box
2nd, does reboot automatically create files?
Do I need to scan scsi bus somehow?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 09:37 AM
тАО01-10-2006 09:37 AM
SolutionPretty sure. That's how I remember it also.
Basically the lun support came late. Originally OSF only had bus + unit. Then support for luns was added and a new naming convention was developped to be compatible with the existing lun-less and thus 'a' less naming.
>> 2nd, does reboot automatically create files?
Yes, but like Ivan says, you need to boot genvmunix, not your own /vmunix kernel. They rebuild, and reboot for a second time with the fresh kernel and fresh device files.
>> Do I need to scan scsi bus somehow?
Not if you go the long, but predictable, genvmunix route.
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 06:12 PM
тАО01-10-2006 06:12 PM
Re: Blast from the past II: presenting a LUN to a 4.0F box
I am 100% sure!!!
Take a look at "normal" systems with only internal SCSI disks. Every SCSI disk connected to "normal" SCSI controller has LUN 0!!! So that is why these disks are called rz1, rz2 etc, NOT rza1, rza2 etc!!!
Once again:
LUN 0 has NO ADDITIONAL LETTER, LUN 1 has letter a (rza8 is BUS 1 ID 0 LUN 1), LUN 2 has letter b ...
I never reboot UNIX systems when I do not have to! UNIX is NOT MS windows!
But you can also do what Ivan said, it will work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 06:33 PM
тАО01-10-2006 06:33 PM
Re: Blast from the past II: presenting a LUN to a 4.0F box
1. Create and present new "disk"
2. Do:
# scu scan edt
and
# scu show edt
to verify OS has found "new disk"
3. Calculate device name from formula:
rzX ((SCSI ID) + (Bus number X 8))
where X is additional letter for LUN number
where LUN 0 has NO ADDITIONAL LETTER, LUN 1 is letter "a", LUN 2 is letter "b" etc
example: BUS 1 ID 1 LUN 1 is rza9
3. Create device files for "new disk"
# cd /dev
# ./MAKEDEV rzXY (./MAKEDEV rza9*)
4. Check everything is OK using "file" command.
5. Be happy it is UNIX and label the "new disk"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 07:48 PM
тАО01-10-2006 07:48 PM
Re: Blast from the past II: presenting a LUN to a 4.0F box
If you only add a new device on an existing SCSI bus (or if you configure a new unit in an existing HSZ/HSG).
2 possibilities exist
- the MAKEDEV tool (already explained)
- simply reboot. It is not necessary to reboot from genvmunix. There is no new device driver needed for a new disk on an existing bus. (Otherwise, running MAKEDEV without rebooting wouldn't work). In fact, all busses are scanned during startup, when the device driver is activating an adapter.
This can be seen in the startup messages.
You only have to reboot from genvmunix if your configuration is changed. f.i.
- a new SCSI adapter is added
- an existing adapter is moved to another slot