Lacie 5Big Network 2 - doesn't boot properly after reboot -f

Lacie 5Big Network 2 - doesn't boot properly after reboot -f

Postby kasya82 » Sun Aug 23, 2020 7:07 pm

Hello! I also have Lacie 5big2 Network device
I've installed fvdw firmware, using: UIMAGE-3142-KIRKWOOD-171-standalone
It is installed OK until reboot -f
After I've typed reboot -f the device doesn't appeared in the network, It makes some activity with hdd-1 continuously, the HDD led blinks blue and it makes some cyclic sound but nothing else happening... So the first my question: after reboot -f how long it typically takes for first start? I'm waiting at least 10 minutes and the behavior is the same...
As I've found on that forum the such problem can occur, so I've made some testing to identify the issue and posted the results here. PS: I've made the new topic not to mix posts with other users with the similar problem, because some of them have found the issue and the solution but my case seems not exactly the same...

I also tried entering the following commands in u-boot console:
Code: Select all
version

Output:
Code: Select all
U-Boot 1.1.4 (Sep  8 2011 - 17:27:17) Marvell version: 3.4.16  LaCie 1.5.23


Code: Select all
printenv

Output:
Code: Select all
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=nand_mtd:0xa0000@0(uboot)ro,0xff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig);
bootm 0x2000000;
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
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
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
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
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
uboot_capabilities=gpt,lba64
start_lump=lump 3
pre_lump=lump 1
resetdisk=ide reset
bootdelay=0
boot_fail=lump
kernel_addr=0x800000
productType_env=BIG5_KW
primaryPart=6
secondaryPart=A
boot_usb=usb start;usbboot 0x800000 0:1;bootm;
resetFlag_env=0
bootcmd=run disk_disk
mtdids=nand0=nand_mtd
mtdparts=mtdparts=nand_mtd:1m(u-boot),16m(uImage),-(root)
boot_nand=setenv bootargs console=ttyS0,115200 ${mtdparts} root=/dev/mtdblock2 ro reset=${resetFlag_env} productType=${productType_env}; nboot ${kerne
l_addr} uImage; bootm ${kernel_addr}
boot_disk10=if disk ${kernel_addr} 5:${primaryPart}; then setenv rootfs /dev/sde7; else run boot_nand; fi
boot_disk9=if disk ${kernel_addr} 6:${primaryPart}; then setenv rootfs /dev/sdd7; else run boot_disk10; fi
boot_disk8=if disk ${kernel_addr} 1:${primaryPart}; then setenv rootfs /dev/sdc7; else run boot_disk9; fi
boot_disk7=if disk ${kernel_addr} 2:${primaryPart}; then setenv rootfs /dev/sdb7; else run boot_disk8; fi
boot_disk6=if disk ${kernel_addr} 3:${primaryPart}; then setenv rootfs /dev/sda7; else run boot_disk7; fi
boot_disk5=if disk ${kernel_addr} 5:${secondaryPart}; then setenv rootfs /dev/sde7; else run boot_disk6; fi
boot_disk4=if disk ${kernel_addr} 6:${secondaryPart}; then setenv rootfs /dev/sdd7; else run boot_disk5; fi
boot_disk3=if disk ${kernel_addr} 1:${secondaryPart}; then setenv rootfs /dev/sdc7; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 2:${secondaryPart}; then setenv rootfs /dev/sdb7; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 3:${secondaryPart}; then setenv rootfs /dev/sda7; else run boot_disk2; fi
boot_disk=if test ${resetFlag_env} -eq 0; then run boot_disk1; else run boot_disk6; fi
disk_disk=run boot_disk; setenv bootargs console=ttyS0,115200 root=${rootfs} ro reset=${resetFlag_env} productType=${productType_env}; bootm ${kernel_
addr};
ethaddr=00:D0:4B:93:09:04
eth1addr=00:D0:4B:93:09:05
ethact=egiga1
ipaddr=192.168.0.252
ncip=192.168.0.104
serverip=192.168.0.104
stdin=nc
stdout=nc
bootargs=console=ttyS0,115200 netconsole=6666@192.168.0.252/,6666@192.168.0.104/ root=/dev/sda7

Environment size: 3052/131068 bytes



Code: Select all
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7
ide reset
diskboot 0x800000 3:6


Output:
Code: Select all
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Port Multiplier found @ 0 0. Vendor: 11ab ports: 4
[0 0 3]: Enable DMA mode
  Device 3 @ 0 0 3:
Model: WDC WD40EFAX-68JH4N0                     Firm: 82.00A82 Ser#:      WD-WX5
2D104LKJ3
            Type: Hard Disk
dev_desc->blksz = 512
            Supports 48-bit addressing
            Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
Port Multiplier found @ 0 1. Vendor: 11ab ports: 4

Marvell>> diskboot 0x800000 3:6
diskboot 0x800000 3:6
## Valid EFI partition found ##

Loading from IDE device 3, partition 6: Name: gpt6
  Type: U-Boot
   Image Name:   linux-4.14.133-kirkwood-fvdw
   Created:      2019-07-17  12:55:42 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4776264 Bytes =  4.6 MB
   Load Address: 00008000
   Entry Point:  00008000
Marvell>>


And the last one:
Code: Select all
bootm

Output:
Code: Select all
## Booting image at 00800000 ...
   Image Name:   linux-4.14.133-kirkwood-fvdw
   Created:      2019-07-17  12:55:42 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4776264 Bytes =  4.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
bootargs from environment variables : console=ttyS0,115200 netconsole=6666@192.168.0.252/,6666@192.168.0.104/ root=/dev/sda7 cap=gpt,lba64

Starting kernel ...


And no other output after starting kernel... The device is doing something with HDD...

PS: Also I can say that the standard firmware working fine with this HDD. Also I can say that my device came to me with old 200 GB HDD on witch the 17.0 fvdw firmware was installed. Also I tried to install 18.1 firmware on that 200 GB HDD and the behavior is the same - it displays "starting kernel..." and then nothing happens except some blinking of HDD-1 led

Have anybody ideas what to do next?
kasya82
Donator VIP
Donator VIP
 
Posts: 5
Joined: Mon Aug 17, 2020 12:42 pm

Re: Lacie 5Big Network 2 - doesn't boot properly after reboo

Postby kasya82 » Sun Aug 23, 2020 7:17 pm

Here is the content of /dev/sda7/boot.log

Code: Select all
start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
5big2
kirkwood
 mount dev/pts
update dev nodes
booting using  root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Sun Aug 23 19:58:23 GMT+1 2020
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
5big2
rebootd-nwsp2
5big2
standbyd-nwsp2
start fan
starting php based setup routines step 1
 * Initialize the volatile db file...    [ OK ]
 * Starting udevd...                                     [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Found database configuration file...  [ OK ]
 * Updating Disks database...                    [ OK ]
 * Starting mount of volumes...
   - Mounting volume Vol-A:  [ OK ]
 * Finishing mount of volumes...                 [ OK ]
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ] 
 * Configuring LAN interface...


seems that it stucks on 'Configuring LAN interface...'
kasya82
Donator VIP
Donator VIP
 
Posts: 5
Joined: Mon Aug 17, 2020 12:42 pm

Re: Lacie 5Big Network 2 - doesn't boot properly after reboo

Postby fvdw » Sun Aug 23, 2020 7:30 pm

Which of the two LAN connectors are you using?
Should be LAN1
Also it could be LAN cable issue, however I would expect that in that case also installation would not have been possible when using standalone kernel.
Another possibility could be a corrupt file in firmware. Did you use a wired connection between pc and LAN to install the firmware?. If so repeat using a wired connection
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie 5Big Network 2 - doesn't boot properly after reboo

Postby kasya82 » Sun Aug 23, 2020 10:36 pm

Thank you for your reply! The problem was in using LAN 2 instead of LAN 1. I have reinstalled the firmware using LAN 1 and it started to work. Also I've used 100 mbit router to avoid using 1gbit ethernet to minimize the risk of errors and changed the cable to be completely sure.. SOLVED!
kasya82
Donator VIP
Donator VIP
 
Posts: 5
Joined: Mon Aug 17, 2020 12:42 pm


Return to Lacie 5big Network vs2

Who is online

Users browsing this forum: No registered users and 5 guests