plugout.net

Jocko wrote:Yes, you have to wait from completing synchronization because sdb will be used to restoring your data when sda (new disk without data on sda8) will be re-add in raid1 volume.

So synchronization has complete

Jocko wrote:you have to use putty (or web-console) on the other steps

From putty :

Code: Select all

login as: root
root@192.168.2.50's password:
root@Lacie-2big-NAS:/ # cd /rw_fs
root@Lacie-2big-NAS:/rw_fs # tar -czf /direct-usb/fvdw/back-mysda5.tgz etc
root@Lacie-2big-NAS:/rw_fs # chmod 666 /direct-usb/fvdw/back-mysda5.tgz
root@Lacie-2big-NAS:/rw_fs #


What have I to expect to see here ?

--EDIT--
I found the file "back-mysda5.tgz" into path \\LACIE-2BIG-NAS\fvdw (see attachment). This is it ?

--EDIT--
Used fvdw-sl console to install the firmware on the new disk but in last step telnet give the error "connection to 192.168.2.50/1080 refused"

So what can I do ?

Hi

Yes it is the expected archive (back-mysda5.tgz). Please to note I remove it from your last post because it contains some settings about user accounts(no one downloaded it before removing)

So I assume you got this error after running this action : "Do the action : "Standalone kernel, load and start". (Note : you have to select the kernel image: UIMAGE-3142-KIRKWOOD-171-standalone)"
In this case you should read this topic : viewtopic.php?f=7&t=2645

Jocko wrote:So I assume you got this error after running this action : "Do the action : "Standalone kernel, load and start". (Note : you have to select the kernel image: UIMAGE-3142-KIRKWOOD-171-standalone)"
In this case you should read this topic : viewtopic.php?f=7&t=2645

I've select "UIMAGE-3142-KIRKWOOD-171-standalone" into the path "\fvdw-sl-console-6-18-1-v2-29jul2019-32bits\tftp"
But use it to laptop with wifi, so I'll try later with ethernet. Maybe this is the problem

Jocko wrote:In this case you should read this topic : viewtopic.php?f=7&t=2645

I've tried everything
-with wifi
-with ethernet
-with antivirus disabled
-with firewall disabled
-with telnet security set to none
but every time the standalone kernel is not uploaded completely.
Some times ends to 89% or 93% but never to 100%

I'm stuck now

--EDIT--

If we suppose that I'm not interesting about old disk data, is there any way to install firmware to a new disk from scratch AND copy settings from the old disk AND set it to a working RAID1 after adding a second new disk ??

Finally I followed a different way

1. With a docking station I cloned old 3TB to new 4TB. So after cloning a had my data and my setting to a new 4TB disk set as sda in RAID1 Volume but showing only 3TB capacity
2. With Linux GParted Live extended new disk data partition (sd8) from (approximately) 3TB to 4TB
3. Last I had to put this disk to my NAS left slot and another new disk 4TB to right slot and wait complete synchronization

That's it !!
After some hours I had all my data and setting to larger capacity

BUT

I'm very disappointed because this is NOT a real RAID1 firmware.
Someone who choose to set a NAS to RAID1 is for data security. So when any disk fail, NAS MUST can boot with only one disk in any slot.