Lacie 2bigNAS

[IAmTroy]

When I boot the firmware without uboot, it hangs up. No telnet, no ping. I then have to use the standalone kernel and uboot to boot , then mount /dev/sda7 and read the boot.log file.

It looks like there is an issue in the laniffunc_configure.finc program. My boot.log file is updating if I edit the laniffunc_configure.finc program, so I know it's getting that far. But it appears to not be completing this step. Seems to be getting caught at the line:

Code: Select all

 if (mwexec("/sbin/udhcpc -b -i " . escapeshellarg($lanif) . " -s {$g['etc_path']}/api/api_dhcpc.php dhcpdCbScript -hostname='{$config['system']['hostname']}'") !=
                                echo "cannot start udhcpc process.\n";
                                return FAIL_E;                                                                       
                        }                   

If I comment out this line, it appears to boot further, but still no network access. I'll keep looking.

[fvdw]

do you have a dhcp server active in your lan?
If not, then getting an ip by dhcp the firmware will fail (the standalone kernel assign some ip manual if dhcp fails).

ps the lan configuration script is ok, it is used for all nas types, I uave a 2bignas myself and it works without an issue

[IAmTroy]

do you have a dhcp server active in your lan?
If not, then getting an ip by dhcp the firmware will fail (the standalone kernel assign some ip manual if dhcp fails).

ps the lan configuration script is ok, it is used for all nas types, I uave a 2bignas myself and it works without an issue

Thanks. I only have the 2BigNAS and a Windows PC connected to a switch and the switch should be providing the DHCP address. I'll keep checking.

[fvdw]

If you enable a dhcp server on your pc it should work.
If there is no dhcp server the firmware will try to get an ip forever, the character @ that you see in the boot.lig. Means dhcp request time out and a new request is sent.

[IAmTroy]

I managed to get it working. It seems my network switch is not providing a dhcp server, so the Lacie would assign a random IP address to the NAS using the format 169.254.xxx.xxx. I was never able to find the fvdw server using fvdw-sl-assistand as the span of IP addresses was too long.

I edited the IPAddr file in the finc directory to provide an address of 169.254.193.xxx instead of the default 169.254.xxx.xxx. This was then able to be found using fvdw-sl-assistant. I'll be placing this device on a different network that uses a DHCP server, but I wanted to get it working before I moved it.

Thanks so much for your help on this. I will be donating to this worthwhile project!

[fvdw]

glad to hear you got it working and thank you for your donation. We prefer to get an ip from a dhcp server as at first time boot it is not possible to know which ip pool is used on the lan. After first boot succeds the user can set a static ip iso automatic using the webinterface of the firmware. Maybe we should add an option during install to set an static ip.