I agreee, when you run the command, you typically will not see the results until you either refresh the GUI, or stop it and restart it
One thing that can cause this that is often overlooked is the Media Condition. By default, this is 36 months, which was oK for the original DDS tape type, but is totally inadequate for today's media. Find out what media Pool the Poor tape is in, look at all the media in that pool, and see if any of it is marked Fair (yellow). If you see any, or, just to act proactively, in the Media Pool properties, in the Condition tab, increase 'Valid For' value to 84 or 96 months, or just export the media and re-format it, and the closk will start running
The 'reset_poor_medium' will not fix this problem
If the media is fairly new, and resetting it does not change it to Good, you will probably need to open a case with the Response Center
In regard to teh Media Consistency error, this is a known problem. You will need to open a case with the Response Center, and have them send you a copy of the Site-Specific patches (SSP) that fixes this problem