Problem finding Nas after upgrading to new firmware version

[leone101]

unfortunatly i tried again to reopen telnet with same command after reboot of nas but......now it can t enter as before....
i tried with different ip 192.168.1.13 but nothing.....just in telnet i can't access.
if i check on router ip addresses it find nas at 192.168.1.252 as kirkwood i installed.
on fvdw assistant in auto mode i can't find it anymore......i also disabled ESET internet security for a while.

[fvdw]

you must connect using 192.168.1.252
As it seems your disk has a problem it might take a while after booting before telnet can connect

[leone101]

i'm sorry fvdw but...i tried many time from telnet but doesn't find it anymore but if i try to find it in netgear router ip connected it sees it.
could be port's problem???

[fvdw]

This is the sequence to be used
1 switch off your nas but leave it connected your lan
2 start fvdw-sl console on your oc
3 select option load and start standalone kernel
4 select the kirkwood standalone kernel
5. A cmd window will popup and mentioning waiting for uboot
6 start your nad
7 you see if the kernel is uploaded and started (do you see this in the cmd window?)
8. Telnet window pops up

Do you do all these steps?

[leone101]

yes! sure! everytime!

[fvdw]

I repeat my question do you actually see in the cmd window that the kernel is uploaded (several lines with ***, and the line mentioning uncompressing kernel and starting kernel. :tapfoot

If yes then there must be something in your lan preventing making contact.
Read this topic https://plugout.net/viewtopic.php?f=7&t=2645

[leone101]

i'm really sorry fvdw i can't writh u everytime soonerbeecause health problems....
u were (obviously ) right...
when i try ithe kernel uploaded trough procedure it doesn t show me now in the cmd some*** .... i also readed the faq u sent me trough link and i disable " temporally" eset internet security and all others ethernet and wireless connection....
ì also tried to link directly the nas to pd bypassing to router to try but nothing.
I don't know why the first time i sent u log data i reached to connect it apparently.....
i really hope not to loodìse my datas...... and reconnect it.
i'm sorry to be dummy.
i really apreciate your teaching from u and Joko

[fvdw]

Sorry to hear from your health problems. Hope that get better soon. Aboutvthe nas, if you liadoad the standalone kernel do you see in the cmd window that it tries to upload the kernel after you start the nas. (The initial message "waiting for uboot" moves up and a line about tftp transfer should be visible with TTTT...
Do you see such a line ?
If yes then your firewall on your pc is blocking transfer.
If no, and only the line waiting for uboot remains visible after starting your nas then your network is blocking fvdw-sl console clunc program that is used to interrupt boot.

Described what you see in the cmd window

[leone101]

Hi Fvdw i'm sorry i can't write much because therapies
after some fight with ethernet access and disabling firewall i reach this point but now i'm blocked.....
what i should do?
i hope not to kill what is inside my nas
i send u photo

According this in boot.log of sda7

Code: Select all

booting using sda2 file system...

the nas tries to boot from sda2 but fails

When running standalone kernel please mount sda7 and give a command to list content of folder /lacie-boot

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
ls -al /lacie-boot

Lets try following
check why it takes so long to boot standalone kernel
Post output when running standalone kernel of this command

Code: Select all

dmesg

And lets see if the file system on sda2 must be repaired
When running standalone kernel give command

Code: Select all

fvdw-sl-programs

Choose option load mini glibc and tools.
After that give this command

Code: Select all

e2fsck -fy /dev/sda2

When being in

[fvdw]

You made an error in the e2fsck command. Do not use a space between /dev/ and sda2 in the e2fsck command
Use the command as indicated earlier

Code: Select all

e2fsck -fy /dev/sda2