Locked-out of fvdw after long absence

[Fuddyduddy]

Hello

It's not far short of 2 years since I last posted here.

I won't bore you with the reasons why, but I gave up using fvdw in despair. Now I thought I'd take it up again, but find that I can't access it.

Two major changes have been made in the interim:- 1) a motherboard upgrade along with upgrading to a Kaby Lake i5 7600 CPU, more memory, etc 2) a new router (Linksys WRT 1900ACS).

The router sees the fvdw NAS but is unable to connect to it, so I'm unable to access the web interface. Also fvdw-Assistant can't connect, despite displaying the correct MAC-address. Likewise, when I open the console and try to access the fvdw from there I get no further than when the Telnet window appears - there's no prompt for username and password and after an interval it just times-out.

The last firmware version that I installed was 16-1. I'm using a wired internet connection and have disabled my firewall.

Are you able, please, to suggest what I might try in order to restore the connection? Or do I need to supply more information first?


Thanks in advance.

EDITS
1) Sorry - wrong forum!!! Should have been "Lacie Network Space vs1"
2) My memory isn't what it was! I think the firmware that is installed is in fact 15-3. Although I downloaded 16-1, I don't believe I had installed it before I broke off using fvdw

[fvdw]

The router sees the fvdw NAS but is unable to connect to it, so I'm unable to access the web interface

How do you know that your router sees the nas?

If you can see the ip address use that in your browser to connect.
It is possible that you are not in the same workroup in that case windows will not see your nas.

[Fuddyduddy]

"How do you know that your router sees the nas?"

I've more than once regretted my choice of replacement router; to judge from multiple comments on various forums this router and/or its firmware is notoriously buggy. The one replaced (a Buffalo product) had an extremely detailed and well-annotated user interface, whereas the interface that comes with the Linksys is at best a PITA!

It displays a 'Network Map' (self-explanatory); on that the fvdw NAS appears along with the other devices on my LAN and in the 'info' panel that pops up when it's clicked are shown the most important details - among them (as previously stated) the correct MAC address, with IP address blank. On another page, called 'Connectivity' - 'Local network' tab, clicking on a box labelled "DHCP reservations" brings up a list showing the IP addresses I've caused to be stable together with (supposedly) the IP addresses of the other devices on my LAN.

Today I manually entered the NAS in the list of 'Reserved addresses' (it didn't appear in the list of 'others', which can if selected be automatically entered) but that has made no difference to the previously-reported behaviour.

And, by the way, PuTTY doesn't find the fvdw NAS either (and nor, as already reported, did Telnet). Doesn't that suggest that the problem isn't with my router - buggy or not - but is happening independently of it - ie somewhere in the fvdw NAS path?

How about this? - when I stopped using the NAS the Buffalo router I was still using had as its IP address pattern 192.168.zzz.xxx (it was 192.168.11.2, specifically) whereas the Linksys has the conventional 192.168.1.xxx pattern. Might the fact that the IP address format got changed while the NAS was out of use perhaps have anything to do with the problem I'm now having?

EDIT

And now I come to think of it, I believe the NAS has always had MSHOME as workgroup whereas my PC has WORKGROUP. However that never stopped them talking to each other.

[fvdw]

did you set a fixed ip address on your nas in the past ?

That could explain why you cannot connect. if thats the case then you have tow options,
1. take out the hdd put it in an usb->sata adapter connect to pc and adapt nas database by hand (not so easy for not experienced user)
2. Change your router settings (temporarily to use as ip pool 192.168.11.xxx

[Jocko]

Hi fuddyfuddy

About point 1, if you have another nas with our firmware, maybe it will be better to plug the disk in the last nas and I can send you command to edit the nas database.

[Fuddyduddy]

Thanks for both replies :-)

"did you set a fixed ip address on your nas in the past ?"

Yes I did (192.168.11.5). But I'm daunted at the prospect of removing the HDD from the Lacie case (though I note that you've given detailed instructions for how to do that). I'm still mulling that over...

Meanwhile though, I'm confused by:- "2. Change your router settings (temporarily to use as ip pool 192.168.11.xxx".

The Linksys router doesn't appear to permit the use of anything other than a range of from 192.168.1.100 to 192.168.1.199. If I try to change the third octile from '1' I get an error message saying "IP address not in valid subnet 192.168.1.1 to 192.168.1.254"

@ Jocko

Sorry but I don't have any other NAS - of any description.

[Jocko]

Hi

Please to note, there is no way to get a rescue access such using fvdw-sl console on a nwsp1. If your nas is not see on the LAN, you have to extract the disk to explore the firmware system.
So you have not many choices :
- If you use a static IP, to bring up your NAS on your LAN, you must use the former subnet
- extract the disk

Then what fvdw wrote previously

[Fuddyduddy]

Hi

Please to note, there is no way to get a rescue access such using fvdw-sl console on a nwsp1.

I'm very embarrassed: I've now just realised that my NAS is in fact a Network Space 2 (not 1). Sorry about that silly mistake.

Does that make a difference?

[Jocko]

So I moved the topic in the right forum.

Indeed it is not the same thing as you may use fvdw-sl console!

Then if it is not yet the case, you need to download the last fvdw-sl console package.
Please to read also this topic : http://plugout.net/viewtopic.php?f=7&t=2645

You need to select the action "Standalone kernel, load and start" and to use as standalone kernel: UIMAGE-3142-NWSP2CL-KIRKWOOD-158-standalone

When you will get a telnet access, do:

Code: Select all

mkdir /sda7 /sda5 /sdax
mount /dev/sda7 /sda7
ls /sda7/lacie-boot


Then you should see a file sda?boot (?=1 or 2) and mount the related partition sda? on /sdax

Code: Select all

mount /dev/sda? /sdax
cat /sdax/boot.log

mount /dev/sda5 /sda5
grep '<lan>' /sda5/etc/nas_conf_db.xml -A 12
grep '<dhcpenabled>' /sda5/etc/nas_conf_db.xml

[Fuddyduddy]

Jocko

When you will get a telnet access, do:...

I've installed Console 16.7, and followed the process up to the point where the Telnet terminal-screen comes up. Then - nothing. The screen stays blank, then times-out.

(This is what happened every time when I was still using ver. 16.6).

I've checked all the points in this post http://plugout.net/viewtopic.php?f=7&t=2645#p24584 None of them applies in my case