Can't connect to NAS after installing fvdw. No DHCP

[fvdw]

If you want to flash uboot I suggest you read carefully the help page provided in the help drop down menu of the fvdw-sl console

Attached a zip archive with the file you will need (u-boot-5big2-spi-3416-1517.bin). It is a copy taken from a 5big2 with spi flash. The .md5 file is a file you could use to verify the md5sum of the .bin file to be sure it did go corrupt in the transfer process from this forum to your pc.
You have to put the u-boot-5big2-spi-3416-1517.bin and md5 file in the tftp folder of the fvdw-sl-console to be able to select it.

Be sure to select the u-boot-5big2-spi-3416-1517.bin file when you perform the flash

[Woodani]

Would disk one (sda) need to be a 2TB HDD or can I use a 4 TB as MBR and just lose the other 2TB of storage on it? I only ask because I already have the 5 4TB drives here and I'm not sure if I have a 2TB drive around or not.

I know this isn't the case but if this was your NAS would you take the risk upgrading the u-boot or leave it as a 4 x 4TB with the 2TB boot drive?

Thanks for posting the instructions I will read through them and make my decision later today.

[fvdw]

Yes you could use a 4 TB disk using only 2TB and ms-dos partition table. However I think the installer might have problems to automatic make such a disk but you could try.

If it was my 5big2 I would upgrade uboot

[fvdw]

You could also consider this method, a hybrid partition table.
https://plugout.net/viewtopic.php?f=4&t=1109&hilit=hybrid
Although a little complicated to setup

Note that your situation is not exactly the same. In that topict an uboot is installed that doesn't support GPT. Yours support GPT but only has 32 bits lba support and as such cannot address total space. I am unsure what your uboot will do with a hybrid partition table, will it use ms-dos table or the gpt ?? To let it work it must use the ms-dos table

[Woodani]

So I attempted to flash my u-boot but I'm getting an error that says: "could not retrieve md5 sum of flash file, abort". I downloaded the file again from this form but got the same results. Could you check the file on your side to make sure it didn't become corrupt when it was uploaded?

[fvdw]

did you put also the file u-boot-5big2-spi-3416-1517.md5 in the tftp folder ?

If yes, rename it to u-boot-5big2-spi-3416-1517.bin.md5

if no put it there and rename it

[fvdw]

I edited my last post

[Woodani]

Yes I put both the file named "u-boot-5big2-spi-3416-1517.bin" and the file named "u-boot-5big2-spi-3416-1517.bin.md5" in the "tftp" folder inside the "fvdw-sl-console-6-18-1-v2-29jul2019-32bits" folder along with the other u-boot files that were already there.

The file was already named "xx.bin.md5" not "xx.md5" when I extracted it from the archive. Did you mean that the otherway? As in it needs to end in .md5 and not .bin.md5?

[fvdw]

let me check some things, I will be back in a moment

[Woodani]

Ok. Thanks again for all your help.