Please Help me with my 5Big Network 2

[vmsosa]

Fvdw,

I assume that vmsosa wants to say pardadeo <=> blinking

Yes Jocko, that's right, sorry I'm speak spanish. The frontal led is blinking in blue color

[vmsosa]

pardadeando

what does this word mean ?

It could be that the Lacie firmware needs a line on first sector of the disk. The Lacie firmware looks at that sector to determine if it is a first boot or new install.
I forgot about that
I have that info as well and will post it at the end of the afternoon when being at home

Hi fvdw, thanks so much man, sorry for "PARPADEANDO" jajaja my spanish.

[fvdw]

ok here is a file that you need to write to beginning of disk sda
Unpack the archive in the tftp directory of the fvdw-sl console
Load the standalone kernel and connect with telnet to the 5big2
Upload the file with tftp (tftp -l 5big2-sc1.img -r 5big2-sc1.img -g ip-pc)
write it to sda using command

Code: Select all

dd if=5big2-sc1.img of=/dev/sda bs=1 count=16

Then try again if it boots (reboot -f)

[vmsosa]

thanks for file and the help, only tell me in that partition should be this 5big2-sc1.zip, thanks

[fvdw]

the command to use is written above. It must not be written to a partition (if you do you will erase data on that partition) it must be written to /dev/sda as you can read in the instruction in my previous post

[vmsosa]

hello again FvdW please point me as to format the partition 2 in XFS, I tried but I get this

Code: Select all

root@(none):/ # tftp -l /sbin/mkfs.xfs -r mkfs.xfs -g 192.168.0.12
mkfs.xfs             100% |*************************************************************************|   337k  0:00:00 ETA
root@(none):/ # chmode 755 /sbin/mkfs.xfs
-sh: chmode: not found
root@(none):/ # chmod 755 /sbin/mkfs.xfs
root@(none):/ # mkfs.xfs /dev/sda2
-sh: mkfs.xfs: not found
root@(none):/ #

please tell me you do

Thanks

[fvdw]

hhhhmmmm, did you try

Code: Select all

/sbin/mkfs.xfs /dev/sda2

on my system it works...(same executable used)

Code: Select all

root@fvdwsl-nwsp2:/ # chmod 755 /sbin/mkfs.xfs
root@fvdwsl-nwsp2:/ # mkfs.xfs --help
mkfs.xfs: invalid option -- -
unknown option --
Usage: mkfs.xfs
/* blocksize */         [-b log=n|size=num]
/* data subvol */       [-d agcount=n,agsize=n,file,name=xxx,size=num,
                            (sunit=value,swidth=value|su=num,sw=num),
                            sectlog=n|sectsize=num
/* inode size */        [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2]
/* log subvol */        [-l agnum=n,internal,size=num,logdev=xxx,version=n
                            sunit=value|su=num,sectlog=n|sectsize=num,
                            lazy-count=0|1]
/* label */             [-L label (maximum 12 characters)]
/* naming */            [-n log=n|size=num,version=2|ci]
/* prototype file */    [-p fname]
/* quiet */             [-q]
/* realtime subvol */   [-r extsize=num,size=num,rtdev=xxx]
/* sectorsize */        [-s log=n|size=num]
/* version */           [-V]
                        devicename
<devicename> is required unless -d name=xxx is given.
<num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
      xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
<value> is xxx (512 byte blocks).
root@fvdwsl-nwsp2:/ #

[vmsosa]

Thanks for your reply, fvdw, you know I have finished the process you indicate in your guide, I've added 5big2-sc1.img to sda, and format the partition 2 in XFS, unfortunately to restart

Code: Select all

reboot-f

Front LED is blinking for long time

Will exist some other way to check the firmware loading process on disk 1 or form done directly by Linux, appreciate your answer. :please

[fvdw]

mmm...the images and kernel I sent you come directly from a 5big2 and that started normally.

But seems something is missing. When trying to get a 5big2 working from draftmanscorp (another member) we saw a similar behavior, everything went fine for install but the front led keeps blinking. We even used two different sets of images and the an extraction from the latest capsule from Lacie. There we ended up to install our firmware instead of the lacie one. However our firmware doesn't support raid yet on this moment

Something is missing preventing it from continuing the boot. It is not the kernel, partition structure, image of sd7 and sda8 (those are exactly the same as form a booting 5big2. We now it is looking for the string in the beginning of sda...but what more does it needs.
I will need to look deeply in the boot script of Lacie to find the reason and where it might be waiting for

[fvdw]

there is one thing you can already try that is fill sda10 partiton with zero's
when booting it will look for a kernel there as well, it should be empty as we did not put anything in it but it can not harm to fill it with zero's (also laci boot script seems to do this)
fire up the satndalone kernel as explained earlier and in the telnet client give as command

Code: Select all

dd if=/dev/zero of=/dev/sda10

One thing more. do not insert more then 1 disk, use only a disk in first slot (sda)

more will follow