New NAS with new HD - best practice to install Alt-F

[Paulo Elifaz Andrielli]

Hi guys,

I got a brand new 320L, and a 4TB hard drive. HD already arrived, and 320L should come in a day or two.

I currently have a 323 revB, with a 2TB HD, which I'm going to make a secondary drive on the 320L. Basically, I would like to have 320 with 4TB drive, and all my files from old 2TB on it. And, of course, 320L running Alt-F.

What will be the best procedure to:

- Install Alt-F on brand new 4TB drive: should I format it with the stock firmware, and then, install from scratch? Can I copy the Alt-F folder from old one, OR use the settings saved from it?

- Copy 2TB drive to the new 4TB. Should I simply put it inside 320L, and starting the copy across the drives, or is it better to have both NAS running, and make this copy?

[]´s

Paulo

[ScDc]

Hi Paulo -

I would go with 320L-4TB+2TB, and you don't need an Alt-F folder on any of the drivers, just flash 320L with Alt-F firmware and you'll have enough functionality to move data around the drives (I think...).

Pros:

+ Single box

+ Using internal bus to move data around (via ssh command prompt), expecting throughput to be better than when ethernet, cables and switches are involved.

Cons:

- mismatching drives limit your RAID options. 

[Paulo Elifaz Andrielli]

Hi ScDc,

I think the same; having both on same NAS, and make the copy over command line. Better than having both NAS on same network (I believe).

Regarding NAS, I just have movies and series on it. Im not worried about losing the data (I download everything from Internet again... Hahaha... :-))

[]'s
Paulo
sent from Android

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/alt-f.
For more options, visit https://groups.google.com/d/optout.

[Paulo Elifaz Andrielli]

Unit just arrived!

However, Looks like it's not simple to migrate the data.....

The original firmware demands that the HD be formatted. So, I formatted the new one (4TB), an tried to attach the old one (with Alt-F folder, 2TB). This 2TB drive, DLink firmware does not recognize, and ask to format.

I even put only the 2TB drive there (so Alt-F can override the orginal firmware), and same thing: it understands that HD needs to be formatted. :-(

I believe the only way to migrate the data will be to have the 2 units on same network, and leave until next year to finishe (really,1,45TB of data).

[]´s

Paulo

[ScDc]

Why not to flash 320L with Alt-F first? Once your 320L system is under Alt-F you should be able to insert and access your 2TB as is, as well as setup 4TB.

[Paulo Elifaz Andrielli]

Man, you're a genius!!!

I'm thinking in a lot of things, but forgot this simply e one.....

Flashing it right now, and will format/check the 4TB drive. Then, I will connect the old one to see how it goes.

Will keep you posted.

PS: I believe, when I received the new device, I was somehow sticking to the original firmware.... don't know, new stuff, but looks like all the same things.... so, why not flash Alt-F directly? ;-)

[]´s

Paulo

2017-12-21 9:11 GMT-02:00 ScDc <ezak...@gmail.com>:

Why not flash 320L with Alt-F first? Once your 320L system us under Alt-F you should be able to insert and access your 2TB as is, as well as setup 4TB.

2017-12-19 6:37 GMT-02:00 Paulo Elifaz Andrielli <paulo...@gmail.com>:

Hi ScDc,

I think the same; having both on same NAS, and make the copy over command line. Better than having both NAS on same network (I believe).

Regarding NAS, I just have movies and series on it. Im not worried about losing the data (I download everything from Internet again... Hahaha... :-))

[]'s
Paulo
sent from Android

Em 19 de dez de 2017 06:33, "ScDc" <ezakha...@gmail.com> escreveu:

Hi Paulo -

I would go with 320L-4TB+2TB, and you don't need an Alt-F folder on any of the drivers, just flash 320L with Alt-F firmware and you'll have enough functionality to move data around the drives (I think...).

Pros:

+ Single box

+ Using internal bus to move data around (via ssh command prompt), expecting throughput to be better than when ethernet, cables and switches are involved.

Cons:

- mismatching drives limit your RAID options. 

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.

To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/alt-f.
For more options, visit https://groups.google.com/d/optout.

[Hooligan99]

And this is what I did:

https://groups.google.com/forum/#!searchin/alt-f/migrate%7Csort:date/alt-f/qjPt8BRCy60/bdApXZo_CwAJ

"assuming the same ALT-F versions on both units, to load up the settings and move the USB key with ALT-F on it, from a 323 rev B1 to a 320L/RE Rev Ax? Swap the drives and expect this to work?"

My Alt-f was on a USB key and it worked as expected. There were a couple of questions but they are covered in the Q&A after the fact...

Warren

[Paulo Elifaz Andrielli]

Yeah, I just faced that!

Alt-F from old HD was active, but I phisically swaped the drives, and it got the newest one (then I renamed the old Alt-F folder and made another boot, to be sure).

Now I'm copying the data over both HDs, using the command line (faster), and then, I will format the old HD as ext4, removing that old small partition that Dlink firmware does.

Again, I would like to thank @ScDc for enlightning me on that! I was preparing all the data to start making the copy until New Year.... now, I mus complete it by tonight! :-)

[]´s

Paulo

--

[ScDc]

Glad to be a help!

On Thursday, December 21, 2017 at 4:12:01 PM UTC+3, Paulo Elifaz Andrielli wrote:

Yeah, I just faced that!

Alt-F from old HD was active, but I phisically swaped the drives, and it got the newest one (then I renamed the old Alt-F folder and made another boot, to be sure).

Just keep in mind, that Alt-F _OS_ (firmware) is what you _flash _ your box with. It offers base functionality, enough to connect to the box using different protocols, and move files around. Alt-F _folder_ on the disk is extensions/utilities folder and "optional" to the base functionality. And, as João was explaining before, OS will considers Alt-F folder the _first_ one it finds when mounting the disks/file systems at startup.

[João Cardoso]

As manipulating the Alt-F folder has its tricks, the best is to use Packages->Alt-F, section "Packages Installed On". You can copy the current Alt-F folder to a new filesystem, and use it always in the future even if it is not the first one found, by disabling (or deleting if not currently in use) all others. Read that webUI online help (?)

Using an always plugged dedicated USB pen with a ext2/3/4 filesystem on it is indeed the best option, as having the Alt-F folder in a normal filesystem prevents some operations on it (such as unmounting, checking, etc).

It has the added benefice of diminishing the "risk" of disk spin up, although the flash pen life expectancy will be somehow reduced.

[Paulo Elifaz Andrielli]

Hummm..... so, I have a spare 8GB USB here that I can use....

After my activities from migrating data, can I simply go to this option, and ask to copy the Alt-F folder to USB drive, so it stays there? Since it's a copy, after doing that, I should remove the others from the HD filesystem using this command, right?

[]´s

Paulo

[Hooligan99]

That's where mine lives. After it was copied over, activated, and tested, I deleted the original and rebooted. Since then I have been making a deactivated copy any time I make a change in case the USB goes bad... periodically I change over to verify it is working as expected... I do this on all three dlinks...

[Paulo Elifaz Andrielli]

I just added a USB drive, and tried to copy the package. Looks like it was copied, and I set the folder as active.

However, the Transmission is not working (I checked the /var/lib/transmission/torrents folder on USB, and torrent files are not there, they are still on old place). And Tramsission log shows a lot of lines with this error, when starting it:

[2017-12-22 14:04:54.488] tr_crypto_utils OpenSSL error: error:24064064:lib(36):func(100):reason(100) (crypto-utils-openssl.c:334)

Is there anything else I need to do to re-enable them in USB?

[]´s

Paulo

2017-12-22 11:10 GMT-02:00 Hooligan99 <wq...@fullerton-quin.ca>:

That's where mine lives. After it was copied over, activated, and tested, I deleted the original and rebooted. Since then I have been making a deactivated copy any time I make a change in case the USB goes bad... periodically I change over to verify it is working as expected... I do this on all three dlinks...

--

[Paulo Elifaz Andrielli]

Correting, I cleaned the logs, and made another restart. It shows only that:

[2017-12-22 14:08:19.831] tr_crypto_utils OpenSSL error: error:24064064:lib(36):func(100):reason(100) (crypto-utils-openssl.c:334)
[2017-12-22 14:08:19.831] UDP Failed to set receive buffer: requested 4194304, got 327680 (tr-udp.c:84)
[2017-12-22 14:08:19.832] UDP Failed to set send buffer: requested 1048576, got 327680 (tr-udp.c:95)
[2017-12-22 14:08:19.833] tr_crypto_utils OpenSSL error: error:24064064:lib(36):func(100):reason(100) (crypto-utils-openssl.c:334)

[]´s

Paulo

[Paulo Elifaz Andrielli]

Forget the error. Just a reboot, and it worked like a charm! :-)

[]´s

Paulo