no ip address, unable to access the NAS

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 2:03 pm

fvdw wrote:Another question, can you connect to the lacie webinterface when lacie firmware is loaded from disk. Ip could be retrieved from router client list or using lacie assistant that runs under windows
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby danilomag » Mon Jun 26, 2023 2:43 pm

can you connect to the lacie webinterface when Lacie firmware is loaded from disk.

no
Ip could be retrieved from router client list or using Lacie assistant that runs under Windows

no, the IP address is not assigned to the NAS, so the modem devices do not show the nas.
I haven't tried with Lacie Assistant yet.
The IP address is assigned only when there are all disks disconnected. But still, I can not access the interface because it restarts.
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 3:15 pm

If I understand you correctly.

No disk installed
The kernel is loaded from flash and you got an ip but the nas reboots

Disk installed
The kernel is loaded from disk but no ip assigned, the nas doesn't reboot but not possible to connect to webintercae (no ip)

Correct?
Ps it could be that the previous owner has configured the nas with static ip.

What you could do is prepare an empty disk, remove all partitions, put that in the nas and ket it boot, now the firmware in flash should initialize the disk and install firmware, when finished reboot and see what happens
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby danilomag » Mon Jun 26, 2023 3:28 pm

No disk installed
The kernel is loaded from flash and you got an ip but the nas reboots

Disk installed
The kernel is loaded from disk but no ip assigned, the nas doesn't reboot but not possible to connect to webintercae (no ip)

Correct?

Yes it's correct

What you could do is prepare an empty disk, remove all partitions, put that in the nas and ket it boot, now the firmware in flash should initialize the disk and install firmware, when finished reboot and see what happens


I think so too.
in what format do I delete it? ntfs? ext3?
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 3:49 pm

Just delete all partitions, so empty partition table.
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby danilomag » Tue Jun 27, 2023 8:43 am

I tried to insert a blank disk, but it doesn't initialize. it boots and then restarts.
Maybe there is a procedure to get the system to install on the disk?
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby danilomag » Tue Jun 27, 2023 2:08 pm

I don't know how I tried to install the firmware again, this is the result, it stays here after the writing "waiting for u-boot"

Code: Select all
> U▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":
"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode"
:0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e"
,"active":2,"ability":0,"mode":0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId"
:"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒
{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version"
:"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":
"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encry


I figured out one thing, when the system boots, I have to wait for this message to start the upgrade.
Code: Select all
Waiting for LUMP (3)
Lump received switching to NetConsole on 192.168.1.185
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby fvdw » Tue Jun 27, 2023 4:31 pm

danilomag wrote:I tried to insert a blank disk, but it doesn't initialize. it boots and then restarts.
Maybe there is a procedure to get the system to install on the disk?

The firmware in flash should do that automatically, maybe that firmware is corrupt??
Was the output on the serial console when booting with an empty disk the same as booting with no disks?
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby danilomag » Tue Jun 27, 2023 4:36 pm

same as booting with no disks?

Yes exactly.
however I discovered that via serial cable I can interrupt the boot with ctrl-c
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby fvdw » Tue Jun 27, 2023 4:40 pm

danilomag wrote:I don't know how I tried to install the firmware again, this is the result, it stays here after the writing "waiting for u-boot"

Code: Select all
> U▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":
"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode"
:0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e"
,"active":2,"ability":0,"mode":0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId"
:"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒
{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":"FvoFqGMb7aKOHyNH","version"
:"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encrypt":true,"productKey":
"FvoFqGMb7aKOHyNH","version":"3.1"}D▒d▒▒UU▒▒{"ip":"192.168.1.40","gwId":"13805622cc50e326651e","active":2,"ability":0,"mode":0,"encry


Do you get this directly after waiting for uboot so with the nas switched off, or does this start after starting the nas??
It is very strange output, never seen this before
I figured out one thing, when the system boots, I have to wait for this message to start the upgrade.
Code: Select all
Waiting for LUMP (3)
Lump received switching to NetConsole on 192.168.1.185

This is expected behaviour, the fvdw-sl send the lump and forces the nas to switch console output/input to netconsole, your pc has ip 192.168.1.185, the fvdw-sl console then use netconsole to send commands. Unclear is which ip the nas has. Maybe it is 192.168.1.40. If that is the case we could try to communicate with the nas using a cmd window and use nc to send commands. I will be back later
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Lacie 5big Network vs2

Who is online

Users browsing this forum: No registered users and 4 guests