Opened 2 years ago

Closed 20 months ago

#716 closed Feature Request (fixed)

System won't boot after security update April 2013

Reported by: rrking Owned by:
Priority: blocker Milestone:
Component: System Configuration Version: 9.1-RELEASE
Keywords: Cc: trac-bugs@…


System update recommended a security update yesterday. My system would not boot this morning. I installed PCBSD 9.1 onto a different hard disk this morning, accepted all updates (including the security update), and the system wouldn't reboot (or, more precisely, reboots as described below).
The BTX loader does its job, but the computer reboots at the end of the BTX loader sequence (displaying the power on screen and then booting again), suggesting that the kernel is no longer bootable. This happens quickly enough that I can't see what the last messages are.
The computer is an old Compaq model with a Sempron processor, and 1.25 GB memory. I am using the i386 version of PCBSD 9.1.

Change History (8)

comment:1 Changed 2 years ago by rrking

This appears to be a FreeBSD problem, rather than a PCBSD problem. Applying freebsd-update (per the instructions on their website with respect to the openssl security problem) yields the same non-bootable system.

comment:2 Changed 2 years ago by delphij


Is it possible for you to check if the updated loader have a MD5 of e4d8fc3ee7b5d91e6c6d6b80ad7ff6b4? We don't seem to be able to reproduce this in virtual box environment here.

Thanks in advance!

comment:3 Changed 2 years ago by rrking

Could you give me the full path name of the file in question? (Or, if this is a temporarily downloaded file, commands for fetching the file?)

comment:4 Changed 2 years ago by delphij

If you have a copy of bad loader:

md5 /boot/loader.bad

comment:5 Changed 2 years ago by rrking

I am getting a different md5:
[rrking@pcbsd-6573] /boot% md5 loader
MD5 (loader) = 272912f2503f32b62ab555f30f8ab3a9

The md5 is the same whether I use PCBSD's update manager, or using freebsd-update. Just to reiterate, this machine is running the x86 version (not x86_64).

comment:6 Changed 2 years ago by kris

We found the issue. Will have an online update coming out shortly to fix it :)

comment:7 Changed 20 months ago by joshms

This issue has been completely resolved now in our latest release.



comment:8 Changed 20 months ago by joshms

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.