DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Installation and Upgrading

OpenBSD Installation and Upgrading Installing and upgrading OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 8th September 2021
SimpL SimpL is offline
Port Guard
 
Join Date: Nov 2020
Location: On a cloud;)
Posts: 31
Question Openbsd upgrade 6.6->6.7 first startup error

Hello all!

I have a little problem with an upgrade. I made a sysupgrade from 6.6->6.7.
I did this a few times already (followed the guidelines written in the upgrade page on openbsd.org) and it was always a success.
But on one machine I got the following after running the upgrade from OpenBSD 6.6 to 6.7.
The upgrade was ok but after the restart it writes:
---------------
root on sd0a (1bc.....532.a) swap on sd0b dump on sd0b
swapctl: 1bc......532.b: no such file or directory
Auto boot .... starting system checks.
Can't open 1bc.....532.a: No such file or directory
CAN'T CHECK FILE SYSTEM.
1bc.....532.a: UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY.
Automatic file system check failed: help!
------------
After this I log into shell and try to fix the problem.fsck_ffs

Checked /etc/fstab:
1bc.....532.b none swap sw
1bc.....532.a / ffs rw,wxallowed 1 1

in /dev:
sd0l sd0m sd0n sd0o sd0p

I can see the system as "root_device" now with "df" mounted on / with only read rights (I think this is default and ok.)

I dont know what should I write for fsck_ffs to check. sd0a, sd0b does not exist, tried sd0l-p, no good either. The writen (1bc......532.a, 1bc......532.b) I could not find anywhere, -p is not enough and fsck_ffs waits for a /dev/**** to check as far as i can tell, but correct me if im wrong.

The operating system is OpenBSD 6.7 for sure, upgrade was ok.

I searched for fsck_ffs and i found a few pages that contained helpful info
but sadly I could not find anything that worked.

If anyone has any solutions ideas are all welcome
Thy in advance

Last edited by SimpL; 8th September 2021 at 12:41 PM.
Reply With Quote
  #2   (View Single Post)  
Old 9th September 2021
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,353
Default

Quote:
Originally Posted by SimpL View Post
in /dev:
sd0l sd0m sd0n sd0o sd0p
If this problem description is accurate, then you are missing special device files /dev/sd0a through /dev/sd0k. Other special device files may also be missing.

You could try the following to recreate these missing device files: These instructions assume only that /dev has been damaged, and that you still have a functional disklabel with a readable "a" partition.
  1. Reboot into the RAMDISK kernel, bsd.rd, in order to have a self-contained working rescue system. At the "boot>" prompt, type "bsd.rd".
  2. At the "(I)nstall, (U)pgrade, (A)utoinstall, or (S)hell" prompt, choose the shell.
  3. Mount your sd0a partition, with # mount /dev/sd0a /mnt.
  4. Change to the dev/ folder in the sd0a partition with # cd /mnt/dev.
  5. Recreate all special device files with # sh MAKEDEV all.
Reboot, and see if your 6.7 system starts correctly.
Reply With Quote
  #3   (View Single Post)  
Old 9th September 2021
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,353
Default

One more item of note. The 6.6->6.7 Upgrade Guide stated:
  • Check diskspace of /usr. Verify that the /usr partition has a size of at least 1.1G. With less space the upgrade may fail and you should consider reinstalling the system instead.
Please be sure /usr has sufficient freespace for this upgrade. If it does, re-run the 6.7 upgrade again to ensure it completes correctly.
Reply With Quote
  #4   (View Single Post)  
Old 9th September 2021
jmccue jmccue is offline
Real Name: John McCue
Shell Scout
 
Join Date: Aug 2012
Location: here
Posts: 86
Default

I do not know your situation, but with either 6.9 or 6.8, OpenBSD File System now defaults to ffs2. That gives you a 2038 compliant File System.

If /usr space mentioned by jggimi is an issue for you, you may want to consider doing a full install of 6.9 to move to ffs2.

EDIT: was curious, did a search, looks like 6.7 the default changed undeadly.org/

Last edited by jmccue; 9th September 2021 at 07:39 PM. Reason: grammer
Reply With Quote
  #5   (View Single Post)  
Old 13th September 2021
SimpL SimpL is offline
Port Guard
 
Join Date: Nov 2020
Location: On a cloud;)
Posts: 31
Default

Quote:
Originally Posted by jggimi View Post
One more item of note. The 6.6->6.7 Upgrade Guide stated:
  • Check diskspace of /usr. Verify that the /usr partition has a size of at least 1.1G. With less space the upgrade may fail and you should consider reinstalling the system instead.
Please be sure /usr has sufficient freespace for this upgrade. If it does, re-run the 6.7 upgrade again to ensure it completes correctly.
The whole partition is under / and its 10gb there is 7 gigs of space left so i think its not a space issue. Ill try your previous post suggestion, and get back to you if it's successfull.
Reply With Quote
  #6   (View Single Post)  
Old 13th September 2021
SimpL SimpL is offline
Port Guard
 
Join Date: Nov 2020
Location: On a cloud;)
Posts: 31
Thumbs up

Quote:
Originally Posted by jggimi View Post
If this problem description is accurate, then you are missing special device files /dev/sd0a through /dev/sd0k. Other special device files may also be missing.

You could try the following to recreate these missing device files: These instructions assume only that /dev has been damaged, and that you still have a functional disklabel with a readable "a" partition.
  1. Reboot into the RAMDISK kernel, bsd.rd, in order to have a self-contained working rescue system. At the "boot>" prompt, type "bsd.rd".
  2. At the "(I)nstall, (U)pgrade, (A)utoinstall, or (S)hell" prompt, choose the shell.
  3. Mount your sd0a partition, with # mount /dev/sd0a /mnt.
  4. Change to the dev/ folder in the sd0a partition with # cd /mnt/dev.
  5. Recreate all special device files with # sh MAKEDEV all.
Reboot, and see if your 6.7 system starts correctly.
Thank you for the answer.
I could start bsd.rd and tried to make the mount, but it was not successful....
mount /dev/sd0a /mnt[/cmd no such file or directory.
In dev I got multiple things but no sd0 anything after ram drive starts.
I got:
cd0a,c
fd0a,b,c,i
rcd0a,c
rd0a,c
rfd0a,b,c,i
rrd0a,c
rwd0a-p
wd0a-p

I thought that its wd0a-p but all I got was no such file/dir or cant open if I tried it with fsck_ffs and mount.

Tried rd0a and rd0c. With rd0a fsck would not run, and rd0c was "/" last (fsck_ffs ran and wrote this...) so I ran fsck_ffs /dev/rd0c I pressed y to clean it. Everything ok and restarted. Did not work. Same error same screen.

Reboot-> bsd.rd -> cd /dev -> ls -> I found there is MAKEDEV, so because i could not run it with the mount commands took a chance and run it from /dev -> failed, wrote that it could not do everything and failed.
Wrote "ls" again AND saw that there is and sd0a!!!! So after that I could make the mount, and the commands you wrote jggimi, ran MAKEDEV from the mounted /mnt/dev, (success) and made a restart.

WEEEEELLLLL..... It WORKED!

Im currently running pkg_add -u && syspatch so that the 6.7 would be up to date and will restart and after that ill try to run the sysupgrade to 6.8, hope that it will clean itself after the patches.

Thank you very much jggimi! and jmccue.


Not 100% sure if the fsck_ffs did anything......


update got a message to the terminal:
reorder_kernel: failed -- see: /usr/share/relink/kernel/GENERIC/relink.log

cat /usr/share/relink/kernel/GENERIC/relink.log:
(SHA256) /bsd: FAILED

Failed to verify /bsd's checksum, therefore a randomly linked kernel (KARL)
is not being built. KARL can be re-enabled for next boot by issuing as root:

sha256 -h /var/db/kernel.SHA256 /bsd

The syspatch could not relink kernel so i ran it manualy:
/usr/libexec/reorder_kernel -> reboot
Kernel still failed.
sha256 -h /var/db/kernel.SHA256 /bsd
reboot
Kernel AOK! 6.7 stable and updated.

Last edited by SimpL; 13th September 2021 at 01:38 PM.
Reply With Quote
  #7   (View Single Post)  
Old 13th September 2021
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,353
Default

I wouldn't worry about kernel relinking at this point. The failure could have been due to an early reboot while relinking was still in progress, as it runs in the background. Once you are fully upgraded and running, if the problem recurs you can look to corrective actions at that time.
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
Boot error ERR M after snapshot upgrade acampbell OpenBSD Installation and Upgrading 19 24th September 2016 09:17 PM
Apache2 on startup OpenBsd 5.6 morophla OpenBSD Packages and Ports 2 21st April 2015 03:39 AM
post-upgrade error | library pthread.13.3 not found daemonfowl OpenBSD Installation and Upgrading 6 29th March 2012 04:31 PM
upgrade installworld error carpman FreeBSD Installation and Upgrading 11 8th February 2009 05:36 PM
freebsd 7.1 upgrade buildworld error map7 FreeBSD Installation and Upgrading 9 30th October 2008 06:54 PM


All times are GMT. The time now is 09:51 AM.


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