fvdw-sl doesnt work for me :(

[fvdw]

mmm..very strange
Lets assume that the flash is ok for the moment.

I agree with Jock
I do not understand the deviations I see in your partition table.
The number blocks is not correct for sdb1 and sdb6. I have several NAS device here (also one with a seagate disk) and all give exact the partiton table as mentioned in the how to guides.
Especially the sdb6 size is suspected as from that partition the Linux kernel is loaded. further if U-boot cannot access sdb7 then boot also will be aborted and the blue led will be steady on.
So it seems in your case that it fails to find either the kernel or the root file system

First step is to get that partition table right
This is the table from the original nwsp2 disk with lacie software on it

Code: Select all

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 250 2008093+ 5 Extended
/dev/sdb2 251 121601 974751907+ 83 Linux
/dev/sdb5 1 32 256977 82 Linux swap
/dev/sdb6 33 33 8001 83 Linux
/dev/sdb7 34 34 8001 83 Linux
/dev/sdb8 35 140 851413+ 83 Linux
/dev/sdb9 141 249 875511 83 Linux
/dev/sdb10 250 250 8001 83 Linux

Notice that partitions of 1 cylinder in size have 8001 blocks

This should be changed to this to run our firmware (as described in the how to guide)

Code: Select all

Device Boot Start End Blocks Id System
/dev/sdb1 1 64 514048+ 83 Linux
/dev/sdb2 65 128 514080 83 Linux
/dev/sdb3 129 192 514080 82 Linux swap
/dev/sdb4 193 121601 9xxxx+ 5 Extended
/dev/sdb5 193 292 803218+ 83 Linux
/dev/sdb6 293 293 8001 83 Linux
/dev/sdb7 294 357 514048+ 83 Linux
/dev/sdb8 358 121601 9xxxx+ 83 Linux

The blocks for sdb1, sdb6 and sdb7 are different in your partition table.
May I suggest that you try to do that again
ps I have read somewhere that if a partiton sdb10 is present containing a kernel it will try to load that and then our firmware will not run. Did you delete all partitions and hit the "w" command after doing that. Seems yes as I do not see sdb10 in your table.
But as said the partition table is not as it should be as such our first line of attack

[FoCMB]

ok.i deleted all partitions. now fdisk /dev/sdd (before it was sdb, noe its sdd, i dont know why):

root@Laptop:/# fdisk /dev/sdd

Befehl (m für Hilfe): u
Changing display/entry units to cylinders (DEPRECATED!)

Befehl (m für Hilfe): p

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 Köpfe, 63 Sektoren/Spur, 121601 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x26f64b88

Gerät boot. Anfang Ende Blöcke Id System

Befehl (m für Hilfe):

[FoCMB]

now i biuld the first partiton:

root@Laptop:/# fdisk /dev/sdd

Befehl (m für Hilfe): u
Changing display/entry units to cylinders (DEPRECATED!)

Befehl (m für Hilfe): p

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 Köpfe, 63 Sektoren/Spur, 121601 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x26f64b88

Gerät boot. Anfang Ende Blöcke Id System

Befehl (m für Hilfe): n
Befehl Aktion
e Erweiterte
p Primäre Partition (1-4)
p
Partitionsnummer (1-4, Vorgabe: 1): 1
Erster Zylinder (1-121601, Vorgabe: 1): 1
Last Zylinder, +Zylinder or +size{K,M,G} (1-121601, Vorgabe: 121601): 64

Befehl (m für Hilfe): w
Die Partitionstabelle wurde verändert!

Rufe ioctl() um Partitionstabelle neu einzulesen.
Synchronisiere Platten.
root@Laptop:/# fdisk /dev/sdd

Befehl (m für Hilfe): u
Changing display/entry units to cylinders (DEPRECATED!)

Befehl (m für Hilfe): p

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 Köpfe, 63 Sektoren/Spur, 121601 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x26f64b88

Gerät boot. Anfang Ende Blöcke Id System
/dev/sdd1 1 64 513056 83 Linux

Befehl (m für Hilfe):


and you see, the block size is different from yours :(

[fvdw]

why do you need to use the command "u" to change the entry/disply units ?
Thats not required on my system

seems your fdisk program is not same as we are using.

edit we use the fdisk version included in busybox

You could try to use knoppix CD to see if that can partition the disk as it should.

[fvdw]

one more remark

In Ubunte you need to put sudo in front of evry command
So instead of

Code: Select all

fdisk /dev/sdb

You should use

Code: Select all

sudo fdisk /dev/sdb

This also for the formatting command used for formatting the partitions sdb5 and sdb8

don't know if it makes a difference as you would expect error messages when using them with sudo.
However sudo gives root priveleges maybe some are need for setting aparameters that won't be set when using them without sudo

[FoCMB]

ha, i tried an older version of fdisk (damn small linux) and so get the following partition table:

Gerät boot. Anfang Ende Blöcke Id System
/dev/sdc1 1 64 514048+ 83 Linux
/dev/sdc2 65 128 514080 83 Linux
/dev/sdc3 129 192 514080 82 Linux Swap / Solaris
/dev/sdc4 193 121601 975217792+ 5 Erweiterte
/dev/sdc5 193 292 803218+ 83 Linux
/dev/sdc6 293 293 8001 83 Linux
/dev/sdc7 294 357 514048+ 83 Linux
/dev/sdc8 358 121601 973892398+ 83 Linux

Befehl (m für Hilfe):

this looks like yours

[fvdw]

yep this is the same, so follow the rest of the steps in the how to and see if it now boots.


ps one question for the night, are you 100% sure that you have a lacie network space vs2 ?
And not an netwotk space vs1 or an internet space vs 1 or 2 ?
This because of the behavior you describe when trying to boot it.
That deviates from the startup procedure of a nwsp2 as I know it.
If it is not a nwsp2 then it won't boot with the package you installed as the kernel in the package is only suitable for the nwsp2 hardware

see you tomorrow, time to go to bed..

[FoCMB]

oh, i am sure that i have a lacie network space 2.

i will do all the steps in the howto friday with the damn small linux. i will post the result.
if this dont work, perhaps i can install the original lacie firmware.

good night and thanks

[FoCMB]

so, i am sure that the flash is ok.
i putted back my backups of mbr and sdb6,7,8,9 to my lacie network space 2 and it booted.
but now there is a new problem. the blue front led is blinking all the time (initialize disk).

[Jocko]

i will do all the steps in the howto friday with the damn small linux. i will post the result.
if this dont work, perhaps i can install the original lacie firmware.

Hi FoCMB
did you put back our backups because the full firmware installation has again failed ? :?