Grass Valley K2 Solo 3G Client Service Manual v.9.0 - Manual (Page 59)

10. In the MegaRAID Storage Manager main window tree-view, verify that one controller reports
configured drives and one controller reports unconfigured drives.
11. For the controller with unconfigured drives, repeat previous steps to import the foreign
configuration.
12. When you have imported the foreign configuration for both controllers, click File | Exit to close
MegaRAID Storage Manager.
13. Restart the K2 Solo 3G system.
Related Topics
Disk controller board removal on page 93
Recovering the media database
This section provides topics about recovering the media database.
About the automatic database backup process
Every 15 minutes the K2 system checks to see if any media operations have changed the media
database. If a change has occurred, the K2 system creates a backup file of the media database. The
backup file is saved in the same directory as the media database using a rotating set of three file
names. These files are named media.db_bakX where X is the number in the rotation. Each time a
backup occurs, the oldest backup file is overwritten. If some condition renders one of the backup
files un-writable, the backup file following that in the rotation is subsequently used for every backup
until the condition is resolved.
Identifying a corrupt media database
The following symptoms could indicate a corrupt media database:
• On startup, the Grass Valley MetaDataService is unable to start. This is indicated in the Services
control panel if the Grass Valley MetaDataService does not display as Started.
• The K2 log displays a “…file is encrypted or is not a database…” error.
As soon as you suspect a corrupt media database, stop all media access and take the K2 system
offline.
Restoring the media database
1. Stop all media access and take the K2 system offline.
2. Navigate to the V:\media directory.
3. Make a copy of the media.db and media.db_bak* files and store them in a secure location.
4. Stop the Grass Valley MetaDataService as follows:
For the standalone K2 system, use the Services control panel to stop the service.
5. Determine which backup file is the most recent good file by examining the file modification date
on each backup file.
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.
06 November 2012 K2 Solo 3G Service Manual 59
Service procedures