
Avid
®
Unity™MediaNetwork5SystemMaintenance
Avid Technology EMEA | Enterprise Customer Success Page12of20
Appendices
1. IdentifyingBadDrives
2. Replacingafaileddrive
3. RecreatingDriveLabels
4. ThePortServerConsole
5. MakingaMetadataback‐up
Appendix 1 - Identifying Bad Drives
TheFileManagerservicetracksdriveandclienterrorsinthefileUnityClientLog.txt.Toanalysetheerrors
whichtriggerthe“DriveErrorAnalysisNeeded”indicatorintheMonitortool,launchtheAvidDiskError
AnalyzerfromtheStartmenuoftheMediaEngine.NavigatetothefileUnityClientLog.txtinthefolder
D:\ProgramFiles\AvidTechnology\AvidUnity.
WhentheDiskErrorAnalyzerloadsitshouldlooksomethinglikeFig.13below:
Fig.13–TheAvidDiskErrorAnalyzer
Fromthepaneontheright‐handsideyoucan choosetodisplayerroroneitheraper‐clientoraper‐drive
basis.Ifaparticulardriveisshowingmanywriteerrorsor“LongReadCommandTime”errorsthenitprobably
requiresreplacing.ContactAvidCustomerSuccesstoarrangea
replacement.PleasenotethatAvidCustomer
SuccessmayaskyoutoperformadditiontestingonthedriveusingAvidStorageManager(ASM)orDiskLog.
NotethattheUnityClientLog.txtfilecanbeanalysedonanyWindowsPCbycopyingboththefileAnalyzer.exe
(theexecutableforAvidDiskErrorAnalyzer)andUnityClientLog.txt
fromthefolderD:\ProgramFiles\Avid
Technology\AvidUnity.
Commentaires sur ces manuels