Messed up openwrt snapshot, can't access gui or ssh

Installing and Using OpenWrt
1

Hello!
I just fiddled too much with my openwrt machine, and I am trying to reestablish some kind of functionality to it. I need some help identifying the culprit.
I have an x86 machine on a proxmox server, this was working but after upgrading some available packages, i lost access to opewrt through Luci and I can't ssh into it also.
The mistery is that vpn server still works, I can connect to it, and from there, I can access the console through proxmox. So internet is also working, as I am not on location.
br-lan seems to be working, as I can ping a client connected through a cable.
Wireless clients are not accessible.

What could I try first to do, in order to reestablish at least ssh, and then Luci access?

2

use owut to upgrade to a stable release (to and from can be the same version), it'll use the packages from stable.

Upgrading packages (via the CLI opkg upgrade command or the LuCI Upgrade... button) can result in major problems. It is generally highly discouraged, unless you know what you are doing or if there is specific instruction to do so.

1 Like
3

First error, I can't install it:

1
11604×720 38.4 KB

4

ah, you're running a snapshot (why ?).

you could upgrade to the latest snapshot, using an image with all the extra packages you had installed.

if can be done at https://firmware-selector.openwrt.org/?version=SNAPSHOT

1 Like
5

But with no access to ssh, is it possible?

Also, running snapshot because I was trying to add a realtek wifi card. Gave up on that, stuck with this until i get on location, to be able to install a stable release.

6

you can copy the generated file link, and use wget on the router to grab it directly from F-S, but upgrading while not being on site is obviously risky.

1 Like
7

Will the update maintain the config files?

8

yes, it should.

did you by any chance resize the rootfs, it makes things tricker.

9

At this time I really do not remember.

10

run df -kh, if rootfs is 100MB, you haven't.

11

does approximately count?

2
2682×136 4.74 KB

1 Like
12

I'm on 24.10.2 and it matches my size(s) :slight_smile:

root@OpenWrt:~# df -kh
Filesystem                Size      Used Available Use% Mounted on
/dev/root                98.3M     55.5M     40.8M  58% /
tmpfs                     3.4G    208.0K      3.4G   0% /tmp
/dev/nvme0n1p1           16.0M      6.3M      9.7M  39% /boot
/dev/nvme0n1p1           16.0M      6.3M      9.7M  39% /boot
tmpfs                   512.0K         0    512.0K   0% /dev
1 Like
13

Sorry for this stupid question, but i can not remember at this time what image type I used, between combined efi, ext4, rootfs...
Any idea if I need to check anything, or should i get the first?

14

ubus call system board should tell you this.

root@OpenWrt:~# ubus call system board
{
        "kernel": "6.6.93",
        "hostname": "OpenWrt",
        "system": "AMD Ryzen Embedded V1756B with Radeon Vega Gfx",
        "model": "HP HP t740 Thin Client",
        "board_name": "hp-hp-t740-thin-client",
        "rootfs_type": "ext4",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.2",
                "revision": "r28739-d9340319c6",
                "target": "x86/64",
                "description": "OpenWrt 24.10.2 r28739-d9340319c6",
                "builddate": "1750711236"
       }
}
1 Like
15

I just hit sysupgrade -v on the .img.gz. It closed all shell connections, fingers crossed.

L.E.
2 minutes later...
You are a great man, for the time you spent on my lesser knowledge.
Thank you very much!

4 Likes
16

hopefully you can now downgrade to stable using owut, if that's something you'd still like to do.

1 Like
17

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.