General NAS-Central Forums

Welcome to the NAS community
It is currently Thu Sep 21, 2017 6:55 am

All times are UTC




Post new topic Reply to topic  [ 132 posts ]  Go to page Previous  1 ... 5, 6, 7, 8, 9
Author Message
PostPosted: Thu Feb 19, 2015 11:17 pm 
Offline

Joined: Thu Jan 15, 2015 9:49 pm
Posts: 70
excellent info i completely forgot about swap !!!

I just hope the new NAS that I have coming, is what I think it is,
then it should set up the drives automatically :P


Top
 Profile  
 
PostPosted: Tue Feb 24, 2015 4:17 pm 
Offline

Joined: Thu Jan 15, 2015 9:49 pm
Posts: 70
My new NAS has arrived, it is the 2Big NAS diskless

it did automatically install the OS 3 to a clean drive

unfortunately the 2Big2 was not happy to start with this drive...
so I will check the serial interface soon to find out where/why it is not loading

here is the partition map of 2Big NAS OS3, I have removed the GUID ID's
Code:
/dev/disk5
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk5
   1: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx                   1.0 MB     disk5s1
   2: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx                   201.3 MB   disk5s2
   3: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx                   1.0 MB     disk5s3
   4:                 Linux_RAID                         1.6 GB     disk5s4
   5:                 Linux_RAID                         1.6 GB     disk5s5
   6:                 Linux_RAID                         1.1 GB     disk5s6
   7:                 Linux_RAID                         268.4 MB   disk5s7
   8:                 Linux_RAID                         2.0 TB     disk5s8


Top
 Profile  
 
PostPosted: Tue Feb 24, 2015 8:04 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
mmm...I have no idea , I don't use the lacie firmware as I don't like it, we made our own
Maybe lacie set something specific for the nas and in case the kernel is specific for the nand version it may not ring on the spi version. Our kernel supports both, you should be able to see what is happening with hooking up your serial port. If the kernel doesn't load well it is obvious what is wrong


Top
 Profile  
 
PostPosted: Tue Feb 24, 2015 9:55 pm 
Offline

Joined: Thu Jan 15, 2015 9:49 pm
Posts: 70
well it does try…

here is the serial log

Code:
Booting Nexus layout from disk 0...
boot_count=0
saved_entry=0
Loading file "/boot/uImage" from ide device 0:4 (gpt4
)
7177340 bytes read

## Checking Image at 00800000 ...
   Image Name:   Linux-2.6.31.14-svn8060
   Created:      2013-08-01  16:47:52 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    7177276 Bytes =  6.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Error: "rescue" not defined
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.31.14-svn8060
   Created:      2013-08-01  16:47:52 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    7177276 Bytes =  6.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
bootargs from environment variables : console=ttyS0,115200 boot=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx cap=gpt,lba64

Starting kernel ...

Uncompressing Linux...................................................................................................................................................
[    0.000000] Linux version 2.6.31.14-svn8060 (root@sbs2_node0.lacie.com) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #1 Thu Aug 1 16:47:48 UTC 2013
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: net2big_v2
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 boot=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx cap=gpt,lba64
[    0.000000] PID hash table entries: 1024 (order: 10, 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] Memory: 256MB = 256MB total
[    0.000000] Memory: 249600KB available (9340K code, 372K data, 140K init, 0K highmem)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[   25.769944] Console: colour dummy device 80x30
[   25.769981] Calibrating delay loop... 1199.30 BogoMIPS (lpj=5996544)
[   25.999971] Mount-cache hash table entries: 512
[   26.000294] CPU: Testing write buffer coherency: ok
[   26.002161] NET: Registered protocol family 16
[   26.004425] Feroceon L2: Enabling L2
[   26.004465] Feroceon L2: Cache support initialised.
[   26.004955]
[   26.004960] CPU Interface
[   26.004965] -------------
[   26.004971] SDRAM_CS0 ....base 00000000, size 256MB
[   26.004983] SDRAM_CS1 ....disable
[   26.004990] SDRAM_CS2 ....disable
[   26.004997] SDRAM_CS3 ....disable
[   26.005005] PEX0_MEM ....base e8000000, size 128MB
[   26.005018] PEX0_IO ....base f2000000, size   1MB
[   26.005029] INTER_REGS ....base f1000000, size   1MB
[   26.005041] NFLASH_CS ....base fa000000, size   2MB
[   26.005053] SPI_CS ....base f4000000, size  16MB
[   26.005069] BOOT_ROM_CS ....no such
[   26.005087] DEV_BOOTCS ....no such
[   26.005106] CRYPT_ENG ....base f0000000, size   2MB
[   26.005125]
[   26.005128]   Marvell Development Board (LSP Version KW_LSP_5.0.3)-- net2big_v2  Soc: 88F6281 A1 LE
[   26.005143]
[   26.005149]  Detected Tclk 166666667 and SysClk 400000000
[   26.006782] Register Marvell USB EHCI Host controller #0
[   26.007755] Kirkwood PCIe port 0:
[   26.007763] link down, ignoring
[   26.015990] bio: create slab <bio-0> at 0
[   26.016367] SCSI Scattered Spinup: Enabled
[   26.016376]   o Maximum Disk Spinup: 1
[   26.016382]   o Disk Spinup timeout: 10
[   26.016907] SCSI subsystem initialized
[   26.019197] NET: Registered protocol family 2
[   26.019299] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[   26.019526] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[   26.019729] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[   26.019842] Switched to NOHz mode on CPU #0
[   26.019943] TCP: Hash tables configured (established 8192 bind 8192)
[   26.019954] TCP reno registered
[   26.020227] NET: Registered protocol family 1
[   29.726147] cpufreq: Init kirkwood cpufreq driver
[   29.740639] gpio-hd-power gpio-hd-power: GPIO Hard Disk power device initialized
[   29.740812] gpio-usb gpio-usb: USB GPIO's initialized
[   29.742086] VFS: Disk quotas dquot_6.5.2
[   29.742135] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   29.742572] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   29.742600] Registering unionfs 2.5.10 (for 2.6.31.14)
[   29.742877] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   29.743525] JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   29.743999] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
[   29.744480] SGI XFS Quota Management subsystem
[   29.744512] msgmni has been set to 488
[   29.744630] alg: No test for cipher_null (cipher_null-generic)
[   29.744697] alg: No test for ecb(cipher_null) (ecb-cipher_null)
[   29.744762] alg: No test for digest_null (digest_null-generic)
[   29.744827] alg: No test for compress_null (compress_null-generic)
[   29.753099] alg: No test for stdrng (krng)
[   30.024135] alg: No test for hmac(digest_null) (hmac(digest_null-generic))
[   30.151728] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[   30.151744] io scheduler noop registered
[   30.151751] io scheduler anticipatory registered (default)
[   30.151760] io scheduler deadline registered
[   30.151814] io scheduler cfq registered
[   30.166391] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[   30.167424] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   30.167447] console [ttyS0] enabled
[   30.599997] brd: module loaded
[   30.603647] sata_mv sata_mv.0: version 1.28
[   30.607959] sata_mv sata_mv.0: slots 32 ports 2
[   30.613303] scsi0 : sata_mv
[   30.616508] scsi1 : sata_mv
[   30.619574] ata1: SATA max UDMA/133 irq 21
[   30.623677] ata2: SATA max UDMA/133 irq 21
[   30.628066] INIT Marvell Ethernet Driver: mv_netdev
[   30.633192] Loading Marvell Ethernet Driver:
[   30.637444]   o Cached descriptors in DRAM
[   30.641542]   o DRAM SW cache-coherency
[   30.645356]   o 2 Giga ports supported
[   30.649089]   o Single RX Queue support - ETH_DEF_RXQ=0
[   30.654299]   o Single TX Queue support - ETH_DEF_TXQ=0
[   30.659499]   o TCP segmentation offload (TSO) supported
[   30.664794]   o Large Receive offload (LRO) supported
[   30.669824]   o Receive checksum offload supported
[   30.674601]   o Transmit checksum offload supported
[   30.679459]   o Network Fast Processing (Routing) supported - (Disabled)
[   30.686134]   o Proc tool API enabled
[   30.689774]   o SKB Reuse supported - (Disabled)
[   30.694377]   o SKB Recycle supported - (Disabled)
[   30.699139]   o Rx descripors: q0=128
[   30.702802]   o Tx descripors: q0=532
[   30.706458]   o Loading network interface(s):
[   30.712002]     o  register under mv_netdev platform
[   30.717462] mv_eth_phy_get_wol: Unsupported PHY ID 0x01410e40
[   30.723662]     o eth0, ifindex = 2, GbE port = 0
[   30.728358]
[   30.728361] Warning: Giga 1 is Powered Off
[   30.733941]
[   30.735436] mvFpRuleDb (cc464000): 2048 entries, 8192 bytes
[   30.741191] console [netcon0] enabled
[   30.744838] netconsole: network logging started
[   30.750735] m25p80 spi0.0: mx25l4005a (512 Kbytes)
[   30.755512] Creating 1 MTD partitions on "spi_flash":
[   30.760573] 0x000000000000-0x000000080000 : "u-boot"
[   30.766530] mice: PS/2 mouse device common for all mice
[   30.772080] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   30.779346] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[   30.785192] IRQ 53/rtc-mv: IRQF_DISABLED is not guaranteed on shared IRQs
[   30.792554] at24 0-0050: 512 byte 24c04 EEPROM (writable)
[   30.798345] g762 0-003e: device successfully initialized
[   30.803937] gpio-fan gpio-fan: GPIO fan initialized
[   30.810269] cpuidle: using governor ladder
[   30.814725] cpuidle: using governor menu
[   30.819158] Registered led device: net2big-v2:blue:power
[   30.824612] Registered led device: net2big-v2:red:power
[   30.829990] Registered led device: net2big-v2:blue:sata0
[   30.835411] Registered led device: net2big-v2:red:sata0
[   30.840760] Registered led device: net2big-v2:blue:sata1
[   30.846180] Registered led device: net2big-v2:red:sata1
[   30.851547] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   30.857923] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   30.899864] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   30.939863] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   30.979862] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   31.019865] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   31.025846] TCP cubic registered
[   31.029062] NET: Registered protocol family 17
[   31.033585] Bridge firewalling registered
[   31.037587] NET: Registered protocol family 5
[   31.042160] RPC: Registered udp transport module.
[   31.046840] RPC: Registered tcp transport module.
[   31.052651] rtc-mv rtc-mv: setting system clock to 2015-02-24 21:47:22 UTC (1424814442)
[   31.219863] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   31.240084] ata1.00: ATA-9: WDC WD20EFRX-68EUZN0, 82.00A82, max UDMA/133
[   31.246755] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   31.270122] ata1.00: configured for UDMA/133
[   31.274626] scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EFRX-68E 82.0 PQ: 0 ANSI: 5
[   31.283475] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   31.291208] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   31.296694] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   31.302423] sd 0:0:0:0: [sda] Write Protect is off
[   31.307281] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.316760]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
[   31.370623] sd 0:0:0:0: [sda] Attached SCSI disk
[   31.649855] ata2: SATA link down (SStatus 0 SControl F300)
[   31.655360] Freeing init memory: 140K
[   31.659459] Freeing initramfs memory: 4284K
Entering runlevel base
 * Starting mount-base
 * Starting parse-cmdline
 * Starting get-board-id
 * Starting fix-config
NEXUS_PLATFORMCONFIG: Product built for "nas2big" but hardware is "net2big_v2"
NEXUS_PLATFORMCONFIG:  * ../nas-tools/net2big_v2 -> /etc/platform/current_config/nas-tools
NEXUS_PLATFORMCONFIG:  * ../prodtools-checker/default -> /etc/platform/current_config/prodtools-checker
 * Starting populate-dev
 * Starting kmap
Entering runlevel boot
 * Starting ipcommd
 * Starting sleepmode
Sleep mode disabled
Set led mode: general_off
sh: ledctrl: not found
Set led mode: general_startup
sh: ledctrl: not found
 * Stopping ipcommd
 * Starting start-raid
mdadm: /dev/md/4 has been started with 1 drive.
mdadm: /dev/md/5 has been started with 1 drive.
mdadm: /dev/md/6 has been started with 1 drive.
mdadm: /dev/md/7 has been started with 1 drive.
 * Starting check-all-fs
 * Starting replicate-nv_data
 * Starting assemble-rootfs
 * Starting switch-root

        Next Generation Init version ( 0.6.10.2 Die bugs die! )
        http://www.initng.org
        Author: Jimmy Wennlund <jimmy.wennlund@gmail.com>
        If you find initng useful, please consider a small donation.

        System is starting up!

      runlevel/default  [starting]
      initial   [starting]
      dbus      [starting]
      dbus/uuidgen      [starting]
      udev/prepare      [starting]
      udev/udevd        [starting]
      udev/filldev      [starting]
      bctrld    [starting]
      ublocks   [starting]
      logrotate [starting]
      syslogd   [starting]
      klogd     [starting]
      http      [starting]
      http/gen  [starting]
      getty/S0  [starting]
      getty/0   [starting]
      sshd/generate_keys        [starting]
      cron      [starting]
      unicorn   [starting]
      first-boot        [starting]
      anyraid   [starting]
      lvm       [starting]
      mdadm/scan        [starting]
      skynetd/start     [starting]
      skynetd/check_config      [starting]
      reflexd   [starting]
      thumbd    [starting]
      unicorn/ready     [starting]
      mdadm/monitor     [starting]
      buttons-manager   [starting]
      notify    [starting]
      notify/ready      [starting]
   5% http/gen  [done]          ( done in 294ms )

 initial start:
  NEXUS_PLATFORMCONFIG: Product built for "nas2big" but hardware is "net2big_v2"
  NEXUS_PLATFORMCONFIG:  * ../ethtool/net2big_v2 -> /etc/platform/current_config/ethtool
  NEXUS_PLATFORMCONFIG:  * ../nas-tools/net2big_v2 -> /etc/platform/current_config/nas-tools
  NEXUS_PLATFORMCONFIG:  * ../notify/default -> /etc/platform/current_config/notify
  load RTC  date: Tue Feb 24 21:47:28 UTC 2015
  save file date: Tue Feb 24 21:47:28 UTC 2015
 
   8% initial   [done]          ( done in 964ms )
  10% mdadm/scan        [done]          ( done in 9ms )
  13% udev/prepare      [done]          ( done in 34ms )
  16% dbus/uuidgen      [done]          ( done in 180ms )
  18% thumbd    [started]       ( pid: 1285 )
  27% udev/udevd        [started]       ( pid: 1281 )
  27% cron      [started]       ( pid: 1283 )
  27% logrotate [done]          ( done in 439ms )
  29% syslogd   [started]       ( pid: 1292 )
  35% klogd     [started]       ( pid: 1293 )
  37% dbus      [started]       ( pid: 1294 )
      udev/udevd        [starting]
      udev/udevd        [starting]
  37% udev/udevd        [started]       ( pid: 1300 )
  40% skynetd/start     [started]       ( pid: 1490 )
  45% http      [started]       ( pid: 1681 )
  48% skynetd/check_config      [done]          ( done in 2810ms )
  54% udev/filldev      [done]          ( done in 6165ms )
  62% getty/S0  [started]       ( pid: 2022 )
  62% getty/0   [started]       ( pid: 2023 )
  64% sshd/generate_keys        [done]          ( done in 32ms )

NAS OS 3.1.4.6
Linux 2.6.31.14-svn8060 on an armv5tel / /dev/ttyS0
LaCie-2big-NAS login:
 lvm start:
  mdadm: /dev/md8 has been started with 1 drive.
 
  67% lvm       [done]          ( done in 1705ms )
  70% ublocks   [started]       ( pid: 2225 )
  72% anyraid   [started]       ( pid: 2226 )
  75% mdadm/monitor     [started]       ( pid: 2228 )
  78% first-boot        [done]          ( done in 750ms )

 bctrld start:
  bctrld failed to start
 
  81% bctrld    [done]          ( done in 7903ms )
  83% buttons-manager   [done]          ( done in 83ms )

 notify start:
  Traceback (most recent call last):
  File "/usr/bin/system_notify", line 8, in <module>
  load_entry_point('notify==1.0', 'console_scripts', 'system_notify')()
  File "/usr/lib/python2.7/site-packages/notify/system_notify.py", line 48, in main
  bctrl_instance.init(init=True, multithread=False)
  File "/usr/lib/python2.7/site-packages/bctrl.py", line 546, in init
  raise BCError(result)
  bctrl.BCError: INVALID_PRODUCT
 
      notify    [SERVICE_FAIL_START_RCODE]
      reflexd   [DAEMON_FAIL_START_TIMEOUT_PIDFILE]
      unicorn   [DAEMON_START_DEPS_FAILED]
      unicorn/ready     [SERVICE_START_DEPS_FAILED]
      notify/ready      [SERVICE_START_DEPS_FAILED]
      runlevel/default  [START_DEPS_FAILED]


        runlevel "runlevel/default" up in, 76982ms.

 Failing services: runlevel/default unicorn reflexd unicorn/ready notify notify/ready



Top
 Profile  
 
PostPosted: Tue Feb 24, 2015 10:14 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
the kernel runs fine but if fails to load fully the lacie firmware, probably because it mentions this
Code:
 NEXUS_PLATFORMCONFIG: Product built for "nas2big" but hardware is "net2big_v2"
  NEXUS_PLATFORMCONFIG:  * ../ethtool/net2big_v2 -> /etc/platform/current_config/ethtool
  NEXUS_PLATFORMCONFIG:  * ../nas-tools/net2big_v2 -> /etc/platform/current_config/nas-tools
  NEXUS_PLATFORMCONFIG:  * ../notify/default -> /etc/platform/current_config/notify

and finally

Code:
 
bctrl.BCError: INVALID_PRODUCT


It must be something in the lacie bootscripts checking for machine type, as the kernel returns the wrong id it seems to fail. That must adaptable I think if you study the boot scripts
A big part of the firmware seems to be loaded already

You must try to let it believe it is a nas2big so search were it use commands like "uname" or maybe it even uses dmesg and grep to find the machine type.


Top
 Profile  
 
PostPosted: Tue Feb 24, 2015 10:39 pm 
Offline

Joined: Thu Jan 15, 2015 9:49 pm
Posts: 70
surely it would be easier to spoof the "nas2big" into a modified u-boot

rather than editing the startup scripts

that way future updates could also work

EDIT:
but I do agree, I need to find out how and what it is checking first, so a patch can be applied correctly.


Top
 Profile  
 
PostPosted: Wed Feb 25, 2015 7:51 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
nas2big doesn't need to be spoofed in u-boot. This is akernel lacie firmware thing.
u-boot only loads the kernel, starts it and points it to the the location of th e root file system and starts execution the boot scripts, these do the checks as described


Top
 Profile  
 
PostPosted: Wed Feb 25, 2015 11:32 pm 
Offline

Joined: Thu Jan 15, 2015 9:49 pm
Posts: 70
the system i have here also lists other models but is lacking config files for 2big2

nexus_platformconfig.sh has an option for spoofing hardware
Code:
#!/bin/sh
#
# Usage: nexus_platformconfig.sh [HARDWARE ID|--reset]
# Adjust software configuration to fit the hardware platform
# args:
#       HARDWARE_ID : Use HARDWARE_ID as platform instead of the one auto-detected (fake mode)
#       --help      : Print current help
#       --reset     : Disable fake mode, ie revert to platform auto-detection for configuration.
#       --list-current : List config files currently in use"

PLATFORM_FAKE_FILE="/etc/platform_fake_id"
PLATFORM_CONFIG_DIR="/etc/platform"
PLATFORM_CURRENT_DIR_NAME="current_config"

perhaps this could be used to fill the gaps......


nexus_hardware.sh is the file that checks the device with uname -m
Code:
#!/bin/sh

DMI_PATH=/sys/devices/virtual/dmi/id

ARCH=$(uname -m)
case $ARCH in
    armv5*)
        if [ -f /proc/device-tree/model ]; then
            model=$(cat /proc/device-tree/model)
            [ "$model" = 'LaCie CloudBox' ] && machine=familybox
        elif [ -f /proc/cpuinfo ]; then
            machine=$(grep ^Hardware /proc/cpuinfo | \
                        sed -n -e "s/^Hardware.*: //p")
        fi
        ;;


Top
 Profile  
 
PostPosted: Thu Feb 26, 2015 10:43 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
seems nexus_hardware.sh is reading the hardware info using the output of cat /proc/cpuinfo and reading the line containing the word Hardware.
To see what it contains you could give the command cat /proc/cpuinfo

You could edit the file that it doesn't use that info but just hard code
Code:
machine=nas2big


and see if that does the trick

ps use a editor that use unix format for end of line (only <LF>. Shell scipts containing <LF><CR> at end of lines will not be executed correctly


Top
 Profile  
 
PostPosted: Sun Oct 11, 2015 11:01 am 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
micromend wrote:
my supercap was blown as I suspected in a previous post

the original was 1F 2.7v but i would need to order from RS, farnell or china

i have replaced mine with a 3F 2.7v off the shelf from maplin for £1.49

it was too big so I had to install it on it's side


as I had already written over the u-boot I have now put mainline with the loader (kwb file)

now my NAS is spinning the disks and getting an IP via DCHP so I think mainline u-boot is now working too

I need to compile clunc for MacOS and install an OS to the drives

will try to access the NAS with clunc some time next week and update with my results

any advice on an OS for the NAS ? as I think the lacie OS will not work with the mainline ROM....

I have been considering debian, I need the NAS to operate in RAID 1 mirror

has the FVDW-SL firmware been updated to support RAID 1 yet ? as I really like the look of that system.

Thanks.



hello guys,
i need a little help

i tried to install debian on a Lacie d2 Network (v2 it sais) following this guide http://lacie-nas.org/doku.php?id=debian_install and modify archNumber to 2203 i manage to boot the kernel, but it remains in
Uncompressing Linux......................................................................................................... done, booting the kernel.

so i thought i need to upgrade the stock uBoot with a newer one ... so i use this guide here http://lacie-nas.org/doku.php?id=uboot
i downloaded the file u-boot-d2net_v2-2011.12-00260-ga24d58e.kwb from ftp://lacie-nas.org/u-boot and gave the command

Code:
bubt u-boot-d2net_v2-2011.12-00260-ga24d58e.kwb


all went well until i pressed y instead of n in "Override Env parameters? (y/n) n" and reset the box.
after reset :
- the drives don't spin
- the lights don't flash
- the network lights do work
- but my router does not assign it an IP

i have read this entire disscution.... i have few questions ...
do you think i can view the default enviroment settings that i write using u-boot-d2net_v2-2011.12-00260-ga24d58e.kwb so that i can recover by netconsole (but i don't know what's the ip address to connect to)??
do you think you can help me reprogram the flash? if you can help ...what do i need, to to that?

best regards


Top
 Profile  
 
PostPosted: Mon Oct 12, 2015 11:03 am 
Offline

Joined: Fri Sep 16, 2011 6:18 am
Posts: 39
Do you have the MAC adress of the box, then you could attempt seting up an ip via"arp/ping", google "give a device an ip via arp".


Top
 Profile  
 
PostPosted: Mon Oct 12, 2015 1:03 pm 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
interesting ideea i'll give it a try but it migh not work since i override the env variables which had the etheraddress (mac)
it seems that i put the flash from lacie d2 netwok 2 to a lacie d2 network v2 ( i was mislead by the name of the file u-boot-d2net_v2) so this way i bricked the device.
it seemns that there is no uboot support for lacie d2 network (with or without v2).


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 132 posts ]  Go to page Previous  1 ... 5, 6, 7, 8, 9

All times are UTC


Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group