On Tue, Apr 7, 2009 at 10:42, Stefan Sperling <stsp@stsp.name> wrote:
quoted text
> On Tue, Apr 07, 2009 at 01:36:21AM +0000, Bryan wrote:
>> Okay I did exactly as your e-mail suggested. B I started the box, put
>> the blu-ray in, and issued a ctrl-alt-esc, and went to ddb>, typed
>> "continue", and then ssh'ed into the box from antoher system.
>>
>> From the SSH session, I attempted to mount the disc. B "mount /dev/cd0c
>> /cdrom", and.... B nothing... B no output on the screen, and my ssh
>> session is dead. B nothing on the screen, just a blinking cursor...
>
> Can you get a disklabel from the thing?
>
> B  B  B  B disklabel cd0
>
> Note that 'c' means "entire disk". Can you try e.g. /dev/cd0a if that
> exists in disklabel?
>

"disklabel cd0" hangs on the SSH session with no output...


quoted text
>> Here's the output:
>>
>> #Stopped at B  B  Debugger+0x4: B  B  leave
>> ddb> continue
>> *blinking cursor*
>
> So the cursor still blinks even though the system does not respond
> to keystrokes and network I/O?
>

okay, I can pop back out to the ddb> prompt if I ctrl-alt-esc again,
but nothing is
happening when I type "continue", it goes back to the blinking cursor.  No
messages, but I did take a screenshot of "ps" and "trace".  By the way, the
"hangman" feature is interesting...

I uploaded them here...
http://picasaweb.google.com/brakeb/31MarchOpenBSDIssue?feat=directlink

trace_2.jpg is much the same as trace_1, but there are 2 lines at the
bottom that I thought would be important.

I did do a boot dump, and after I rebooted, I went into that "gdb"
that was talked about in crash(8),
did a "file /var/crash/bsd.0", and then "where"

It said "No stack."

quoted text
>> at this point, I have to hit the power button for 4 secs to poweroff
>
> What happens if you try to break into the debugger again at this point?
>
>> Now, I've been looking through my BIOS settings, and there appears to
>> be a setting for SATA with three choices IDE, RAID, and AHCI. B The HP
>> guys appear to have set it to "AHCI". B This is probably where everyone
>> facepalms, but if I set that to "IDE" would I fix this issue?
>
> Who knows? Only you can find out. Try all possible settings.

I attempted to set SATA to "IDE", but I get a blue screen when trying
to boot the
vista portion, and the following from OpenBSD:

WARNING: / was not properly unmounted
Automatic boot in progress: starting file system checks.
Can't open /dev/rsd0a: No medium found
CAN'T CHECK FILE SYSTEM.
/dev/rsd0a: UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY.
Automatic file system check failed: help!
Enter pathname of shell or RETURN for sh:*blinking cursor*

I actually got this error on a laptop that had the "AHCI" and "IDE"
options for it's SATA connection.
Once I changed it back to "AHCI" everything boots and file system
check work as intended.


What gets me about the disc issue, is that running commands on the
drive should show some kind of activity.
Blinking lights, spinning up of the disc, etc...  not this...  I get
three or four blinks from the indicator light on the drive,
and then....  nothing....  I assume it reads something quite quickly,
then gags...


I have an 8GB SD card laying around here, I'll boot install OpenBSD
with the IDE setting set in the BIOS,
and PXEBOOT install from my server, and see if that makes a difference...

Thanks
Bryan