I just upgraded 12-p1 to 13 and lost everything (almost?)

userxbw

userxbw

I upgraded to 13 reboot. lost xwindows logged in user finished updating reboot lost root and user login so now I'm sitting in Linux writing this what to do? how to fix it?
 
You can always drop into the bootloader, if not possible boot with a freebsd-iso and fix the problem.
If needed perform a fsck, if needed reinstall bootcode, check if you can chroot , mount filesystems, change root password, etc...
 
Alain De Vos said:
You can always drop into the bootloader, if not possible boot with a freebsd-iso and fix the problem.
If needed perform a fsck, if needed reinstall bootcode, check if you can chroot , mount filesystems, change root password, etc...
Click to expand...
I've been away from linux and freeBSD for three years. I'm basically almost brain dead on commands. but thanks it's a start

it boots .. so how to change root passwd? whats the install root passwd , did does it have a defualt passed? (memory is gone, got to relearn a lot of this stuff)


I suppose that is still valid.
  1. Power on your machine.
  2. At the BSD bootloader press 2 to “Boot Single User”
  3. The system will boot up to a administrative root shell without asking for a password.
  4. Type “mount -u /”
  5. Type “passwd root”
  6. Enter your new password and confirm.
  7. Reboot your machine.
 
userxbw said:
I upgraded to 13 reboot.
Click to expand...
First reboot? Only ran freebsd-update install once? Finish the upgrade. Also make sure to update all your installed packages/ports when indicated (after the second freebsd-update install).
 
SirDice said:
First reboot? Only ran freebsd-update install once? Finish the upgrade. Also make sure to update all your installed packages/ports when indicated (after the second freebsd-update install).
Click to expand...
i ran update reboot, lost x org so from the CLI I ran update again to finish it, rebooted the 2nd time came back and then lost user and root login. I just booted into single user had to run fsck fix the errors to the hdd, then mount -u / passwd root it did passwd twice reboot inbetween , and still do not have root or user login . it is just stuck at the login prompt

how's your day going...
 
userxbw said:
I ran update again to finish it
Click to expand...
What exactly did you run?

userxbw said:
I just booted into single user and mount -u / passwd root twice
Click to expand...
Ok, maybe something went wrong with the merging of some new accounts that needed to be added. Boot to single user mode again, double check you actually have UFS, mount -a to mount everything. Edit /boot/loader.conf and /etc/rc.conf and disable everything you don't need to boot the machine. You don't want to boot straight to X, stick to the console until you've finished/fixed the upgrade.
 
SirDice said:
What exactly did you run?


Ok, maybe something went wrong with the merging of some new accounts that needed to be added. Boot to single user mode again, double check you actually have UFS, mount -a to mount everything. Edit /boot/loader.conf and /etc/rc.conf and disable everything you don't need to boot the machine. You don't want to boot straight to X, stick to the console until you've finished/fixed the upgrade.
Click to expand...
I ran freebsd-upgrade install
and okay? hope my memory comes back its been 3 years since I deal with any of this stuff.
 
userxbw said:
I ran freebsd-upgrade install
Click to expand...
Ok, that's good. The reason I asked is that I've seen people do freebsd-update fetch in an attempt to "fix" things. DO NOT DO THAT. It's going to royally screw up things even more.

userxbw said:
hope my memory comes back its been 3 years since I deal with any of this stuff.
Click to expand...
It's like riding a bike. You might be a bit wobbly at first but it'll all come flooding back soon enough ;)
 
SirDice said:
Ok, that's good. The reason I asked is that I've seen people do freebsd-update fetch in an attempt to "fix" things. DO NOT DO THAT. It's going to royally screw up things even more.


It's like riding a bike. You might be a bit wobbly at first but it'll all come flooding back soon enough ;)
Click to expand...
yeah, at mulit user login. it says libncurses.so.8 missing required by bash

on single user, which I have no experice on whatsoever. it shows me in root home on ls . so can i run commands like that or is there a special set before hand, if so how to?
 
boot single user mode.
Mount the filesystem.
go to /etc/passwd
Check the login shell of root.
If it is bash change to sh, that has no dependencies on ncurses. So it always works.
 
Alain De Vos said:
boot single user mode.
Mount the filesystem.
go to /etc/passwd
Check the login shell of root.
If it is bash change to sh, that has no dependencies on ncurses. So it always works.
Click to expand...
how tos
chsh -s /usr/local/bin/bash

so i'd be
chsh -s /usr/local/sh
 
Alain De Vos said:
Or you can edit the password file with vipw
The shell is
Code: 
/bin/sh
Click to expand...
Yeah I figured that out, but the passwd
root:*:0:0: Charlie &:/root:/bin/sh
Charlie isn't my password
Mod

Okay I'm in root account with access to the internet.

Version check
13.0 release p13

Entry inconsistent
Error service module
Pam sm chauttok pw copy failed for user passwd change ³
 
Alain De Vos said:
if you have internet:
Code: 
pkg update -f
pkg upgrade
Click to expand...
Newer freebsd version zziplib Package 1301000
Running kernel 3000139
Repo freebsd wrong os version package for freebsd 13


So should I just be ignoring everything and see what happens
Mod
I just seen
Major os version upgrade detected run pkg bootstrap -frrecommended I'll do that instead
 
userxbw said:
root:*:0:0: Charlie &:/root:/bin/sh
Charlie isn't my password
Click to expand...
That's not the password. That's just the gecos field of root. Which, by default, says "Charlie root" (the & is a placeholder for the user's account name). Passwords aren't stored in /etc/passwd. Actually, your user account isn't actually stored there either.
userxbw said:
I just seen
Major os version upgrade detected run pkg bootstrap -frrecommended I'll do that instead
Click to expand...
Yes.
pkg bootstrap -f followed by pkg upgrade. Once that's finished run freebsd-upgrade install for a third and final time. This will clean up old libraries and other files.
 
SirDice said:
That's not the password. That's just the gecos field of root. Which, by default, says "Charlie root" (the & is a placeholder for the user's account name). Passwords aren't stored in /etc/passwd. Actually, your user account isn't actually stored there either.

Yes.
pkg bootstrap -f followed by pkg upgrade. Once that's finished run freebsd-upgrade install for a third and final time. This will clean up old libraries and other files.
Click to expand...
After upgrade, it did what I thought it would, took off and came back and it stops with a y/n question.

Anyways,
3 GB MORE space yes no, yes
Reinstalling freetype 100%
Pkg libglvnd 1.4.0_2 conflicts with mesa libs 18.3.2._4 installs files into the same place. Problematic file/usr/local/include/EGL/EGL.h
Stopped

Reboot
Pkg update -f
Ran until
Creating Pulse
? Pulse rt
Creating user pulse uid 563
User pulse disappeared during update

pre install script failed

Stop

Fixed it, found something on Google.

freebsd-upgrade install
Not found
.. the days not over yet
 
Right, it's obviously been a while since your last update. Just pkg delete -f mesa-libs nvidia-driver and start pkg upgrade again. Are you actually using an NVidia card? Depending on the card model you may need to switch to x11/nvidia-driver-470 or x11/nvidia-driver-390. The latest NVidia driver dropped support for a number of older cards.

Code: 
20210617:
  AFFECTS: users of graphics/mesa-libs and x11/nvidia-driver
  AUTHOR: kbowling@FreeBSD.org

  Some libraries from mesa-libs are now provided by libglvnd while
  others were renamed. nvidia-driver already used libglvnd but bundled
  a copy which is now provided as a separate package. When building
  outside poudriere make sure to remove mesa-libs and nvidia-driver
  first in order to avoid conflict with libglvnd.

  For portmaster users:
  # pkg delete -f mesa-libs nvidia-driver
  # portmaster -a

  For portupgrade users:
  # pkg delete -f mesa-libs nvidia-driver
  # portupgrade -a
 
SirDice said:
Right, it's obviously been a while since your last update. Just pkg delete -f mesa-libs nvidia-driver and start pkg upgrade again. Are you actually using an NVidia card? Depending on the card model you may need to switch to x11/nvidia-driver-470 or x11/nvidia-driver-390. The latest NVidia driver dropped support for a number of older cards.

Code: 
20210617:
  AFFECTS: users of graphics/mesa-libs and x11/nvidia-driver
  AUTHOR: kbowling@FreeBSD.org

  Some libraries from mesa-libs are now provided by libglvnd while
  others were renamed. nvidia-driver already used libglvnd but bundled
  a copy which is now provided as a separate package. When building
  outside poudriere make sure to remove mesa-libs and nvidia-driver
  first in order to avoid conflict with libglvnd.

  For portmaster users:
  # pkg delete -f mesa-libs nvidia-driver
  # portmaster -a

  For portupgrade users:
  # pkg delete -f mesa-libs nvidia-driver
  # portupgrade -a
Click to expand...
I got past that, and now I'm getting
freebsd-upgrade
Not found message
Xorg
Cannot run in framebuffer mode please specify busID for all frame
That might have something to do with it's not booting up in 1080 it's just standard VGA booting now.

I forgot which config file that's
And yeah it's been 3 years since I was on this laptop and Slackware got me too. I ended up having to completely reinstall after trying to upgrade that just got done with that one yesterday and
Now here I go again with freeBSD 13
 
K5KGT said:
SirDice typo'd (I saw it as I've done the same several times)

it's freebsd-update install and not freebsd-upgrade...

that's why you get "not found"
Click to expand...
Thanks I finally figured that out, freking eye balls are going out. Now it's telling me

13.0 RELEASE p13 has passed it's end of life date WTF, and I still have to fix xorg
 
I think you're merging two things into your problem

First, there is no 13.0-RELEASE-p13, the current one is "13.1-RELEASE-p2".

Once you get Freebsd properly updated/upgraded then worry about xorg.



---
[edit - we're all full of typo's today, thanks W.hâ/t! That's what I get for doing several things at once.]
 
You must log in or register to reply here.
Back
Top