Update with problems

[Jocko]

Ok

We need to investigate more what happens and then use telnet access with fvdw-sl console.

So stop your nas and select the action "Standalone kernel, load and start". Of course you need to use this time the standalone kernel version for 5big1.
Connect you and post the outputs of these commands

Code: Select all

mkdir sda7 sda5 sda1 sda2
mount /dev/sda7 /sda7
ls -l /sda7/lacie-boot   (please to see if it lists a file sda1boot or sda2boot)
cat /sda7/boot.log

mount /dev/sda5 /sda5
cat /sda5/etc/install-firmware.log        (this will get the upgrade log of your last upgrade attempt)

# according the listed file (sda1boot or sda2boot), mount the related partition (sda1 or sda2)
mount /dev/sdax /sdax             (x=1 or 2)
cat /sdax/boot.log


Note: there is another critical step : when the script swaps the firmware partition. So if it happens at the time as you did a roll-back, the nas will fail to restart because the nas database contains data not supported by the firmware version used at the first install.

[Basajaun]

Good morning Jocko,

i've followed your steps, but when it try to connect to box via telnet (172.16.100.83:23), we have this error:

Connection to 172.16.100.83/telnet timed out

Thanks in advance !

Best regards,

[Jocko]

Hi

So, currently you have an issue with the console (surely with your computer environment, the kernel is not loaded: standalone and external version)
Then the previous tests (yesterday) can not be conclusive.

Please to see https://plugout.net/viewtopic.php?f=7&t=2645

[fvdw]

I think the problem with standalone kernel is that he uses only a switch to connect pc and nas. That means there is no dhcp server to assign an ip. Then he must use the static ones build into the kernel 196.168.1.251 or 192.168.0.251 and set his pc to use as ip pool 196.168.1.0/255 or 192.168.0.0/255 or use a router with dhcp instead of switch.

And of course set correct ip in telnet client to connect.

[fvdw]

Another option is if you have an usb-sata interface is to take out the sda disk and connect it to your other 5big1 or pc running linux and investigate the disk in that way. But prefered is the standalone kernel.

Ps do you use raid on this 5big1?

[Jocko]

on standalone feature a switch (and not a hub: an hub broadcasts nothing, it is a passive equipment) can be used without a dhcp server (there is a topic about that) but the ip (xx.xx.xx.83) used to connect is false and Basajaun had to set it manually. nas IP in this case is 172.16.100.252

[fvdw]

huh :scratch I don't see how the standalone kernel would give itself that ip address

[fvdw]

(there is a topic about that)

That topic concerns assigning a static ip after the firmware is installed viewtopic.php?f=30&t=2878

[Jocko]

You forgot a change you made on version 5.3 or 6.0!
See https://plugout.net/viewtopic.php?f=26&t=3094&p=30284&hilit=console#p30284

[fvdw]

huh :scratch I don't see how the standalone kernel would give itself that ip address

I checked the init script of 5big1 and indeed it picks the ip from netconsole line so ip 172.16.100.83 should be set by the standalone kernel

that ip is specified here viewtopic.php?f=30&t=3113#p30441