Can't see 5Big2 NAS after subnet change

[Kippara]

I have two 5Big Net2 NAS, one for media with static IP 192.168.30.50 and one for backups with static IP 192.168.100.100. I recently had to replace my VOIP router and decided to modify my network configuration. I moved my media subnet to 10.0.40.X and my backups to 10.0.50.X.
After the re-configuration I re-attached the two NAS but was unable to see them with the assistant or any other way which is probably understandible. I configured another router with the old media subnet of 192.168.100.X and attached the backup NAS expecting to be able to access it using the WEB interface. The NAS was the only device attached to the router but I kept getting the "refused to connect" message from the WEB interface and I could not ping the old static IP address. This is the case for the Media NAS as well.
Using the Standalone (Kirkwood) I am able to telnet to each NAS but am unfamiliar with BusyBox Linux commands. Some questions.
Is there is a reference for the fvdw BusyBox command set so I could set new static IP addresses using the CLI?
Is this the right approach or do you recommend another way to get access?
Is there a guide for a repair procedure to restore the NAS and check it's integrity?
Any assistance would be appreciated.

[Jocko]

Hi

. I configured another router with the old media subnet of 192.168.100.X and attached the backup NAS expecting to be able to access it using the WEB interface. The NAS was the only device attached to the router but I kept getting the "refused to connect" message from the WEB interface and I could not ping the old static IP address. This is the case for the Media NAS as well.

Yes that is the easiest way but your laptop was it on the same subnet when you tried to load the fw web-interface ? I think not if you write "The NAS was the only device attached to the router"

[fvdw]

In addition to Jocko answer.
Your laptop must be connected to same router as the nas and have an ip 192.168.100.xxx

[Kippara]

Sorry, my bad, there were two devices attached to the router, the NAS and my computer. My computer had a static IP of 192.168.100.200 i.e. the subnet the NAS was originally configured to.
I am sure I did not change the static IP I had assigned to the NAS but it was a couple of months ago and anything is possible. Is there a way I can see what the IP address the NAS is configured with from the Standalone kernel?

[fvdw]

what you could do is load the standalone kernel and connect with telnet to the nas.
Then mount sda7

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7

Then look into boot log

Code: Select all

cat /sda7/boot.log

It should look something like this

Code: Select all

start boot log
detect and set platform
2bignas
kirkwood
UIMAGE-414102-KIRKWOOD-22
Current kernel: 4.14.168 #1 PREEMPT Wed Jan 29 16:24:04 CET 2020
2bignas
 mount dev/pts
update dev nodes
booting using sda1 file system...
else loop1 finished
rcS finished


It if the nas is booting from sda1 or sda2 partition
Assume it is mentioning boot from sda1 then mount sda1 and list boot.log

Code: Select all

mkdir /sda1
mount /dev/sda1 /sda1
cat /sda1/boot.log

If nas is booting from sda2 perform above actions for sda2 instead of sda1
The boot.log should show which ip is used by the nas

The last part of the boot.log on sda1 or 2 will look something like this
In your case it should show the static ip you have set

Code: Select all

....<snip>.....

*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 18.2
    built on: October 18 2019

    LAN IP address: 192.168.1.54 (DHCP)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings


[Kippara]

Thanks for that.
sda1 & sda7 mounted successfully.
sda2 will not mount
error
root@fvdw-sta-kirkwood:/ # mount /dev/sda2 /sda2
mount: mounting /dev/sda2 on /sda2 failed: Function not implemented

output of sda1 boot.log
root@fvdw-sta-kirkwood:/ # cat /sda1/boot.log
start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
5big2
kirkwood
mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Wed Dec 22 01:10:09 EST 2021
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
5big2
rebootd-nwsp2
5big2
standbyd-nwsp2
start fan
starting php based setup routines step 1
* Initialize the volatile db file... [ OK ]
* Starting udevd... [ OK ]
* Starting RAID monitor: [ OK ]
* Starting restore RAID devices...
- Assembling device /dev/md0: [ OK ]
* Finishing restore RAID devices... [ OK ]
* Found database configuration file... [ OK ]
* Updating Disks database... [ OK ]
* Starting mount of volumes...
- Mounting volume Backup-NAS:

[fvdw]

So apparently it is booting from sda1. Did you check that in boot.log of sda7?.please check. This because the boot.log can also be an old one as with installing upgrades the boot partition is swapped between sda1 and sda2.
This boot.log you posted from sda1 is incomplete, interesting is the bottom part where ip is mentioned, you should pist that bottom part.

[Kippara]

sda7 boot.log
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
5big2
kirkwood
mount dev/pts
update dev nodes
booting using sda1 file system...
root@fvdw-sta-kirkwood:/ #

that is the complete sda1 boot.log. When I look at it with vi the last line looks like this
- Mounting volume Backup-NAS:@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
with a lot more @^
Sorry, what do you mean "you should pist that bottom part." What is pist?

[fvdw]

:-D with "pist" I meant "paste" sorry for that type error.

When the boot.log of sda1 is really what you posted it means something goes wrong during boot. Most likely a corrupt filesystem.
The fact that you mentioned that sda2 could not be mounted is now a problem as we cannot use that partition to boot the system.
Being both partitions corrupt is remarkable, you might have a harddisk problem??
Did you poweroff the nas without shutting it down first? That could corrupt files.
Anyhow we can try to restore the firmware on sda1 and sda2 using the fvdw-sl console. You must use fdw-sl console 6.0 with 18-1 firmware. (Later you can upgrade to 18-2 once nas is up and running again.
In fvdw-sl console use action " write firmware image to disk"
And write firmware to partition sda1 and sda2. Do NOT write it to sda7.
If that goes without a probkem than reboot the nas and see if you can connect to it using the old static ip.

Ps use a wired connection between pc and router. Using wireless can cause file corruption when uploading the firmware image.

[Kippara]

I have written the fvdw-sl firmware to sda1 and sda2 but not sda7 successfully.

After reboot -f the NAS appears to have booted correctly with all blue lights and none blinking. I have tried all old IP addresses including 192.168.1.252 and 192.168.0.252 but cannot communicate with the NAS. The router which hosts DHCP does not show a lease for the NAS after connecting the NAS to the router and rebooting.
Since the NAS does not seem to get an IP address via DHCP can we assume it has a static address and is there any way I can find out what that IP address might be?