Blue LED Blinking and no network access to 2Big Network

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 11:58 am

it might take some time to load firmware
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 12:00 pm

The only thing I can think of is that this hard disk has an issue.

To see were boot stops you can repeat the steps as posted earlier
https://plugout.net/viewtopic.php?f=27&t=3659&start=70#p37526
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 12:42 pm

So I've put the other hard disk into left bay
Repeat the steps from the beginning to install standalone kernel with no luck
Tried to install external kernel with no luck. Mention that when I try to load external kernel, front led is blinking blue from the time of power on until until the cmd window closes without any change to blinking mode

Can you explain me please what means steady red led and blinking blue led ??
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 12:57 pm

to avoid misunderstanding.

1. you have put the other disk in most lefthand slot, nas is switched off
2. installed the fvdw-sl firmware using fvdw-sl console and using the instructions provided
meaning selected the dtandalone kernel, started the fvdw-sl-programs and selecvted install firmware etc..
3. The install was completed successful
4. you switched of the nas with poweroff -f in the telnet windwo
5. You switched on the nas
6. the front led color becomes ?? please specify

with external kernel
E1. you used the fvdw-sl console option load and start external kernel, your nas is switched off
E2. you selected the kirkwood kernel in sub folder firmware/kirkwood
E3. you waited till cmd windows mentioned waiting for uboot
E4. you powered on your nas
E5. the front becomes , please specify

A red front led means , the device con not find a disk
A blue led blinking in regular pattern means it is trying loading kernel and firmware
A solid blue led means ready with boot

About red led sometimes we have seen that a unstable power supply was responsible for not able to detect a disk.
But because you can access the disk using standalone kernel it is unlikely in your case

I am sorry that you experience these problems but something seems to be wrong with this nas.
As last resort we can try to have a look at the bootloader uboot, the fvdwl console has also an option to open a uboot cmd window. But lets first verify the above.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 1:15 pm

fvdw wrote:to avoid misunderstanding.

1. you have put the other disk in most lefthand slot, nas is switched off
2. installed the fvdw-sl firmware using fvdw-sl console and using the instructions provided
meaning selected the dtandalone kernel, started the fvdw-sl-programs and selecvted install firmware etc..
3. The install was completed successful
4. you switched of the nas with poweroff -f in the telnet windwo
5. You switched on the nas
6. the front led color becomes ?? please specify


6. solid red
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 1:20 pm

fvdw wrote:to avoid misunderstanding.

with external kernel
E1. you used the fvdw-sl console option load and start external kernel, your nas is switched off
E2. you selected the kirkwood kernel in sub folder firmware/kirkwood
E3. you waited till cmd windows mentioned waiting for uboot
E4. you powered on your nas
E5. the front becomes , please specify


E5. blinking blue
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 1:24 pm

ok thank you

lets have a look at the boot loader

power off the nas , select in fvdw-sl console the action u-boot console
Wait for the window waiting for u-boot
Start your nas
You should get a prompt like this
marvell>>

At this prompt give as command
Code: Select all
printenv

post the output (the cmd window support copying tekst, right click on top bar)
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 1:35 pm

provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter


Code: Select all
Marvell>> printenv
printenv
bootargs=console=ttyS0,115200
bootcmd=run nexus_boot; run legacy_boot
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
netmask=255.255.255.0
uboot_capabilities=gpt,lba64
start_lump=lump 3
pre_lump=lump 1
resetdisk=ide reset
boot_fail=lump
loadaddr=0x800000
console=console=ttyS0,115200
kernel_addr=${loadaddr}
mtdids=nand0=nand_mtd
mtdparts=mtdparts=nand_mtd:1m(u-boot),16m(uImage),-(root)
disk_list=0 1
legacy_set_rootfs=if test $boot_disk -eq 0; then rootfs=/dev/sda7; elif test $bo
ot_disk -eq 1; then rootfs=/dev/sdb7; fi
legacy_nand_bootargs=setenv bootargs ${console} reset=${resetFlag_env} root=/dev
/mtdblock2;
legacy_nand_boot=echo Booting legacy NAND installer...; if nboot ${loadaddr} uIm
age; then run legacy_nand_bootargs; bootm; fi
legacy_disk_bootargs=setenv bootargs ${console} reset=${resetFlag_env} root=${ro
otfs};
legacy_disk_boot=echo Booting legacy layout...; if test ${resetFlag_env} -ne 0;
then part_list=6; else part_list="A 6"; fi;for p in ${part_list}; do for boot_di
sk in ${disk_list}; do if disk ${loadaddr} ${boot_disk}:$p; then run legacy_set_
rootfs; run legacy_disk_bootargs; bootm; fi; done; done
legacy_boot=run legacy_disk_boot || run legacy_nand_boot
nexus_max_count=3
nexus_nv_part=3
nexus_inc_count=if test ${boot_count} -eq 0; then setenv boot_count 1; elif test
 ${boot_count} -eq 1; then setenv boot_count 2; else setenv boot_count ${nexus_m
ax_count}; fi
nexus_set_root=if test $saved_entry -eq 1; then root_part=5; else root_part=4; f
i
nexus_load_flags=ext2get ide ${boot_disk}:${nexus_nv_part} /ubootenv boot_count
saved_entry
nexus_save_flags=ext2set ide ${boot_disk}:${nexus_nv_part} /ubootenv boot_count
${boot_count}
nexus_load_image=ext2load ide ${boot_disk}:${root_part} ${loadaddr} ${image} &&
iminfo ${loadaddr}
nexus_uuid=ext2uuid ide ${boot_disk}:${nexus_nv_part}; boot_uuid=${uuid}; ext2uu
id ide ${boot_disk}:${root_part}; root_uuid=${uuid}
nexus_bootargs=run nexus_uuid; setenv bootargs ${console} boot=UUID=${boot_uuid}
 root=UUID=${root_uuid}
nexus_can_boot=test ${bootfail} -eq 0 -a ${countfail} -eq 0 -a ${button} -eq 0 -
a ${user} -eq 0
nexus_rescue_countfail=test ${boot_count} -ge ${nexus_max_count}
nexus_rescue_user=ext2get ide ${boot_disk}:3 /ubootenv rescue && test ${rescue}
-eq 1
nexus_rescue_bootargs=test -n ${bootfail} && setenv bootargs bootfail=${bootfail
} ${bootargs}; test -n ${countfail} && setenv bootargs countfail=${countfail} ${
bootargs}; test -n ${user} && setenv bootargs user=${user} ${bootargs}; test -n
${button} && setenv bootargs button=${button} ${bootargs}
nexus_nand_bootargs=setenv bootargs ${console} root=/dev/mtdblock2; if test -n $
{boot_disk}; then run nexus_uuid; setenv bootargs ${bootargs} boot=UUID=${boot_u
uid}; fi
nexus_boot_rescue=echo Booting Nexus rescue from NAND...; if nboot ${loadaddr} u
Image; then run nexus_nand_bootargs; run nexus_rescue_bootargs; bootm; fi
nexus_panic=boot_disk=; run nexus_boot_rescue
nexus_boot=test -n ${resetFlag_env} && button=${resetFlag_env}; for boot_disk in
 ${disk_list}; do echo Booting Nexus layout from disk ${boot_disk}...; countfail
=0; bootfail=0; user=0; if run nexus_load_flags; then run nexus_rescue_countfail
 && countfail=1; run nexus_set_root; image=/boot/uImage; run nexus_load_image ||
 bootfail=1; run nexus_rescue_user && user=1; if run nexus_can_boot; then run ne
xus_inc_count; run nexus_save_flags; run nexus_bootargs; bootm; bootfail=1; fi;
run nexus_boot_rescue; fi; done; bootfail=1; countfail=; user=;run nexus_panic
run_diag=yes
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/m
tdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
disaMvPnp=no
ethaddr=00:D0:4B:93:20:0D
ethmtu=1500
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
resetFlag_env=0
bootdelay=0
pcieTune=no
ethact=egiga0
ipaddr=10.0.0.252
ncip=10.0.0.77
serverip=10.0.0.77
stdin=nc
stdout=nc

Environment size: 4287/131068 bytes
Marvell>>
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 1:43 pm

this looks normal
give command
Code: Select all
ide reset
and post result
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 1:45 pm

Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter

Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (5)
Device 0 @ 0 0:
Model: WDC WD40EFRX-68N32N0 Firm: 82.00A82 Ser#: WD-WCC
7K6YY01DX
Type: Hard Disk
Supports 48-bit addressing
Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
PCIe SATA:ffffffff

Marvell>>
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

PreviousNext

Return to Lacie 2Big Network vs2

Who is online

Users browsing this forum: No registered users and 6 guests