New install - NS2 Classic

New install - NS2 Classic

Postby sarbirus » Thu Nov 19, 2020 3:43 am

So it's 3am and I have been trying to get this to work since yesterday. I have used the search, but can not find anything that matches my problem. But then again, sometimes knowing the right search terms are the key.

I am trying to install the fvdw-sl 6-18-1-v2 firmware onto my networkspace2 Classic.

I have checked that it can not support GPT, so have been selecting no to this during the install, and have been selecting no to a hard drive larger than 2tb (it is just a replacement 1tb drive I am trying to use)

Everything seems to work on the surface during the install... the only odd thing is when the telnet screen is on the destroying the mbr section, it does bring up a warning that it is going to change the format to GPT and the only option is to either exit, or select Y for yes... If Y and enter is not input, it goes ahead anyway.. but seems to proceed through the remaining stages fine.

Here is that message...

***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if
you don't want to convert your MBR partitions to GPT format!
***************************************************************

(side note - while writing this, I selected quit, and then ran the fvdw programs again, and second time round it does not complain of this, and seems to take longer on the section where it copies files, or this could be imagining it)

I continue past this...

Gets to the end, I key in the reboot -f when instructed.

At this point the NS2 shutsdown, rather than rebooting (LED goes off, hardrive spins down), so then I hit the power button (about 2 seconds, anything less and it just brings on the led for a second and it goes off and the drive does not spin up)

After a second or two, the hard drive spins up, a second or so later the LED rapidly blinks for about half a second.

Up until now, all seems well.

Try to use the fvdw-sl-assistant and it can not find the device, hit the auto scan button, still can't find it.

Try to visit the ip address of 192.168.1.252 which connects fine during the install... Nothing... Set the router up to assign that address to the NS2 mac address just in case that was a problem or conflict... still the same result.

If I go back into the console (closed down during reboot with other windows), I can go through the same processes again, and again without any hangups or errors.

Can not telnet into the NS2 after the reboot -f and restarting the device, connection times out.

If I leave the assistant running and keep scanning, the only time it can find the NS2 is when the kernal is first booted from the console and can see it all the way through to when I "reboot -f"

It almost seems like the format of the drive is being completely forgotten during the reboot.

I have donated tonight, double the suggested amount as this is a project that I really like the idea of, and want to unlock the other features, as I love upcycling old hardware rather than throwing it away.

Please help!
sarbirus
Donator VIP
Donator VIP
 
Posts: 15
Joined: Wed Nov 18, 2020 11:14 pm

Re: New install - NS2 Classic

Postby sarbirus » Thu Nov 19, 2020 3:52 am

Here is the output of a "Cat install.log" following installation but before a "Reboot -f"



fvdw-sl-installer log
tftpd ip address 192.168.1.245
getting required programs from tftp server 192.168.1.245
Dialog installed
xterm installed
mke2fs-ext3 present
gdisk present
Start fvdw-sl firmware installer version 4.0
cpuinfo= LaCie Network Space v2
selected nas type nwsp2 platform kirkwood
selected disk /dev/sda
gpt support bootloader selected no
selected partion table type msdos
Deleting old msdos partiton table
deleting msdos partition succeeded

create new partiton table
create ms-dos partiton table
max cylinder 121601
ms-dos partiton scheme disk last cylinder 121600 (-1)
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.


The number of cylinders for this disk is set to 121601.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)


Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-121601, default 1): Last cylinder or +size or +sizeM or +sizeK (9-121601, default 121601):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-121601, default 1): Last cylinder or +size or +sizeM or +sizeK (73-121601, default 121601):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-121601, default 1): Last cylinder or +size or +sizeM or +sizeK (137-121601, default 121601):
Command (m for help): Partition number (1-4): Hex code (type L to list codes): Changed system type of partition 3 to 82 (Linux swap)

Command (m for help): Command action
e extended
p primary partition (1-4)
Selected partition 4
First cylinder (1-121601, default 1): Last cylinder or +size or +sizeM or +sizeK (201-121601, default 121601):
Command (m for help): First cylinder (201-121600, default 201): Last cylinder or +size or +sizeM or +sizeK (209-121600, default 121600):
Command (m for help): First cylinder (201-121600, default 201): Last cylinder or +size or +sizeM or +sizeK (321-121600, default 121600):
Command (m for help): First cylinder (201-121600, default 201): Last cylinder or +size or +sizeM or +sizeK (337-121600, default 121600):
Command (m for help): First cylinder (201-121600, default 201): Last cylinder or +size or +sizeM or +sizeK (409-121600, default 121600):
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
creating ms-dos partiton table succeeded
format partition 5
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
52304 inodes, 208845 blocks
2088 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=213909504
7 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 37 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
formatting sda5 succeeded
writing kernel to partition 6
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
9328+1 records in
9328+1 records out
4776328 bytes (4.6MB) copied, 0.351500 seconds, 13.0MB/s
writing kernel to partition 6 succeeded
Getting firmware image from tftp server
firmware disk image uploaded succesfully\n
format partition 7
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
128520 inodes, 514080 blocks
5140 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
63 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
formatting sda7 succeeded
mounting partition succeeded
extracting firmware base files
tar: invalid magic
tar: short read
Adapting firmware image for nwsp2\n
Transfer of firmware correction from tfp server succeeded, starting pacthing of firmware image
mkdir: can't create directory '/fvdw-sl': File exists
etc/
etc/init.d/
etc/init.d/insert-modules.5big2
etc/init.d/insert-modules.2big2
etc/init.d/insert-modules.cloudbox
etc/init.d/insert-modules.nwsp2
etc/init.d/insert-modules.isp2
etc/init.d/insert-modules.nwspmax
etc/init.d/insert-modules.d2nw2
etc/init.d/insert-modules.2bignas
etc/init.d/insert-modules.wsp2
etc/platform
lib/
lib/modules/
lib/modules/4.14.133/
lib/modules/4.14.133/snd-usbmidi-lib.ko
lib/modules/4.14.133/videobuf-core.ko
lib/modules/4.14.133/rtl8187.ko
lib/modules/4.14.133/isofs.ko
lib/modules/4.14.133/snd-timer.ko
lib/modules/4.14.133/target_core_pscsi.ko
lib/modules/4.14.133/hid-samsung.ko
lib/modules/4.14.133/usb_f_mass_storage.ko
lib/modules/4.14.133/snd-seq-midi.ko
lib/modules/4.14.133/nbd.ko
lib/modules/4.14.133/rt2x00usb.ko
lib/modules/4.14.133/target_core_mod.ko
lib/modules/4.14.133/usblp.ko
lib/modules/4.14.133/zstd_decompress.ko
lib/modules/4.14.133/g_ether.ko
lib/modules/4.14.133/ftdi-elan.ko
lib/modules/4.14.133/hid-sunplus.ko
lib/modules/4.14.133/hid-monterey.ko
lib/modules/4.14.133/xxhash.ko
lib/modules/4.14.133/modules.builtin
lib/modules/4.14.133/hid-petalynx.ko
lib/modules/4.14.133/iscsi_target_mod.ko
lib/modules/4.14.133/rt2x00lib.ko
lib/modules/4.14.133/iscsi_tcp.ko
lib/modules/4.14.133/snd-seq-device.ko
lib/modules/4.14.133/lzo_compress.ko
lib/modules/4.14.133/rtlwifi.ko
lib/modules/4.14.133/rt2800usb.ko
lib/modules/4.14.133/hid-gyration.ko
lib/modules/4.14.133/snd-seq-midi-event.ko
lib/modules/4.14.133/usb_f_rndis.ko
lib/modules/4.14.133/macvlan.ko
lib/modules/4.14.133/ftdi_sio.ko
lib/modules/4.14.133/mtdram.ko
lib/modules/4.14.133/snd-seq.ko
lib/modules/4.14.133/mac80211.ko
lib/modules/4.14.133/usb-storage.ko
lib/modules/4.14.133/soundcore.ko
lib/modules/4.14.133/sg.ko
lib/modules/4.14.133/veth.ko
lib/modules/4.14.133/pl2303.ko
lib/modules/4.14.133/hid-belkin.ko
lib/modules/4.14.133/hid-cherry.ko
lib/modules/4.14.133/rtc-pcf8563.ko
lib/modules/4.14.133/rtl8192c-common.ko
lib/modules/4.14.133/snd.ko
lib/modules/4.14.133/cdrom.ko
lib/modules/4.14.133/libiscsi.ko
lib/modules/4.14.133/snd-pcm.ko
lib/modules/4.14.133/libcomposite.ko
lib/modules/4.14.133/modules.order
lib/modules/4.14.133/ums-sddr55.ko
lib/modules/4.14.133/rt2800lib.ko
lib/modules/4.14.133/hid-ezkey.ko
lib/modules/4.14.133/ehci-orion.ko
lib/modules/4.14.133/snd-rawmidi.ko
lib/modules/4.14.133/configfs.ko
lib/modules/4.14.133/xhci-hcd.ko
lib/modules/4.14.133/scsi_transport_iscsi.ko
lib/modules/4.14.133/g_mass_storage.ko
lib/modules/4.14.133/ehci-hcd.ko
lib/modules/4.14.133/u_ether.ko
lib/modules/4.14.133/cramfs.ko
lib/modules/4.14.133/block2mtd.ko
lib/modules/4.14.133/snd-pcm-oss.ko
lib/modules/4.14.133/usbserial.ko
lib/modules/4.14.133/hid-a4tech.ko
lib/modules/4.14.133/snd-usb-audio.ko
lib/modules/4.14.133/ums-jumpshot.ko
lib/modules/4.14.133/zr364xx.ko
lib/modules/4.14.133/bonding.ko
lib/modules/4.14.133/videobuf-vmalloc.ko
lib/modules/4.14.133/squashfs.ko
lib/modules/4.14.133/hid-logitech.ko
lib/modules/4.14.133/ums-freecom.ko
lib/modules/4.14.133/hid-chicony.ko
lib/modules/4.14.133/libiscsi_tcp.ko
lib/modules/4.14.133/target_core_iblock.ko
lib/modules/4.14.133/btrfs.ko
lib/modules/4.14.133/hid-apple.ko
lib/modules/4.14.133/rtl8192cu.ko
lib/modules/4.14.133/target_core_file.ko
lib/modules/4.14.133/rtl_usb.ko
lib/modules/4.14.133/snd-hwdep.ko
lib/modules/4.14.133/usb_f_ecm_subset.ko
lib/modules/4.14.133/tcm_loop.ko
lib/modules/4.14.133/snd-mixer-oss.ko
lib/modules/4.14.133/r8712u.ko
lib/modules/4.14.133/hid-pl.ko
lib/modules/4.14.133/hid-cypress.ko
lib/modules/4.14.133/pktgen.ko
lib/modules/4.14.133/udf.ko
lib/modules/4.14.133/sisusbvga.ko
lib/modules/4.14.133/udc-core.ko
lib/modules/4.14.133/mv_udc.ko
lib/modules/4.14.133/usbhid.ko
lib/modules/4.14.133/nlmon.ko
lib/modules/4.14.133/hid-sony.ko
lib/modules/4.14.133/ums-sddr09.ko
lib/modules/4.14.133/cfg80211.ko
lib/modules/4.14.133/modules.dep
lib/modules/4.14.133/michael_mic.ko
lib/modules/4.14.133/lzo_decompress.ko
lib/modules/4.14.133/phy-gpio-vbus-usb.ko
lib/modules/4.14.133/ums-datafab.ko
lib/modules/4.14.133/rt73usb.ko
lib/modules/4.14.133/usb_f_ecm.ko
lib/modules/4.14.133/sr_mod.ko
lib/modules/4.14.133/ums-alauda.ko
lib/modules/4.14.133/rtc-m41t80.ko
lib/modules/4.14.133/rt2500usb.ko
lib/modules/4.14.133/hid-microsoft.ko
lib/modules/4.14.133/zstd_compress.ko
lib/modules/4.14.133/wire.ko
lib/modules/4.14.133/mdc800.ko
correcting firmware image for nwsp2 succeeded\n
write default database to partition 5
uploading default database on partition 5 succeeded
extraction and installing of the default database on partition 5 succeeded
format partition 8 shared folder partition
formating partition 8 succeeded
create shared folder public on partition 8
Installation completed



I have not gone through this with a fine tooth comb, partly because I am not as much of a linux wiz as I would like to be, but have highlighted a couple of items which I think may be a problem, but that is just my lack of knowledge of how much impact these items would have.

I hope this helps.

Jon
sarbirus
Donator VIP
Donator VIP
 
Posts: 15
Joined: Wed Nov 18, 2020 11:14 pm

Re: New install - NS2 Classic

Postby fvdw » Thu Nov 19, 2020 7:54 am

Hi, sorry to hear that you have trouble with installing.
Lets see if we can find the cause
You mention this:
At this point the NS2 shutsdown, rather than rebooting (LED goes off, hardrive spins down), so then I hit the power button (about 2 seconds, anything less and it just brings on the led for a second and it goes off and the drive does not spin up)

After a second or two, the hard drive spins up, a second or so later the LED rapidly blinks for about half a second.

This not the normal behaviour of a nwsp2.
It should continue boot. There seems to something wrong with the bootloader (uboot).
Please try to connect to the nas using the uboot console of the fvdw-sl console.
When you have the marvell>> prompt give following commands and post output of each command (you can use copy paste in uboot console , right click on title bar of uboot console)
Code: Select all
ide reset
ide part
printenv
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: New install - NS2 Classic

Postby Jocko » Thu Nov 19, 2020 9:38 am

Hi

@fvdw
There is an amazing thing with the disk and outputs are not logical.
First it seems the disk used a former gpt partition table with its gtp table and its protective ms-dos partition
Found invalid GPT and valid MBR

but later in install log, the script did not detect that : only a ms-dos partition:
Deleting old msdos partition table
deleting msdos partition succeeded
and confirmed also when it tried to create a new one:
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
so after the deleting table step, the disk seems to be without any old partition table setting :scratch
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: New install - NS2 Classic

Postby sarbirus » Thu Nov 19, 2020 11:38 am

Thanks fvdw and Jocko

Really glad your responses were not "You fool, have you not read......" I could still be a fool and doing something daft though.

Here is the dump from those three commands Fvdw..

provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter
no lump receive; continuing
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>> ide part
ide part

Partition Map for IDE device 0 -- Partition Type: DOS

Partition Start Sector Num Sectors Type
1 128520 1028160 83
2 1156680 1028160 83
3 2184840 1028160 82
4 3213000 1950291000 5 Extd
5 3341520 1670760 83
6 5140800 128520 83
7 5397840 1028160 83
8 6554520 1946949480 83
Marvell>> printenv
printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=spi_flash:0x80000@0(uboot)ro,0x300000@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
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
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
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
start_lump=lump 3
resetdisk=ide reset
bootdelay=0
boot_fail=lump
kernel_addr=0x800000
productType_env=ASTON_KW
primaryPart=6
secondaryPart=A
resetFlag_env=0
bootargs=console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW
bootcmd=run disk_disk
boot_disk4=disk ${kernel_addr} 1:${primaryPart}; setenv rootfs /dev/sdb7;
boot_disk3=if disk ${kernel_addr} 0:${primaryPart}; then setenv rootfs /dev/sda7; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 1:${secondaryPart}; then setenv rootfs /dev/sdb7; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 0:${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_disk3; 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:8D:B2:89
ipaddr=192.168.1.252
ncip=192.168.1.245
serverip=192.168.1.245
stdin=nc
stdout=nc

Environment size: 1947/4092 bytes
Marvell>>
sarbirus
Donator VIP
Donator VIP
 
Posts: 15
Joined: Wed Nov 18, 2020 11:14 pm

Re: New install - NS2 Classic

Postby sarbirus » Thu Nov 19, 2020 12:19 pm

Just in case it helps narrow it down, I have just tried two other hard drives, a 500gb traditional hard drive, and a 120gb SSD, both do the same thing.

I guess this might indicate a problem with...
1 Something stupid I am doing
2 Something wrong with the bios/firmware/bootstrap of the NWS2
3 Something wrong with the hardware of the NWS2

I think it is probably number 1 or 2, as number 3 I would have thought would fail during installation?
sarbirus
Donator VIP
Donator VIP
 
Posts: 15
Joined: Wed Nov 18, 2020 11:14 pm

Re: New install - NS2 Classic

Postby fvdw » Thu Nov 19, 2020 4:13 pm

Looks ok
When in uboot console give commands
Code: Select all
ide reset
bootcmd
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: New install - NS2 Classic

Postby sarbirus » Thu Nov 19, 2020 5:53 pm

Thanks for the continued support, really appreciated.

Here is the output of those two commands in uboot.


*****
provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter
no lump receive; continuing
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>> bootcmd
bootcmd
Unknown command 'bootcmd' - try 'help'
Marvell>>

*******


Really interesting (I think) that bootcmd is not recognised.
sarbirus
Donator VIP
Donator VIP
 
Posts: 15
Joined: Wed Nov 18, 2020 11:14 pm

Re: New install - NS2 Classic

Postby sarbirus » Thu Nov 19, 2020 5:58 pm

But if I issue a command of "boot" (having typed in help, not through any knowledge!) (in the same window, having just processed the "ide reset" I get the following....


*******
Marvell>> boot
boot

** 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 ...

******

Still "no nas found, click scan button" following an "Auto Scan" in "fvde assistant"
sarbirus
Donator VIP
Donator VIP
 
Posts: 15
Joined: Wed Nov 18, 2020 11:14 pm

Re: New install - NS2 Classic

Postby fvdw » Thu Nov 19, 2020 8:26 pm

oops my fault
try this
Code: Select all
ide reset
run bootcmd


ps the command "boot" will not pass the boot arguments and as result kernel cannot load the root file system and firmware
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Next

Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: Bing Bot and 8 guests