fvdw-sl firmware on a Network Space MAX

Re: fvdw-sl firmware on a Network Space MAX

Postby morgand » Tue Jul 30, 2013 6:32 pm

Sorry for the error, here it is:

Code: Select all
df /dev/sda8
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda8            1919632524    200180 1899930000   0% /share/1000


Code: Select all
/usr/sbin/smartctl -a /dev/sdb | grep -i serial | awk '{print $3}'
5YD0SPNV


For the PM, after a logoff/logon I still get the message:
We are sorry, but you are not authorised to use this feature. You may have just registered here and may need to participate more to be able to use this feature.
morgand
 
Posts: 10
Joined: Wed Jul 24, 2013 2:05 pm
Location: Montreal, QC, Canada

Re: fvdw-sl firmware on a Network Space MAX

Postby Jocko » Tue Jul 30, 2013 6:40 pm

Thanks

Please could you try again to send a pm
Jocko
Site Admin - expert
 
Posts: 11564
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: fvdw-sl firmware on a Network Space MAX

Postby Jocko » Tue Jul 30, 2013 7:37 pm

I sent you a pm with some attached files.

To upgrade your NAS, we will do it by 2 steps.

1) overwrite the current database :

Copy the nas database that I sent you by pm to the share public
In putty, give these commands
Code: Select all
cp /share/1000/public/nas_conf_db.xml.new /rw_fs/etc/nas_conf_db.xml
chmod 777 /rw_fs/etc/nas_conf_db.xml

Now check if you can see the two disks in the web interface :
In the disk setup menu, in the disk table you must have now two lines (Disk-1 and Disk-2)
and in the share menu, if you try to create one more, in the volume table, you must have also two lines.

Note : Be careful, DO MAKE ANY SUBMIT.

So if all is OK, reboot the NAS.

2) Upgrade now manually the firmware

After restarting, check again if in the two previous menus you have still the two disks. if it's Ok, do :
* Copy the firmware image to the share public and in putty, give these commands:
* In putty, list the content of the folder /lacie-boot
Code: Select all
ls -al /lacie-boot


=> (case 1) if you have the file sda1boot rename it : sda2boot
Code: Select all
mv /lacie-boot/sda1boot /lacie-boot/sda2boot


=> (case 2) if you have the file sda2boot rename it : sda1boot
Code: Select all
mv /lacie-boot/sda2boot /lacie-boot/sda1boot


=> (case 3) if it's empty, create a file sda1boot:
Code: Select all
touch sda1boot


*Now copy the image to the partition sda1 (if you are in the cases 2 or 3)
Code: Select all
dd if=/share/1000/public/fvdw-sl-14-1-nwsp2-07jun2013.img of=/dev/sda1

or copy the image to the partition sda2 (if you are in the case 1)
Code: Select all
dd if=/share/1000/public/fvdw-sl-14-1-nwsp2-07jun2013.img of=/dev/sda2


and restart the NAS with the command reboot
Code: Select all
reboot -f
Jocko
Site Admin - expert
 
Posts: 11564
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: fvdw-sl firmware on a Network Space MAX

Postby Jocko » Tue Jul 30, 2013 8:32 pm

I forgot to mention that you need to close all browser windows after upgrading the firmware to empty the cache.
Jocko
Site Admin - expert
 
Posts: 11564
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: fvdw-sl firmware on a Network Space MAX

Postby morgand » Tue Jul 30, 2013 8:38 pm

Nice, I can see the two disks and after the reboot, free space on the second disk is showing OK.

I used case 3 for the upgrade, it went smooth.

I still see the two disks, there are now labelled single (and of type single).
morgand
 
Posts: 10
Joined: Wed Jul 24, 2013 2:05 pm
Location: Montreal, QC, Canada

Re: fvdw-sl firmware on a Network Space MAX

Postby Jocko » Tue Jul 30, 2013 8:44 pm

ouups, I made a cosmetic error in the nas database.

I will send you a new version and repeat these commands :
Copy the nas database that I sent you by pm to the share public
In putty, give these commands
Code: Select all
cp /share/1000/public/nas_conf_db.xml.new /rw_fs/etc/nas_conf_db.xml
chmod 777 /rw_fs/etc/nas_conf_db.xml
--edit---
Note : no need to reboot the NAS


Otherwise, we will check if all is Ok.

Post these outputs, with putty do :
Code: Select all
dmesg
mount
cat /boot.log
Jocko
Site Admin - expert
 
Posts: 11564
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: fvdw-sl firmware on a Network Space MAX

Postby morgand » Tue Jul 30, 2013 9:01 pm

OK, I see what you meant.

Well, I did notice maybe a small glitch:

On the view system information page I've got:
Total Storage 1830.71 GB

Available Storage 3623.58 GB

Just to let you know.

I rebooted the NAS anyway.

Results of the commands:

Code: Select all
root@fvdwsl-base:/ # dmesg | more
Linux version 2.6.39.4 (root@fvdwsl-nwsp2.local) (gcc version 4.5.4 (GCC) ) #57 PREEMPT Sun Nov 18 14:17:12 GMT+1 2012
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: LaCie Network Space Max v2
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat c0643b08, node_mem_map c0661000
  Normal zone: 512 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 65024 pages, LIFO batch:15
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 253328k/253328k available, 8816k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd0800000 - 0xfe800000   ( 736 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc002f000   ( 156 kB)
      .text : 0xc002f000 - 0xc0617000   (6048 kB)
      .data : 0xc0618000 - 0xc06441e0   ( 177 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:114
sched_clock: 32 bits at 166MHz, resolution 5ns, wraps every 25769ms
Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=166666667.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
initial MPP regs: 01112222 00003311 00551100 00000000 00000000 00000000 00000000
  final MPP regs: 01112222 00003311 00551100 00000000 00000000 00000000 00000000
 orion-ehci registered
bio: create slab <bio-0> at 0
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
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
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
NetWinder Floating Point Emulator V0.97 (double precision)
gpio-usb gpio-usb: USB GPIO's initialized
Switched to NOHz mode on CPU #0
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NTFS driver 2.1.30 [Flags: R/W].
fuse init (API version 7.16)
JFS: nTxBlock = 1979, nTxLock = 15833
SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
msgmni has been set to 494
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
loop: module loaded
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
m25p80 spi0.0: mx25l4005a (512 Kbytes)
Creating 2 MTD partitions on "spi_flash":
0x000000000000-0x00000007dfff : "u-boot"
mtd: partition "u-boot" doesn't end on an erase block -- force read-only
0x00000007e000-0x00000007f000 : "u-boot-env"
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:d0:4b:8f:a4:5d
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
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>
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver ipheth
aoe: AoE v47 initialised.
input: gpio-keys as /devices/platform/gpio-keys/input/input0
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
at24 0-0050: 512 byte 24c04 EEPROM, writable, 16 bytes/write
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
gpio-fan gpio-fan: GPIO fan initialized
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
Registered led device: ns_v2:red:fail
Registered led device: ns_v2:blue:sata
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3958 buckets, 15832 max)
IPv4 over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 5
NET: Registered protocol family 37
VFP support v0.3: not present
Gating clock of unused units
before: 0x00c7c1dd
 after: 0x00c7c1c9
rtc-mv rtc-mv: setting system clock to 2013-07-31 03:50:25 UTC (1375242625)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata1.00: ATA-8: ST2000DL001-9VT156, CC41, max UDMA/133
ata1.00: 3907029168 sectors, multi 0: LBA48
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      ST2000DL001-9VT1 CC41 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0: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 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2.00: ATA-8: ST2000DL001-9VT156, CC41, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      ST2000DL001-9VT1 CC41 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdb] 4096-byte physical blocks
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 >
sd 1:0:0:0: [sdb] Attached SCSI disk
EXT3-fs: barriers not enabled
EXT3-fs (sda7): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:7.
kjournald starting.  Commit interval 5 seconds
Freeing init memory: 156K
EXT3-fs (sda7): warning: checktime reached, running e2fsck is recommended
EXT3-fs (sda7): using internal journal
EXT3-fs: barriers not enabled
EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): recovery complete
EXT3-fs (sda1): mounted filesystem with ordered data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
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
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: Marvell Orion EHCI
usb usb1: Manufacturer: Linux 2.6.39.4 ehci_hcd
usb usb1: SerialNumber: orion-ehci.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usblp
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)
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda8): using internal journal
EXT3-fs (sda8): recovery complete
EXT3-fs (sda8): mounted filesystem with ordered data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdb8): using internal journal
EXT3-fs (sdb8): recovery complete
EXT3-fs (sdb8): mounted filesystem with ordered data mode
ADDRCONF(NETDEV_UP): eth0: link is not ready
mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
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)
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda8): using internal journal
EXT3-fs (sda8): recovery complete
EXT3-fs (sda8): mounted filesystem with ordered data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdb8): using internal journal
EXT3-fs (sdb8): recovery complete
EXT3-fs (sdb8): mounted filesystem with ordered data mode
ADDRCONF(NETDEV_UP): eth0: link is not ready
mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udevd (797): /proc/797/oom_adj is deprecated, please use /proc/797/oom_score_adj instead.
eth0: no IPv6 routers present
svc: failed to register lockdv1 RPC service (errno 97).


Code: Select all
mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=0,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
/dev/sda8 on /share/1000 type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
/dev/sdb8 on /share/1001 type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)


Code: Select all
cat /boot.log
start boot log
booting using sda1 root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
buttons-nwsp2 daemon started
Wed Jul 31 04:50:27 GMT+1 2013
run udevstart to update dev nodes when necessary
inserting kernel modules:
configure loopback netwerk interface
starting php based setup routines step 1



 * Initial XML configuration file...     [ OK ]
 * Configuring Disks...                                  [ OK ]
 * Configuring System Users...
        Root password: use default password
        Set users, linux and samba accounts      [ OK ]
 * Starting mount of volumes...
   - Mounting volume Disk-1:                     [ OK ]
   - Mounting volume Disk-2:                     [ OK ]
 * Finishing mount of volumes...                 [ OK ]
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Configuring LAN interface...                  [ OK ]
 * Starting udevd...                                     [ OK ]
 * Starting web server...                                [ OK ]
 * Initializing Timezone...                      [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Starting syncawayd...                                 [ OK ]
start portmap service
starting php based setup routines step 2


 * Starting NFS Server...                                [ OK ]
 * Starting dropbear...                                  [ OK ]
 * Kill temporary dropbear...                    [ OK ]
 * Starting daemon update Hosts File...  [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 14.1
    built on: May 12 2013

    LAN IP address: 10.1.10.13 (DHCP)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
rcS finished
morgand
 
Posts: 10
Joined: Wed Jul 24, 2013 2:05 pm
Location: Montreal, QC, Canada

Re: fvdw-sl firmware on a Network Space MAX

Postby Jocko » Tue Jul 30, 2013 9:15 pm

Nice, I noted no error in your last post :-D.

So, I think that you can use all features of the firmware.

About Total Storage error, is just an information bug, so nothing serious.

Currently, you use the disks as single disk (not RAID 0 or RAID 1). We will work in the next months to implement a RAID feature
Jocko
Site Admin - expert
 
Posts: 11564
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: fvdw-sl firmware on a Network Space MAX

Postby fvdw » Wed Jul 31, 2013 7:03 am

great to see we can add another supported device to the list

In the dmesg output I noticed one small issue
Code: Select all
Creating 2 MTD partitions on "spi_flash":
0x000000000000-0x00000007dfff : "u-boot"
mtd: partition "u-boot" doesn't end on an erase block -- force read-only
0x00000007e000-0x00000007f000 : "u-boot-env"

It will not influence operation of the NAS only when we want to replace u-boot present in flash from user land (while running Linux).
But that ction is in principle not needed we can use the the fvdw-sl console to to that.
Flashing u-boot might be required to get GPT support i(required if you want to put in disk > 2 TB).
In you output I see this
Code: Select all
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW

(Newer versions of lacie u-boot mention in this line when they have gpt support)
That indicates that the current version of u-boot probably has no GPT support. Our kernel has support for it but u-boot also must support to be able to recognize and read the disk and initiate the boot process.

Anyhow, I made some modifications to the kernel to correct this issue. In the new release it will be fixed to eliminate this small error
fvdw
Site Admin - expert
 
Posts: 13474
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: fvdw-sl firmware on a Network Space MAX

Postby morgand » Wed Jul 31, 2013 1:55 pm

Great ! The RAID support will be a welcomed feature :-)
morgand
 
Posts: 10
Joined: Wed Jul 24, 2013 2:05 pm
Location: Montreal, QC, Canada

PreviousNext

Return to Development

Who is online

Users browsing this forum: No registered users and 10 guests