Overvolted by psu; now how to get logs?

[senselessfull]

So I overvolted my pi accidentally (8+V in) and it seems to have crashed a lot of things but the actual pi did survive.
I have no output on the hdmi nor can i access it via ssh, sadly.
BUT, it boots up and all the LEDs blink and it seems to work.
Is there a way i could let it boot and then view the logs to see what happened?
I tried chrooting already but I don't have another armv6h device and it doesn't seem to work without that.

Hopefully you can point me into the right direction.

[WarheadsSE]

It has a serial port.

[senselessfull]

Yeah, I should have thought before I posted here.
Problem was, I tried to use the serialport output but it didn't output much usable.
Somehow the powersurge destroyed part of my original arch-installation and when I tried a new raspbian(and later arch) it worked fine, just headless.
Hdmi seems to be busted but that's just a minor inconvenience.
Thread for my troubleshooting and explaining of polyfuses is here:

http://www.raspberrypi.org/forums/viewtopic.php?f=28&t=79518&p=564115

[sdjf]

If nothing else works, you could always poweroff safely and then put your SD card into another Linux box and view the logs in /var/log from there. I had to do that all the time when I first was getting my Pi set up, and was running headless and having trouble getting ssh set up.

[senselessfull]

I did that but my logs were just binary scramble and nothing usefull.
Or is there a programm I'd need to use for that?

[sdjf]

Sounds like you do not have regular logs enabled, I have lots of logs in /var/log that are totally readable text files. If you do not have an everything.log and a kernel.log (for example) then your system was not set up to run those. I am running a system based on a year old image, never could get logs running properly when I tried to use the newer images.

Look up how to enable logs and get them running if you do not see those files.

[moonman]

Journald in systemd logs to binary files. You can enable syslog-ng if you want: https://wiki.archlinux.org/index.php/sy ... ith_syslog

[crashmaster]

The SoC has a lot of circuits and at least hdmi seems to be destroyed. Although it boots up well but you never know what has been (partially) damaged in the chip. I think it's not only a simple "good or bad" question, everything is possible, it's like the chance of a gambler
I would keep that in eyes and a log can't tell you such hardware details. Better to buy a new one if you run important applications.

Regards, mmi