New install - NS2 Classic

[sarbirus]

No problem, it's a good learning process for me..

****************************************
Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode
Device 0 @ 0 0:
Model: WDC WD10EZEX-00BN5A0 Firm: 01.01A01 Ser#: WD-WCC3FPJ8S5ZS
Type: Hard Disk
Supports 48-bit addressing
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)

Marvell>> run bootcmd
run bootcmd

** Device 1 not available

Loading from IDE device 0, partition 6: Name: hda6
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
## 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

Starting kernel ...

********************************************************

Nothing found on search with with fvdw-assistant

[fvdw]

Odd..seems to boot normally
Please use the fvdw-sl console to load and start the kirkwood standalobe kernel and connect via telnet.
At the linux prompt give these commands

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7


Now post output if this command

Code: Select all

cat /sda7/boot.log

This will show if the nas has booted and if boot was complete or not

[sarbirus]

**************************
root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
cat: can't open '/sda7/boot.log': No such file or directory
root@fvdw-sta-kirkwood:/ #
**************************

[fvdw]

And what does the command

Code: Select all

ls -al /sda7

Give as output

[fvdw]

Ps do you have a nwsp2 or nwsp2max (2 disk device) ?
If it is a nwsp2max put the disk in the other slot and see if it boots

[sarbirus]

Lacie NetworkSpace 2 - Classic (with the heatsink on the processor pressed against the perforated metal base)

Here is the output from the "ls -al /sda7"

*********************************
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
cat: can't open '/sda7/boot.log': No such file or directory
root@fvdw-sta-kirkwood:/ # ls -al /sda7
total 15
drwxr-xr-x 5 root root 1024 Nov 20 17:57 .
drwxrwxrwt 13 root root 360 Nov 20 18:02 ..
drwxrwxrwx 3 root root 1024 Nov 20 17:57 etc
drwxr-xr-x 3 root root 1024 Nov 20 17:57 lib
drwx------ 2 root root 12288 Nov 20 17:57 lost+found
root@fvdw-sta-kirkwood:/ #

*********************************************

[fvdw]

Seems only correction files are installed and not the firmware itself. Do you use a wireless connection between PC and LAN?

[fvdw]

Looking more close to the installer log you posted I see this

formatting sda7 succeeded
mounting partition succeeded
extracting firmware base files
tar: invalid magic
tar: short read
Adapting firmware image for nwsp2\n

That means the firmware is not extracted and as result not written to sda7.
The firmware tar archive may have gone corrupt in the transfer to the nas. This may happen when using wireless connection between pc and LAN

[sarbirus]

Just out of interest, does this look right?

ls of the main root directory...


Pre Install having run a "Install fvdw-sl firmware" from console, but before running "fvdw-sl-programs"
*******************
root@fvdw-sta-kirkwood:/ #
root@fvdw-sta-kirkwood:/ # ls
bin fvdw-sl-programs lib proc sys
dev init linuxrc sbin usr
etc ip.txt mnt sda7 var
root@fvdw-sta-kirkwood:/ #


After install - when prompted to type "reboot -f"
******************
root@fvdw-sta-kirkwood:/ # ls
KERNELVERSION fvdw-sl installer.log proc sys
NAME fvdw-sl-installer-4-0.sh ip.txt programs.log usr
bin fvdw-sl-programs lib sbin var
dev fvdw-sl-programs.sh linuxrc sda5
devid.sh fvdw-sl-programs.txt menu.sh sda7
etc init mnt sda8
root@fvdw-sta-kirkwood:/ #

After reboot -f
Having typed "reboot -f"
the system shuts down instantly (not reboot, but shutdown and off"


Once I have powered it on again, and performed a "standalone kernal, load and start" from the console...
********************
root@fvdw-sta-kirkwood:/ # ls
bin etc init lib mnt sbin usr
dev fvdw-sl-programs ip.txt linuxrc proc sys var

I am probably way off base and it might be supposed to be like this.

[sarbirus]

Sorry I was experimenting with the previous post I just submitted...

All wired connection, no wifi, just a rackmounted 48 port switch between my pc and the networkspace2, with a router connected to the switch for dhcp and internet access... (and loads of other computers in the building)