Grass Valley K2 Summit Storage Area Network Installation - Manual (Page 316)

6. Rename the current media.db file (which is assumed to be corrupt) to another name, and rename
the most recent good media.db_bakX file to media.db.
7. Restart the K2 system following normal procedures.
8. Confirm that the systems come up correctly with the restored database now in place.
9. Use Storage Utility Clean Unreferenced Files and Clean Unreferenced Movies to repair any
inconsistencies between the contents of the database and the file system.
Working with RAID storage
This section refers to K2 10G RAID storage devices.
K2 Level 2, 3, 10, 20, 30, and 35 RAID storage devices were released with previous versions of K2
SANs. Refer to previous versions of this manual for information about those levels.
Use the procedures in this section when doing configuration or service work on the RAID storage
devices of an existing K2 SAN.
Related Links
Checking RAID storage subsystem status on page 316
Checking controller microcode on page 317
Identifying disks on page 317
Get controller logs on page 319
Unbind RANK on page 320
About full/background bind on page 321
Bind RANK on page 321
Binding Hot Spare drives on page 323
Loading RAID controller and expansion chassis microcode on page 323
Downloading disk drive firmware on page 324
Replacing a disk module on page 325
Replacing a controller on page 326
Configuring RAID chassis network and SNMP settings on page 327
Checking RAID storage subsystem status
Some limited status information for storage subsystems is displayed in the Storage Utility. This can
be helpful when configuring storage. You can view status information by selecting items in the tree
view.
Status information displayed Item in tree view
Number of Controllers Controllers in Device
316 K2 SAN Installation and Service Manual 18 November 2010
Administering and maintaining the K2 SAN