fvdw-sl-console for ms windows install without removing HDD

[favroom]

will be this evening
I have some family visiting us right now

I succeeded in loading the firmware!
NMAP helped me in finding the correct ip address after booting the firmware...

Many thanks for your help!

[favroom]

Any suggestions on how to copy the content from my NWSP1 to my new NWSP2?
I am looking into rsync, but see some errors...

Code: Select all

rsync -e ssh user@192.168.2.30:/share/1000/public/video /share/1000/public/video/


Returns:
rsync: Failed to exec ssh: No such file or directory (2)
rsync error: error in IPC code (code 14) at pipe.c(84) [Receiver=3.0.9]
rsync: writefd_unbuffered failed to write 4 bytes to socket [Receiver]: Broken pipe (32)
rsync error: error in IPC code (code 14) at io.c(1532) [Receiver=3.0.9]

[Jocko]

Think you need to read the help page of the backup menu. ;)

E. Remote backup with a SSH access

You can't do remote backups using this menu. However, you can run remote backups from a shell in two configurations :

a)Backup is executed by a remote host that attempts an access to the SSH server (dropbear) of the NAS.
b)Backup is executed by the NAS that attempts an SSH access to a Remote Host.

Case "a", step to do :

on the Remote Host :

- Install a ssh client for linux (or window)

- Install rsync (if linux) or equivalent window (cwRync)

on the NAS,

- Install the RSA public key used by the Remote Host (see Help for SSH access menu)

on the Remote Host,

- use these command patterns (linux):

rsync -e "[yourclientSSH [options]]" -azv... source_on_the_remote_host root@youripnas:destination_on_the_nas (copy Host => Nas)

or

rsync -e "[yourclientSSH [options]]" -azv... root@youripnas:source_on_the_nas destination_on_the_remote_host (copy NAS => Host)



with :

- destination_on_the_nas (or source_on_the_nas) : full path on the nas (/share/1000/sharename/subfolder/...)

- yourclientSSH : fullname of your SSH client

- [options] : options for your SSH (usually path of your rsa key and SSH port used by dropbear)

Case "b", step to do :

on the Remote Host :

- Install a SSH server for linux (or window)

- Install rsync (if linux) or equivalent window (cwRync)

- Install the RSA public key of the NAS

on the NAS,

- either from a script or a Shell Terminal use these command patterns (linux):

rsync -e "/usr/bin/dbclient -p [yourSSH port] -i dropbear_rsa_host_key" -azv... source_on_the_nas login@youriphost:destination_on_the_remote_host (copy NAS => Host)

or

rsync -e "/usr/bin/dbclient -p [yourSSH port] -i dropbear_rsa_host_key" -azv... login@youriphost:source_on_the_remote_host destination_on_the_nas (copy host => Nas)



with :

- destination_on_the_nas (or source_on_the_nas): full path on the nas (/share/1000/sharename/subfolder/...)

- login : name authorized to do an SSH access by your remote host

- yourSSH port : SSH port used by the SSH server of the remote host



Note: if the remote SSH serveur uses the same port as SSH server of NAS, option"-e" is useless in this configuration, because the environment variable "RSYNC_RSH" is set

-With SSH access with key

RSYNC_RSH=/usr/bin/dbclient -p [SSH port] -i /rw_fs/etc/dropbear/dropbear_rsa_host_key

-With SSH access with password

RSYNC_RSH=/usr/bin/dbclient -p [SSH port]

RSYNC_RSH=/usr/bin/dbclient -p [SSH port]



So the command to use is simplified:

For exemple : rsync -azv... source_on_the_nas login@youriphost:destination_on_the_remote_host

ssh is an alias used openssh !
You must use dbclient as SSH client as written in the SSH server help page

[favroom]

Think you need to read the help page of the backup menu. ;)

E. Remote backup with a SSH access

You can't do remote backups using this menu. However, you can run remote backups from a shell in two configurations :

a)Backup is executed by a remote host that attempts an access to the SSH server (dropbear) of the NAS.
b)Backup is executed by the NAS that attempts an SSH access to a Remote Host.

Case "a", step to do :

on the Remote Host :

- Install a ssh client for linux (or window)

- Install rsync (if linux) or equivalent window (cwRync)

on the NAS,

- Install the RSA public key used by the Remote Host (see Help for SSH access menu)

on the Remote Host,

- use these command patterns (linux):

rsync -e "[yourclientSSH [options]]" -azv... source_on_the_remote_host root@youripnas:destination_on_the_nas (copy Host => Nas)

or

rsync -e "[yourclientSSH [options]]" -azv... root@youripnas:source_on_the_nas destination_on_the_remote_host (copy NAS => Host)



with :

- destination_on_the_nas (or source_on_the_nas) : full path on the nas (/share/1000/sharename/subfolder/...)

- yourclientSSH : fullname of your SSH client

- [options] : options for your SSH (usually path of your rsa key and SSH port used by dropbear)

Case "b", step to do :

on the Remote Host :

- Install a SSH server for linux (or window)

- Install rsync (if linux) or equivalent window (cwRync)

- Install the RSA public key of the NAS

on the NAS,

- either from a script or a Shell Terminal use these command patterns (linux):

rsync -e "/usr/bin/dbclient -p [yourSSH port] -i dropbear_rsa_host_key" -azv... source_on_the_nas login@youriphost:destination_on_the_remote_host (copy NAS => Host)

or

rsync -e "/usr/bin/dbclient -p [yourSSH port] -i dropbear_rsa_host_key" -azv... login@youriphost:source_on_the_remote_host destination_on_the_nas (copy host => Nas)



with :

- destination_on_the_nas (or source_on_the_nas): full path on the nas (/share/1000/sharename/subfolder/...)

- login : name authorized to do an SSH access by your remote host

- yourSSH port : SSH port used by the SSH server of the remote host



Note: if the remote SSH serveur uses the same port as SSH server of NAS, option"-e" is useless in this configuration, because the environment variable "RSYNC_RSH" is set

-With SSH access with key

RSYNC_RSH=/usr/bin/dbclient -p [SSH port] -i /rw_fs/etc/dropbear/dropbear_rsa_host_key

-With SSH access with password

RSYNC_RSH=/usr/bin/dbclient -p [SSH port]

RSYNC_RSH=/usr/bin/dbclient -p [SSH port]



So the command to use is simplified:

For exemple : rsync -azv... source_on_the_nas login@youriphost:destination_on_the_remote_host

ssh is an alias used openssh !
You must use dbclient as SSH client as written in the SSH server help page

Thanks for al these pointers. Seems a bit to hard for me right now. Lazy evening:)
I created a remote share and am using cp -R now:)

[Fivepints]

Hello all,

I thought id give this a go over this weekend. Since i have only windows experience then this seemed an ideal method, i decided not to use the stock disc (1TB) so removed this & replced it with a 2TB segate drive.

Followed the instructions carefully, took a few snpashots along the way but it failed. I tried again (remembering to delete any patritions there) & again it showed no signs of failing until i rebooted.

Ive read through this thread & see that some of the problems have been touched on so i tried once more, again only to find a constant flashing blue/red led.
Since i kept the original disk i decided to put it back & maybe try again later. Sadly the original disk is no longer recognised at this point.

End result so far is both drives only spin up but not a full spin if you follow, you can hear its not correctly booting/spinning up to full speed, then the flashing blue.red led.

Both drives once removed & hooked-up into my windows setup are then recognised with various partitions i assume were created by fvdw-sl?? on the 2TB drive with the 1TB drive being original partitions.

there is no data on either of the drives so no loss there but i am keen to get this working & i am happy to follow any instructions to assist in getting a more stable installation for us all...

Finally, I cannot use the U-boot console at present of course as it continues to wait to interrupt a drive thats not booting well enough, so i cannot try any of the other commands thats within this thread...

regards for now

[fvdw]

@fivepints

which nas do you have ?

If it is a nwsp2
did you damage the main board when pulling the HDD (some smd components are close to the HDD and can be ripped of when pulling out is not done carefully, see separate post on this warning viewtopic.php?f=11&t=1082

[fvdw]

one thought more

if your nwsp2 was a Lite version or a classic with GPT support then it might be possible that the fvdw-sl installer script did not remove all partitions, I posted an update of the script today.
If you have used the option new disk then it must have no partition table. You have to check presence of ms-dos partitions and GPT partitions and delete all of them manually using fdisk (ms-dos) and gdisk (GPT)

The fact that the original disk is also not booting is strange. The installer doesn't touch anything in the bootloader (U-boot). Red/blue flashing means that the the boot loader doesn't recognize the disk.

Finally, I cannot use the U-boot console at present of course as it continues to wait to interrupt a drive thats not booting well enough, so i cannot try any of the other commands thats within this thread...

The u-boot console doesn't need a disk to be booted, it even should work without a disk installed


To see if u-boot can see the disk you can switch off the nas and start the u-boot console in the fvdw-sl console.
The start the nwsp2 and connect to it with the u-boot console
In the u-boot console give the command

Code: Select all

ide reset

and see if it finds the disk
then

Code: Select all

ide part

to see partition information and which type

[Fivepints]

hello, thanks for such a speedy response....

first i have the NWSP2 version, & no damage to the pcb so far thankfully, im better with hardware than the software that runs it, and just for good measure once i have loosened all screws and removed leads i then lay it on my hand - hard drive down - so i can lift slightly the casing up and then slide it away... better to let gravity assist i say... those components are very small..

I made sure no partitions were present but i did this inside windows disk management?? hope that was ok and i did take a snapshot of this once i had completed my fist install - if you want to see what the results were i can post it.

as i've had this drive for some time i guessed it didnt support GPT so i chose accordingly on this.

Nice to know what the flashing led indicates but it also means there is no effective off switch & removing the power lead is the only option here, likewise when powering up having started fvdw-sl-console its a case of power lead back in..

this is where i'm up to right now with the 2TB drive installed & ready so i will try whats above & report back shortly..

regards

[fvdw]

I don't know what windows does with the partiton table, better use fdisk in the fvdw-sl console when having telnet access using the standalone kernel.

I made sure no partitions were present but i did this inside windows disk management?? hope that was ok and i did take a snapshot of this once i had completed my fist install - if you want to see what the results were i can post it.

You can post images on this form (upload attachment)

[Fivepints]

ok,

tried with the 2TB drive in situ... again nothing getting past the blue/red flashing led. i then put it back into windows so i can see whats there and i had removed all partitions in readiness to start over.

put this to one side while i retried the stock disc again, and again nothing getting past the flashing led.

I do start the console though in the hope i can issue those commands but this just says waiting for u-boot and command prompt just the flashing cursor.

so i decided to download the free for home use of partition master (before i came back here) & i snapped the partition as it is right now.
i used the free version as it works in windows 7/8 & others may want to see for themselves if the're watching this with the same issues..

Since i'd already done this i now see you'd prefer me to use fdisk from the console, this is my problem at present, i cant use u-boot to issue any commands yet or am i missing something? remember i am new to this kind of stuff but im willing to learn/ follow your lead..

regards

p.s. what does windows do to a drive when partitions are deleted? looking at it it shows an unpartitioned drive (im sure that is what your wanting)