Very odd issue, from the description I doubt this is media related at all. Sound more like some kind of bug or a resource exhaustion, you might get this behavior if the session table was full and no more resources were available. A normal reboot probably would have cleared this.
Were you able to log into the device during the incident?
How did the performance metrics look?
Any change you looked at the sessions table size?