Try to Get a Disk Image of Drive of 2Big V2

[RedSun]

3rd SS.

[RedSun]

Another

[RedSun]

It appears to me, the box is indeed a 2big2. The kirkwood kernel boots fine. The HD has a MBR partition table. The sda7 partition has the necessary root system.

One question I get is that, there is only one HD. It has always been on the 1st slot, or the left side from the back. I believe that should be the 1st drive, or sda. But fvdm-sl considers it as sdb. Or it is just the way it is. It appears fvdm-sl boots.

I'm not sure why the box can't get an valid IP. I also used two other standalone routers. Always the same. No IP. No network connection.

[Jocko]

Ok

Some good news : partition table ok; bootloader detects the disk and the firmware starts (=> kernel image is ok)

But the firmware failed to set the LAN interface. This explains why you can not get an access to the NAS

Other point, after a fresh install it is not the expected result the firmware mount a data volume "Vol-B" but should be "Vol-A".

That would mean you did not plug the system disk is the right slot. This one is the first left slot when you look at the slot side of the NAS.

Before putting it in its right slot can you post

Code: Select all

mkdir /sda5
mount /dev/sda2 /sda5
grep '<disks>'  -A 22 /sda5/etc/nas_conf_db.xml
grep '<lan>'  -A 10 /sda5/etc/nas_conf_db.xml

So stop the nas, put the system disk on the right slot and remove all other disks. reboot and check if you detect the NAS on your LAN

[RedSun]

Ok

Some good news : partition table ok; bootloader detects the disk and the firmware starts (=> kernel image is ok)

But the firmware failed to set the LAN interface. This explains why you can not get an access to the NAS

Other point, after a fresh install it is not the expected result the firmware mount a data volume "Vol-B" but should be "Vol-A".

That would mean you did not plug the system disk is the right slot. This one is the first left slot when you look at the slot side of the NAS.

Before putting it in its right slot can you post

Code: Select all

mkdir /sda5
mount /dev/sda2 /sda5
grep '<disks>'  -A 22 /sda5/etc/nas_conf_db.xml
grep '<lan>'  -A 10 /sda5/etc/nas_conf_db.xml

So stop the nas, put the system disk on the right slot and remove all other disks. reboot and check if you detect the NAS on your LAN

As to the left or right slot, I installed fvdm-sl in the left slot. Then boot it in that slot. Since no boot, I put it in the right slot. I believe that boot log is from my last boot in the right slot. If I put it in the left slot, it should show the sda instead of sdb. Just to answer your question. Still no IP in the left slot.

[Jocko]

So issue no linked with the used slot

Check if you have really a DHCP service on your LAN according with this topic, you have a similar issue : http://plugout.net/viewtopic.php?f=27&t=3803&start=10

[RedSun]

The net mask shows 255.255.0.0. Is that a problem?

[RedSun]

So issue no linked with the used slot

Check if you have really a DHCP service on your LAN according with this topic, you have a similar issue : http://plugout.net/viewtopic.php?f=27&t=3803&start=10

That is certain. I can login into the router(s) and configure the router. This is how I find my NAS. I get about 5 NAS in my network, but not on at the same time.

I've also tried to reserve a static IP with the MAC address. But still the same.

[RedSun]

Here it is part of DHCP client table. Right now, the LaCie has an IP of 192.168.1.252. But it is not in DHCP client table. It is just connected to fvdm-sl box.

[Jocko]

fvdw-sl console does not use dhcp service but builds the nas ip (x.252) from the laptop ip

We go to enable the debug mode on the nas. so uncompressed the attached file in the folder tftp. You should get a new file 'globals.inc'

From the telnet window, do

Code: Select all

mv /sda7/etc/inc/globals.inc  /sda7/etc/inc/globals.inc.org
ls  /sda7/etc/inc/globals.*    (it should list only one file with .org as extension)
busybox tftp -r  globals.inc -l /etc/inc/globals.inc -g  YOURIP
ls  /sda7/etc/inc/globals.*    (it should now list two files with .org and .inc as extension)

replace YOURIP by the current ip of your laptop

Reboot the nas only if you have the 2 files
stop again the nas and get a new telnet window (repeat action "standalone kernel, load and start action"). When your are logged, do

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
cat /sda7/boot.log