OK, willingly.fvdw wrote:then you need to repeat it and have a lok what happens...
@ JockoJocko wrote:Note: the NAS Ip when you use fvdw-sl console is 192.168.(0/1).252
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?
is not clear because if I recall well, only the first two cases were possible but maybe Fvdw added this last possibility.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.
The backup has failed. The script will exit to prevent data loss...
reboot -f
fdisk -l /dev/sda
I clicked on 'Edit -> Autocopy selection' - but then didn't know where the copy had been stored :dohfvdw wrote: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 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.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.
Return to Lacie Network Space vs2 and max version
Users browsing this forum: No registered users and 3 guests