Lacie Cloudbox

Re: Lacie Cloudbox

Postby fvdw » Fri Jul 19, 2013 7:43 am

check your PM box I have sent you another standalone test kernel. New are that I eliminated the initialization of usb part (not necessary for the cloudbox) Modified the leds driver, thanks to your test i found that also nwsp2 lite would have had this problem.
Lats I eliminated the initialization of I2C, it is used on the other Lacies to access the eeprom on board, seems the cloudbox doesn't have it. At least in GPL code of Lacie I do not see the initialization of I2C. Looking to the erro mesage in your dmesg output it seems indeed to be the case that is not there in the cloudbox.
We will need some adaptations in the fvdw-sl firmware itself for the cloudbox such as not loading modules for usb ports.
Would be nice if you can test this kernel and post dmesg output to see if all error messages are gone now.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby rimoth » Fri Jul 19, 2013 10:33 pm

After a number of attempts I managed to get the kernel loaded. From what I can tell there was difficulty in transferring/ftp'ing the kernel from the pc to the cloudbox. That aside once the kernel loaded, it did so quickly and here is the output from dmesg

Code: Select all
(none) login: root
Password:
root@(none):/ # dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.9.5 (root@fvdwsl-nwsp2.local) (gcc version 4.5.4 (GCC) ) #159 PREEMPT Thu Jul 18 20:24:20 GMT+1 2013
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: familybox
[    0.000000] Ignoring unrecognised tag 0x41000403
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c096f9cc, node_mem_map c09a9000
[    0.000000]   Normal zone: 512 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 65536 pages, LIFO batch:15
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 netconsole=6666@192.168.1.252/,6666@192.168.1.58/ cap=gpt,lba64
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] __ex_table already sorted, skipping sort
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 249964k/249964k available, 12180k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06a5330   (6773 kB)
[    0.000000]       .init : 0xc06a6000 - 0xc093a3b4   (2641 kB)
[    0.000000]       .data : 0xc093c000 - 0xc0970120   ( 209 kB)
[    0.000000]        .bss : 0xc0970120 - 0xc09a8b44   ( 227 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000000] sched_clock: 32 bits at 166MHz, resolution 5ns, wraps every 25769ms
[   21.748220] Calibrating delay loop... 996.14 BogoMIPS (lpj=4980736)
[   21.838179] pid_max: default: 32768 minimum: 301
[   21.838301] Mount-cache hash table entries: 512
[   21.838841] CPU: Testing write buffer coherency: ok
[   21.839165] Setting up static identity map for 0xc0509f90 - 0xc0509fcc
[   21.841606] xor: measuring software checksum speed
[   21.938175]    arm4regs  :   909.600 MB/sec
[   22.038149]    8regs     :   545.600 MB/sec
[   22.138152]    32regs    :   755.600 MB/sec
[   22.138167] xor: using function: arm4regs (909.600 MB/sec)
[   22.138184] pinctrl core: initialized pinctrl subsystem
[   22.138372] NET: Registered protocol family 16
[   22.139409] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[   22.141862] Register Driver 'dummy'
[   22.142216] Kirkwood: MV88F6281-A1, TCLK=166666667.
[   22.142237] Feroceon L2: Enabling L2
[   22.142274] Feroceon L2: Cache support initialised.
[   22.143270] familybox, skipping usb init
[   22.143281] initial MPP regs: 01002222 00003311 00000000 00000000 00000000 00000000 00000000
[   22.143315]   final MPP regs: 01002222 00003311 00000000 00000000 00000000 00000000 00000000
[   22.164749] bio: create slab <bio-0> at 0
[   22.328791] raid6: int32x1     89 MB/s
[   22.498269] raid6: int32x2    121 MB/s
[   22.668619] raid6: int32x4    110 MB/s
[   22.838441] raid6: int32x8    128 MB/s
[   22.838452] raid6: using algorithm int32x8 (128 MB/s)
[   22.838461] raid6: using intx1 recovery algorithm
[   22.839317] SCSI subsystem initialized
[   22.839768] libata version 3.00 loaded.
[   22.840035] Register Driver 'Generic PHY'
[   22.840319] Register Driver 'usbfs'
[   22.840488] usbcore: registered new interface driver usbfs
[   22.840505] Register Driver 'hub'
[   22.840660] usbcore: registered new interface driver hub
[   22.840734] Register Driver 'usb'
[   22.840856] usbcore: registered new device driver usb
[   22.841122] Register Driver 'i2c-gpio'
[   22.842808] Switching to clocksource orion_clocksource
[   22.844838] NET: Registered protocol family 2
[   22.845329] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[   22.845387] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[   22.845421] TCP: Hash tables configured (established 2048 bind 2048)
[   22.845483] TCP: reno registered
[   22.845498] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   22.845520] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   22.845690] NET: Registered protocol family 1
[   22.846007] RPC: Registered named UNIX socket transport module.
[   22.846019] RPC: Registered udp transport module.
[   22.846027] RPC: Registered tcp transport module.
[   22.846034] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   22.846047] PCI: CLS 0 bytes, default 32
[   22.869302] NetWinder Floating Point Emulator V0.97 (double precision)
[   22.869322] Register Driver 'gpio-usb'
[   22.869898] Register Driver 'alarmtimer'
[   22.956228] VFS: Disk quotas dquot_6.5.2
[   22.956281] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   22.956651] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   22.956919] NTFS driver 2.1.30 [Flags: R/W].
[   22.956967] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   22.957131] fuse init (API version 7.21)
[   22.957709] JFS: nTxBlock = 1952, nTxLock = 15622
[   22.958494] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[   22.958844] msgmni has been set to 488
[   22.959910] async_tx: api initialized (async)
[   22.960105] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[   22.960119] io scheduler noop registered
[   22.960128] io scheduler deadline registered
[   22.960149] io scheduler cfq registered (default)
[   22.960167] Register Driver 'kirkwood-pinctrl'
[   22.960354] Register Driver 'mv_xor'
[   22.960403] mv_xor mv_xor.0: Marvell shared XOR driver
[   22.992893] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   23.032889] mv_xor mv_xor.0: Marvell XOR: ( xor fill cpy )
[   23.033123] mv_xor mv_xor.1: Marvell shared XOR driver
[   23.072887] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   23.112887] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   23.118267] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   23.118922] Register Driver 'serial8250'
[   23.139213] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   23.673493] console [ttyS0] enabled
[   23.685215] brd: module loaded
[   23.692375] loop: module loaded
[   23.695581] Register Driver 'at24'
[   23.699183] Register Driver 'eeprom'
[   23.703894] Register Driver 'sd'
[   23.707331] Register Driver 'ahci'
[   23.710985] Register Driver 'sata_mv'
[   23.714917] Register Driver 'sata_mv'
[   23.718697] sata_mv sata_mv.0: version 1.28
[   23.718741] sata_mv sata_mv.0: cannot get optional clkdev
[   23.724231] sata_mv sata_mv.0: slots 32 ports 1
[   23.730254] scsi0 : sata_mv
[   23.733566] ata1: SATA max UDMA/133 irq 21
[   23.738665] Register Driver 'physmap-flash'
[   23.743150] Generic platform RAM MTD, (c) 2004 Simtec Electronics
[   23.749218] Register Driver 'mtd-ram'
[   23.753203] Register Driver 'm25p80'
[   23.757012] Register Driver 'gen_nand'
[   23.760960] Register Driver 'orion_nand'
[   23.765251] platform_driver_probe 5 retval= -19 code= 0
[   23.770542] Register Driver 'orion_spi'
[   23.774974] m25p80 spi0.0: mx25l4005a (512 Kbytes)
[   23.779931] Creating 2 MTD partitions on "spi_flash":
[   23.785057] 0x000000000000-0x00000007d000 : "u-boot"
[   23.790996] 0x00000007e000-0x00000007f000 : "u-boot-env"
[   23.797635] tun: Universal TUN/TAP device driver, 1.6
[   23.802664] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   23.809091] ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[   23.817354] ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[   23.826170] Register Driver 'mv643xx_eth'
[   23.830284] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   23.837238] libphy: mv643xx_eth smi: probed
[   23.841591] Register Driver 'mv643xx_eth_port'
[   23.848222] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:d0:4b:94:be:05
[   23.857106] PPP generic driver version 2.4.2
[   23.861662] PPP Deflate Compression module registered
[   23.866806] PPP MPPE Compression module registered
[   23.871578] NET: Registered protocol family 24
[   23.876091] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
[   23.883572] Register Driver 'pegasus'
[   23.887453] usbcore: registered new interface driver pegasus
[   23.893149] Register Driver 'ipheth'
[   23.896941] usbcore: registered new interface driver ipheth
[   23.903619] aoe: AoE v81 initialised.
[   23.907323] Register Driver 'rtc-ds1307'
[   23.911444] Register Driver 'rtc-mv'
[   23.915438] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[   23.921426] platform_driver_probe 5 retval= 0 code= 0
[   23.926637] i2c /dev entries driver
[   23.930244] Register Driver 'mv64xxx_i2c'
[   23.934542] Register Driver 'gpio-fan'
[   23.938525] Register Driver 'lm75'
[   23.942118] Register Driver 'lm77'
[   23.945767] md: linear personality registered for level -1
[   23.951231] md: raid0 personality registered for level 0
[   23.956572] md: raid1 personality registered for level 1
[   23.961857] md: raid10 personality registered for level 10
[   23.967397] md: raid6 personality registered for level 6
[   23.972682] md: raid5 personality registered for level 5
[   23.978005] md: raid4 personality registered for level 4
[   23.983512] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com
[   23.992049] device-mapper: multipath: version 1.5.1 loaded
[   23.997552] device-mapper: multipath round-robin: version 1.0.0 loaded
[   24.004082] device-mapper: multipath queue-length: version 0.1.0 loaded
[   24.010665] device-mapper: multipath service-time: version 0.2.0 loaded
[   24.017333] device-mapper: dm-log-userspace: version 1.1.0 loaded
[   24.023437] device-mapper: raid: Loading target version 1.4.2
[   24.029159] Register Driver 'mmcblk'
[   24.032953] Register Driver 'leds-gpio'
[   24.036911] leds-gpio leds-gpio: pins are not configured from the driver
[   24.043949] Register Driver 'leds-ns2'
[   24.047922] Register Driver 'leds-ns2l'
[   24.052192] Register Driver 'leds-netxbig'
[   24.056690] Register Driver 'mv_crypto'
[   24.061383] Register Driver 'hid-generic'
[   24.065726] Netfilter messages via NETLINK v0.30.
[   24.070457] nf_conntrack version 0.5.0 (3905 buckets, 15620 max)
[   24.076951] IPv4 over IPv4 tunneling driver
[   24.081989] ip_tables: (C) 2000-2006 Netfilter Core Team
[   24.087506] TCP: cubic registered
[   24.090847] NET: Registered protocol family 10
[   24.096095] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   24.101552] sit: IPv6 over IPv4 tunneling driver
[   24.106982] NET: Registered protocol family 17
[   24.111426] NET: Registered protocol family 5
[   24.115944] NET: Registered protocol family 37
[   24.120454] VFP support v0.3: not present
[   24.125510] netpoll: netconsole: local port 6666
[   24.130105] netpoll: netconsole: local IPv4 address 192.168.1.252
[   24.136267] netpoll: netconsole: interface 'eth0'
[   24.140947] netpoll: netconsole: remote port 6666
[   24.145700] netpoll: netconsole: remote IPv4 address 192.168.1.58
[   24.151765] netpoll: netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[   24.158644] netpoll: netconsole: device eth0 not up yet, forcing it
[   24.166825] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   24.242869] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   24.282902] ata1.00: ATA-8: ST3000DM001-1CH166, CC44, max UDMA/133
[   24.289057] ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   24.352893] ata1.00: configured for UDMA/133
[   24.373136] scsi 0:0:0:0: Direct-Access     ATA      ST3000DM001-1CH1 CC44 PQ: 0 ANSI: 5
[   24.382077] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[   24.390215] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   24.395697] sd 0:0:0:0: [sda] Write Protect is off
[   24.400472] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   24.400576] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   24.453081]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
[   24.461000] sd 0:0:0:0: [sda] Attached SCSI disk
[   25.956874] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   25.966625] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   25.976412] console [netcon0] enabled
[   25.980074] netconsole: network logging started
[   25.984636] Register Driver 'gpio-keys'
[   25.988955] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   25.996186] rtc-mv rtc-mv: setting system clock to 2001-05-10 12:26:39 UTC (989497599)
[   26.011805] Freeing init memory: 2640K
root@(none):/ #


I hope there are not major problems with the output - there's still mention of usb and possibly an issue with leds, but then again I could be completely wrong!
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby fvdw » Fri Jul 19, 2013 10:43 pm

thanks for testing, it looks good.
yes it mentions some registering of usb but that is fine, it is because this is a kernel also for the other lacie box. Not all of them are used by the cloudbox.
This is the proof that it skips usb initialization
Code: Select all
[   22.143270] familybox, skipping usb init


Also the waiting for I2C is gone as well as the bug with leds-ns2l driver registration.
So basically everything looks ok :thumbup :punk

What are the leds doing on the cloudbox ? Is the blue led on there will not be a lot of sata activity so it won't blink a lot in this setup. You could mount a partition and o a directy listing so see if that let it blink
But thats for later concern if they don't do yet what we want, with or without the leds the kernel can run...
Think we can go on with this kernel for normal operation in combination with the fvdw-sl firmware.
need to make some adaptations in the boot scripts of for the cloudbox to avoid that it tries to load kernel modules for usb. Also jocko has to make some adaptations to disable a few usb functions in the web interface of the firmware
But that will be later. Coming week I will be not much on line because of holiday activities

ps The problem with tftp could occur if you use a wireless connection. If you are doing that then using a wired will give more stable result.
Otherwise check your cables and connectors
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby rimoth » Mon Jul 29, 2013 9:49 pm

I did some further testing with the kernel. Output from dmesg is the same, which you would expect. As for the led activity, the blue led is flashing on-off at a constant rate (fairly slow - 0.5 seconds). As you suggested I mounted sda5 and listed the lib directory but this had no bearing on the led activity.

Let me know if you want me to do further tests.

ps. I was using a wireless connection, which could be the source of the kernel transfer problem. Thanks for the tip.
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby fvdw » Mon Jul 29, 2013 10:45 pm

ok , I will prepare a kernel for running with fvdw-sl (tomorrow tuesday)

basically the sequence will be prepare a disc with using the the fvdw-sl console as it was a nwsp2. This will write a kernel not supporting the cloudbox, butbefore rebooting we will upload the new kernel using telnet client and tftp server. This we will write to sda6 and then reboot.
ps the led blinking will an issue to be studied later. Lets see if it wants to run the firmware.
It will complain that it can't find modules but also that is for later as most of the modules loaded are for usb support.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby fvdw » Mon Jul 29, 2013 10:56 pm

pm send with trial kernel for testing if the cloudbox can run the fvdw-sl firmware
Connect to the cloudbox with fvdw-sl console and choose as action install firmware-14-0. Choose the right standalone kernel to be loaded, the one you used the last time. Now follow the instructions to install the firmware but do not reboot at the end.
Using the telnet client upload the new run time kernel with tftp Put the kernel in the tftp folder of the fvdw-sl console
Code: Select all
tftp -l /UIMAGE-395-NWSP2CL-161 -r UIMAGE-395-NWSP2CL-161 -g ip-pc

replace ip-pc by actual ip addres of the pc running the fvdw-sl console)
When the kernel is uploaded write it to sda6
Code: Select all
dd if=/UIMAGE-395-NWSP2CL-161 of=/dev/sda6

After this sync the disk and reboot
Code: Select all
sync
reboot -f


and see if the webinterface comes up.
There might be a problem with starting the web server. If so try to connect to it using ssh server (for instance by using putty, username: root, password: giveit2me)
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby rimoth » Tue Jul 30, 2013 10:18 pm

I have had limited success so far. As you would expect I am able to load the standalone kernel and start off the install process.

I selected the network space 2 classic option. The first time I tried I selected to backup the disk partitions. However this uses sda9 locally on the nas to backup the disk partitions. I tried changing the install script so that it used sda2 instead, but unfortunately this did not work. It appeared to fail at the dd command backing up the first image sda6.

I then tried again but this time elected not to backup up the disk images. The installer then progressed to the stage of uploading the new firmware. This took an hour at which point it then failed to write the firmware to the disk.

I believe the failure may be due to the disk not having a clear partition table, as the installer process clearly warns.

I tried to delete the partitions using fdisk, but I believe this doesn't support 2TB+ drives.

I am attempting another install as I type (currently copying the firmware to the nas) and I will post back results.

Any guidance on how to clear the partition table from the standalone kernel would be appreciated
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby fvdw » Tue Jul 30, 2013 10:24 pm

yes the installer supports disk bigger then 2TB but then you need to select GPT partition table when asked.
Indeed do not select to back up the images
and be sure to use the latest version of the console. version 5 had some bugs wrt writing firmware
And do not use wireless to upload files via fvdw-sl console seems the tftp server doesn't like dropouts.
Uploading the firmware should take less then 1 minute.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby rimoth » Tue Jul 30, 2013 10:31 pm

The current upload of the firmware is taking ages (an hour eta). I am going to cancel it and start again with a wired connection.

One question should I select classic or lite when prompted by the installer?
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby fvdw » Tue Jul 30, 2013 10:33 pm

It doesn't matter if you selct classic or Lite, the difference is that the classic might need a bootloader (U-boot) upgrade to be able to use GPT partition tables (to get support for disk bigger ten 2 TB)
if you have GPT partition tables, you must use "gdisk" to delete them manually
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Lacie cloudbox (white casing)

Who is online

Users browsing this forum: No registered users and 12 guests