Grass Valley K2 Summit 3G v.8.0 - Manual (Page 92)

Media File System problems
Corrective Actions Possible Causes Problem
1. If the problem is only
associated with a specific clip or
clips, delete the problem clips.
If the problem persists, proceed
with the next step.
2. Use Storage Utility and Check
File System. If the file system
fails the check process you must
make a new file system. When
you do so you lose all media.
The media database is out of
sync with the media files or
there is a corrupt media file.
Also check the storage system
for causes related to certain
usage patterns. One or more clips do not play
or record correctly. This can be
accompanied by a StatusPane
message indicating a fault in
the media file system.
Use Storage Utility and Check
File System. If the file system
fails the check process you must
make a new file system. When
you do so you lose all media. The file system is corrupt or
disks are faulty/missing such
that they are not part of a stripe
group. During K2 Summit system
startup a “…no file system
running…” message appears.
Related Topics
Checking the storage system on page 93
Media disk problems
On the Windows desktop open the "My Computer" for you K2 system and do a quick check of the
drives. You should see C: and V: drives.
Corrective Actions Possible Causes Problem
Open Storage Utility and identify faulty
disks. Replace faulty disks. A media disk is bad or
there has been a
hardware failure. No clips appear in the Clips
pane. This may be
accompanied by a startup
message or a StatusPane
message regarding media
disks being unavailable.
In Recorder, select the Time Dome and
choose
Available Storage . If the Time Dome
is filled it confirms that your K2 Summit
system is out of space. Make space on the
media drives by doing the following:
- Delete unused clips and empty the Recycled
Bin.
The media disks are
reaching maximum
capacity. The StatusPane message
“Media disks getting full…”
appears or a “FSS
‘default(0)’” message
appears.
92 K2 Summit 3G Production Client Service Manual 02 February 2012
Troubleshooting problems