|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
OpenBSD quit booting
As the tile says. This is OpneBSD 6.3. The screen shows:
Code:
Loading . . . . . . probing: pc0 mem[630k 3061M 1024M a20=on] disk: hd0+ >> OpenBSD/amd64 BOOT 3.34 boot> booting hda0:/bsd [several numbers separated by + I cannot read so quickly] entry point at 0x1000158 I can boot /bsd.rd Any help would be appreciated. Kindest regards, M Last edited by ocicat; 24th May 2018 at 09:54 PM. Reason: Please use [code] & [/code] tags when posting console output. |
|
||||
Quote:
There really is not enough details to guess at this.
__________________
My best friends are parrots |
|
||||
Posting a follow-up to be sure these are conducted in the least disruptive order.
|
|
|||
Hi GarryR,
first, thank you for a reply. Since I can boot both /bsd.rd and /bsd.sp, see my response to jggimi below, I can certainly post the dmesg. However, before I pollute the thread, what is to be gained? Since the system boots, there should be no anomaly there, should it? Hi jggimi, thank you for the reply. The system does boot both /bsd.rd and /bsd.sp, but does not boot /bsd.booted and/or /bsd, with the same symptoms as described in my first post. Likewise, /bsd.mp does not boot with message: "No such file or directory". And, indeed, the file is not present, although I would think that such file should be present because the CPU is a two-core unit (T2370). Or is the /bsd really a copy of /bsd.mp? So, what do I do now? Kindest regards, M |
|
||||
The kernel file /bsd is the default kernel, and will either be GENERIC or GENERIC.MP, depending on the number of cpu(4) devices discovered during installation.
Quote:
If you copy the appropriate bsd.mp file into your root directory as /bsd, it will be the default kernel loaded at boot time. If that GENERIC.MP kernel boots, you will know that the problem was caused by a local problem with your kernel files, and is not a problem with your hardware. If you were running -release plus binary patches obtained through the syspatch(8) utility, I recomend reverting all patches (-R) then reinstalling them to be sure you have a correctly patched kernel. |
|
|||
Hi jggimi,
thank you for your help. I have downloaded the bsd.mp, then: Code:
syspatch -R Code:
rm bsd.booted rm bsd mv bsd.mp bsd Code:
syspatch I cannot find any source how to re-create the file. Any more help, please? Kindest regards, M |
|
|||
O.K., I am officially an idiot:
Code:
sha256 -h /var/db/kernel.SHA256 /bsd There is still a question - is there a way to find out what caused the problem? Kindest regards, M |
|
|||
Hi jggimi,
The idiot comment was in regards to the kernel.SHA256 issue. Not that there are no other reasons. And, you are, of course, correct again. I looked through the /var/log/messages and, indeed, the re-link failure was what cause the boot to abort. The kernel.SHA256 file still existed, but was corrupted to make its size 0. Once again, thank you. Kindest regards, M |
|
||||
I'll guess that you may have powered down while the relinking process was still in progress. But that is not necessarily idiotic. Discovering the hash failure and recreating (or deleting) the hash file is the hallmark of an astute, self-supporting admin.
You owe yourself a beer. |
|
|||
Hi jggimi,
Well, studying the /var/log/messages, the re-link failed, then the system issued reboot and so on. It really is a mystery. With all due respect, I would have never figured it out without your help/hints, so if someone is owed a beer, it is you. Kindest regards, M |
|
|||
Quote:
Many threads on these forums would be solved more quickly is the original poster would provide dmesg(8) output at the very beginning. |
|
|||
Hi ocicat, jggimi,
if I understand correctly, the dmesg, does not necessarily identify the problem, but provides information helpful for troubleshooting, correct? How do you make the dmesg(8) point to the man page? Kindest regards, M |
|
|||
Quote:
Quote:
|
|
|||
Hi ocicat,
thank you. Kindest regards, M |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to guarantee booting without manual intervention on an OpenBSD router | mamalos | OpenBSD General | 11 | 29th January 2016 03:05 PM |
OpenBSD Native EFI booting coming to OpenBSD | ocicat | News | 10 | 17th September 2015 01:25 PM |
Dual booting encrypted OpenBSD with Windows | e1-531g | OpenBSD General | 2 | 16th August 2015 02:06 PM |
dual booting OpenBSD and NetBSD | daemonfowl | NetBSD Installation and Upgrading | 1 | 21st February 2012 01:06 PM |
Beep or visual signal after booting OpenBSD/sparc64 | hansivers | OpenBSD General | 10 | 20th September 2009 04:08 PM |