plugout.net

I get both a LaCie 2Big NAS and a LaCie 2Big Network v2. I got the 2Big NAS work after some effort. But I still can't get the 2Big N V2 work. I have spent a lot of effort.

I first built the 2x HDs and copied the partitions according to the direction (Mijzelf) from Wiki. LaCie stock firmware. The box booted successfully. I was able to login to the system. So the build was a success. But I believe something was done to the built file systems. After the re-boot, I could not see the LaCie. The DHCP could not assign an IP to the box. When I mounted the HDs, I found the partitions to be different. This comes to a dead end.

Then I tried to install the latest fvdw-sl 6.18. I selected the correct Kirkwood kernel. The tftp and telnet both work well. I was able to install the fvdw-sl. I tried a single 160GB and 250GB HD. I selected MBR partition table since I'm not sure if my unit support GPT. Again after the reboot, the DHCP can't assign an IP. The ethernet cable goes dark.

My router is a ZyXEL. I have Buffalo, Seagate and WD NAS boxes from the same router. So I believe the router is not the problem.

I was able to login to the box after the first boot from the built HDs. So the ethernet port of the box works. I've done this trice.

Not sure what the issue is. At this point, I'd like to acquire a working HD or even get a disk image. Small size is just fine. I'd like to get this work. Not to throw it away as another electronic box.

Appreciate any help.

Hi

So you want to use Lacie firmware and we do not have what you asked.

Sorry

Jocko wrote:Hi

So you want to use Lacie firmware and we do not have what you asked.

Sorry

I can go either way. Not sure why the fvdm-sl won't work. Can't get an IP from DHCP.

Here is an observation or question. When I installed fvdm-sl, I selected MBR partition table since I was not sure if my 2Big Network v2 supports GPT. Today I removed that drive and found that it is still formatted with GPT. This explains why the box would not boot and find an IP.

Not sure if I did anything wrong, or there is a bug somewhere with the fvdm-sl installation.

Hi

Indeed it may happen fvdw-sl fails to delete the original partition table and on such cases the nas can not boot with our firmware.

What you can try is to delete before the gpt table and also the protective ms-dos table

Jocko wrote:Hi

Indeed it may happen fvdw-sl fails to delete the original partition table and on such cases the nas can not boot with our firmware.

What you can try is to delete before the gpt table and also the protective ms-dos table

I just installed fvdw-sl on another 160GB HD with MBR and no partition. Still the same. Can't find an IP from DHCP. The ethernet port tries from time to time. But never succeed.

Since the box boots with the kernel and U-boot, the box hardware and DHCP server both work. But somehow the fvdw-sl does not work.

Hi

We go to investigate if the firmware is really loaded on nas booting.

But before some questions :
- Are you sure you have a 2big nas v2.There are several 2big platform : 2big nas v1, 2big nas v2, 2bignas and 2bignas review which is a x86 platform and our firmware can not be used on it
- what kernel image file did you select ?

To investigate, we go to open a telnet console via fvdw-sl console, so switch off the nas,select this time the action "Standalone kernel, load and start" and following the intsructions . Then when you are connected with the root account, do

Code: Select all

gdisk -l /dev/sda
cat /proc/partitions
mkdir /sda7
mount /dev/sda7 /sda7
ls -a /sda7
cat /sda7/boot.log

It is surely a 2Big Network v2. See the screenshot of the boot screen from the original Lacie firmware. Again, after the first boot, it would not reboot again. Somehow the drive structure was changed after the first boot.

It is the standard Kirkwood kernel. It boots just fine and it went through all the tftp and telnet, and installed the fvdm firmware. I took a look of the hard drive and it has Linux partitions on the empty HD.

I'll take a look at the debugging you stated.

Here we go:

Second