you wrote this
Oh. :doh I only use static IPs on the lan being used. There is no DHCP server active or router on this network.
I read through some earlier threads on the big5 v2 and it seems this may be a problem? I saw an earlier thread today fro 2015 where you said something about a DHCP server assigning the IP address. I will try find a router I can set up properly.
Although there is no dhcp server I would expect that the nas should boot but will give itself a 169.xxx.xxx.xxx address.
I did disconnect the network cable from the Big5. When I powered it up the big blue LED only flashed for about 3 seconds before going solid blue.
After it went solid I held the big blue button down for more than 5 seconds and nothing happened. I tried this about 5 times more but nothing happened. The unit does not power off. But your theory on the network seems like it might be a problem.
That means the firmware is loading and hangs
Otherwise it does seem to have something running or trying to when I boot it. The little blue light above the first drive indicates it is flashing like a hard drive being active. Also after it finishes the red lights above the other drive slots turn off. When I put in a blank drive the red lights never go off.
That is because the kernel seems to be loading and part of the initialization is done of the firmware. But it is unclear why the firmware hangs on configuring the lan interface.
I earlier made a video of the last install along with the log (before your last message). Even though it may be unneeded I attached it anyway along with the install log and photo.
I watched the videos, it seems that the firmware file and also the others is not fully uploaded, if I saw correctly the firmware file stopped after 97%. You can check in the tftpd32 log viewer how many bytes were transferred.
If that is so the firmware installation is incomplete although the installer mentions it is complete as the installer only installs the files it received. But also that is strange because if a tar archive is not fully transferred then an extraction error should be visible.
The installer log is too big for your screen so I can only see a part.
To get it you can use the tftp command
- Code: Select all
tftp -l /installer.log -r installer.log -p ip-of-your-pc
It will then be in the tftp folder of the console. You can then put it in a archive and post it here
For the moment it is a mystery why this install fails