Grass Valley K2 System Guide v.7.2 - Manual (Page 117)

07 April 2010 K2 System Guide 117
Bind Luns
5. When progress reports 100% complete, the LUN is unbound.
6. Restart the K2 system.
NOTE: On the K2 Media Client, remember that the LUN 0 (disks 0_0 and 0_1) is the
system drive. Do not attempt disk operations on the system drive.
Bind Luns
When you bind a LUN, you select one or more unbound disks and create a new LUN.
The Storage Utility places this new LUN at the bottom of the list and numbers it
accordingly. However, with internal storage, disk numbers are enforced by the chassis
slot in which the disk resides. Therefore, depending on the number and sequence of
LUNs created, it is possible that the LUN numbers and the disk numbers do not
match. When you create a new file system, this mismatched numbering does not
hamper functionality. However, to make the internal storage K2 system easy to
service, you should retain the correct numbering sequence. To do this you must
unbind all media LUNs and then bind disks in sequence. On a K2 Media Client, do
not unbind LUN0, which is the system drive.
For a direct-connect storage, refer to “Setting up direct-connect RAID storage” on
page 173 .
To bind a LUN, do the following:
1. In the tree view, right-click the Unbound node and select Bind LUN .
2. If online, messages appear “…offline mode now?” and “…continue?”. Click Yes
to put the system in offline mode.
AppCenter channels go offline.