Well courtesy of the Apple support discussions I have an answer.
It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.
So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.
Tuesday, January 6, 2009
server woes solved
Well courtesy of the Apple support discussions I have an answer.
It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.
So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.
It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.
So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.
Server, Final Cut Server, Drobo woes solved
Well courtesy of the Apple support discussions I have an answer.
It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.
So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.
It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.
So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.
Monday, January 5, 2009
Arctic Strategy? Digital content plan? Nope, Server woes
Today was another of those days that I had blocked out for all kinds of creative strategy. But, first I figured I'd do a little Final Cut Server house-cleaning. All was well until about 150 error messages popped up on my screen. Much "okay" clicking ensued followed by a server check that shows the servers system drive is entirely full.
Not a good thing.
Whatever files are there are hidden and bad things have happened. Either it is a coincidence or FCSvr decided that the system drives was suddenly a great place to write files.
It looks like OS X server doesn't index the system drive so searches are useless. First the snow, then the power failure, now the server "failure". Something doesn't want me to plan out 2009.
Not a good thing.
Whatever files are there are hidden and bad things have happened. Either it is a coincidence or FCSvr decided that the system drives was suddenly a great place to write files.
It looks like OS X server doesn't index the system drive so searches are useless. First the snow, then the power failure, now the server "failure". Something doesn't want me to plan out 2009.
Subscribe to:
Posts (Atom)