plugout.net

by **tbn69** » Wed Apr 16, 2014 9:50 pm

Hello

Since few weeks i try to replace a 2 To disk on my Network space vs2 classic : the old one is die.. i found your site and was very impatient to try !
I try first with the fvdw-sl-console and firmware 15.1 and all was working well in the script but at the end of the process, when i reboot the box, i cannot browse or ping it.....

So i read some posts and try version 11.0 with manual installation. After experienced the disk block size issue on a USB/SATA enclosure (block size was 4096) i connect directly on a sata port and performed installation, but with the same results as above.
I have flashed the u-boot to have GPT partition support and retry install with console...same result

So now i don't know what is wrong on my disk. Below is the Fdisk result command
I think about the MBR block : perhaps i have to wrote one on the disk ?

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 9 72 514080 83 Linux
/dev/sda2 73 136 514080 83 Linux
/dev/sda3 137 200 514080 82 Linux swap
/dev/sda4 201 243201 1951905532+ 5 Extended
/dev/sda5 209 312 835380 83 Linux
/dev/sda6 321 328 64260 83 Linux
/dev/sda7 337 400 514080 83 Linux
/dev/sda8 409 243201 1950234772+ 83 Linux

Thanks to give me some ways to troubleshoot my Nas.
Regards
Thierry (From France, witch can explained my poor English)

by **fvdw** » Wed Apr 16, 2014 9:58 pm

probably your disk is fine and the firmware is running.
Which ip address did you use to pint it and did you try to use the fvdw-sl assistant to find your nas in the LAN ?
viewtopic.php?f=7&t=1488
This will show if the nwsp2 is visible in the network and specify the ip to use

If it is not present we can try following.
We can check if the nas loaded the firmware partially or not. Switch off the nwsp2 after you have tried to boot.
Now load the standalone kernel.
In the telnet client mount sda7

Code: Select all: mkdir sda7 mount /dev/sa7 /sda7

change to /sda7 folder and list content of the directory

Code: Select all: cd /sda7 ls -al

if the nas has tried to load the firmware there should be a file with name boot.log
if so pint the content and post the output here

Code: Select all: cat boot.log

by **tbn69** » Wed Apr 16, 2014 10:50 pm

Thanks for your quick answer :
I already try fvdw-sl assistant but nothing found, even a network scanner can't find it.

No boot.log created...
root@(none):/sda7 # ls -al
total 96
drwxr-xr-x 20 root root 4096 Feb 18 2014 .
drwxr-xr-x 13 root root 0 May 4 19:34 ..
lrwxrwxrwx 1 root root 20 Feb 18 2014 .mldonkey -> /share/1000/mldonkey
drwxr-xr-x 2 root root 4096 Feb 18 2014 bin
drwxr-xr-x 2 root root 4096 Feb 18 2014 bin_cab
drwxr-xr-x 2 root root 4096 Sep 25 2013 boot
drwxrwxrwx 2 root root 4096 Feb 18 2014 clunc
drwxr-xr-x 3 root root 12288 Feb 18 2014 dev
drwxrwxrwx 15 root root 4096 Jan 27 2014 etc
drwxr-xr-x 4 root root 4096 Jan 28 2014 lib
lrwxrwxrwx 1 root root 11 Feb 18 2014 linuxrc -> bin/busybox
drwx------ 2 root root 16384 Jan 3 2008 lost+found
drwxr-xr-x 3 root root 4096 Feb 18 2014 mail
drwxr-xr-x 2 root root 4096 Aug 27 2008 nowhere
drwxr-xr-x 7 root root 4096 Feb 18 2014 opt
drwxrwxrwx 2 root root 4096 Mar 5 2011 proc
drwxr-xr-x 2 root root 4096 Jan 3 2008 root
drwxr-xr-x 2 root root 4096 Feb 18 2014 sbin
drwxrwxrwx 2 root root 4096 Mar 5 2011 share
drwxrwxrwx 2 root root 4096 Mar 5 2011 sys
drwxr-xr-x 22 root root 4096 Feb 18 2014 usr
drwxr-xr-x 2 root root 4096 Mar 9 2012 var
root@(none):/sda7 #

by **fvdw** » Thu Apr 17, 2014 9:12 pm

then the only thing I can think off that the kernel is not loading.
We can try to boot the nas using the option load external kernel in the fvdw-sl console
Unpack the kernel in attached zip archive and put it in the tftp folder of the fvdw-sl console and select this kernel when you use the option load external kernel. If this makes the nas boot then the problem is that the writing the kernel to sda6 didn't work or something is wrong with your bootloader

by **tbn69** » Wed Apr 23, 2014 7:10 pm

Just tested now, but the nas isn't accessible after loading external kernel with u-boot process...
So perhaps an issue with Nas Firmware ?

by **fvdw** » Wed Apr 23, 2014 8:16 pm

strange, the fact that you could load the standalone kernel indicates that in principle the processor seems to be ok, the fact that you could install the firmware using fvdw-sl console proves that the disk interface works ok.

We need to check the content of the partitions sda1, sda2, sda5 and sda7.
So load the standalone kernel and create folders sda1, sda2, sda5 and sda7

Code: Select all: mkdir /sda1

mount each partition

Code: Select all: mount /dev/sda1 /sda1

and list the content

Code: Select all: ls -al /sda1

post the output
repeat for sda2, sda5 and sda7

for sda5 also post the dir listing of the folder /etc inside /sda5

ps you must perform this using the standalone kernel to be sure that that kernel access all partitions correctly

by **tbn69** » Wed Apr 23, 2014 9:13 pm

Below the results
Hope you can find something wrong that can explain why firmware isn't loaded..

Code: Select all: root@(none):/ # ls -al /sda1 total 96 drwxr-xr-x 20 root root 4096 Feb 18 2014 . drwxr-xr-x 14 root root 0 May 11 17:41 .. lrwxrwxrwx 1 root root 20 Feb 18 2014 .mldonkey -> /share/1000/mldonkey drwxr-xr-x 2 root root 4096 Feb 18 2014 bin drwxr-xr-x 2 root root 4096 Feb 18 2014 bin_cab drwxr-xr-x 2 root root 4096 Sep 25 2013 boot drwxrwxrwx 2 root root 4096 Feb 18 2014 clunc drwxr-xr-x 3 root root 12288 Feb 18 2014 dev drwxrwxrwx 15 root root 4096 Jan 27 2014 etc drwxr-xr-x 4 root root 4096 Jan 28 2014 lib lrwxrwxrwx 1 root root 11 Feb 18 2014 linuxrc -> bin/busybox drwx------ 2 root root 16384 Jan 3 2008 lost+found drwxr-xr-x 3 root root 4096 Feb 18 2014 mail drwxr-xr-x 2 root root 4096 Aug 27 2008 nowhere drwxr-xr-x 7 root root 4096 Feb 18 2014 opt drwxrwxrwx 2 root root 4096 Mar 5 2011 proc drwxr-xr-x 2 root root 4096 Jan 3 2008 root drwxr-xr-x 2 root root 4096 Feb 18 2014 sbin drwxrwxrwx 2 root root 4096 Mar 5 2011 share drwxrwxrwx 2 root root 4096 Mar 5 2011 sys drwxr-xr-x 22 root root 4096 Feb 18 2014 usr drwxr-xr-x 2 root root 4096 Mar 9 2012 var root@(none):/ # root@(none):/ # ls -al /sda2 total 96 drwxr-xr-x 20 root root 4096 Feb 18 2014 . drwxr-xr-x 13 root root 0 May 11 17:39 .. lrwxrwxrwx 1 root root 20 Feb 18 2014 .mldonkey -> /share/1000/mldonkey drwxr-xr-x 2 root root 4096 Feb 18 2014 bin drwxr-xr-x 2 root root 4096 Feb 18 2014 bin_cab drwxr-xr-x 2 root root 4096 Sep 25 2013 boot drwxrwxrwx 2 root root 4096 Feb 18 2014 clunc drwxr-xr-x 3 root root 12288 Feb 18 2014 dev drwxrwxrwx 15 root root 4096 Jan 27 2014 etc drwxr-xr-x 4 root root 4096 Jan 28 2014 lib lrwxrwxrwx 1 root root 11 Feb 18 2014 linuxrc -> bin/busybox drwx------ 2 root root 16384 Jan 3 2008 lost+found drwxr-xr-x 3 root root 4096 Feb 18 2014 mail drwxr-xr-x 2 root root 4096 Aug 27 2008 nowhere drwxr-xr-x 7 root root 4096 Feb 18 2014 opt drwxrwxrwx 2 root root 4096 Mar 5 2011 proc drwxr-xr-x 2 root root 4096 Jan 3 2008 root drwxr-xr-x 2 root root 4096 Feb 18 2014 sbin drwxrwxrwx 2 root root 4096 Mar 5 2011 share drwxrwxrwx 2 root root 4096 Mar 5 2011 sys drwxr-xr-x 22 root root 4096 Feb 18 2014 usr drwxr-xr-x 2 root root 4096 Mar 9 2012 var root@(none):/ # root@(none):/ # ls -al /sda5 total 36 drwxr-xr-x 7 root root 4096 May 4 17:29 . drwxr-xr-x 15 root root 0 May 11 17:44 .. drwxr-xr-x 2 root root 4096 May 4 17:29 etc drwx------ 2 root root 16384 Jan 1 2000 lost+found drwxr-xr-x 2 root root 4096 Aug 12 2011 tmp drwxr-xr-x 3 root root 4096 May 4 17:29 usr drwxr-xr-x 3 root root 4096 May 4 17:29 var root@(none):/ # root@(none):/ # ls -al /sda5/etc total 20 drwxr-xr-x 2 root root 4096 May 4 17:29 . drwxr-xr-x 7 root root 4096 May 4 17:29 .. -rwxrwxrwx 1 root root 3420 Aug 12 2011 nas_conf_db.xml -rw-r--r-- 1 root root 104 Mar 15 2009 nas_ext_hdd_db.xml -rw-r--r-- 1 root root 40 Oct 3 2009 ntp.conf root@(none):/ # ls -al /sda7 total 96 drwxr-xr-x 20 root root 4096 Feb 18 2014 . drwxr-xr-x 16 root root 0 May 11 17:49 .. lrwxrwxrwx 1 root root 20 Feb 18 2014 .mldonkey -> /share/1000/mldonkey drwxr-xr-x 2 root root 4096 Feb 18 2014 bin drwxr-xr-x 2 root root 4096 Feb 18 2014 bin_cab drwxr-xr-x 2 root root 4096 Sep 25 2013 boot drwxrwxrwx 2 root root 4096 Feb 18 2014 clunc drwxr-xr-x 3 root root 12288 Feb 18 2014 dev drwxrwxrwx 15 root root 4096 Jan 27 2014 etc drwxr-xr-x 4 root root 4096 Jan 28 2014 lib lrwxrwxrwx 1 root root 11 Feb 18 2014 linuxrc -> bin/busybox drwx------ 2 root root 16384 Jan 3 2008 lost+found drwxr-xr-x 3 root root 4096 Feb 18 2014 mail drwxr-xr-x 2 root root 4096 Aug 27 2008 nowhere drwxr-xr-x 7 root root 4096 Feb 18 2014 opt drwxrwxrwx 2 root root 4096 Mar 5 2011 proc drwxr-xr-x 2 root root 4096 Jan 3 2008 root drwxr-xr-x 2 root root 4096 Feb 18 2014 sbin drwxrwxrwx 2 root root 4096 Mar 5 2011 share drwxrwxrwx 2 root root 4096 Mar 5 2011 sys drwxr-xr-x 22 root root 4096 Feb 18 2014 usr drwxr-xr-x 2 root root 4096 Mar 9 2012 var root@(none):/ #

by **fvdw** » Wed Apr 23, 2014 9:30 pm

that looks perfect.

now lets check your boot loader, shutdown the nwsp2 and open an u-boot console using the fvdw-sl console
start the nwsp.
The u-boot console will interrupt boot and you should get a prompt

Code: Select all: marvell>>

list the u-boot environment variables by giving the command

Code: Select all: printenv

post result here (you can copy the content of the u-boot console window by clicking with right mouse button on top of the window)

it should contain amongst others this
bootargs=console=ttyS0,1152000 root=/dev/sda7 ro
if bootargs doesn't conatin this string then set it

Code: Select all: setenv bootargs console=ttyS0,1152000 root=/dev/sda7

activate netconsole output

Code: Select all: setenv ipaddr ${ipaddr} setenv serverip ${serverip}

(enter exactly the commands as shown above !)

now try to boot the kernel form partition 6

Code: Select all: ide reset diskboot 0x800000 0:6

if the kernel loads then boot it

Code: Select all: bootm

by **tbn69** » Thu Apr 24, 2014 8:04 pm

Below the result, after the message "starting kernel" nothing happen. I have no access to web interface , no ping reply ...
I retry fvdw-sl-assistant without success.
ipaddr and serverip variables was correct (i didn't set them for the first try). I retry and set the 2 like you wrote, but same result
:hammerhead

Code: Select all: 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@0x10 0000(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/m tdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x20 00000; 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 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 uboot_capabilities=gpt,lba64 start_lump=lump 3 pre_lump=lump 1 resetdisk=ide reset bootdelay=0 boot_fail=lump kernel_addr=0x800000 productType_env=ASTON_KW primaryPart=6 secondaryPart=A boot_usb=usb start;usbboot 0x800000 0:1;bootm; 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/sd b7; else run boot_disk3; fi boot_disk1=if disk ${kernel_addr} 0:${secondaryPart}; then setenv rootfs /dev/sd a7; else run boot_disk2; fi boot_disk=if test ${resetFlag_env} -eq 0; then run boot_disk1; else run boot_dis k3; fi disk_disk0=run boot_disk; setenv bootargs console=ttyS0,115200 root=${rootfs} ro reset=${resetFlag_env} productType=${productType_env} GPT fvdw vs80; bootm ${ke rnel_addr}; uimage=uimage-nwsp2 usbpartboot1=/dev/sdb1 usbpartboot2=/dev/sdb1 disk_disk=run disk_disk0 usb_fvdw1=if usbboot 0x800000 0:1; then setenv bootargs ip=dhcp console=ttyS0,11 5200 root=${usbpartboot2} ro rootwait; bootm; else usb stop; ide reset; run disk _disk0; fi usb_fvdw=if iminfo 0x800000; then setenv bootargs ip=dhcp console=ttyS0,115200 r oot=${usbpartboot1} ro rootwait; bootm; else run usb_fvdw1; fi ethaddr=00:D0:4B:8A:C0:24 fvdw_boot_usb=ide reset; usb start; ext2load usb 0:1 0x800000 /${uimage}; run us b_fvdw; ethact=egiga0 ipaddr=192.168.0.252 ncip=192.168.0.16 serverip=192.168.0.16 stdin=nc stdout=nc Environment size: 2545/4092 bytes 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 WD20EFRX-68EUZN0 Firm: 80.00A80 Ser#: WD-WMC 4M2718249 Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512) Marvell>> diskboot 0x800000 0:6 diskboot 0x800000 0:6 ## Valid DOS partition found ## Loading from IDE device 0, partition 6: Name: hda6 Type: U-Boot Image Name: Linux-3.9.5 Created: 2014-01-09 22:26:07 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4319672 Bytes = 4.1 MB Load Address: 00008000 Entry Point: 00008000 Marvell>> Marvell>> diskboot 0x800000 0:6 diskboot 0x800000 0:6 ## Valid DOS partition found ## Loading from IDE device 0, partition 6: Name: hda6 Type: U-Boot Image Name: Linux-3.9.5 Created: 2014-01-09 22:26:07 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4319672 Bytes = 4.1 MB Load Address: 00008000 Entry Point: 00008000 Marvell>> bootm bootm ## Booting image at 00800000 ... Image Name: Linux-3.9.5 Created: 2014-01-09 22:26:07 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4319672 Bytes = 4.1 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ...

plugout.net

Disk Replacement : Nas unreachable...

Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Re: Disk Replacement : Nas unreachable...

Who is online