fvdw-sl doesnt work for me :(

[fvdw]

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).

I assume you installed the lacie firmware and kernel. Does the Lacie webinterface comes up ? Think you als have to make sdb1,2,5 and 10
sdb2 is the data partiton, believe it must be formatted in XFS. If thats not done properly that could be a reason. TheLacie boots but cannot mount that partiton.

ps if you nwsp2 boots then I see no reason why fvdw-sl firmware should not run. Also on the lacie firmware the kernel is loaded from sdb6 and then the bootloader looks for a a root fs in sdb7 for further boot and loading the firmware.
Uptil now almost 80 people did the installation and all succeed (except one) so you must be overlooking something

[FoCMB]

the lacie webinterface comes up.
i formated the sda2 as xfs and the sda5 as swap.

can you post me your output of: cat /proc/cpuinfo , cat /proc/filesystems and cat /proc/mounts ? then i can search for differences.

[fvdw]

the lacie webinterface comes up.
i formated the sda2 as xfs and the sda5 as swap.

can you post me your output of: cat /proc/cpuinfo , cat /proc/filesystems and cat /proc/mounts ? then i can search for differences.

if you mean when running Lacie firmware then no I can't because I do not use the lacie firrmware anymore, but it is posted in several wiki's.
For the fvdw-sl firmware i can do that (when I am at home)

PS I noticed in the picture you posted from gparted shwowing the partitions. I noticed something strange, it mentions for sda1, sda2 and sda7 about 500 MB. Thats is correct, however it also mentions 463 MB used and that is strange while the disk image if the fvdw-sl firmware is only 160 MB in size.....it should mention 160MB used

I found a post here of someone with a similar isue as you describe, not able to boot. http://forum.nas-central.org/viewtopic.php?f=236&t=4285

In his post the same strange devistion is noticble for partion of 1 cylinder in size (7008 blocks instead on 8001) He used a script from another use to partiton the disk and that made a partition table with the correct numbers. Then his diks booted. Further down in that post an issue is mentioned with "advandced format" disks and that there are versions of fdisk that recognize those and thread them differently. The strange number for used space in your picture could possible a result form this. And if so this can be the reason why booting fails of our firmware as the partiton images are made for normal disks. Maybe using you "small linux" generating a correct partition table as you posted might be the solution to let the fvdw-sl firmware run.
The fact that the original firmware runs is because you made an image of the original (advanced format ?) disk

I am at work now so i can't make a print of used space per partion right now but I will do this this evening.

[fvdw]

can you post me your output of: cat /proc/cpuinfo , cat /proc/filesystems and cat /proc/mounts ? then i can search for differences.

This the requested output on my nwsp2 running fvdw-sl-9-0

Code: Select all

# cat /proc/cpuinfo
Processor       : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS        : 797.90
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1

Hardware        : LaCie Network Space v2
Revision        : 0000
Serial          : 0000000000000000


Code: Select all

# cat /proc/filesystems
nodev   sysfs
nodev   rootfs
nodev   bdev
nodev   proc
nodev   tmpfs
nodev   sockfs
nodev   usbfs
nodev   pipefs
nodev   anon_inodefs
nodev   rpc_pipefs
nodev   inotifyfs
nodev   devpts
        ext3
        ext2
nodev   ramfs
        vfat
        msdos
nodev   nfs
nodev   nfsd
nodev   cifs
        iso9660
        ntfs
nodev   fuse
        fuseblk
nodev   fusectl


Code: Select all

 # cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,relatime,errors=continue,data=ordered 0 0
none /proc proc rw,relatime 0 0
none /sys sysfs rw,relatime 0 0
/dev/sda5 /rw_fs ext3 rw,noatime,errors=continue,data=ordered 0 0
tmpfs /rw_fs/tmp/usr/var tmpfs rw,relatime,size=200k 0 0
/proc/bus/usb/ /proc/bus/usb usbfs rw,relatime 0 0
/dev/sda8 /share/1000 ext3 rw,relatime,errors=continue,data=ordered 0 0


[mikesmth]

Hi Guys,

Looks like I have the same problems. The difference is, I use a WD 2.5 Tb disk.
I partitioned the disk with knoppix, because in Ubuntu I had the same layout before.
Now the layout seems fine,but the device still won't boot.

[fvdw]

is this an advanced format HDD ? (http://en.wikipedia.org/wiki/Advanced_format), I read on the internet web more strange issues with those . Anyhow lets see if we can fix it, in the end more then 100 users succeeded to get it running on the nwsp2 ;)

Below a screenshot of my partition table, its from a 2 TB WD green caviar disk. I also added the info from the expert command v (first change to expert mode using x). This verifies the partition table. Do you get the same output. I think not, why ?

Your partition table is for the majority same as mines but there is beside the number of cylinders , which is bigger in your case which is logical because it is a bigger disk, another difference. This is that in the partition table the end cylinder of the extended partition 4 and that of partition 8 is not the same as the total number of cylinders on the disk. It should be 304001 and not 267349 Did you set this by purpose ? It basically means the disk is not fully used is there another partition after sda8 ? If so this can cause issues with booting as the lacie bootloader looks for partitions 9 and 10 and if found and they contains something, it tries to laod the kernel from there instead of sda6.

Below in the output of my partition table you can see that the end cylinder of sda8 matches the max cylinder number of the disk.

Suggest you try again with using the complete disk

part-tabel1.JPG

[mikesmth]

Right now I'm making a backup of my (original) lacie disk, so I'm not able to check yet. >>edit:run out of disk space.. so will try later on to another disk...
I used knoppix for partitioning, and used the defaults which fdisk suggested. I assumed it would take the left over space, which it didn't. In stead it took 2Tb. It's a brand new disk as i didn't want to take a risk I wouldn't be able to boot at all anymore ;-)
If you check on the wd site, this is what they say about large capacity drives, so the only conclusion can be my drive has bigger sectors than 512b.
see http://www.wdc.com/wdproducts/library/WhitePapers/ENG/2579-771501.pdf

Here's the results for your request:

layout.png

Groetjes en thanks,

Mike

[fvdw]

thats a big part not used for the rest it looks a normal
My disk only show 310 only 310 unallocated sectors.

If the space not occupied is causing the problem without having made it a partition that would surpirise . Think tis advanced format HDD is is giving the problem her. Would be nice to learn how to solve this

[mikesmth]

I would say, let's solve this!

I wil look for a solution myself as well. For example, I could try to dd the original drive to the new one, let's see what the result is. If it boots, at least we'll know its possible. The only challenge would then be to get your firmware running and how to get to the leftover diskspace.
;-)

[fvdw]

I would say, let's solve this!

I wil look for a solution myself as well. For example, I could try to dd the original drive to the new one, let's see what the result is. If it boots, at least we'll know its possible. The only challenge would then be to get your firmware running and how to get to the leftover diskspace.
;-)

sound good mike thanks for trying
Question from what you write it seems that fdisk is not able to allocate the total space of a 2.5 TB disk?? that is strange, there are people that have done it.
If the 1 TB original disk runs (assumng that it is not a advanced format HDD as well :? ) then we know tyour nwsp2 is capable of running it and there is no reason why it shouldn't . It will run no doubt. If then the 2.5 TB disk (now fully occupied) won't boot then it must be the disk.
A long shot could be that the sata driver of Linux 2.6.33.1 don't support the drive (very very unlikely) but I am currently also working on a release based on the newest linux kernel 2.6.39.4 that could also be worth a try.