Fail to get an IP from DHCP server after installing fvdw-sl

[fvdw]

Yes we discussed that just a minute ago but there us an issue with this old 5big2, need tocheck my archive what we did.

Another idea could be prepare a new disk in old 5big2 using fvdw-sl console and if that boots put it in the new 5big2. This will avoid destroying the sda disk of old 5big2 if we put that in new 5big2.

Ps e2fsck did not indicate filesystem corruption

[Draftmancorp]

Yes we discussed that just a minute ago but there us an issue with this old 5big2, need tocheck my archive what we did.
Another idea could be prepare a new disk in old 5big2 using fvdw-sl console and if that boots put it in the new 5big2. This will avoid destroying the sda disk of old 5big2 if we put that in new 5big2.
Ps e2fsck did not indicate filesystem corruption

I was thinking that installation firmware procedure write any file in ram memory...or other memory of Lacie Nas. Becouse of this i'm fear to use my old Nas becouse i don't remember what he had.
If you wan i try a make one new disk on my Old 5big2...

@fvdw, I tried just now, the power supply sems is not the problem.

[Draftmancorp]

Yes we discussed that just a minute ago but there us an issue with this old 5big2, need tocheck my archive what we did.
Another idea could be prepare a new disk in old 5big2 using fvdw-sl console and if that boots put it in the new 5big2. This will avoid destroying the sda disk of old 5big2 if we put that in new 5big2.
Ps e2fsck did not indicate filesystem corruption

I was thinking that installation firmware procedure write any file in ram memory...or other memory of Lacie Nas. Becouse of this i'm fear to use my old Nas becouse i don't remember what he had.
If you wan i try a make one new disk on my Old 5big2...

Other idea, maybe the power supply of your new 5big2 is unstable or to low power because of a defect, you could swap the powrr supply and use the one from your old 5big2 to see if that solves it

I tried just now, the power supply sems is not the problem.
EDIT: OPS...double post up there... sorry i see database erro.

[fvdw]

I checked some old posts, it seems your problem was upgrading from older to newer version.

To check if your old 5big2 runs on latest kernel remove all disks and load standalone kernel using fvdw-sl console if telnet works then it is ok to use 17-0 kernel.

If so put the disk prepared in new 5big2 in slot1 of old 5big2 and boot (no other disks installed).;

[Draftmancorp]

I checked some old posts, it seems your problem was upgrading from older to newer version.

To check if your old 5big2 runs on latest kernel remove all disks and load standalone kernel using fvdw-sl console if telnet works then it is ok to use 17-0 kernel.

If so put the disk prepared in new 5big2 in slot1 of old 5big2 and boot (no other disks installed).;

Whait a moment!!!!
I had a brilliant idea.
I put back the 5 disks that were there before in raid6 etc etc ... I turned on the nas, and I see the nas in dashboard lacie dashboard software so i begin to mange it...
I see the ip that is in dhcp and no one will ever assign it to him :doh , so I put it in the manual now and save configuration (can help this?).
However I'm managing the nas from its dashboard, it seems to work everything.

So can we exclude hardware problems?

[fvdw]

Yes if lacie firmware runs and raid6 is ok then we can exclude hardware problem

[fvdw]

But if that is the case I see no reason why fvdw-sl firmware should not run. In fact that leaves only few possibilities. Either the fvdw-sl console package has gone corrupt in the download or when uploading files to the nas some data is lost. The second option is not so likeky as many user succeeded and were able to boot the 5big2.

So I am interrsted to see if we encounter same problem with the old 5big2 when using a new disk or preparing a new disk via fvdw-sl console

[Draftmancorp]

But if that is the case I see no reason why fvdw-sl firmware should not run. In fact that leaves only few possibilities. Either the fvdw-sl console package has gone corrupt in the download or when uploading files to the nas some data is lost. The second option is not so likeky as many user succeeded and were able to boot the 5big2.

So I intersted to see if we encounter same problem with the old 5big2 when using a new disk or preparing a new disk via fvdw-sl console

I'm making one disk with old nas.

[Draftmancorp]

But if that is the case I see no reason why fvdw-sl firmware should not run. In fact that leaves only few possibilities. Either the fvdw-sl console package has gone corrupt in the download or when uploading files to the nas some data is lost. The second option is not so likeky as many user succeeded and were able to boot the 5big2.
So I am interrsted to see if we encounter same problem with the old 5big2 when using a new disk or preparing a new disk via fvdw-sl console

Woh... Even with the old 5big I can't find the nas after the reboot. we are over 5 minutes of waiting now.
from ignorant, for me seems that it boot but it seems also that the installation does not give a valid IP configuration, if not, at least I will ping it from cmd prompt, isn't it?

the same thing like new 5Big... so... is not the nas? :thinking
(see you tomorrow or monday, i'd like to reach a goal with you guise!!)

[fvdw]

Probably not, I am going to make a fvdw-sl console package for you in smaller sub archives, and a md5 sum so you can vheck if oackage is well received.
the only thing I can think of that something in your current version of fvdw-sl console is corrupt