lacie 5 big network v.1 please support for fvdw

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Sun Oct 27, 2013 10:35 am

:bananadance

nice now perform this command and post the output, we will need to see the change if we are going to check the dev nodes
Code: Select all
 ls -al /dev | grep sd
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby totorweb » Sun Oct 27, 2013 10:40 am

Code: Select all
root@(none):/dev # ls -al /dev | grep sd
lrwxrwxrwx    1 root     root             9 Oct 26  2013 nfsd -> ./socksys
brw-rw----    1 root     root        8,   0 Oct 26  2013 sda
brw-rw----    1 root     root        8,   1 Oct 26  2013 sda1
brw-rw-rw-    1 root     root        8,  10 Oct 26  2013 sda10
brw-rw----    1 root     root        8,   2 Oct 26  2013 sda2
brw-rw----    1 root     root        8,   3 Oct 26  2013 sda3
brw-rw----    1 root     root        8,   4 Oct 26  2013 sda4
brw-rw----    1 root     root        8,   5 Oct 26  2013 sda5
brw-rw----    1 root     root        8,   6 Oct 26  2013 sda6
brw-rw----    1 root     root        8,   7 Oct 26  2013 sda7
brw-rw----    1 root     root        8,   8 Oct 26  2013 sda8
brw-rw-rw-    1 root     root        8,   9 Oct 26  2013 sda9
brw-rw-r--    1 root     root        8,  16 Oct 26  2013 sdb
brw-r--r--    1 root     root        8,  17 Oct 26  2013 sdb1
brw-r--r--    1 root     root        8,  18 Oct 26  2013 sdb2
brw-rw----    1 root     root        8,  19 Oct 26  2013 sdb3
brw-rw----    1 root     root        8,  20 Oct 26  2013 sdb4
brw-rw----    1 root     root        8,  21 Oct 26  2013 sdb5
brw-rw----    1 root     root        8,  22 Oct 26  2013 sdb6
brw-rw----    1 root     root        8,  23 Oct 26  2013 sdb7
brw-rw----    1 root     root        8,  24 Oct 26  2013 sdb8
brw-rw----    1 root     root        8,  32 Oct 26  2013 sdc
brw-rw----    1 root     root        8,  33 Oct 26  2013 sdc1
brw-rw----    1 root     root        8,  34 Oct 26  2013 sdc2
brw-rw----    1 root     root        8,  35 Oct 26  2013 sdc3
brw-rw----    1 root     root        8,  36 Oct 26  2013 sdc4
brw-rw----    1 root     root        8,  37 Oct 26  2013 sdc5
brw-rw----    1 root     root        8,  38 Oct 26  2013 sdc6
brw-rw----    1 root     root        8,  39 Oct 26  2013 sdc7
brw-rw----    1 root     root        8,  40 Oct 26  2013 sdc8
brw-rw----    1 root     root        8,  64 Oct 26  2013 sde
brw-rw----    1 root     root        8,  65 Oct 26  2013 sde1
brw-rw----    1 root     root        8,  66 Oct 26  2013 sde2
root@(none):/dev #


sdd seem's not to be there.
It is seen at uboot boot

Code: Select all
scsi 1:0:0:0: Direct-Access     ATA      ST31500341AS     CC1H PQ: 0 ANSI: 5
fvdw1 disk index 1
fvdw2 disk indexfvdw 1
fvdw3 disk indexfvdw 3
fvdw4 disk diskname= sdd
sd 1:0:0:0: [sdd] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 1:0:0:0: [sdd] Write Protect is off
sd 1:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO
 or FUA
 sdd: sdd1
sd 1:0:0:0: [sdd] Attached SCSI disk
totorweb
 
Posts: 46
Joined: Fri Oct 18, 2013 11:28 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Sun Oct 27, 2013 10:44 am

that is the default setting and indeed sdd is missing in the deault

now upload the udevstart binary (unpack the attached zip archive) to the 5big1 when running the standalone kernel, for this put the binary in the tftp folder of the fvdw-sl console

Then upload it
Code: Select all
tftp -l /sbin/udevstart -r udevstart -g ip-pc

(replace ip-pc by the actual ip address of your pc)
make it executable
Code: Select all
chmod 755 /sbin/udevstart

run it
Code: Select all
/sbin/udevstart


now repeat the command
Code: Select all
ls -al /dev | grep sd

and post the output

udevstart is now available here:
http://plugout.net/viewtopic.php?f=7&t=1271&p=18801#p18801
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby totorweb » Sun Oct 27, 2013 10:48 am

sdd is in the place :hail
Code: Select all
root@(none):/dev # ls -al /dev | grep sd
lrwxrwxrwx    1 root     root             9 Oct 26  2013 nfsd -> ./socksys
brw-rw----    1 root     root        8,  64 Jan  1 00:21 sda
brw-rw----    1 root     root        8,  65 Jan  1 00:21 sda1
brw-rw----    1 root     root        8,  74 Jan  1 00:21 sda10
brw-rw----    1 root     root        8,  66 Jan  1 00:21 sda2
brw-rw----    1 root     root        8,   3 Oct 26  2013 sda3
brw-rw----    1 root     root        8,   4 Oct 26  2013 sda4
brw-rw----    1 root     root        8,  69 Jan  1 00:21 sda5
brw-rw----    1 root     root        8,  70 Jan  1 00:21 sda6
brw-rw----    1 root     root        8,  71 Jan  1 00:21 sda7
brw-rw----    1 root     root        8,  72 Jan  1 00:21 sda8
brw-rw----    1 root     root        8,  73 Jan  1 00:21 sda9
brw-rw----    1 root     root        8,  48 Jan  1 00:21 sdb
brw-rw----    1 root     root        8,  49 Jan  1 00:21 sdb1
brw-rw----    1 root     root        8,  58 Jan  1 00:21 sdb10
brw-rw----    1 root     root        8,  50 Jan  1 00:21 sdb2
brw-rw----    1 root     root        8,  19 Oct 26  2013 sdb3
brw-rw----    1 root     root        8,  20 Oct 26  2013 sdb4
brw-rw----    1 root     root        8,  53 Jan  1 00:21 sdb5
brw-rw----    1 root     root        8,  54 Jan  1 00:21 sdb6
brw-rw----    1 root     root        8,  55 Jan  1 00:21 sdb7
brw-rw----    1 root     root        8,  56 Jan  1 00:21 sdb8
brw-rw----    1 root     root        8,  57 Jan  1 00:21 sdb9
brw-rw----    1 root     root        8,  32 Oct 26  2013 sdc
brw-rw----    1 root     root        8,  33 Oct 26  2013 sdc1
brw-rw----    1 root     root        8,  42 Jan  1 00:21 sdc10
brw-rw----    1 root     root        8,  34 Oct 26  2013 sdc2
brw-rw----    1 root     root        8,  35 Oct 26  2013 sdc3
brw-rw----    1 root     root        8,  36 Oct 26  2013 sdc4
brw-rw----    1 root     root        8,  37 Oct 26  2013 sdc5
brw-rw----    1 root     root        8,  38 Oct 26  2013 sdc6
brw-rw----    1 root     root        8,  39 Oct 26  2013 sdc7
brw-rw----    1 root     root        8,  40 Oct 26  2013 sdc8
brw-rw----    1 root     root        8,  41 Jan  1 00:21 sdc9
brw-rw----    1 root     root        8,  16 Jan  1 00:21 sdd
brw-rw----    1 root     root        8,  17 Jan  1 00:21 sdd1
brw-rw----    1 root     root        8,   0 Jan  1 00:21 sde
brw-rw----    1 root     root        8,   1 Jan  1 00:21 sde1
brw-rw----    1 root     root        8,  10 Jan  1 00:21 sde10
brw-rw----    1 root     root        8,   2 Jan  1 00:21 sde2
brw-rw----    1 root     root        8,   5 Jan  1 00:21 sde5
brw-rw----    1 root     root        8,   6 Jan  1 00:21 sde6
brw-rw----    1 root     root        8,   7 Jan  1 00:21 sde7
brw-rw----    1 root     root        8,   8 Jan  1 00:21 sde8
brw-rw----    1 root     root        8,   9 Jan  1 00:21 sde9
totorweb
 
Posts: 46
Joined: Fri Oct 18, 2013 11:28 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Sun Oct 27, 2013 10:55 am

excellent

also note that the block numbering changed of the several dev nodes (the number behind the 8 on each line, thats also crucila to be able to mount the right partition.

! Remember this kernel is running in RAM so the dev nodes needs to be corrected everytime you reboot. They are not stored in the initramfs.
So the changes are lost at reboot. Tomake them persisitent I need to update the initramfs with your data and recompile the kernel.


But for the moment yu can also use the udevstart manual upload.
Normally it is part of the standalone kernel but because the 5big1 can not load kernels bigger then 2 MB I had to take it out.

When the dev nodes are corrected you should be ready to go with mdadm....(I am no expert in thatbut our member Mijzelf is)

Later today I will adapt the default initramfs for the 5big1 with the data you posted
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby totorweb » Sun Oct 27, 2013 11:03 am

making manual operations is not a problem it's just for maintenance and recovery not an eveyr day task :)

I have already download mdadm with tftp and i'am woring on it :)

I really thank you and i'll give information of my work and eventually bugs ;)

:applause
totorweb
 
Posts: 46
Joined: Fri Oct 18, 2013 11:28 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Sun Oct 27, 2013 12:04 pm

glad to hear that

ps please note that in your output disk sdd indicates that has less partitions then the other ones (only sdd1) udevstart creates accordingly only a dev node for that partition. If you need the others you will need to create them manually.
This are then the commands to create them
Code: Select all
cd /dev
mknod -m 666 sdd2 b 8 18
mknod -m 666 sdd3 b 8 19
mknod -m 666 sdd4 b 8 20
mknod -m 666 sdd5 b 8 21
mknod -m 666 sdd6 b 8 22
mknod -m 666 sdd7 b 8 23
mknod -m 666 sdd8 b 8 24
mknod -m 666 sdd9 b 8 25
mknod -m 666 sdd10 b 8 26


ps 2 There are also dev nodes wrong or missing for sda, sdb and sde...
sda3 and sda4 have wrong id's (old numbers, probably partitions are not present )
sdb3 and sdb4 have wrong id's (old numbers, probably partitions are not present )

sde3 and sde4 are missing, probably partitions are not present, here no old numbers because those were not present in original default dev nodes list

(sdc3 and sd4 are present but also this seem to be old numbers, so all disks have no 3 and 4 partition apparently. This is normal for lacie setup.
If you create this partitions you need to correct the dev nodes again by running udevstart or do it manually

So overhaul it looks something is wrong with your disk sdd

I think you will need them to restore the raid array on that disk (you mentioned the problem you had with one disk)
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby Mijzelf » Sun Oct 27, 2013 12:13 pm

fvdw wrote:This u-boot version does not set a TEXT_BASE value (address in ram where u-boot is loaded as far as I understood) in the config.mk file of the edmini_v2
Instead they set this
Code: Select all
# TEXT_BASE must equal the intended FLASH location of u-boot.
CONFIG_SYS_TEXT_BASE = 0xfff90000

If you convert this hex number to decimal then you get a number that is much bigger than the RAM size of theses boards, so it can not be the address where it is loaded in RAM. But what does is the real meaning then ?


I found this address mapping for the 88F5182:
Code: Select all
DDR SDRAM CS0 0 0x0E 256 MB 0000.0000–0FFF.FFFF
DDR SDRAM CS1 0 0x0D 256 MB 1000.0000–1FFF.FFFF
DDR SDRAM CS2 0 0x0B 256 MB 2000.0000–2FFF.FFFF
DDR SDRAM CS3 0 0x07 256 MB 3000.0000–3FFF.FFFF
Reserved - - 1 GB 4000.0000–7FFF.FFFF
PCI Express Memory 4 0x59 512 MB 8000.0000–9FFF.FFFF
PCI Memory 3 0x59 512 MB A000.0000–BFFF.FFFF
PCI Express I/O 4 0x51 64 KB C000.0000–C000.FFFF
Reserved - - - C001.0000–C7FF.FFFF
PCI I/O 3 0x51 64 KB C800.0000–C800.FFFF
Security Accelerator Internal 9 0x00 64 KB C801.0000–C801.FFFF
Reserved - - C802.0000–CFFF.FFFF
Internal Address Space3 - 1 MB D000.0000–D00F.FFFF
Reserved - - - D010.0000–DFFF.FFFF
Device CS0 1 0x1E 128 MB E000.0000–E7FF.FFFF
Device CS1 1 0x1D 128 MB E800.0000–EFFF.FFFF
Device CS2 1 0x1B 128 MB F000.0000–F7FF.FFFF
Flash Boot CS 1 0x0F 128 MB F800.0000–FFFF.FFFF
I don't know what it all means. but indeed in the highest 128MB flash is mapped. Nor flash, I guess, as AFAIK that is directly addressable.
So apparently those other boxes have a different flash type as the 5Big. Or something else is in the wrong memory range. It could also be the u-boot stack/heap, which is always somewhere in ram.

BTW, if you use gz compression for the kernel, you can squeeze some extra bytes (+/- 10%) by using lzma (or xz) compression instead.
Mijzelf
 
Posts: 255
Joined: Wed Nov 21, 2012 9:12 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Sun Oct 27, 2013 1:07 pm

thks mijzelf for this info and tip.
including udevstart (static version) will give approximate 150 kb. Thats to much I think we are now only about 70 kB below the limit

ps I edited that post of me on the text_base question. In the meantime i found that for edmin_v2 and look alikes u-boot is indeed loaded in virtual memory at the number mentioned . So those boards can handle bigger standalone kernel as u-boot is not present in first part of the RAM
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Sun Oct 27, 2013 1:08 pm

Attached a new 5big1 standalone kernel with adapted default dev nodes for the disk setup of the 5big1
In principle uploading and running udevstart should now not be necessary anymore
But it can never harm
You do not have the required permissions to view the files attached to this post.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 4 guests