|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
||||
Here's the 'trace':
Code:
ddb> trace Debugger(d03b7b10,d3530008,d353af1c,cfbfdff1,0) at Debugger+0x4 panic(d037bffa,d037bfba,16,0,0) at panic+0x55 start_init(d27be000) at start_init+0x16d Bad frame pointer: 0xd044ced8 ddb> Code:
ddb> ps PID PPID PGRP UID S FLAGS WAIT COMMAND 13 0 0 0 3 0x100200 bored crypto 12 0 0 0 3 0x100200 aiodoned aiodoned 11 0 0 0 3 0x100200 syncer update 10 0 0 0 2 0x100200 cleaner 9 0 0 0 3 0x100200 reaper reaper 8 0 0 0 3 0x100200 pgdaemon pagedaemon 7 0 0 0 3 0x100200 pftm pfpurge 6 0 0 0 3 0x100200 cardslotev cardslot1 5 0 0 0 3 0x100200 cardslotev cardslot0 4 0 0 0 3 0x100200 bored syswq 3 0 0 0 3 0x100200 idle0 2 0 0 0 3 0x100200 kmalloc kmthread * 1 0 0 0 7 0 swapper 0 -1 0 0 3 0x80200 scheduler swapper ddb> |
|
|||
The error is kind of obvious.. read it.. process it...
Code:
filesystem type 8 not known.. assuming ffs warning: /dev/console error 22 exec /sbin/init: error 22 exec /sbin/oinit: error 22 exec /sbin/init.bak: error 22 init: not found panic: no init Stopped at Debugger+0x4: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> Take this as an opportunity to install 4.4, a fresh installation is always fun. |
|
|||
There are no OpenBSD developers here who could diagnose the dbd output that. you provided. But even then it would be difficult because you using a custom kernel
I would suggest to get a bigger >512 CF card. That way you can do a normal install. Installing using a 'bsd.rd' installation kernel would now be the easiest way. At least if the filesystem isn't too corrupted
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
That particular panic happens whenever the kernel can be located by the bootloader, but the kernel cannot locate /sbin/init for any reason, such as a missing "a" partition.
To recreate, delete your "a" partition from your disklabel, reboot, and give the bootloader the location of a kernel residing on another partition. The kernel will look for the "a" partition, not find it, and panic. |
|
|||
Quote:
Here is a 512 layout: Filesystem Size Used Avail Capacity Mounted on /dev/wd0a 97.8M 28.1M 64.9M 30% / /dev/wd0d 23.7M 2.0K 22.5M 0% /tmp /dev/wd0e 195M 151M 33.6M 82% /usr /dev/wd0f 98.3M 6.3M 87.1M 7% /var You do not need swap or X or games or compilers but I ALWAYS leave the manpages on. In any case look at how little space is actually used. This was not optomised because there was plenty to spare once 256MB cards became scarcer and the newer bigger ones are faster and have more wear levelling space. We now use 2GB cards and have miles of spare space... |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Soekris experiences | Carpetsmoker | General Hardware | 42 | 21st August 2009 01:52 PM |
Soekris Help | revzalot | General Hardware | 2 | 27th August 2008 01:35 PM |