@mitu Yeah I figured that after. I think I couldn't run any commands, so I plugged it out.
I think I was testing to see if the hub worked on USB 2.0 a little bit before the error occured, so I've kept it in a USB 3.0 port. I've been testing for a while now and there don't seem to be any issues anymore. Hopefully, the problem won't come up again.