Thwarted in attempt to install fvdw-sl-console

[fvdw]

then you need to repeat it and have a lok what happens...

[Fuddyduddy]

then you need to repeat it and have a lok what happens...

OK, willingly.

However, the only way I can see to kick this off is to pull out the power-supply lead to the NS2 (because, as reported previously, it hasn't responded to any of the normal ways of shutting it down) thereafter to be re-started.

I can't see any other choice, can you?

But if I do pull the plug, will there then be a likelihood that it will be bricked...? :shock:

[Fuddyduddy]

Note: the NAS Ip when you use fvdw-sl console is 192.168.(0/1).252

@ Jocko

Did you see this in my last post but one?

But first, there's something that's confusing me which I need to get completely clear. In the instructions for installing the firmware, under "ip address NAS and telnet server" three alternative addresses are listed to choose among. The first two are when devices in the LAN start with 192.168.1.xxx or 192.168.0.xxx; mine start with neither, because my Buffalo Air-Station router's 'DHCP Address Pool' is from 192.168.11.2 for up to 64 addresses (note: '.11.' not '.1.' or '.0.'). I therefore concluded that I must choose the third alternative "Address assigned by your DHCP server" (although in fact my NS2's address is fixed, having been assigned by me).

Was this correct?

[Jocko]

Hi Fuddyduddy,

I did not note this post (I saw only the last post with Fvdw)

Indeed, in this chapter

ip address NAS and telnet server:
The telnet server in the standalone kernel will be accessible using one these three ip addresses:
192.168.1.252 (use this when devices in your LAN have ip addresses starting with 192.168.1.xxx)
192.168.0.252 (use this when devices in your LAN have ip addresses starting with 192.168.0.xxx)
Address assigned by your DHCP server.
Be sure that the two first mentioned ip addresses are not used by other devices.
To avoid problems with connecting the advice is to use the addresses 192.168.1.252 or 192.168.0.252 dependent on the setting of your dhcp server.

is not clear because if I recall well, only the first two cases were possible but maybe Fvdw added this last possibility.

So need to wait Fvdw answer.

[fvdw]

well the standalone kernel has two fixed Ip addresses as mentioned. It also attempts to get a dynamic one by contacting the dhcp server but it might not succeed if the dhcp server for whatever reason doesn't lease an address. The automatic start of the telnet server only can use the address specified in the fvdw-sl console as it cannot ask the router. So if you know the ip address assigned by the router you could use that instead of the two fixed ones.

The IP you have set as static (assigned by you) when using the Lacie firmware is useless, that one is stored somewhere in the lacie firmware and only valid when the lacie firmware is loaded. The ip assigned by the dhcp server when running the standalone kernel will not be the same.

You need to look to the dhcp list of your router and find which address is assigned to the nwsp2. If you know the mac address it should be easy as a router normally specify assigned ip's by mac address.
If you cannot figure out the ip but have a list of IP's in your LAN then after the telnet client has started and timed out use the connect button in the telnet client fill in the ip address by hand. You could then try all addresses listed in your router cq LAN.

ps When running the standalone kernel and when you are not doing an action that cause writing to the disk it is safe to disconnect the power supply of the nwsp2 to switch it off

[Fuddyduddy]

Failure :sob

All went completely according to the process as described in the Help document - until step 10.

I identified my NS2's hard disk as "sda", and the firmware on it as Lacie's native. To the question did I want to back-up the firmware I replied "yes", and the backup started. After what seemed quite a short time this message came up:-

Code: Select all

The backup has failed.  The script will exit to prevent data loss...

I clicked on OK. Nothing happened except that the command prompt appeared at the bottom of the dialogue-box, so next I typed-in

Code: Select all

reboot -f

and when this failed to do anything I tried re-booting the NS2 manually (by pressing the power-button). The NS2 did not re-boot but instead is just cycling its blue LED at about once per second, and is unreachable via either the fvdw web interface (using 192.168.0/1.252) or Lacie's.

I've wracked my brains but I can't see that anything I did can have caused the process to go off the rails. Any suggestions, please, as to what I might do to get it back on track?

[fvdw]

funny... :scratch

Just pull the power plug, a blue fashing led normally means it cannot find a disk.
This could happen if you erased the partition table before stating the installer script. the making backups will fail too.

So power off yopur nwsp2 and keep it connected to the LAN, start the fvdw-sl console and choose action load standalone kernel.
When the telnet client has connected give on the command line as command

Code: Select all

fdisk -l /dev/sda

and post the output you get

[Fuddyduddy]

funny... :scratch

Just pull the power plug, a blue fashing led normally means it cannot find a disk.
This could happen if you erased the partition table before stating the installer script. the making backups will fail too.

So power off yopur nwsp2 and keep it connected to the LAN, start the fvdw-sl console and choose action load standalone kernel.
When the telnet client has connected give on the command line as command

Code: Select all

fdisk -l /dev/sda

and post the output you get

I clicked on 'Edit -> Autocopy selection' - but then didn't know where the copy had been stored :doh

So I resorted to making a screen dump and have attached that instead

[Fuddyduddy]

Meanwhile, a note to try to wrap-up the "correct ip" question:-

The IP you have set as static (assigned by you) when using the Lacie firmware is useless, that one is stored somewhere in the lacie firmware and only valid when the lacie firmware is loaded. The ip assigned by the dhcp server when running the standalone kernel will not be the same.

You need to look to the dhcp list of your router and find which address is assigned to the nwsp2. If you know the mac address it should be easy as a router normally specify assigned ip's by mac address.

I couldn't find a dhcp list (named as such) in my router's network interface, but under a heading "Network service list" are shown names and ip addresses of all connected PC's (inc. NS2). This gives as its ip address the static one I assigned to it.

Having therefore no alternative, that's the ip address I duly continued to use. As you'll already have deduced, it worked: using it the installation procedure worked flawlessly up to the point where backing-up of the Lacie firmware malfunctioned.

[Fuddyduddy]

May I please ask for advice as to what are the options now open to me?

As of one week since I'm completely stuck, and can go neither forwards nor backwards. I replaced the Lacie firmware with the fvdw firmware but I'm unable to run it (as things stand right now).

So do I have to conclude that my NS2 is now irrecoverably bricked?

Or is there something that can be done to enable me to get it working again, and if so with which firmware?

Help would be much appreciated.