Fail to install fvdw-sl

Re: Fail to install fvdw-sl

Postby Jocko » Sun Oct 04, 2015 8:15 pm

So that means that sda7 content is corrupted.

Open again a telnet window (or umount sda7 if it is still open)
mount sda5
Code: Select all
mkdir /sda5
mount /dev/sda5


upload the firmware image
Code: Select all
busybox tftp -r firmware/xfvdw-sl-16-0-nwsp2-11apr2015.img -l /sda5/tmp/fw.img -g ippc
(ippc -ip of your laptop)
check integrity of the image file
Code: Select all
busybox md5sum /sda5/tmp/fw.img
md5 should be '78d94e607b8dbb83b0206e40c597b767'

if it is ok copy it again on da7, sda1, sda2
Code: Select all
dd if=/sda5/tmp/fw.img of=/dev/sda7
dd if=/sda5/tmp/fw.img of=/dev/sda1
dd if=/sda5/tmp/fw.img of=/dev/sda2


Mount again sda7 and check if sbin is not empty
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Fail to install fvdw-sl

Postby fvdw » Sun Oct 04, 2015 8:24 pm

then we have found the problem

as alternative mentioned to the methos described by Jocko I suggest that you could use the image writer action in the fvdw-sl console. It lets you write a firmware image to sda1,2 and 7

Read the help file for this action, the folder where the image is has name "firmware" (without the quotes) assuming you use 5.5 version of the console
It will be an image for nwsp2 but don't worry your nas will boot with it, after first boot log in in the web interface of the firmware and install latest upgrade package for your 5big1
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Fail to install fvdw-sl

Postby jahotinc » Mon Oct 05, 2015 4:51 pm

Jocko's method worked !!

Code: Select all

(none) login: root
Password:
root@(none):/ # mkdir /sda5
root@(none):/ # mount /dev/sda5 /sda5
root@(none):/ # busybox tftp -r firmware/xfvdw-sl-16-0-nwsp2-11apr2015.img -l /sda5/tmp/fw.img -g 192.168.1.42
firmware/xfvdw-sl-16 100% |****************************************************************|   250M  0:00:00 ETA
root@(none):/ # busybox md5sum /sda5/tmp/fw.img
78d94e607b8dbb83b0206e40c597b767  /sda5/tmp/fw.img
root@(none):/ # dd if=/sda5/tmp/fw.img of=/dev/sda7
512000+0 records in
512000+0 records out
262144000 bytes (250.0MB) copied, 42.605638 seconds, 5.9MB/s
root@(none):/ # dd if=/sda5/tmp/fw.img of=/dev/sda1
512000+0 records in
512000+0 records out
262144000 bytes (250.0MB) copied, 42.342153 seconds, 5.9MB/s
root@(none):/ # dd if=/sda5/tmp/fw.img of=/dev/sda2
512000+0 records in
512000+0 records out
262144000 bytes (250.0MB) copied, 42.925450 seconds, 5.8MB/s
root@(none):/ # mkdir /sda7
root@(none):/ # mount /dev/sda7 /sda7
root@(none):/ # ls -al /sda7/sbin
total 3288
drwxr-xr-x    2 root     root          4096 Dec 30  2014 .
drwxr-xr-x   20 root     root          4096 Dec 30  2014 ..
lrwxrwxrwx    1 root     root            14 Dec 30  2014 adjtimex -> ../bin/busybox
-rwxr-xr-x    1 root     root         11212 Feb 20  2014 ata_id
-rwxr-xr-x    1 root     root          7924 Feb 20  2014 collect
lrwxrwxrwx    1 root     root            14 Dec 30  2014 devfsd -> ../bin/busybox
-rwxrwxr-x    1 root     root         52260 Jan  3  2008 dosfsck
-rwxr-xr-x    1 root     root        180900 Nov  6  2011 ethtool
lrwxrwxrwx    1 root     root            14 Dec 30  2014 fdisk -> ../bin/busybox
-rwxr-xr-x    1 root     root         89840 Dec 28  2012 fdisk-new
-rwxr-xr-x    1 root     root           518 Sep 29  2008 firmware.sh
-rwxr-xr-x    1 root     root         89508 Dec 28  2012 fixparts
-rwxr-xr-x    1 root     root         15952 Jan 11  2013 fw_printenv
lrwxrwxrwx    1 root     root            11 Dec 30  2014 fw_setenv -> fw_printenv
-rwxr-xr-x    1 root     root        260612 Dec 28  2012 gdisk
lrwxrwxrwx    1 root     root            14 Dec 30  2014 halt -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 hwclock -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 ifconfig -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 ifdown -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 ifup -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 init -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 insmod -> ../bin/busybox
-rwxr-xr-x    1 root     root           250 Jan 26  2014 is_esata
lrwxrwxrwx    1 root     root            14 Dec 30  2014 klogd -> ../bin/busybox
-rwxr-xr-x    1 root     root        631460 Jan 26  2014 ldconfig
lrwxrwxrwx    1 root     root            14 Dec 30  2014 loadkmap -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 logread -> ../bin/busybox
-rwxr-xr-x    1 root     root         26916 Aug  7  2012 losetup
lrwxrwxrwx    1 root     root            14 Dec 30  2014 lsmod -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 makedevs -> ../bin/busybox
-rwxr-xr-x    1 root     root        218096 Jan  3  2008 mdadm
-rwxrwxr-x    1 root     root         34012 Jan  3  2008 mkdosfs
lrwxrwxrwx    1 root     root            16 Dec 30  2014 mkfs.ntfs -> /usr/sbin/mkntfs
lrwxrwxrwx    1 root     root            14 Dec 30  2014 mkswap -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 modprobe -> ../bin/busybox
-rwxr-xr-x    1 root     root          6272 Mar 28  2013 mount.fuse
lrwxrwxrwx    1 root     root            15 Dec 30  2014 mount.lowntfs-3g -> /bin/lowntfs-3g
-rwxr-xr-x    1 root     root         84744 Jan 18  2014 mount.nfs
lrwxrwxrwx    1 root     root             9 Dec 30  2014 mount.nfs4 -> mount.nfs
lrwxrwxrwx    1 root     root            12 Dec 30  2014 mount.ntfs-3g -> /bin/ntfs-3g
lrwxrwxrwx    1 root     root            14 Dec 30  2014 nameif -> ../bin/busybox
-rwxr-xr-x    1 root     root         11800 Sep 29  2008 path_id
lrwxrwxrwx    1 root     root            14 Dec 30  2014 pivot_root -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 poweroff -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 reboot -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 rmmod -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 route -> ../bin/busybox
-rwxr-xr-x    1 root     root         24092 Feb 20  2014 scsi_id
-rwxr-xr-x    1 root     root        504084 May 25  2010 sleepmode_config
-rwxr-xr-x    1 root     root        512092 Jan 26  2014 sln
lrwxrwxrwx    1 root     root            14 Dec 30  2014 sulogin -> ../bin/busybox
lrwxrwxrwx    1 root     root             6 Dec 30  2014 swapoff -> swapon
-rwxr-xr-x    1 root     root         19180 Aug  7  2012 swapon
lrwxrwxrwx    1 root     root            14 Dec 30  2014 sysctl -> ../bin/busybox
lrwxrwxrwx    1 root     root            14 Dec 30  2014 syslogd -> ../bin/busybox
-rwxr-xr-x    1 root     root         90192 Oct 28  2013 test-udev
-rwxr-xr-x    1 root     root        108548 Oct 28  2013 udevadm
-rwxr-xr-x    1 root     root        104512 Oct 28  2013 udevd
-rwxrwxr-x    1 root     root         43944 Jan  3  2008 udevinfo
-rwxr-xr-x    1 root     root         59480 Feb  1  2014 udevstart
lrwxrwxrwx    1 root     root            14 Dec 30  2014 udhcpc -> ../bin/busybox
lrwxrwxrwx    1 root     root             9 Dec 30  2014 umount.nfs -> mount.nfs
lrwxrwxrwx    1 root     root             9 Dec 30  2014 umount.nfs4 -> mount.nfs
-rwxr-xr-x    1 root     root         26524 Feb 20  2014 usb_id
-rwxr-xr-x    1 root     root         14544 Feb 20  2014 vol_id
lrwxrwxrwx    1 root     root            14 Dec 30  2014 watchdog -> ../bin/busybox
-rwxr-xr-x    1 root     root         14324 Mar  4  2014 xxd
root@(none):/ #
root@(none):/ #


after this, i rebooted (reboot -f) and assitant found my nas at ip 152 (different ip than the used while installing). Web interface works also. I'm goig to try to update the firmware using web.
jahotinc
 
Posts: 35
Joined: Mon Apr 07, 2014 11:39 am

Re: Fail to install fvdw-sl

Postby jahotinc » Mon Oct 05, 2015 5:16 pm

Firmware upgrade finished ok (ver. 16.1) and the nas is working after a shutdown.

Thank you very much for your help and patience.

Next step is to add three more 1.5 Tb disks ... i'll follow the guide.

Do you know the reason for this problem? i have tried with 3 different disks so i think it is not a hardware problem ...
jahotinc
 
Posts: 35
Joined: Mon Apr 07, 2014 11:39 am

Re: Fail to install fvdw-sl

Postby Jocko » Mon Oct 05, 2015 5:17 pm

:thumbup

Note you can install directly version 16.1 for 5big1 (install version 16.0 for 5big1 is useless)
And in your case, you need to install the patch available in this topic viewtopic.php?f=7&t=2314
Do you know the reason for this problem? i have tried with 3 different disks so i think it is not a hardware problem ...
I don't know really but maybe you had a LAN issue and it corrupted the firmware image when fvdw-sl console uploaded it.
But it will be strange that occurs 3 times :scratch
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Previous

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: boerie and 8 guests