Lacie 2bigNAS

[IAmTroy]

I have a Lacie 2bigNAS that was hit with a malware attack. I've been able to install the fvdw firmware on the drives using the KIRKWOOD-171_standalone kernel. I'm able to tftp the kernel, boot it, get a telnet session, partition, format and install the firmware (Kirkwood?). But upon rebooting, I am unable to connect to it either through Telnet or the web interface. Using clunc, I can get the Marvell>> prompt, but it seems to not be able to boot the Linux kernel on the disks. It is able to see the partitions when I issue: ide reset, then: ide part. And booting standalone KIRKWOOD kernels is no problems using tftp.

Any suggestions? I will point out this is also the diskless NAS that contains the Lacie kernel on the flash, but now has 2x 3TB drives. I've seen references to nexus_boot (?) when issuing printenv.

I am trying this using fvdw-sl 18-3.

Thanks.

[fvdw]

in which slot, seen from the back, did you install the disk with fvdw-sl firmware?
Also posting output of printenv command when being in uboot console may give some information if uboot setup is correct.

[fvdw]

If it is a 2bignas read this topic
https://plugout.net/viewtopic.php?f=27&t=3469#p34736

[IAmTroy]

in which slot, seen from the back, did you install the disk with fvdw-sl firmware?
Also posting output of printenv command when being in uboot console may give some information if uboot setup is correct.

I tried both slots, then right only, then left only. No joy in any configuration. I did notice that the left slot is being recognized as /dev/sda when booting the standalone kernel, so I've been using that one slot only the last couple times. I'll take a look at the printenv variables. I'm away from the machine right now, but will do that when I get back to it.

Appreciate the help.

[IAmTroy]

If it is a 2bignas read this topic
https://plugout.net/viewtopic.php?f=27&t=3469#p34736

Interesting. I'll take a look and see if this helps. Does the 18-3 installer include support for the 2bigNAS? Which version of firmware should I install for the 2bigNAS? Kirkwood (option 1)? Thanks for the help.

[fvdw]

yes 18-3bsupport a 2bignas, it has a kirkwood kernel. But the bootloader (uboot) setting must be adapted to let it boot from disk, see that topic that I mentioned in my previous post.

[IAmTroy]

OK thanks. I was able to install the firmware and edit the bootloader commands. It now appears the NAS is booting off the hard disk. When I keep the u-boot console open after the firmware install, it displays the Linux boot commands, then ends with:

Code: Select all

...
[   40.385335] udevd (1053): /proc/1053/oom_adj is deprecated, please use /proc/1053/oom_score_adj instead.
[   40.395042] udev: starting version 130
[   40.772859] synth uevent: /gpiochip0: failed to send uevent
[   40.772875] gpio gpiochip0: uevent: failed to send synthetic uevent
[   40.885470] synth uevent: /gpiochip1: failed to send uevent
[   40.885486] gpio gpiochip1: uevent: failed to send synthetic uevent
[   43.184284] random: crng init done
[   49.045306] EXT4-fs (sda8): warning: checktime reached, running e2fsck is recommended
[   49.619967] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: user_xattr,acl,nodelalloc]


It seems to be sitting here and I cannot telnet into it, or check the webpages for the device. I cannot even ping it. It looks to be close to starting though.

[fvdw]

you cannot keep uboot window open after firmware install, it close automatic after uploading the standalone kernel before connecting with telnet and installing firmware.Maybe you mean the telnet window or you dud something different then firmware install.
Please give some more infi on what you are doing otherwise it is difficult to help you.

After firmware install you should reboot the nas with as indicated by the installer. And be sure your system disk is in most left hand slot seen from the back.

[IAmTroy]

I open the u-boot console and then start the NAS. If I hit ENTER, I get the Marvell>> prompt. If I then type: reset, it restarts. I can keep the u-boot console open during this entire time and see the firmware loading on the NAS. From these boot messages, I see the hard drive partitions being mounted and the eth0 controller starting. However, it gets to mounting /dev/sda8, then hangs. If I remove the ethernet cable and then reinsert it, I get a message that says the ethernet is down, then that it is reestablished. So the NAS is awake and responding.

Could it be related to the netconsole option in the boot command?

Code: Select all

setenv bootcmd 'disk 0x800000 0:6 ; setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7 ; bootm 0x800000;'

I've also loaded the standalone kernel and can mount /dev/sda7 manually. The boot.log looks like:

Code: Select all

start boot log
is a physical machine
detect and set platform
2bignas
kirkwood
UIMAGE-414133-KIRKWOOD-5
Current kernel: 4.14.133 #5 PREEMPT Thu Aug 10 15:38:37 CEST 2023
device 2bignas
family kirkwood
Arm: found a non valid system disk , setting it to sda
system disk = sda
 mount dev/pts
update dev nodes
booting using  root file system...
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 = 2bignas
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Mon Jan  1 12:00:00 UTC 2018
configuration partition is rightly mounted
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
2bignas
rebootd-nwsp2
2bignas
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 to be hanging when configuring the LAN interface. Do you know where this occurs in the firmware?

I'm not sure if this in my boot.log or one that was in the installed firmware.

[fvdw]

I see, I never used uboot in that way. What happens if you do not use uboot to reboot the nas. So witch it off and power it up and let it boot.
If uboot has locked the ethernet interface the firmware startup script may fail to initialize it.