Drobo, Again

Drobo's performance has plummeted from subpar to unusable over the last few days. Maybe this is somehow related to the false positives about being critically low on space upon boot? To test if it was the disks, I pulled them out one at a time for 30s and navigated around in the Finder / Terminal to see if it started behaving like its former self. I tried the top three drives with no success, but then some magic happened. When I put the 3rd drive back in the Drobo it rebooted (uncleanly unmounting), and then started rebuilding my array. Performance is back to normal during the rebuild process (well 7 MB/s read is about half of normal), which I can look forward to for 2-3 days according to the progress indicator.

Corrupted drive? Crippled in software due to a capacity bug? Who knows. I'll see what happens when the rebuild finishes... in any case there's now hope that I can get my data off of Drobo if weirdness persists.

Update on 10:17 PM by Chris H.

My Drobo just fnished rebuilding, and as soon as I tried to write something to it I'm running into the same old performance problems again.  Next step is to dump everything off it, reformat the Drobo, and reload everything on it. If that doesn't work, I'm eyeing some RAID enclosures.

-bash: make: command not found

Yet another Snow Leopard / Time Machine screw upHmm, more Snow Leopard / Time Machine problems. I tried to do a subversion checkout of some code and got an error about not being able to connect. It turned out that mod_wsgi was missing from my restore and apache was failing to start. So I went into the mod_wsgi source which was still there and did a make...

-bash: make: command not found

Click to read more ...

Adobe CS4: Licensing has stopped working Error 150:30

I replaced a hard disk and did a Snow Leopard Time Machine restore to find that my CS4 applications wouldn't start. I found the solution here on Erik Hansen's blog, but it took me awhile to find it. I'm posting it again here in the hopes that others will be able to find it faster.

1. Download Adobe's Licensing Repair Tool
2. Run that, restart, run it again, etc. as the instructions state. This doesn't work for me, and looks like it's erroring out each time though it doesn't give a human readable error message.
3. Delete /Library/Preferences/FLEXnet Publisher
4. Photoshop magically starts working again

Screen sharing bug in Snow Leopard?

Screen Saring.app error message :-(Today I tried screen sharing between my laptop and desktop over a local network and it wouldn't work in either direction. I kept getting "Authentication Failed" messages which told me to check my username and password. I got it to work once by entering my unix username and password and then quitting screen sharing while it was trying to connect. I then started a new session with the old login window still doing it's thing, and it logged in immediately and brought up the remote computer. This wasn't repeatable, and leaves extra login windows sitting around that I couldn't figure out how to close.

Solution

In the end, using my full name instead of my unix username appears to be working. This is weird, since using my unix username works for file sharing...