after a power outage on a hpux box the Oracle DB will not start, I get this error ORA-03113: end-of-file on communication channel

You should be able to simply start a new client-server connection (ssh); start your listener(s) if necessary, then start SQLPLUS as sysdba.  If the instance hasn't autostarted, you need to start it manually.  The 3113 simply occurs when your network connection is broken or times out.  

I forgot to mention, there is no network involved.  I'm trying to start the DB from the hp box where it resides.  I've logged on as sysdba and tried to restart it but I get the same error.  

Anything in the alert log or any other trace files being generated?

ORA-03113 is not necesarily a network disconnect.

I looked in the dirctory that most people sugtested online, but there was no trace file.  

What about the alert log?

I did a find the entire hpux box and there was no alert log.

It should be in the directory that is defined as background_dump_dest in the init.ora.  The actual name should be alert_${ORACLE_SID}.log

that's why there is no log, that option is not in the init.ora

nope no such log file, I hope that's not the only way I can fix my problem.
dialer1(admin)@/opt/oracle/OraHome1 [1029]
$ go $ORACLE_HOME
dialer1(admin)@/opt/oracle/OraHome1 [1030]
$ ls *.log
rollup.log
dialer1(admin)@/opt/oracle/OraHome1 [1031]
$

I don't see the find command I gave you.  It is not in the $ORACLE_HOME directory, it is in one of the sub directories.

oh I see it now.  below is what I got from the bdump dir
  control_files= /opt/oracle/oradata/orastd/control01.ctl, /opt/orac
le/oradata/orastd/control02.ctl, /opt/oracle/oradata/orastd/control03.ctl
  db_block_buffers= 8192
  db_block_size= 4096
  compatible= 8.1.0
  log_buffer= 12288
  log_checkpoint_interval  = 10000
  log_checkpoint_timeout   = 1800
  transactions_per_rollback_segment= 2
  rollback_segments= RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6, RBS10, RB
S11, RBS12, RBS13
  max_enabled_roles= 30
  remote_login_passwordfile= EXCLUSIVE
  instance_name= orastd
  service_names= orastd
  sort_area_size= 327680
  sort_area_retained_size  = 327680
  db_name= orastd
  open_cursors= 100
  os_authent_prefix=
  job_queue_processes= 1
  background_dump_dest     = /opt/oracle/OraHome1/admin/orastd/bdump
  user_dump_dest= /opt/oracle/OraHome1/admin/orastd/udump
  core_dump_dest= /opt/oracle/OraHome1/admin/orastd/cdump
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
Tue Jun 17 01:33:48 2008
ALTER DATABASE  orastd MOUNT
***
Corrupt block relative dba: 0x00000003 file=0. blocknum=3.
Fractured block found during controlfile block read
Data in bad block - type:0. format:0. rdba:0x00000000
last change scn:0x0000.00000000 seq:0x0 flg:0x00
consistancy value in tail 0x00000000
check value in block header: 0x0, check value not calculated
spare1:0x0, spare2:0x0, spare2:0x0
LGWR: terminating instance due to error 227
Instance terminated by LGWR, pid = 5574

That's not good...  
Corrupt block relative dba: 0x00000003 file=0. blocknum=3.
Fractured block found during controlfile block read
Data in bad block - type:0. format:0. rdba:0x00000000

those were not the words I wanted to hear.  I wanted to hear oh that's a simple fix.

So do you know how to fix it?