DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
Old 30th December 2014
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 6,241
Default

Quote:
Originally Posted by hulten View Post
Is it fine to boot from the official installation medium (5.6 release), do a clean install and select the software sets from http, pointing to the snapshot (same url as above)? Or should I expect the installation software (5.6 release) to be incompatible with newer software sets (snapshot 2014-12-27)?
You must always use a matching RAMDISK kernel for the system you are upgrading to or installing. From downloading and booting the newer bsd.rd or booting installation media, per your preference. This is because not only do the filesets have different signatures, the install and upgrade scripts change during development. And between 5.6-release and -current as of today the collection of filesets has also changed. (The etc56.tgz and xetc56.tgz filesets are no longer shipped as filesets, they are embedded, and during upgrade are unpacked during your post-upgrade sysmerge(8) step.)
Quote:
Originally Posted by Carpetsmoker View Post
I have :-)
I only use the tests during burn-in or when a problem indicative of hardware appears. That may be why I have not seen false positives.
Reply With Quote
Old 30th December 2014
ibara's Avatar
ibara ibara is offline
GNU gold linker
 
Join Date: Jan 2014
Posts: 566
Default

Quote:
Originally Posted by jggimi View Post
This is because not only do the filesets have different signatures
Signify actually takes care of this one; that is now only historically (pre-signify) true.
The rest of what you said is valid though.
Reply With Quote
Old 30th December 2014
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 6,241
Default

Thanks for the correction, ibara. This also gives me the opportunity to answer another question.
Quote:
Originally Posted by hulten View Post
However, it gives an "ERR M" ...
This is an error issued by the first stage bootloader. It did not point to a valid second stage bootloader -- the ERR M signifies the second stage bootloader location does not have a valid magic number. Quoting FAQ 14:
Quote:
This generally means whatever it was that was read in was NOT /boot, usually meaning installboot(8) was run incorrectly, the /boot file was altered, or you have exceeded your BIOS's ability to read a large disk.
Reply With Quote
Old 31st December 2014
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 801
Default

Quote:
Originally Posted by hulten View Post
I looked carefully at all capacitors, but they all look like nice cylinders without any bulging or leakage.
I'm glad those look good. But, given that both Linux and OpenBSD are crashing (and given the age of the machine) my sense is that the chances that this is due to hardware failing are probably > 50%. If it's not the capacitiors, it could be any other component on the motherboard, or a bad connection, or failing voltage regulation in the power supply, or ... .

If it were my machine (and it's not ...) I would be checking for crashes under any other OS I could conveniently boot on it, including DOS, and even just flipping around in the BIOS setup program and waiting for a crash. With each new software environment under which you can reproduce a crash, the case against the hardware becomes that much stronger.
Reply With Quote
Old 2nd January 2015
hulten hulten is offline
Port Guard
 
Join Date: Dec 2014
Posts: 25
Post problem reported

I have done an official/consistent install through two USB sticks, one with floppy56.fs (that had no support for my network interface) and one with an FFS file system. This circumvented the "ERR M" problem (apparently my BIOS cannot handle large disks). While it took some effort to figure out, a nice side effect is that I now know much more about the boot process and disk partitioning.

IdOp is right that I could do some sensible Bayesian updating on whether it is hardware failure or not by means of more testing. However, I do not have local access to the computer for several months from next Sunday, and I think that it may be useful that some OpenBSD hacker has a look at it at this point, so I did a bug report:

http://marc.info/?l=openbsd-bugs&m=142023435825321&w=2

(Strange thing on marc.info is that sometimes the message cannot be found; refreshing a few times works.)
Reply With Quote
Old 3rd January 2015
shep shep is offline
Rc.conf Instructor
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,129
Default

Quote:
(Strange thing on marc.info is that sometimes the message cannot be found; refreshing a few times works.)
I think marc.info has a slight hang over for the new year. The Nabble mirror appears to be intact
http://openbsd.7691.n7.nabble.com/op...r-misc-f3.html
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
bwi0 on Powerbook G4 crashes tsarpal OpenBSD General 3 23rd February 2013 02:40 AM
sparcstation 20 cgfourteen crashes darf NetBSD General 7 11th March 2010 05:06 AM
FreeBSD 7.0 with SSD Crashes map7 FreeBSD General 4 5th February 2009 10:08 PM
net-im/sim-im* crashes blackbox TerryP FreeBSD Ports and Packages 0 28th September 2008 08:29 AM
Akregator crashes map7 FreeBSD Ports and Packages 2 13th July 2008 11:22 PM


All times are GMT. The time now is 12:55 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick