Blue LED Blinking and no network access to 2Big Network

[Jocko]

I assume you stay the default options with lan setup: get IP from DHCP, If on your LAN DHCP is provided by your ISP box then DNS and gateway are automatically set and your NAS has Internet access.

[fvdw]

ok I'm sending

I do not see an error in this mbr. :scratch so the mysterie is not yet solved why uboot cannot read the partitions.
I hope u-boot is not corrupt, if so then only way to solve it is writing a new uboot to flash memory.
That is always an operation with a risk, if it fails then your nas will no longer be bootable and restoring will be difficult.
On the other hand several users did it with positive result. The fvdw-sl console supports writing to flash for 2big2.

Anyhow before considering that, please connect with ssh and give me the output of

Code: Select all

gdisk -l /dev/sda

PS I will be not available this evening

[Jocko]

Other point when you tried to patch the firmware, you use a patch for version 18.2 (which you will have to use when version 18.2 will be installed on the nas).

Currently you have to install the patch for version 18.1 to be able to upgrade to version 18.2. See topic viewtopic.php?f=7&t=3532

[Jocko]

And according with your last capture, your nas is not a 2big v2 but a 2 bignas which has better performance :thumbup

BUT do not try to flash uboot by using version for 2big2 !!!!

[PaaNooS]

ok I'm sending

I do not see an error in this mbr. :scratch so the mysterie is not yet solved why uboot cannot read the partitions.
I hope u-boot is not corrupt, if so then only way to solve it is writing a new uboot to flash memory.
That is always an operation with a risk, if it fails then your nas will no longer be bootable and restoring will be difficult.
On the other hand several users did it with positive result. The fvdw-sl console supports writing to flash for 2big2.

Anyhow before considering that, please connect with ssh and give me the output of

Code: Select all

gdisk -l /dev/sda

PS I will be not available this evening

login as: root
root@10.0.0.236's password:
root@fvdwsl-base:/ # gdisk -l /dev/sda

Code: Select all

GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 7814037168 sectors, 3.6 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            4096         1052671   512.0 MiB   8300  Linux filesystem
   2         1052672         2101247   512.0 MiB   8300  Linux filesystem
   3         2101248         3149823   512.0 MiB   8200  Linux swap
   4         3149824         3166207   8.0 MiB     8300  Linux filesystem
   5         3166208         4739071   768.0 MiB   8300  Linux filesystem
   6         4739072         4755455   8.0 MiB     8300  Linux filesystem
   7         4755456         5804031   512.0 MiB   8300  Linux filesystem
   8         5804032      7814037134   3.6 TiB     8300  Linux filesystem

root@fvdwsl-base:/ #

[Jocko]

Please to use the bbcode [code], when you post a output much more readable...

See https://plugout.net/faq.php?mode=bbcode

[PaaNooS]

And according with your last capture, your nas is not a 2big v2 but a 2 bignas which has better performance :thumbup

BUT do not try to flash uboot by using version for 2big2 !!!!

Sorry but I'm very confused
All these days we try with fvdw to install 2big2 firmware. Is this wrong ??

[Jocko]

our firmware uses the same configuration for 2bignas and 2big2. So no need to make a different installation according to the platform type.

an 2bignas does not use the same CPU (better performance) and has more ram.

About uboot, we have first to check if uboot for 2big2 may be used on a 2bignas platform.

[Jocko]

And if I remember rightly the bootloader options (boot cmd) has to be updated so that it can load our firmware which would explain your current behaviour. I need to talk with fvdw about this point.

[PaaNooS]

OK. So I'm waiting for good news.
For now I'd like to thank both of you
See you tomorrow