Tried upgrade from GUI but…

[Tismofied]

I chose to upgrade from the latest 23.1 version to 23.7 but when I noticed the router didn't reboot I plugged it to a monitor and I got an error.

Code Select Expand

** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
WRITE CHANGES? yes
***** FILE SYSTEM IS CLEAN *****
** 83443 journal records in 11701248 bytes for 22.82%
utilization
** Freed 12 inodes (0 dirs) 16 blocks, and 36 frags.
***** FILE SYSTEM MARKED CLEAN *****
WARNING: /mnt: reload pending error: blocks 296 files 7
mount: /dev/gpt/rootfs: R/W mount of /mnt denied. Filesystem is not clean - ill invalidate journal contents: Operation not permitted mkdir: /tmp/.cdrom: Read-only file system
mount_unionts: /tmp/ cdrom: No such file or directory mkdir: /tmp/.cdrom: Read-only file system mount
_unionfs: /tmp/. cdrom: No such file or directory mkdir: /tmp/.cdrom: Read-only file system mount
_unionfs: /tmp/. cdrom: No such file or directory mkdir: /tmp/.crom: Read-only file system mount
_unionfs: /tmp/.cdrom: No such file or directory mkir: /tmp/.cdrom: Read-only file system
mount_unionfs: /tmp/.cdrom: No such file or directory mkdir: /tmp/.crom: Read-only file system
mount_unionfs: /tmp/.cdrom: No such file or directory mkdir: /tmp/.cdrom: Read-only file system
mount_unionfs: /tmp/.crom: No such file or directory pwd_mkdb: /etc/pwd,db.tmp: Read-only file system
pwd
_mkdb: /etc/pwd. db, tmp: Read-only file system
Setting hostuuid: 621f8a21-be9c-11ed-906a-60beb407fa72.
Setting hostid: 0x8ac8701日.
Configuring vt: blanktime,
override ru-r--r-- root/wheel for /var/run/dmesg.boot？



What am I looking at here? Please help the family already picked up the pitch forks

[Tismofied]

When I run fsck I get

Code Select Expand

***** FILE SYSTEM IS CLEAN *****
** 83443 journal records in 11701248 bytes for 22.82% utilization
** Freed 12 inodes (0 dirs) 16 blocks, and 36 frags.
***** FILE SYSTEM MARKED CLEHN *****
WARNING: /mnt: reload
pending
error: blocks 296 files ?
** /dev/gpt/efifs (NO
WRITE›
** Phase 1 - Read FAT
and checking connectivity
** Phase 2 - Checking
Directories
** Phase 3 - Checking
for Lost Files
6 files, 254 MiB free (520774 clusters)
MARK FILE SYSTEM CLEAN? по
***+@ FILE SYSTEM IS LEFT MARKED AS DIRTY *****

[Tismofied]

Tried multiple times to do a fresh install but any time I boot from hardrive it reverts back to 23.1 and get the errors in previous reply. Please someone direct me to a possible solution

[newsense]

There's no reverting on bare metal, if you end up on 23.1 after installing 23.7 replace your storage device

[Tismofied]

what if i just wanted to do a fresh reinstall of 23.1 and restore my backup?

[newsense]

23.1 reached end of life.

After you replace the ssd/hdd you can either:

Code Select Expand

install 23.1 - upgrade to 23.1.11 - upgrade to 23.7.1 - import the config - check or updates to pull all plugins - reboot

OR

Code Select Expand

install 23.7.1 - import the config - check or updates to pull all plugins - reboot

[Tismofied]

Thank you for your replies.
So you're basically saying the msata ssd is gone and can't be salvaged?

[newsense]

Excluding human error - as in thinking you were installing 23.7 but got the 23.1 USB stick instead - the only way the old OS survives is when the drive is not working properly anymore and needs to be replaced.


Logical errors would have been fixed on reboot or at the very least you would have had a fresh 23.7 install. Neither of those two options happened.


If you have HDMI output you could try booting Linux, mount the drive read-only and attempt to copy the config file if you don't have a copy. Better start from scratch though.

[Tismofied]

Just to fully explain what I did in case there is a misunderstanding of what I did.
My system was up-to-date , plugins and everything.
I checked yesterday for an update as I do all the time I login to my dashboard and I noticed there a major update to 23.7 and it also stated that 23.1 has reached end of its life. I clicked on update from the gui and left it do it's thing. After an hour or so I noticed the system didn't come back online so I shut it off, I unplugged it from the rack and moved it closer to a monitor to plug it in through hdmi. When I turned it on I was presented with the errors above. So I went and I got me a different usb and used Rufus to flash a new download of 23.7 I plug that in and reboot from it , I logged in as installer and followed the prompts but as soon as I change password and complete install I wait a little and remove the usb stick so it would boot from the internal msata ssd drive, it boots into 23.1 instead and I get the errors .

I even tried with my other usb stick that have 23.1 to try and do fresh install of that and just get back to where I was before the update but it still didn't work.
I also tried deleting any partition from the msata ssd drive.

[CJ]

Shutting the system off would explain the unclean boot but it seems like you have other issues going on.

What machine are you using?  Is the msata the only drive in the system?  Have you checked the BIOS to confirm that it's booting from the msata and not something like an internal emmc?

You might want to try using something like dban to completely zero out every drive on the system.  That way you know you're starting from a clean slate.

[Tismofied]

My system is a qotom mini pc with intel celeron(R)  j4125 @2.00 GHz and with an 128 GB msata ssd that it came with. I always go to Bios and choose the usb install stick as the boot device. I choose the installer and select my msata ssd as the install target but I hit complete install and reboot , it gives me the prompt :

Code Select Expand

override ru-r--r-- root/wheel for /var/run/dmesg.boot？


Plus other prompts like it.

At this point I just wanna nuke the ssd and start fresh.
I just finished using an updated version of dban called shredos and it still loads the corrupted version of 23.1 and gets stuck at the above prompt

[newsense]

Dban wipes healthy drives, cannot help when the drive is dead or dying

[Patrick M. Hausen]

If you write the drive with dd and the data is still there afterwards, the drive is broken in some way. I have only ever seen this with RasPis and SD cards but there might be cases outside of that scenario.

[Tismofied]

If you write the drive with dd and the data is still there afterwards, the drive is broken in some way. I have only ever seen this with RasPis and SD cards but there might be cases outside of that scenario.

Thank you sir for helping. I already ordered a new ssd drive. Do you suggest I do zfs or ufs since I only have one drive?

[CJ]

If you write the drive with dd and the data is still there afterwards, the drive is broken in some way. I have only ever seen this with RasPis and SD cards but there might be cases outside of that scenario.

Thank you sir for helping. I already ordered a new ssd drive. Do you suggest I do zfs or ufs since I only have one drive?

zfs is helpful even with only one drive.