lacie 5 big network v.1 please support for fvdw

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

Postby jahotinc » Wed Aug 13, 2014 8:39 pm

This is boot.log before as it is now, before doing any change:

Code: Select all
login as: root
root@192.168.1.238's password:
root@mc:/ # cat /boot.log
start boot log
detect and set platform
5big1
UIMAGE-395-5BIG1-25
5big1
update dev nodes
booting using  root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = 5big1
source = buttons-nwsp2
buttons-nwsp2 daemon started
Wed Aug 13 21:17:12 UTC 2014
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: 'cifs.ko': unknown symbol in module or invalid parameter
modprobe: 'isofs.ko': unknown symbol in module or invalid parameter
modprobe: 'ntfs.ko': unknown symbol in module or invalid parameter
modprobe: 'fuse.ko': unknown symbol in module or invalid parameter
modprobe: 'usblp.ko': unknown symbol in module or invalid parameter
modprobe: 'sunrpc.ko': unknown symbol in module or invalid parameter
modprobe: 'sunrpc.ko': unknown symbol in module or invalid parameter
modprobe: 'lockd.ko': unknown symbol in module or invalid parameter
modprobe: 'nfs.ko': unknown symbol in module or invalid parameter
modprobe: 'sunrpc.ko': unknown symbol in module or invalid parameter
modprobe: 'sunrpc.ko': unknown symbol in module or invalid parameter
modprobe: 'lockd.ko': unknown symbol in module or invalid parameter
modprobe: 'nfsd.ko': unknown symbol in module or invalid parameter
modprobe: 'iscsi_trgt.ko': unknown symbol in module or invalid parameter
modprobe: 'scsi_transport_iscsi.ko': unknown symbol in module or invalid parameter
modprobe: 'libiscsi.ko': unknown symbol in module or invalid parameter
modprobe: 'scsi_transport_iscsi.ko': unknown symbol in module or invalid parameter
modprobe: 'libiscsi.ko': unknown symbol in module or invalid parameter
modprobe: 'libiscsi_tcp.ko': unknown symbol in module or invalid parameter
modprobe: 'scsi_transport_iscsi.ko': unknown symbol in module or invalid parameter
modprobe: 'iscsi_tcp.ko': unknown symbol in module or invalid parameter
modprobe: 'videodev.ko': unknown symbol in module or invalid parameter
modprobe: 'videodev.ko': unknown symbol in module or invalid parameter
modprobe: 'v4l2-common.ko': unknown symbol in module or invalid parameter
modprobe: 'videodev.ko': unknown symbol in module or invalid parameter
modprobe: 'videodev.ko': unknown symbol in module or invalid parameter
modprobe: 'videobuf2-core.ko': unknown symbol in module or invalid parameter
modprobe: 'videobuf2-memops.ko': unknown symbol in module or invalid parameter
modprobe: 'videobuf2-vmalloc.ko': unknown symbol in module or invalid parameter
modprobe: 'uvcvideo.ko': unknown symbol in module or invalid parameter
mount: unknown filesystem type 'nfsd'
configure loopback netwerk interface
setting reboot and standby
5big1
rebootd-isp1
5big1
standbyd-isp1
start fan
fan5big daemon started
starting php based setup routines step 1

 * Found XML database configuration file...      [ OK ]
 * Updating Disks database...                    [ OK ]
 * Starting mount of volumes...
   - Mounting volume Vol-A:              [ OK ]
   - Mounting volume Vol-B:              [ OK ]
   - Mounting volume Vol-C:              [ OK ]
   - Mounting volume Vol-D:              [ OK ]
 * Finishing mount of volumes...                 [ OK ]
 * Starting udevd...                                     [ OK ]
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ]
 * Configuring LAN interface...                  [ OK ]
 * Initializing Timezone...                      [ OK ]
 * Starting web server...                                [ OK ]
 * Configuring Disks...                                  [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Configuring System Users...
        Root password: use default password
        Set users, linux and samba accounts      [ OK ]
 * Starting syncawayd...                                 [ OK ]
 * Starting Fvdw-sl Discovery Daemon...  [ OK ]
start rpcbind service
starting php based setup routines step 2
 * Starting dropbear...                                  [ OK ]
 * Kill temporary dropbear...                    [ OK ]
starting php based setup routines step 3
 * Starting daemon update Hosts File...  [ OK ]
 * Starting Disk Temperature Guard...    [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...                     [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 15.3
    built on: May 30 2014

    LAN IP address: 192.168.1.238 (static)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
else loop1 finished
rcS finished
root@mc:/ #
jahotinc
 
Posts: 35
Joined: Mon Apr 07, 2014 11:39 am

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

Postby jahotinc » Wed Aug 13, 2014 9:43 pm

you can count with my help and my 5bg1 if you need to do some more testings.

now the new kernel is loaded as 'external'. These are the results:

dmesg
Code: Select all
root@mc:/ # dmesg
Booting Linux on physical CPU 0x0
Linux version 3.9.5 (root@fvdwsl-5big2.local) (gcc version 4.8.1 (GCC) ) #25 Thu Feb 27 22:22:32 GMT+1 2014
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: LaCie 5Big1 Network
Clearing invalid memory bank 0KB@0x00000000
Clearing invalid memory bank 0KB@0x00000000
Clearing invalid memory bank 0KB@0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat c039aed8, node_mem_map c03cb000
  Normal zone: 256 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 32768 pages, LIFO batch:7
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F5281 productType=5Big reset=0
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
__ex_table already sorted, skipping sort
Memory: 128MB = 128MB total
Memory: 126024k/126024k available, 5048k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc0355fdc   (3384 kB)
      .init : 0xc0356000 - 0xc0374ebc   ( 124 kB)
      .data : 0xc0376000 - 0xc039bee0   ( 152 kB)
       .bss : 0xc039bee0 - 0xc03ca8dc   ( 187 kB)
NR_IRQS:64
sched_clock: 32 bits at 166MHz, resolution 5ns, wraps every 25769ms
Console: colour dummy device 80x30
Calibrating delay loop... 498.89 BogoMIPS (lpj=2494464)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc028ffc8 - 0xc0290004
NET: Registered protocol family 16
DMA: preallocated 1024 KiB pool for atomic coherent allocations
Register Driver 'dummy'
5big1 init started
Orion ID: MV88F5281-D0. TCLK=166666667.
Orion: Applying 5281 D0 WFI workaround.
5big1 init 1
initial MPP regs: 00000003 00000000 00170000
  final MPP regs: 00000003 00000000 00170000
5big1 init 2
net5big: powering up SATA drives
5big1 init 3
5big1 init 4
5big1 init 5
5big1 init 6
5big1 init 7
5big1 init 8
5big1 init 9
5big1 init 10
5big1 init 11
5big1 init 12
net5big: turning off power-off control GPIO
net5big: Flash writing is not yet supported.
5big1 init end
orion_gpio_is_valid: invalid GPIO 20
orion_gpio_is_valid: invalid GPIO 20
net5big_pci_preinit failed to gpio_request 20
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0000:00:00.0: [11ab:5281] type 00 class 0x058000
pci 0000:00:00.0: reg 10: [mem 0xf1000000-0xf10fffff 64bit pref]
pci 0000:00:00.0: reg 18: [mem 0x00000000-0x07ffffff]
PCI: bus0: Fast back to back transfers disabled
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
PCI host bridge to bus 0000:01
pci_bus 0000:01: root bus resource [mem 0xe8000000-0xefffffff]
pci_bus 0000:01: root bus resource [io  0x10000-0x1ffff]
pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
pci 0000:01:00.0: [11ab:5281] type 00 class 0x058000
pci 0000:01:00.0: reg 10: [mem 0x00000000-0x07ffffff 64bit pref]
pci 0000:01:00.0: reg 18: [mem 0x10000000-0x1fffffff 64bit pref]
pci 0000:01:00.0: reg 20: [mem 0xf1000000-0xf10fffff 64bit]
pci 0000:01:00.0: reg 30: [mem 0xe0000000-0xe7ffffff pref]
pci 0000:01:00.0: supports D1 D2
pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot
pci 0000:01:07.0: [11ab:6081] type 00 class 0x010000
pci 0000:01:07.0: reg 10: [mem 0x40000000-0x400fffff 64bit]
pci 0000:01:07.0: reg 18: [io  0xf0100000-0xf01000ff]
PCI: bus1: Fast back to back transfers enabled
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
pci 0000:01:07.0: BAR 0: assigned [mem 0xe8000000-0xe80fffff 64bit]
pci 0000:01:07.0: BAR 2: assigned [io  0x10000-0x100ff]
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
Register Driver 'Generic PHY'
Register Driver 'usbfs'
usbcore: registered new interface driver usbfs
Register Driver 'hub'
usbcore: registered new interface driver hub
Register Driver 'usb'
usbcore: registered new device driver usb
Register Driver 'i2c-gpio'
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
PCI: CLS 32 bytes, default 32
Register Driver 'alarmtimer'
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 246
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Register Driver 'mv_xor'
mv_xor mv_xor.0: Marvell shared XOR driver
mv_xor mv_xor.0: Self-test copy failed compare, disabling
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Register Driver 'serial8250'
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
Register Driver 'serial'
brd: module loaded
loop: module loaded
Register Driver 'at24'
Register Driver 'eeprom'
Register Driver 'sd'
Register Driver 'ahci'
Register Driver 'sata_mv'
sata_mv 0000:01:07.0: version 1.28
sata_mv 0000:01:07.0: Gen-II 32 slots 8 ports SCSI mode IRQ via INTx
scsi0 : sata_mv
scsi1 : sata_mv
scsi2 : sata_mv
scsi3 : sata_mv
scsi4 : sata_mv
scsi5 : sata_mv
scsi6 : sata_mv
scsi7 : sata_mv
ata1: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8022000 irq 52
ata2: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8024000 irq 52
ata3: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8026000 irq 52
ata4: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8028000 irq 52
ata5: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8032000 irq 52
ata6: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8034000 irq 52
ata7: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8036000 irq 52
ata8: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8038000 irq 52
Register Driver 'sata_mv'
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: cannot get optional clkdev
sata_mv sata_mv.0: slots 32 ports 5
scsi8 : sata_mv
scsi9 : sata_mv
scsi10 : sata_mv
scsi11 : sata_mv
scsi12 : sata_mv
ata9: SATA max UDMA/133 irq 29
ata10: SATA max UDMA/133 irq 29
ata11: SATA max UDMA/133 irq 29
ata12: SATA max UDMA/133 irq 29
ata13: SATA max UDMA/133 irq 29
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
Register Driver 'mv643xx_eth'
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
libphy: mv643xx_eth smi: probed
Register Driver 'mv643xx_eth_port'
mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:d0:4b:88:5b:ff
mousedev: PS/2 mouse device common for all mice
Register Driver 'rtc-ds1307'
Register Driver 'rtc-ds1374'
Register Driver 'rtc-rs5c372'
i2c /dev entries driver
Register Driver 'mv64xxx_i2c'
rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.6
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
at24 0-0050: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
Register Driver 'g762'
g762 probe started
g762 probe 1
g762 probe 2
g762 probe 3
g762 probe 4
g762 probe 5
g762 probe 6
g762 probe 7
Register Driver 'gpio-fan'
Register Driver 'lm75'
Register Driver 'lm77'
Register Driver 'leds-gpio'
Register Driver 'mv_crypto'
Netfilter messages via NETLINK v0.30.
IPv4 over IPv4 tunneling driver
TCP: cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 5
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
console [netcon0] enabled
netconsole: network logging started
rtc-rs5c372 0-0032: setting system clock to 2014-08-13 22:28:13 UTC (1407968893)
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: ST31500341AS, CC4H, max UDMA/133
ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      ST31500341AS     CC4H PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 0
device-name= sata_mv
fvdw2 disk index after get_sd_name = 3
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 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] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdd: sdd4 < sdd5 sdd6 sdd7 sdd8 >
sd 1:0:0:0: [sdd] Attached SCSI disk
ata9: failed to resume link (SControl 0)
ata9: SATA link down (SStatus 0 SControl 0)
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ATA-8: ST31500341AS, CC4H, max UDMA/133
ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access     ATA      ST31500341AS     CC4H PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 1
device-name= sata_mv
fvdw2 disk index after get_sd_name = 2
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sdc
sd 2:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc4 < sdc5 sdc6 sdc7 sdc8 >
sd 2:0:0:0: [sdc] Attached SCSI disk
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-8: ST31500341AS, CC4H, max UDMA/133
ata4.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access     ATA      ST31500341AS     CC4H PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 2
device-name= sata_mv
fvdw2 disk index after get_sd_name = 1
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sdb
sd 3:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb4 < sdb5 sdb6 sdb7 sdb8 >
sd 3:0:0:0: [sdb] Attached SCSI disk
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-8: WDC WD1502FAEX-007BA0, 05.01D05, max UDMA/133
ata5.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
scsi 4:0:0:0: Direct-Access     ATA      WDC WD1502FAEX-0 05.0 PQ: 0 ANSI: 5
fvdw1 disk index before get_sd_name = 3
device-name= sata_mv
fvdw2 disk index after get_sd_name = 0
fvdw3 prefix[0]=s  prefix[1]=d
fvdw4 diskname = sda
sd 4:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 4:0:0:0: [sda] Attached SCSI disk
ata6: SATA link down (SStatus 0 SControl 300)
ata7: SATA link down (SStatus 0 SControl 300)
ata8: SATA link down (SStatus 0 SControl 300)
ata10: failed to resume link (SControl 0)
ata10: SATA link down (SStatus 0 SControl 0)
ata11: failed to resume link (SControl 0)
ata11: SATA link down (SStatus 0 SControl 0)
ata12: failed to resume link (SControl 0)
ata12: SATA link down (SStatus 0 SControl 0)
ata13: failed to resume link (SControl 0)
ata13: SATA link down (SStatus 0 SControl 0)
EXT3-fs (sda7): recovery required on readonly filesystem
EXT3-fs (sda7): write access will be enabled during recovery
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda7): recovery complete
EXT3-fs (sda7): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:55.
Freeing init memory: 120K
EXT3-fs (sda7): warning: checktime reached, running e2fsck is recommended
EXT3-fs (sda7): using internal journal
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda5): warning: checktime reached, running e2fsck is recommended
EXT3-fs (sda5): using internal journal
EXT3-fs (sda5): recovery complete
EXT3-fs (sda5): mounted filesystem with ordered data mode
Adding 514076k swap on /dev/sda3.  Priority:-1 extents:1 across:514076k
NTFS driver 2.1.30 [Flags: R/W MODULE].
fuse init (API version 7.21)
Register Driver 'usblp'
usbcore: registered new interface driver usblp
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
iSCSI Enterprise Target Software - version trunk
iscsi_trgt: Registered io type fileio
iscsi_trgt: Registered io type blockio
iscsi_trgt: Registered io type nullio
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
Linux video capture interface: v2.00
uvcvideo: Unable to create debugfs directory
Register Driver 'uvcvideo'
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda8): warning: checktime reached, running e2fsck is recommended
EXT3-fs (sda8): using internal journal
EXT3-fs (sda8): recovery complete
EXT3-fs (sda8): mounted filesystem with ordered data mode
EXT2-fs (sdb8): warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs (sdc8): warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs (sdd8): warning: mounting unchecked fs, running e2fsck is recommended
udevd (892): /proc/892/oom_adj is deprecated, please use /proc/892/oom_score_adj instead.
udev: starting version 130
mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
root@mc:/ #


boot.log
Code: Select all
root@mc:/ # cat /boot.log
start boot log
detect and set platform
5big1
UIMAGE-395-5BIG1-25
5big1
update dev nodes
booting using  root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = 5big1
source = buttons-nwsp2
buttons-nwsp2 daemon started
Wed Aug 13 22:28:22 UTC 2014
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
configure loopback netwerk interface
setting reboot and standby
5big1
rebootd-isp1
5big1
standbyd-isp1
start fan
fan5big daemon started
starting php based setup routines step 1

 * Found XML database configuration file...    [ OK ]
 * Updating Disks database...           [ OK ]
 * Starting mount of volumes...
   - Mounting volume Vol-A:        [ OK ]
   - Mounting volume Vol-B:        [ OK ]
   - Mounting volume Vol-C:        [ OK ]
   - Mounting volume Vol-D:        [ OK ]
 * Finishing mount of volumes...        [ OK ]
 * Starting udevd...                 [ OK ]
 * Generating Hosts File...           [ OK ]
 * Configuring System Hostname...        [ OK ] 
 * Configuring LAN interface...        [ OK ]
 * Initializing Timezone...           [ OK ]
 * Starting web server...              [ OK ]
 * Configuring Disks...              [ OK ]
 * Configuring Samba...                [ OK ]
 * Configuring System Users...
   Root password: use default password
   Set users, linux and samba accounts    [ OK ]
 * Starting syncawayd...              [ OK ]
 * Starting Fvdw-sl Discovery Daemon...    [ OK ]
start rpcbind service
starting php based setup routines step 2
 * Starting dropbear...              [ OK ]
 * Kill temporary dropbear...          [ OK ]
starting php based setup routines step 3
 * Starting daemon update Hosts File...  [ OK ]
 * Starting Disk Temperature Guard...     [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...           [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 15.3
    built on: May 30 2014

    LAN IP address: 192.168.1.238 (static)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
else loop1 finished
rcS finished
root@mc:/ #
jahotinc
 
Posts: 35
Joined: Mon Apr 07, 2014 11:39 am

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

Postby jahotinc » Wed Aug 13, 2014 9:48 pm

one little difference is that now thw front blue light is off. i put it off in the web interface but it has not switched off until this version

And other question: is the internal fan working? the temperature of disks is increasing and i don't hear any fan noise inside.
jahotinc
 
Posts: 35
Joined: Mon Apr 07, 2014 11:39 am

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

Postby fvdw » Wed Aug 13, 2014 10:20 pm

thanks for testing so we need to use kernel 25 and not 24. The dmesg output of kernel 25 and the boot.log with that kernel are without failure os to see.
With kernel 24 you see that inserting of the kernel modules fails.

To write the 25 kernel to sda6 you could do the following.
Boot the 5big1 by using the load external kernel feature and choose the #25 kernel to load.
When the firmware is up and running the samba server should work and you should be able to see a shared folder with name "public' in your network.
(using this in explorer \\ip-nas\public should open it, of course replace ip-nas in this line by the actual ip of the 5big1)
The shared folder public was made during installation of the firmware

Put the UIMAGE-395-5BIG1-25 kernel in that shared folder.
Now connect to the ssh server of the 5big1 with putty and write the kernel to disk partition sda6 with this command
Code: Select all
dd if=/share/1000/public/UIMAGE-395-5BIG1-25 of=/dev/sda6


Then reboot the 5big1 using the command in the webinterface. Now the 5big1 should boot with #25 kernel by itself.

ps I have some family issues right now to take care off so I have on this moment less time for support, sorry for this. In a few days it will be better
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 jahotinc » Fri Aug 15, 2014 9:14 pm

The update is done
jahotinc
 
Posts: 35
Joined: Mon Apr 07, 2014 11:39 am

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

Postby taetae » Sun Aug 31, 2014 10:24 am

@fvdw

Sorry for my absence but I'm back for business reasons have not been there if you need a hand I'm here to test...

until I read the previous posts a cafe and gift to you and Jocko;-)


edit:

lights are always flashing my nas both behind and ahead of the blue and the fan is not coming in never really understand whether or pate turns and stops
@fvdw
I'm installing directly the 15.3 from version 15.1 just finished let you know
Control of the request code: what should I put? (find "unzip")
but should not be ....


@jahotinc

how it behaves in these circumstances instead ???


Ps: miss for a week for 5 days and then I'll have the nas available before leaving for work so I am testing various-)
You do not have the required permissions to view the files attached to this post.
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

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

Postby fvdw » Sun Aug 31, 2014 10:19 pm

Hi tatue to upgrade and using the "bin file you need to use the lacie-firmware menu

and thanks very much for your donation
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 gvideo » Tue Nov 04, 2014 10:26 pm

gvideo wrote:thank you! I read the forum .. I try out tomorrow :)
good night!


Dear fvdw!
We have corresponded in the summer for a Lacie5big network. You gave me guidance on how I can upload the firmware. I made it with your help. Since then, everything works well. Thank you very much for your help!
Sincerely,
lacka
gvideo
 
Posts: 7
Joined: Mon Jul 07, 2014 1:48 pm

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

Postby isrgil » Wed Jan 28, 2015 11:01 pm

good night
I attached the log of installation on the occasion of trying to find the cause of why can not I finish the installation successfully
sorry my English

root
Password:
Login incorrect
(none) login: root
Password:
root@(none):/ # fdisk /dev/sda

The number of cylinders for this disk is set to 60801.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 9 72 514080 83 Linux
/dev/sda2 73 136 514080 83 Linux
/dev/sda3 137 200 514080 82 Linux swap
/dev/sda4 201 60801 486777532+ 5 Extended
/dev/sda5 209 312 835380 83 Linux
/dev/sda6 321 328 64260 83 Linux
/dev/sda7 337 400 514080 83 Linux
/dev/sda8 409 60801 485106772+ 83 Linux

Command (m for help): d
Partition number (1-8): 1

Command (m for help): d
Partition number (1-8): 2

Command (m for help): d
Partition number (1-8): 3

Command (m for help): d
Partition number (1-8): 4

Command (m for help): p

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
root@(none):/ # fdisk -l /dev/sda

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
root@(none):/ # tftp -r busybox1 -l /bin/busybox1 -g 192.168.1.104

busybox1 45% |************************* | 476k 0:00:01 ETA
busybox1 100% |

********************************************************| 1049k 0:00:00 ETA
busybox1 100% |********************************************************| 1049k

0:00:00 ETA
root@(none):/ # chmod 755 /bin/busybox1
root@(none):/ # mv /bin/tar /bin/tar-old
root@(none):/ # cd /bin
root@(none):/bin #
root@(none):/bin # cd /binln -s busybox1 tar
root@(none):/bin # cd /
root@(none):/ # tftp -r fvdw-sl-installer.sh -l fvdw-sl-installer -g 192.168.1.104

fvdw-sl-installer.sh 100% |********************************************************| 19462 0:00:00 ETA
fvdw-sl-installer.sh 100% |

********************************************************| 19462 0:00:00 ETA
root@(none):/ # chmod 755 fvdw-sl-installer
root@(none):/ # /fvdw-sl-installer 192.168.1.104
Installer version 1.0.1
/fvdw-sl-installer: line 12: nwsp2firmware: not found
/fvdw-sl-installer: line 13: nwsp2kernel: not found
step 1: check to make sure all dependencies are present on the server and nas:
Dialog:
dialog 93% |**************************************************** | 318k 0:00:00 ETA
dialog 100% |

********************************************************| 341k 0:00:00 ETA
dialog 100% |********************************************************| 341k

0:00:00 ETA
Installed

xterm 100% |********************************************************| 3258 0:00:00 ETA
xterm 100% |

********************************************************| 3258 0:00:00 ETA
xterm installed

mke2fs-ext3 100% |********************************************************| 261k 0:00:00 ETA
mke2fs-ext3 100% |

********************************************************| 261k 0:00:00 ETA
mke2fs-ext3 installed
[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=(B(B










 (0

[37mlqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0

[47mx(B(0x(B  (0x(B(0x(B

[30m  (0x(B(0x(B  (0x(B

[30m(0x(B  (0x(B(0x(B 

[44m (0x(B(0x(B  (0x(B

[20;81H(0x(B  (0x(B(0x(B 

[22;21H (0x(B(0x(B  (0

[47mtqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B  (0x(B

[24;48H(B< OK >(B(0x(B  (0

[37mm(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  

[24;51H(BWelcome to the fvdw-sl firmware installer.This installer will prepare your harddisk for use inyour Lacie NAS.

[20;24HAll we need is some info, which will be asked in thenext minutes.(B[?1000l
[?1l>[?1049h(B[?7h[?1049l

[2J[?1h=[?1000h[?1h=[?1h=(B(B











 (0lqqqqqqqqqq(B

[34mfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0x(B

[15;81H(0x(B  (0x(B What is the unique device ID of your disk?(0

[47mx(B  (0x(B(0x(B  (0

[47mx(B If connected to main sata interface this should be : sda (0x(B  (0x(B

[30m (0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0k(B (0x(B 

[20;21H (0x(B (0x(B(0x(B (0x(B 

[36m (0x(B (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B (0

[0mx(B  (0tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B

 (0x(B(B< OK >(B <C

(Bancel(B>(0x(B  (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  (B

[47m(Bs(Bd(Ba(B[?1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=

[?1000h[?1h=(B(B













 (0lqqqqqqqqqq(B

[47mfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0x(B(0

[0mx(B  (0x(B(0x(B  (0

[0;1mx(B(0x(B  (0

[47mtqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B  (0x(B

[21;40H(B< Yes >(B <(B (BN(Bo (B>

[18X(0x(B  (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B

[0;1m  (BIs device /dev/sda the original Lacie disk with Lacie

[19;24Hfirmware?(B<(B (BY(Bes (B>(B< N

[33mo >(B[?1000l
[?1l>1
[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=(B(B











 (0

[0;1mlqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0

[37mx(B(0x(B  (0x(B(0x(B

[0;1m  (0x(B(0x(B  (0x(B

[0m(0x(B  (0x(B(0x(B 

[36m (0x(B(0x(B  (0x(B

[58X(0x(B  (0x(B(0x(B 

[23;21H (0tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B  (0x

(B(B< Yes >(B <(B (BN(Bo

(B>(0x(B  (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  (B

[16;24HNot the original disk, does it have an empty partitiontable ?If not installation will fail or give erratic results(B

[26;83H[?1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=(B(B










[K


 (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B

[K (0x(B(0x(B  (0x(B

(0x(B  (0x(B(0x(B  

(0x(B(0x(B  (0x(B(0

[47mx(B  (0x(B(0x(B  (0

[47mx(B(0x(B  (0

[47mtqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B  (0x(B

[23;40H(B< Yes >(B <(B (BN(Bo (B>

[18X(0x(B  (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B

[0;1m  (BIs your NAS a network space 2 classic?(B

[m[?1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=(B(B









[K



 (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B

[44m (0x(B(0x(B  (0x(B

[16;81H(0x(B  (0x(B(0x(B 

[18;21H (0x(B(0x(B  (0x(B(0

[0mx(B  (0x(B(0x(B  (0

[0;1mx(B(0x(B  (0

[47mtqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B  (0x(B

[23;40H(B< Yes >(B <(B (BN(Bo (B>

[18X(0x(B  (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B

[0;1m  (BDoes your nwsp2-classic bootloader support GPT partion

[17;24Htables?If not you cannot use a disk bigger then 2 TBIn that case you need to upgrade the bootlader first(B[?1000l


[?1l>[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=(B(B











 

(0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0

[0;1mx(B(0x(B  (0x(B(0x

(B  (0x(B(0x(B  (0x

(B(0x(B  (0x(B(0x(B

 (0x(B(0x(B  (0x(B

[58X(0x(B  (0tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B

[0;1m  (0x(B(B< Yes >(B

<(B (BN(Bo (B>(0x(B  (0m

(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  

(BIs the harddisk capacity bigger then 2 TB?(B<(B (BY(Bes (B>

[23;56H(B< No >(B[?1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=[?

1000h[?1h=(B(B











 (0lqqqqqqqqqq(Bfvdw-sl

firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0x(B(0

[47mx(B  (0x(B(0x(B  (0

[47mx(B(0x(B  (0x(B(0x(B

[30m  (0x(B(0x(B  (0x(B

[30m(0x(B  (0x(B(0x(B 

[44m (0tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0u(B  (0

[37mx(B(B< Yes >(B <(B (BN(B

[30mo (B>(0x(B  (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  (B

[16;24HDo you want to use GPT partition table ?When you answer [no] then msdos partion table will beused(B<(B

[0;1m (BY(Bes (B>(B< No >(B[?

1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=(B(B













[14;21H (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B

[1K (0x(B(0x(B  (0x(B(0

[47mx(B  (0x(B(0x(B  (0

[47mx(B(0x(B  (0x(B(0x(B

[30m  (0x(B(0x(B  (0x(B

[30m(0x(B  (0tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0

[30mu(B  (0x(B(B< Yes >(B

[30m <(B (BN(Bo (B>(0x(B  (0

[0;1mm(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  

[23;42H(BReady to make a new msdos partition table on /dev/sdaAll data on the disk will be lost!Do you want to proceed ?

[23;42H(B[?1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=[?25l(B(B

[H













 (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0

[0mk(B (0x(B(0x(B  (0

[47mx(B New disk, assuming empty with partition table (0x(B  (0x(B

[30m(0x(B  (0x(B (0

[47mlqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0k(B (0x(B  (0

[47mx(B (0x(B0%(0x(B (0x(B 

[22;21H (0x(B (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B (0

[47mx(B  (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B 

[44m (B(B (B2(B[?12l[?25h

[24;83H[?1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=[?25l(B(B








[K






 (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B

[0;1m (0x(B(0x(B  (0x(B

Creating new partition partitioning scheme on /dev/sda. (0x(B  (0x(B(0

[0mx(B  (0x(B (0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0

[0mk(B (0x(B  (0x(B (0x(B

[21;52H0%(0x(B (0x(B  (0x(B (0

[47mm(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B (0x(B  (0

[47mm(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  

[39;49m(B(B (B25(B[?12l[?25h[?1000l
[?1l>
The number of cylinders for this disk is set to 60801.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (9-60801, default 60801):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (73-60801, default 60801):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (137-60801, default 60801):
Command (m for help): Partition number (1-4): Hex code (type L to list codes): Changed system type of partition 3 to 82 (Linux swap)

Command (m for help): Command action
e extended
p primary partition (1-4)
Selected partition 4
First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (201-60801, default 60801): Using default value 60801

Command (m for help): First cylinder (201-60801, default 201): Last cylinder or +size or +sizeM or +sizeK (209-60801, default 60801):
Command (m for help): First cylinder (201-60801, default 201): Last cylinder or +size or +sizeM or +sizeK (321-60801, default 60801):
Command (m for help): First cylinder (201-60801, default 201): Last cylinder or +size or +sizeM or +sizeK (337-60801, default 60801):
Command (m for help): First cylinder (201-60801, default 201): Last cylinder or +size or +sizeM or +sizeK (409-60801, default 60801): Using default value 60801

Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=[?25l(B(B















[16;21H (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B

[1K (0x(B(0x(B  (0x(B msdos Partitioning

scheme created on /dev/sda (0x(B  (0x(B(0x(B

[0;1m  (0x(B (0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0k(B

[0m (0x(B  (0x(B (0x(B0%

[21;78H(0x(B (0x(B  (0x(B (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B (0x(B  (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  (B(B

[0;1;7m (B2(B[?12l[?25h[?1000l
[?1l>[?1049h(B[?7h[?1049l[?1h=

[?1000h[?1h=[?25l(B(B













 (0lqqqqqqqqqq(B

[47mfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0x(B(0

[0mx(B  (0x(B Formatting /dev/sda5, this will take some time (0x

(B  (0x(B(0x(B  (0x

(B (0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0k(B (0x(B 

[K (0x(B (0x(B0%(0x(B (0x(B

[0;1m  (0x(B (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B

[0m (0x(B  (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

(B  (B(B (B3

[39;49m(B[?12l[?25h[?1000l
[?1l>mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
52304 inodes, 208845 blocks
2088 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=213909504
7 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840

Writing inode tables: 0/71/72/73/74/75/76/7done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=[?25l(B(B















[16;21H (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B

[1K (0x(B(0x(B  (0x(B Successfully formatted

/dev/sda5(0x(B  (0x(B(0x(B 

[36m (0x(B (0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0k(B (0

[0mx(B  (0x(B (0x(B0%(0

[47mx(B (0x(B  (0x(B (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B (0x(B  (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  (B(B

[0;1;7m (B3(B[?12l[?25h[?1000l
[?1l>[?1049h(B[?7h[?1049l

[?1h=[?1000h[?1h=[?25l(B(B













 (0lqqqqqqqqqq(B

[34mfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0x(B

[17;81H(0x(B  (0x(B Getting kernel from tftp server(0x(B

[0;1m  (0x(B(0x(B  (0x(B

[0m (0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0k(B (0x(B 

[21;21H (0x(B (0x(B0%(0x(B (0x(B

[0;1m  (0x(B (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B

[0m (0x(B  (0m(0qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

(B  (B(B (B35

[39;49m(B[?12l[?25h[?1000l
[?1l>tftp: server error: (1) File not found
tftp: server error: (1) File not found
[?1049h(B[?7h[?1049l[?1h=[?1000h[?1h=[?25l(B(B















[16;21H (0lqqqqqqqqqq(Bfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B

[1K (0x(B(0x(B  (0x(B Transfer of kernel from

tftp server failed(0x(B  (0x(B(0x(B

[40m  (0x(B (0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0k(B

(0x(B  (0x(B (0x(B0%(0

[30mx(B (0x(B  (0x(B (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B (0x(B  (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  (B(B

[0;1;7m (B37(B[?12l[?25h[?1000l
[?1l>[?1049h(B[?7h[?1049l

[2J[?1h=[?1000h[?1h=(B(B












 (0lqqqqqqqqqq(B

[47mfvdw-sl firmware installer V: 1.0.1 (0qqqqqqqqqqqq(0k(B (0x(B(0

[0mx(B  (0x(B(0x(B  (0

[0;1mx(B(0x(B  (0x(B(0x

(B  (0x(B(0x(B  (0x

(B(0x(B  (0tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(0

[0mu(B  (0x(B(B< OK >

(B(0x(B  (0m(0

[47mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B  (B

[17;24HCannot find kernel on sda5.The script will exit, installation incomplete.(B[?1000l
[?1l>root@(none):/ #
root@

(none):/ # /fvdw-sl-installer 192.168.1.104
root@(none):/ # chmod 755 fvdw-sl-installer
root@(none):/ # tftp -r fvdw-sl-installer.sh -l fvdw-sl-installer -g

192.168.1.104
root@(none):/ # cd /
root@(none):/ # ln -s busybox1 tar
root@(none):/ # cd /bin
root@(none):/ # mv /bin/tar /bin/tar-old
root@(none):/ # chmod 755

/bin/busybox1
root@(none):/ # tftp -r busybox1 -l /bin/busybox1 -g 192.168.1.104
root@(none):/ # fdisk -l /dev/sda
root@(none):/ # fdisk /dev/sda

The number of cylinders for this disk is set to 60801.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 9 72 514080 83 Linux
/dev/sda2 73 136 514080 83 Linux
/dev/sda3 137 200 514080 82 Linux swap
/dev/sda4 201 60801 486777532+ 5 Extended
/dev/sda5 209 312 835380 83 Linux
/dev/sda6 321 328 64260 83 Linux
/dev/sda7 337 400 514080 83 Linux
/dev/sda8 409 60801 485106772+ 83 Linux

Command (m for help):
isrgil
 
Posts: 7
Joined: Thu Jan 22, 2015 11:00 am

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

Postby isrgil » Fri Jan 30, 2015 11:04 am

This is the error that I get to finish the installation

ÚÄÄÄÄÄÄÄÄÄÄfvdw-sl firmware installer V: 1.0.1 ÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ³
³ Cannot find kernel on sda5. ³
³ ³
³ The script will exit, installation incomplete. ³
³ ³
³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ < OK > ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
isrgil
 
Posts: 7
Joined: Thu Jan 22, 2015 11:00 am

PreviousNext

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 1 guest