Failed Update

Need support for GhostBSD. Ask here if your question does not fit elsewhere.
Post Reply
Christoph
Posts: 2
Joined: Sat May 18, 2024 8:25 am

Failed Update

Post by Christoph »

Hi,

I did an update last night via the update station, rebooted and a second round of updates was available. This second update failed.
2 Boot Environments are available but they don't work, if I let my computer start up without picking a BE, it ends up with a blank screen but with CTRL ALT F4 I can log in my account. All files are still available, my data pool accessible.

ghostbsd version
1302508
24.01.1
13.2-STABLE

manual update (the instructions fron the GhostBSD 24.01.1 now available page) doesn't work.

Intel i5-3570 32ram on a Asrock B75 motherboard.

Please help, tia
Christoph
Posts: 2
Joined: Sat May 18, 2024 8:25 am

Re: Failed Update

Post by Christoph »

Hi,

I reread the GhostBSD 24 announcement https://www.ghostbsd.org/news/GhostBSD_ ... _Available and notice that I should have upgraded my pool, but I don't even have an EFI partition to start with?

I'm a little lost/dissapointed why I can't use the Boot Environments, that's the point of creating BE's before updating. In my case the BE's are worse cause I can't even get a CLI prompt, but the failed update does.

The fact that both my OSpool and Data pool are still working, makes me hope it isn't that catastrophic to solve, but I'm at a loss.
User avatar
neville
Developer
Posts: 144
Joined: Fri Aug 13, 2021 10:27 am
Location: Japan

Re: Failed Update

Post by neville »

Sorry about that. Try running the command

pkg update && pkg upgrade -f
Insane654
Posts: 7
Joined: Fri Jul 24, 2020 1:21 pm

Re: Failed Update

Post by Insane654 »

Hi, I'm Christoph

For starters I want to tell I'm really grateful with GhostBSD to make FreeBSD available in a much more easy way to people like me, who aren't that proficient with vanilla BSD.

I still got a lot of question -not that urgent- which might aslo be of interest to other people like me.

1) Can I get some good practices with a data-pool on a different vdev than my zroot pool? It's always a struggle to 'get my files back' after a re-install due to ownership changes. (chmod and chown on a pool with snapshots freaks out)

2) How to prepare for the next 'crisis', fi what if my SSD with zroot fails? Are there some hints/tips to copy the basic files to my data pool (plenty of room on a RAIDZ2) to make a rescue less painfull? (I had lots of trouble to copy my home directory due to some 'special' files which halted a copy)

3)Although Boot Environmnets saved me today, I still don't grasp how to use those correctly. I reloaded a BE to return to a state before a mishap with cmus, but I still could see some artefacts of cmus in my home folder, is that correct? If you go back to a BE, are satisfied, do you rename that to default and continue using it? If you go back to a BE and are not satisfied, do you just delete it?

Thank you all

Christoph
Post Reply