Stuck pushing firmware to a completely empty 2Big Network v1

[BrainSuperGlue]

Hi,

I need some help. I've been trying to troubleshoot this for four hours....

OK, so completely blank hard disks in the 2Big Network V1 NAS, ergo no firmware. Drives were DBANed. Didn't realise the Lacie firmware was on the drives, anyway....

In a nutshell, in fvdw-sl console I select the UIMAGE file, I've chosen both (separate attempts) 1.1.1 and 1.1.4, the command window appears showing "waiting for uboot"

UIMAGE-26394-2BIG1-27-1-1-1-standalone
UIMAGE-26394-2BIG1-47-1-1-4-standalone

I turn on the NAS...
"waiting for uboot" just stays there and doesn't install the firmware.

So 1. Is it that in the console "IP address for NAS" is the IP that has already been set up the NAS? But how can I set the IP address of the NAS without firmware on the NAS to allow me to set the IP address? It's chicken and egg.....

or 2. Does the install process just listen for a polling packet and once the firmware is installed, the NAS IP address set in the console is the static one for the NAS that telnet then automatically connects to?

The NAS hardware was fine. Drive 1 spins up, drive 2 spins up. Of course it finds no firmware then the drives spin down and the network port blinks as normal.

Where am I going wrong?

Thanks

[BrainSuperGlue]

Just to confirm.

uPNP is enabled.
No firewall in way
2Big Network on same LAN as Windows PC tuning console
SMB1 has been enabled
Tried discovery in both Safe100 and Big modes

[fvdw]

Please read the info in this link https://plugout.net/viewtopic.php?f=7&t=2645

Especially the point having more then one ethernet card may be the issue why the console doesn't connect to the nas

[uelpenich]

There is a Windows issue if you have more than one network interface.
https://plugout.net/viewtopic.php?f=26&t=1402&p=22333&hilit=WinIPBroadcast#p22333
I use WinIPBroadcast.

[BrainSuperGlue]

OK, so good news.

Yes, my motherboard has two physical RJ45 connectors. I only use one and disabled the other but the console wouldn't find the NAS then. I realise now that virtual network interfaces (VirtualBox) would also need to be disabled leaving literally only one interface on the system.

However, with the one physical and one virtual enabled, I installed WinIPBroadcast.

The NAS was detected. Hurrah.

UBoot 1.1.1 got part of the way but UBoot 1.1.4 completed.

Had to check the DHCP server to see what IP it had given out.

Connected via web console with admin-nas, admin and I'm in.

Many thanks.

Now it's proved that the hardware is good, I'll create a static LAN IP for it and continue on.

I saw that the Orion bootloader for the 2Big VS1 doesn't have GPT enabled as standard. Looking through the forum I can't see how to update this Orion bootloader to have both MBR and GPT.

Is there are recommended link?

Thanks

[BrainSuperGlue]

Donation.

I've donated as given the 8.5MB/s transfer rate despite now all SSDs in the NAS and a gigabit route from 2BN through to PC, I need Samba 4.

Please can you add me to the donators list.

BTW how can I add 9k jumbo packet? I could on the stock firmware.

Thanks

[BrainSuperGlue]

There is definitely something odd going on with this NAS.

Using SMB1, was getting around 9MB/s
Using SMB2/3 it peaked at 11.5MB/s

Now it's down to 8KB/s... yes KB/s

This is with two 1TB SSDs in RAID1 -> Cat6 -> Gig switch -> Cat6 -> Gig interface PC

I appreciate this is an old NAS with a 400MHz processor but really?

Is that the bottleneck?

[fvdw]

Well it depends, if you are copying large files (> 100 MB) I expect you will get max around 15MB/s, cpoying many small file (few MB or smaller) it may drop to the kB range. This because of more i/o to write the file headers. The limited power of the cpu and rather small size of RAM are limiting the speed.
However another important point is correct partitioning the disk especially ssd's or disk using 4096 sector size. Ssd's also use this sector size if I remember correctly. The linux system uses 512 sector size. The disk firmware emulates a 512 sector size to be compatible. If partition start sector (count based on 512 bytes)is not on a boundary of a 4096 sector then writing speed will considerably suffer. (More info on the internet)
Maybe you should check out this point