Filter
Top Products
Chapter 10 Troubleshooting 10-3
Poor video quality
Possible causes: Content is stored at a bit rate different from that at which it was
encoded. Content might be poorly encoded. The destination client might not be
able to keep up with the video stream.
Check the bit rate of the content. The bit rate should be roughly
filesize * 8/playtime, where playtime is the duration of a title, in seconds. Try
another title, preferably one encoded at a lower bit rate. Try a different
destination client.
Corrupt disk labels
You cannot complete the boot process because of corrupt disk labels.
Possible cause: shutting down a server which is the midst of delivering streams.
Reboot single-user and relabel affected disks with format.
Kernel panic with SAHI queue threshold messages
Likely cause: ATM cable is disconnected.
Disk failure
If you have a single bad disk, use the procedure specified in Chapter 8
“Administering MFS Disks,” to replace the disk and restore data to the new disk.
You do not have to interrupt the operation of the server to do this. If you have
multiple simultaneous data disk failures, you must, following replacement, use
smc_tar or ftp to restore original content.
Inconsistent video performance
Possible cause: “soft” disk errors.
Check /var/adm/messages for console messages indicating non-fatal disk
errors. If you have SunNet Manager or other SNMP-conformant manager, check
the diskErrorTable structure on the server.
If a single disk is displaying frequent non-fatal errors, have your Sun Sales
Engineer replace the disk and restore content from the parity disk to the new
disk. There is no need to power down the server to do this. Chapter 8
“Administering MFS Disks,” describes a procedure for “hot” disk replacement.
On a Sun MediaCenter server equipped with multiple Fast Ethernet interfaces,
this could be caused by not having all (or both) of the Fast Ethernet links
connected, if load sharing has been specified for those interfaces. When load
sharing is in effect, the Sun MediaCenter software performs load balancing across
multiple Fast Ethernet interfaces, treating the multiple interfaces like a single,
logical output interface. Failure to connect all Fast Ethernet links results in
difficult-to-diagnose stream delivery failures. This is not a requirement on a
server with multiple ATM interfaces. Clients can address ATM interfaces
individually.