NSA325 v2 Bullseye SSH connection refused after trying to set static IP

Hi guys,

Having updated my 325 V2 to 6.4.11 kernel /not uboot yet/ i was trying to set static IP, after reboot lost access-got CONNECTION REFUSED on SSH. Where /how should i work to restore access to the box?



Edited 1 time(s). Last edit at 10/25/2023 11:28AM by zebe.

zebe,

> Having updated my 325 V2 to 6.4.11 kernel /not
> uboot yet/ i was trying to set static IP, after
> reboot lost access-got CONNECTION REFUSED on SSH.
> Where /how should i work to restore access to the
> box?

There are many ways to do this. Some is quite easy and painless. But you need to tell a bit about your box setup.

1. Do you have serial console connected?
2. What u-boot version is installed currently? is it 2017.07-tld-1 from the release thread?
3. Is the rootfs on one of the HDDs, or is it on USB drive? (I can guess it is on HDD, just want to be sure).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hello, Bodhi

So-answering:
1. Do you have serial console connected?
2. What u-boot version is installed currently? is it 2017.07-tld-1 from the release thread?
3. Is the rootfs on one of the HDDs, or is it on USB drive? (I can guess it is on HDD, just want to be sure).

Ad. 1 Not anymore, already disconnected and assembled after primary flashing from stock
Ad. 2. most probably 2017.07-thats the u-boot i flashed in place of stock one
Ad. 3 hdd only


cheers,

zebe,


> Ad. 1 Not anymore, already disconnected and
> assembled after primary flashing from stock
> Ad. 2. most probably 2017.07-thats the u-boot i
> flashed in place of stock one
> Ad. 3 hdd only

Ok, so there is 3 different ways to fix this problem: serial console, HDD removal, and USB rescue. I'd prefer the USB rescue approach since it is applicable to all Kirkwood boxes that runs my u-boot build for 2017.07.

1. Connect serial console, log in as root and reverse whatever you did. In the case, restore the /etc/network/interfaces file back to dynamic IP.

2. With the NSA325, the HDD is in a caddy, so it is easy to shutdown the box, remove it. Connect a USB-HDD adapter (you don't even have unscrew the HDD from the caddy). And plug it in another Linux box, log in, become root, and reverse whatever you did.

3. Create a USB rootfs and boot with it. And log into the box as root while it's running USB rootfs. and reverse whatever you did. Let me write this in a separate post so I can add it to the Wiki.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

See here:

https://forum.doozan.com/read.php?2,136049

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
(....)
>
> 3. Create a USB rootfs (....)

Ok, thanx,I am in. Unfortunately evan after restoring dhcp-still no network on the box.
Actually i cannot effectively chroot into box's hdd rootfs.
I d greatly appreciate some consistent procedure also re wiki/links to existing/:
how to:
1. prepare needed hdd setup/Raid on box
2. transfer rootfs from usb
3. update to latest kernel and uboot
3. setup CIFS/?/ so the box be dynamically discovered in LAN with Windows
4. Vnc remote console



Edited 1 time(s). Last edit at 10/27/2023 10:39AM by zebe.

zebe,

> Ok, thanx,I am in. Unfortunately evan after
> restoring dhcp-still no network on the box.
> Actually i cannot effectively chroot into box's
> hdd rootfs.

It's possibly because HDD rootfs file system has error. Check that with e2fsck.

Also, when you want to chroot, you need to mount the HDD rootfs under the runnnig rootfs /mnt.


======

All your topics are covered in the Wiki thread.

> 1. prepare needed hdd setup/Raid on box

Quote

RAID

Making a RAID1 rootfs
Booting btrfs RAID 1 rootfs on Kirkwood boxes

> 2. transfer rootfs from usb

Backup and Cloning rootfs 

Back up a live rootfs using rsync 
CrashPlan 4.3.0 
Backup/Restore rootfs using tar command 
Adjust udev rules after cloning rootfs 
Stock Pogoplug rootfs 
How to clone a rootfs from one Kirkwood box to another: Step 1 and Step 2 
How to clone SATA rootfs to USB rootfs 
How to clone USB rootfs to SATA rootfs

> 3. update to latest kernel and uboot

Kernel release thread:

https://forum.doozan.com/read.php?2,12096

No need to update u-boot (2017.07-tld-1 is good enough). But the newer u-boot for this NSA325 is also mentioned in the u-boot release thread

Quote

Update 26 May 2023
Update 20 May 2023
Updated 07 May 2023

I've released 2023.04 u-boot for Kirkwood boards listed below. For normal installation, the 2017.07 u-boot will be good enough in most cases.

2023.04 U-Boot Kirkwood - Pogo V4. This version adds the capability of booting with the rootfs attached to one of the USB 3.0 ports in the back, among other capabilities.

2023.04 U-Boot Kirkwood - ZyXEL NSA325. This version adds the capability of booting with the rootfs attached to the USB 3.0 port in the front, among other capabilities.

> 3. setup CIFS/?/ so the box be dynamically
> discovered in LAN with Windows

Quote

Samba

Samba smb.conf for a simple set up
HowTo setup Samba/CIFS shares
Samba server project on POGO-V4

> 4. Vnc remote console

Quote

Debian Desktop

XFCE desktop Pogoplug Debian
LXDE / XFCE Desktop on HP T5325 (Kirkwood)
Pogoplug Debian with XDM display manager
Linux Logo

VNC is covered in these Desktop setup threads.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thank you very much !

Ps. Just tried with SSD on USB adapter/instead of USB stick/ but didnt work so far..- plan to set rootfs on SSD /1st bay/ and hdd for Data on the other bay of NSA325.