Fail to get an IP from DHCP server after installing fvdw-sl

[Draftmancorp]

You can install 17-0. Release of 18-0 will take still a while.
Read the install help file that is present for using fvdw-sl console to install the firmware. See here https://plugout.net/viewtopic.php?f=7&t=2691

Perfect, thanks. :doh

[Draftmancorp]

You can install 17-0. Release of 18-0 will take still a while.
Read the install help file that is present for using fvdw-sl console to install the firmware. See here https://plugout.net/viewtopic.php?f=7&t=2691

Hi :disapprove I'm not lucky.
I followed all the instruction in the help file "install_fvdw_sl_firmware_hlp".
Selected "UIMAGE-3142-KIRKWOOD-158-standalone".
U-boot transfer all perfectly then start telnet console.
Used the command "fvdw-sl-programs", chose 5Big2 and chose GPT table (and MS second time, is not so importanti becouse I use 2TB HDD, so when ask if i use HDD > 2TB i say no becouse the size of 2TB disk is something like 1.8TB).
All finish with Installation complete!
Then i give reboot -f and then no way :dontknow to find the ip, also with fvdw-sl-assistant. no nas found.
Only after installation finish the nas do a intermittent sound (try to share in attacchement).
If i start from begin and formatting HDD etc.. for the all process time there is no sound like this.

i performa a cat installer log:

Code: Select all

root@fvdw-sta-kirkwood:/ # cat installer.log
fvdw-sl-installer log
tftpd ip address 192.168.1.177
getting required programs from tftp server 192.168.1.177
Dialog installed
xterm installed
mke2fs-ext3 present
gdisk present
Start fvdw-sl firmware installer version 3.1

selected nas type 5big2 platform kirkwood
selected disk /dev/sda
gpt support bootloader selected yes
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 243201
ms-dos partiton scheme disk last cylinder 243200 (-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 243201.
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-243201, default 1): Last cylinder or +size or +sizeM or +sizeK (9-243201, default 243201):
Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-243201, default 1): Last cylinder or +size or +sizeM or +sizeK (73-243201, default 243201):
Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-243201, default 1): Last cylinder or +size or +sizeM or +sizeK (137-243201, default 243201):
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-243201, default 1): Last cylinder or +size or +sizeM or +sizeK (201-243201, default 243201):
Command (m for help): First cylinder (201-243200, default 201): Last cylinder or +size or +sizeM or +sizeK (209-243200, default 243200):
Command (m for help): First cylinder (201-243200, default 201): Last cylinder or +size or +sizeM or +sizeK (321-243200, default 243200):
Command (m for help): First cylinder (201-243200, default 201): Last cylinder or +size or +sizeM or +sizeK (337-243200, default 243200):
Command (m for help): First cylinder (201-243200, default 201): Last cylinder or +size or +sizeM or +sizeK (409-243200, default 243200):
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 28 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
9544+1 records in
9544+1 records out
4887024 bytes (4.7MB) copied, 0.297471 seconds, 15.7MB/s
writing kernel to partition 6 succeeded
Getting firmware image from tftp server
firmware disk image uploaded succesfully\n
Unpacking firmware image from archive
firmware disk image extracted succesfully\n
Adapting firmware image for 5big2\n
Transfer of firmware correction from tfp server succeeded, starting pacthing of firmware image
mounting firmware image succeeded
./
./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.wsp2
./etc/platform
./lib/
./lib/modules/
./lib/modules/4.6.6/
./lib/modules/4.6.6/videobuf-core.ko
./lib/modules/4.6.6/ehci-pci.ko
./lib/modules/4.6.6/isofs.ko
./lib/modules/4.6.6/hid-samsung.ko
./lib/modules/4.6.6/usb_f_mass_storage.ko
./lib/modules/4.6.6/usblp.ko
./lib/modules/4.6.6/xhci-pci.ko
./lib/modules/4.6.6/g_ether.ko
./lib/modules/4.6.6/ftdi-elan.ko
./lib/modules/4.6.6/hid-sunplus.ko
./lib/modules/4.6.6/hid-monterey.ko
./lib/modules/4.6.6/modules.builtin
./lib/modules/4.6.6/hid-petalynx.ko
./lib/modules/4.6.6/iscsi_tcp.ko
./lib/modules/4.6.6/hid-gyration.ko
./lib/modules/4.6.6/usb_f_rndis.ko
./lib/modules/4.6.6/ftdi_sio.ko
./lib/modules/4.6.6/mtdram.ko
./lib/modules/4.6.6/usb-storage.ko
./lib/modules/4.6.6/sg.ko
./lib/modules/4.6.6/pl2303.ko
./lib/modules/4.6.6/hid-belkin.ko
./lib/modules/4.6.6/hid-cherry.ko
./lib/modules/4.6.6/rtc-pcf8563.ko
./lib/modules/4.6.6/cdrom.ko
./lib/modules/4.6.6/libiscsi.ko
./lib/modules/4.6.6/libcomposite.ko
./lib/modules/4.6.6/modules.order
./lib/modules/4.6.6/ums-sddr55.ko
./lib/modules/4.6.6/hid-ezkey.ko
./lib/modules/4.6.6/ehci-orion.ko
./lib/modules/4.6.6/configfs.ko
./lib/modules/4.6.6/xhci-hcd.ko
./lib/modules/4.6.6/scsi_transport_iscsi.ko
./lib/modules/4.6.6/g_mass_storage.ko
./lib/modules/4.6.6/ehci-hcd.ko
./lib/modules/4.6.6/u_ether.ko
./lib/modules/4.6.6/cramfs.ko
./lib/modules/4.6.6/block2mtd.ko
./lib/modules/4.6.6/usbserial.ko
./lib/modules/4.6.6/hid-a4tech.ko
./lib/modules/4.6.6/ums-jumpshot.ko
./lib/modules/4.6.6/zr364xx.ko
./lib/modules/4.6.6/bonding.ko
./lib/modules/4.6.6/videobuf-vmalloc.ko
./lib/modules/4.6.6/squashfs.ko
./lib/modules/4.6.6/hid-logitech.ko
./lib/modules/4.6.6/ums-freecom.ko
./lib/modules/4.6.6/hid-chicony.ko
./lib/modules/4.6.6/libiscsi_tcp.ko
./lib/modules/4.6.6/btrfs.ko
./lib/modules/4.6.6/hid-apple.ko
./lib/modules/4.6.6/usb_f_ecm_subset.ko
./lib/modules/4.6.6/r8712u.ko
./lib/modules/4.6.6/hid-pl.ko
./lib/modules/4.6.6/hid-cypress.ko
./lib/modules/4.6.6/pktgen.ko
./lib/modules/4.6.6/udf.ko
./lib/modules/4.6.6/sisusbvga.ko
./lib/modules/4.6.6/udc-core.ko
./lib/modules/4.6.6/mv_udc.ko
./lib/modules/4.6.6/usbhid.ko
./lib/modules/4.6.6/hid-sony.ko
./lib/modules/4.6.6/ums-sddr09.ko
./lib/modules/4.6.6/modules.dep
./lib/modules/4.6.6/michael_mic.ko
./lib/modules/4.6.6/ums-datafab.ko
./lib/modules/4.6.6/usb_f_ecm.ko
./lib/modules/4.6.6/sr_mod.ko
./lib/modules/4.6.6/ums-alauda.ko
./lib/modules/4.6.6/rtc-m41t80.ko
./lib/modules/4.6.6/hid-microsoft.ko
./lib/modules/4.6.6/wire.ko
./lib/modules/4.6.6/mdc800.ko
./lib/modules/3.14.2/
./lib/modules/3.14.2/videobuf-core.ko
./lib/modules/3.14.2/ehci-pci.ko
./lib/modules/3.14.2/usb_f_mass_storage.ko
./lib/modules/3.14.2/readme.txt
./lib/modules/3.14.2/usblp.ko
./lib/modules/3.14.2/g_ether.ko
./lib/modules/3.14.2/ftdi-elan.ko
./lib/modules/3.14.2/iscsi_tcp.ko
./lib/modules/3.14.2/ftdi_sio.ko
./lib/modules/3.14.2/usb-storage.ko
./lib/modules/3.14.2/sg.ko
./lib/modules/3.14.2/pl2303.ko
./lib/modules/3.14.2/iscsi_trgt.ko
./lib/modules/3.14.2/cdrom.ko
./lib/modules/3.14.2/libiscsi.ko
./lib/modules/3.14.2/libcomposite.ko
./lib/modules/3.14.2/ehci-orion.ko
./lib/modules/3.14.2/configfs.ko
./lib/modules/3.14.2/scsi_transport_iscsi.ko
./lib/modules/3.14.2/g_mass_storage.ko
./lib/modules/3.14.2/ehci-hcd.ko
./lib/modules/3.14.2/usbserial.ko
./lib/modules/3.14.2/zr364xx.ko
./lib/modules/3.14.2/bonding.ko
./lib/modules/3.14.2/videobuf-vmalloc.ko
./lib/modules/3.14.2/libiscsi_tcp.ko
./lib/modules/3.14.2/btrfs.ko
./lib/modules/3.14.2/r8712u.ko
./lib/modules/3.14.2/pktgen.ko
./lib/modules/3.14.2/udc-core.ko
./lib/modules/3.14.2/mv_udc.ko
./lib/modules/3.14.2/modules.dep
./lib/modules/3.14.2/modules.dep.bb
./lib/modules/3.14.2/wire.ko
correcting firmware image for 5big2 succeeded\n
Writing firmware to partion 7
512000+0 records in
512000+0 records out
262144000 bytes (250.0MB) copied, 15.286475 seconds, 16.4MB/s
writing firmware file to partition 7 succeeded
writing firmware to partition 1
512000+0 records in
512000+0 records out
262144000 bytes (250.0MB) copied, 15.778588 seconds, 15.8MB/s
writing firmware file to partition 1 succeeded
writing firmware to partition 2
512000+0 records in
512000+0 records out
262144000 bytes (250.0MB) copied, 16.175152 seconds, 15.5MB/s
writing firmware file to partition 2 succeeded
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
root@fvdw-sta-kirkwood:/ #

I do this procedure with 1HDD in the 1st slot. all the other slot are empty.
The disk is a seagate unformatted 2TB.

[fvdw]

the disk must be in the most lefthand side slot (seen from the backside of the nas.

For the rest it seems you have done everything right
The ticking sound may indicate a disk problem.

What you could do is load the standalone kernel using fvdw-sl console, connect with telnet and mount sda7 and check the boot.log file. Maybe this gives info if the nas has performed firmware boot or not and if it has boot why it failed.
So in telnet client

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
cd /sda7
cat boot.log

[Draftmancorp]

the disk must be in the most lefthand side slot (seen from the backside of the nas.

For the rest it seems you have done everything right
The ticking sound may indicate a disk problem.

What you could do is load the standalone kernel using fvdw-sl console, connect with telnet and mount sda7 and check the boot.log file. Maybe this gives info if the nas has performed firmware boot or not and if it has boot why it failed.
So in telnet client

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
cd /sda7
cat boot.log

Yes, it is in the most left slot, the first one.
For the sound, i tryed to connect the HDD to a PC via sata->USB adapter and sems to format correctly, opened in explorer and transfered some files...ther's no ticking sound.
Ok i will try this step for earn more info from sda7

[Jocko]

Hi

Then i give reboot -f and then no way :dontknow to find the ip, also with fvdw-sl-assistant. no nas found.

Please to note the related daemon used to detect the nas starts with a delay after a rebooting (around 90''). This to be sure the nas got an Ip lease from the dhcp service on your LAN (in the other case the daemon will abort)

So you need to wait around this time and to scan again the lan with fvdw-sl assistant

[Draftmancorp]

Hi

Then i give reboot -f and then no way :dontknow to find the ip, also with fvdw-sl-assistant. no nas found.

Please to note the related daemon used to detect the nas starts with a delay after a rebooting (around 90''). This to be sure the nas got an Ip lease from the dhcp service on your LAN (in the other case the daemon will abort)

So you need to wait around this time and to scan again the lan with fvdw-sl assistant

I had wait for 15 minut left :-D.
I'm home.
Now I'm trying with a new HDD, if not work i perform a cat log on sda7

edit.: i'm not in a grid with router. I'm in a standalone grid, so if the NAS going in to dhcp, no one giv to it a ip...but i don't think is this a problem becouse i give ip to it witn telnet first procedure...right?

[Draftmancorp]

nope... whit a new HDD seagate 2tb open from original fresh plastic... is the same.
Installation complete, then no way to find nas.
So i performed log from sda7

...any bad news?

Code: Select all


root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cd /sda7
root@fvdw-sta-kirkwood:/sda7 # cat boot.log
start boot log
detect and set platform
5big2
kirkwood
UIMAGE-466-KIRKWOOD-7
Current kernel: 4.6.6 #7 PREEMPT Sun May 7 11:50:52 CEST 2017
5big2
 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...
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Wed Nov 16 12:00:00 GMT+1 2011
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
create temporary group file
configure loopback network interface
setting reboot and standby
5big2
rebootd-nwsp2
5big2
standbyd-nwsp2
start fan
starting php based setup routines step 1
root@fvdw-sta-kirkwood:/sda7 #


[fvdw]

No, nothing bad, but the log is incomplete there should follow more lines.
Are you sure that there is nothing more?

If there are no lines after starting php based based setup routines then the only thing I can think off is dat the firmware package was corrupt when writing it to disk. Normally a corrupted image archive should fail to extract.

If I remember well you had a similar problem in the past with downloading large files. We should compare md5sum of the firmware image. I am not at home right now but will come back to you later.

What you could do in the meantime is use the action write firmware image of the fvdw-sl console and write the firmware image again to sda7.
Be sure to use a wired connecting between your pc and your lan.

[Draftmancorp]

No, nothing bad, but the log is incomplete there should follow more lines.
Are you sure that there is nothing more?

If there are no lines after starting php based based setup routines then the only thing I can think off is dat the firmware package was corrupt when writing it to disk. Normally a corrupted image archive should fail to extract.

If I remember well you had a similar problem in the past with downloading large files. We should compare md5sum of the firmware image. I am not at home right now but will come back to you later.

What you could do in the meantime is use the action write firmware image of the fvdw-sl console and write the firmware image again to sda7.
Be sure to use a wired connecting between your pc and your lan.

Hi guise,
Yes i use only 2 cat6 cable with prosafe switch.
I've disabled windows firewall and other ethernet adapter in my pc.

I performed WRITE firware to disk with console as you suggest, and writo ONLY to sda7, not1 and not2 when it ask to me.
Ate reboot the same situation. no way to find nas so i performet cat sda7, this time sems so different.

Code: Select all

root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cd /sda7
root@fvdw-sta-kirkwood:/sda7 # cat boot.log
start boot log
detect and set platform
5big2
kirkwood
UIMAGE-466-KIRKWOOD-7
Current kernel: 4.6.6 #7 PREEMPT Sun May 7 11:50:52 CEST 2017
5big2
 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...
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Wed Nov 16 12:00:00 GMT+1 2011
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
create temporary group file
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... root@fvdw-sta-kirkwood:/sda7 #

I'm here waiting but sems it is stopped at last string * Configuring LAN interface... root@fvdw-sta-kirkwood:/sda7 #

[fvdw]

Which lan port are you using? (On the nas)