Stuck in I dont know what mode?!

NextBox
1

I turned my nextbox off via nextbox app in nextcloud. Pulled the cables (ether & usb-c/power), changed location, plugged in again (same ethernet/router), but I cant connect. Neither can I detect the box via nmap -sn 192.168.0.0/24, and my router doesnt see it as “connected device”. What is happening? See also the status LED…is this “reset button pressed”? WTF, obviously, it is not :wink: @daringer what should I do? I don’t want to pull the power…no?

photo_2021-10-25_11-25-53
photo_2021-10-25_11-25-53960×1280 71.7 KB

2

Hey @benzkji,

this is not the “real blue” LED, this is the state of the led for the first 1-2 minutes during boot where we do not have control over the LED. (it’s also not as bright as with the LED under NextBox’s control)

This under the line means you NextBox did not boot properly, could you please just pull the power and try rebooting again?

best

1 Like
3

werks! but how come? will check the logs.

4

funny, kern.log shows entries from yesterday, and continues today, seeming like power was never interrupted? it continues like for 3 more pages, with the same blocking/non blocking state messages.

anyway, thx for the quick help, glad a simple reboot fixed it.

   Oct 24 13:06:06 nextbox kernel: [   34.264310] Adding 2097148k swap on /srv/swap.  Priority:-2 extents:4 across:2244604k FS
    Oct 24 13:06:07 nextbox kernel: [   35.039543] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    Oct 24 13:06:07 nextbox kernel: [   35.039554] Bluetooth: BNEP filters: protocol multicast
    Oct 24 13:06:07 nextbox kernel: [   35.039569] Bluetooth: BNEP socket layer initialized
    Oct 24 13:06:09 nextbox kernel: [   37.732467] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
    Oct 24 13:06:09 nextbox kernel: [   37.732504] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Oct 25 12:01:02 nextbox kernel: [   77.916678] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
    Oct 25 12:01:02 nextbox kernel: [   77.956823] Bridge firewalling registered
    Oct 25 12:01:06 nextbox kernel: [   81.629663] br-767d61d8412e: port 1(veth84dee37) entered blocking state
    Oct 25 12:01:06 nextbox kernel: [   81.629684] br-767d61d8412e: port 1(veth84dee37) entered disabled state
    Oct 25 12:01:06 nextbox kernel: [   81.630015] device veth84dee37 entered promiscuous mode
    Oct 25 12:01:06 nextbox kernel: [   81.735111] IPv6: ADDRCONF(NETDEV_CHANGE): veth9b7778b: link becomes ready
    Oct 25 12:01:06 nextbox kernel: [   81.735238] IPv6: ADDRCONF(NETDEV_CHANGE): veth84dee37: link becomes ready
    Oct 25 12:01:06 nextbox kernel: [   81.735290] br-767d61d8412e: port 1(veth84dee37) entered blocking state
    Oct 25 12:01:06 nextbox kernel: [   81.735297] br-767d61d8412e: port 1(veth84dee37) entered forwarding state
    Oct 25 12:01:06 nextbox kernel: [   81.735377] IPv6: ADDRCONF(NETDEV_CHANGE): br-767d61d8412e: link becomes ready
    Oct 25 12:01:07 nextbox kernel: [   82.733261] br-767d61d8412e: port 2(veth2a06840) entered blocking state
    Oct 25 12:01:07 nextbox kernel: [   82.733274] br-767d61d8412e: port 2(veth2a06840) entered disabled state
1 Like