fvdw-sl doesnt work for me :(

[mikesmth]

That took a while...
I copied the original 1Tb disk to the 2.5 Tb disk by bitcopying the whole disk... took just 23+ hours...
But it IS booting from the 2.5 Tb disk now.
I updated the (original) firmware to the latest (2.0.6) available, and formatted the disk trough the web-interface.
I reconnected the disk to my Ubuntu machine and tried resizing the data partition... The largest size I could format with gparted is around 2 Tb.
It simply does not accept any larger sizes. when I choose larger sizes it errors out telling that msdos formatting does not allow more than a certain amount of sectors. Anyways, after creating a partition size of 2Tb the firmware shows a drive size of 2.1Tb with a data partition available of 1.9Tb.
I still would rather use fvdw-sl...

What next?

[fvdw]

I am a little lost Mike

I understand you have copied everything on the original 1 TB disk to the 2.5 TB disk.

So you could do a trial with the 1 TB disk to set that up for fvdw-sl and see if your nwsp2 likes that disk.
if that boots we know the issue is with the 2.5 TB disk

If your software don't allow you to make bigger partitions then 2 TB you could consider to make sda7 500 GB and sda8 2000GB
If then the disk boots we know that in principle the disk is ok.
Then we need to figure out why you can not make bigger partitions, ext3 format allows much higher size as 2TB. What fdisk only does is setting up an partition table if it can read the max cylinder number it should also be able to write it in the table would be my guess. unfortunate I never tried a 2.5 TB disk so I can try it.

need to google on the internet

[fvdw]

mmm..seems fdisk can indeed not make partitions bigger then 2 TB

see here http://www.cyberciti.biz/tips/fdisk-una ... r-2tb.html

In the article also a solution is given....at least to create a bigger partition, if it then boots ??

[mikesmth]

So... Like you suggested I tried the procedure on the original disk, without success, same result.
I'm guessing its must have something to do with linux versions in which the procedure is being done.
Either that or my device differs from others.
I used the procedure within knoppix, version KNOPPIX_V6.7.0CD-2011-08-01-EN.
Which linux version would you suggest?

Greetz,

Mike

[fvdw]

in the past I used knoppix_V5.1.1CD-2007-0-04-EN
Later I used an old portable PC with suse 10.0 Linux and today I use the Linux as present on my sp8020 or networkspace 2, I simply connect the sata-usb connector to the usb port of the NAS and do the preparation from the command line using Putty (ssh access).
With that I prepared already three disk for two different nwsp2 (max 2 TB) and all of them worked without a problem.
I think Jocko prepared recently his new nwsp2 using Ubuntu.
So you mus be doing something wrong or indeed you have a unique nwsp2. But it is hard to believe as the original Lacie bootloader also loads the kernel form sda6 and the root file system from sda7. Exactly the same as our firmware does.
Are you sure you have a nwsp2 ?
If the original firmware runs and you have ssh access then look at the output the command "dmesg" after connecting for eample with Putty gives and post that here. It will mention the mainboard and where it looks for the root file system. Then we can compare if its the same as form my original nwsp2 (I kept that output on disk).
Also you could try to use the Lacie kernel on sda6 instead of our kernel in combination with our firmware setup. In this setup it should boot but not all functions of the fvdw-sl firmware will work as there are some kernel dependent features like nfs server and the interface for ntfs write support.

ps this is the dmesg output of a original nwsp2

Code: Select all

networkspace 2 demsg output 23 okt 2010

Linux version 2.6.22.18 (sbs@node5.lacie.com) (gcc version 4.2.1) #1 Tue May 25 15:42:44 UTC 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
Machine: netspace_v2
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 65536
  DMA zone: 512 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 65024 pages, LIFO batch:15
  Normal zone: 0 pages used for memmap
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 65024
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour dummy device 80x30
....<snip>
  Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- netspace_v2  Soc: MV88F6281 Rev 3 LE
.....<snip>
 

And this from one running fvdw-sl

Code: Select all

root@fvdwsl-nwsp2:/ # dmesg
Linux version 2.6.33.1 (root@linux-fw1) (gcc version 4.2.0 20070413 (prerelease) (CodeSourcery Sourcery G++ Lite 2007q1-21)) #50 PREEMPT Thu Jul 14 23:54:04 CEST 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: LaCie Network Space v2
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat c03b13b4, node_mem_map c03ca000
  Normal zone: 512 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 65024 pages, LIFO batch:15
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
.......<snip>

O f interest is beside the fact that it must the same main board type (Soc: MV88F6281 Rev 3 LEsee output original firmware lacie) and the kernel command line (Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW)

[mikesmth]

As you suggested I used the orinial disk... so no more original firmware there....

[fvdw]

As you suggested I used the orinial disk... so no more original firmware there....

:shock: :o :?

But you still have you 2.5TB disk witht he original firmware copy and that booted you wrote ??

and do you have the douments (CD) that came with the original device ? From that it must be possible to retrieve what kind of device it is.

[fvdw]

Can you also post the partition table from the 2.5TB disk with has a copy of the original firmware ?

From that we migh also learn something and compare it with what we need

[mikesmth]

Sorry, none there anymore. I was experimenting with the 2.5 Tb disk in other ways, so partition table is gone.
Right now I'm trying to get back to a working situation using the instructions in
http://forum.nas-central.org/viewtopic.php?f=236&t=4285
Tried a couple of times already with no luck...
Anyone with a backup of the original disk partitions?

[fvdw]

Mike I suspect you have a network space "lite" vs2

I just discovered today that there such a lite version out there. because a post her in another forum
http://forum.nas-central.org/viewtopic.php?f=236&t=4775
This "lite" version has different hardware inside such as a different type of main board and very pity half the amount of ram (only 128 MB instead of 256 MB).
I could test this because a spare nwsp2 I had bought a while ago appears to be a "lite" version as well.
After reading the post on the other forum I checked that spare one, and ...dammed it is a lite version. But good for you because I could do some tests :lol:
The reason why our fvdw-sl firmware doesn't run on this "lite" device is because the kernel is for normal nwsp2 hardware. As result loading of the kernel fails on the lite version. I will need to develop a kernel for it. But that will take some time.
But there is a workaround that you could try for the time being and that is running our firmware in combination with the original Lacie nwsp-lite kernel until we developed a kernel for it. I tested it, running the device with the original kernel and ourt firmware, and the device boots and the firmware comes up just fine. Some kernel dependent features as nfs server and so one might not work but all others will.

I attached for you a zip archive that contains a copy of the original sda6 partition of the nwsp2 "lite" version. That contains the original lacie nwsp2-lite kernel.
Install the fvdw-sl firmware according the guides provided but write the kernel instead of the kernel in our first time install package of the fvdw-sl firmware the file in the attachment to sda6 using the dd command

ps The blue led will keep blinking after finishing boot. Will deal with that later

uImage-nwsp2-lite-org.zip