FreeLists / openbeos / [openbeos] - actually: [off-topic] and [selfish]

[Jared <jared@xxxxxx>]

i hate to do this - but i'm posting a self-important SOS "please help" 
sort of thing today.  *sigh*  and i was always secretly proud of being 
idealistic and keeping my posts on-topic (few as they may be)

the last thing i did was to copy the WAV folder from an audio CD to my 
Desktop.  Tracker crashed about 650MB into it.  the CD was prone to 
skipping and causing the drive to stutter and pause, so i wasn't 
surprised.  but when the machine locked up and i had to reboot....well, 
i am now surprised.

bootman comes up and waits his 5 seconds, clears the screen and leaves 
me with just:  Loading BeOS R5.  Error loading OS; press any key to reboot.

so i've booted off the R5 pro cd and ran chkbfs -f
it 'fixed' several hundred thousand lost clusters (i forget what 
nomenclature was used there...but lost clusters they were)

it now runs "clean" through chkbfs, but nonetheless i can see this error 
above the "no errors" satement:
Failed to load (NULL)/beos (ino # 1049569)
Files processed: 11650read_vnode : (bi @ 0x805ef008 104972) 
betree==NULL??!? (thid 261)

so, a point of clarification, i'm boned, right?  does "bi" mean i have a 
bad spot on the drive or something?  Axel? (wink wink - nudge nudge - 
say no more say no more) i remember you boasting bout your bfs tools.... 
if i get my hands on another blank drive and install BeOS on it (or Zeta 
when it arrives) you think maybe i'll get back my old install?  or 
should i just break down and sob now?

anyways, there are a number of other chkbfs erors reported concerning 
data in other places, but this seemed to be the only one that would be 
critical to loading the OS (yup, can't find an OS to load).

thanks for putting up with me - hopefully someone has some nice light to 
shine on this.
-jared