Ok, I looked at the source pf your berried.net/old “index” page, and see that your old version was 2.01 (released over 2 years ago!) - there have been database changes since then.
This means that since you updated the application, you have probably also updated the database (if you followed the one-click success email instructions), and this means the databases are no longer compatible between the “old code” and the new upgrade.
There are a few ways to deal with this …
If your content is important to you, and I assume it is, I think the best approach to take is to try to get your blog back to the way it was, and then develop an upgrade strategy.
To do this, in addition to the steps I described in my first response, you need to “retrieve” and “old” copy of your database from before the upgrade attempt.
You should be able to do this via the Web Panel -> Goodies -> Manage MySQL screen by clicking the “Restore DB” link under the “Actions” column of the database your WordPress installation is using.
Once you have done that, and replaced the “old” files/directories over the “new”, your blog should be back where it was.
It is often problematic to upgrade “skipping” numerous intermediate upgrades, as there are often intermediate changes and “upgrade scripts” may not always catch all the differences (they often assume you are upgrading from a recent version).
My advice is to get your blog working again, and then investigate whether or not you need to do some intermediate upgrades to get yourself current. You will probably have to do this “manually” at this point (since you let your blog get so out of date version wise), but that can be done.