General NAS-Central Forums

Welcome to the NAS community
It is currently Fri Apr 28, 2017 11:46 pm

All times are UTC




Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Fri Nov 20, 2015 10:56 pm 
Offline

Joined: Fri Mar 28, 2014 7:23 pm
Posts: 4
I have Lacie 2big Network 1TB (2x500GB drives). The drives are blank but they appear to be fine (extended smart tests return no errors). I used the instructions listed here:

http://lacie.nas-central.org/wiki/Insta ... 82Big_2%29

with the partition images found here:

http://downloads.lacie.nas-central.org/ ... s%202.2.3/

The result was: front blinking blue led, rear left blue led, rear right led was mostly off. Never got the Lacie Ethernet/Network Agent to detect the drive. My router has not seen the Lacie either.

I tried with both SAFE 100 and BIG mode. The OFF switch did not seem to work, so I had to pull out the power plug.

When I reconnected the drives to my desktop, I noted one of them was untouched, the other one has partition table changed to match partition table below, but all the Linux raid autodetect (fd) partitons were changed to Linux (83) except for sda5 that was Linux Swap (82) partition.

So I modified the partition table to match this:

Code:
Disk /dev/sdb: 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/sdb1               1         125     1004031   5 Extended
/dev/sdb2             126       60801   487379970  fd Linux raid autodetect
/dev/sdb5               1          16      128457  fd Linux raid autodetect
/dev/sdb6              17          17        8001  83 Linux
/dev/sdb7              18          18        8001  fd Linux raid autodetect
/dev/sdb8              19          40      176683+ fd Linux raid autodetect
/dev/sdb9              41         124      674698+ fd Linux raid autodetect
/dev/sdb10            125         125        8001  83 Linux


And followed with the same install.

The result was: front blue led on with intermittent red blinking (6 or so blinks every minute or so), rear left blue led mostly on, rear right led was mostly off. Never got the Lacie Ethernet/Network Agent to detect the drive. My router has not report the Lacie either.

Any clue what went wrong and what to try next?


Top
 Profile  
 
PostPosted: Sat Nov 21, 2015 4:40 pm 
Offline

Joined: Fri Mar 28, 2014 7:23 pm
Posts: 4
I connected Lacie through serial to realterm and captured this:

Code:
     
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** LOADER **
 ** MARVELL BOARD: DB-88F5182-LaCie LE

U-Boot 1.1.4 (Apr 29 2009 - 14:17:35) Marvell version: 2.4.9  LaCie: 1.00.0005

U-Boot code: 00200000 -> 0026FFF0  BSS: -> 00283280

Soc: 88F5182 A2 (DDR2)
CPU running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CS[0] base 0x00000000   size  64MB
DRAM Total size  64MB  32bit width
mvFlash_init
Flash: 512 kB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done
*** Warning - bad CRC, using default environment


CPU : ARM926 (Rev 0)
88F5182 A2 streaming disabled

USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
POWER Manager
<SW OFF>
                       
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** LOADER **
 ** MARVELL BOARD: DB-88F5182-LaCie LE

U-Boot 1.1.4 (Apr 29 2009 - 14:17:35) Marvell version: 2.4.9  LaCie: 1.00.0005

U-Boot code: 00200000 -> 0026FFF0  BSS: -> 00283280

Soc: 88F5182 A2 (DDR2)
CPU running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CS[0] base 0x00000000   size  64MB
DRAM Total size  64MB  32bit width
mvFlash_init
Flash: 512 kB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done
*** Warning - bad CRC, using default environment


CPU : ARM926 (Rev 0)
88F5182 A2 streaming disabled

USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
POWER Manager
<SW ON>
disk Power ON
Hit any key to stop autoboot:  3  2  1  0
Waiting for LUMP (2)
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
ATAstatus =80
  Device 0: OK
Model: ST3500620AS                              Firm: LC11     Ser#:             9QM2M0RJ
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
ATAstatus =50
  Device 1: OK
Model: ST3500620AS                              Firm: LC11     Ser#:             9QM2X83V
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)


Loading from IDE device 0, partition 10: Name: hda10
  Type: U-Boot

** Bad Magic Number **

Loading from IDE device 1, partition 10: Name: hdb10
  Type: U-Boot

** Bad Magic Number **

Loading from IDE device 0, partition 6: Name: hda6
  Type: U-Boot
   Image Name:   Linux-2.6.22.7
   Created:      2009-04-09  14:07:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1780216 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.22.7
   Created:      2009-04-09  14:07:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1780216 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux......................................................................................................... done, booting the kernel.

Linux version 2.6.22.7 (root@grp-dash) (gcc version 4.2.1) #1 Thu Apr 9 16:07:45 CEST 2009
CPU: ARM926EJ-S [41069260] revision 0 (ARMv5TEJ), cr=a0053177
Machine: Feroceon
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
Built 1 zonelists.  Total pages: 16256
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F5182 productType=2Big reset=0
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB 0MB 0MB 0MB = 64MB total
Memory: 61568KB available (2796K code, 185K data, 356K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Sys Clk = 200000000, Tclk = 166666667

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size  64MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e0000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
PCI0_MEM ....base e8000000, size 128MB
PCI0_IO ....base f2100000, size   1MB
INTER_REGS ....base f1000000, size   1MB
DEVICE_CS0 ....no such
DEVICE_CS1 ....no such
DEVICE_CS2 ....no such
DEV_BOOCS ....base fff80000, size 512KB
CRYPT_ENG ....base f0000000, size  64KB

  Marvell Development Board (LSP Version 3.0.5_NAS_GDP_p8)-- DB-88F5182-LaCie  Soc: 88F5182 A2

 Detected Tclk 166666667 and SysClk 200000000
Init Marvell USB port 0 => HOST
Marvell USB EHCI Host controller #0: c3c07600
Init Marvell USB port 1 => HOST
Marvell USB EHCI Host controller #1: c3c07400
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: orion_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
cesadev_init(c000e7a8)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Use the XOR engines (acceleration) for enhancing the following functions:
  o RAID 5 Xor calculation
  o kernel memcpy
  o kenrel memzero
  o copy user to/from kernel buffers
Number of XOR engines to use: 2
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Registering unionfs 2.4 (for 2.6.22.19)
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 4) is a 16550A
Marvell Ethernet Driver 'mv_ethernet':
  o Uncached descriptors in DRAM
  o DRAM SW cache-coherency
  o TCP segmentation offload enabled
  o Checksum offload enabled
  o Marvell ethtool proc enabled
  o Rx desc: 128
  o Tx desc: 256
  o Loading network interface 'egiga0'
Intergrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi 0:0:0:0: Direct-Access     Seagate  ST3500620AS      LC11 PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access     Seagate  ST3500620AS      LC11 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
 sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 > sda2
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
 sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 > sdb2
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
cfi_flash_0: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
cfi_flash_0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
ehci_marvell ehci_marvell.4523: Marvell Orion EHCI
ehci_marvell ehci_marvell.4523: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.4523: irq 17, io base 0xf1050100
ehci_marvell ehci_marvell.4523: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ehci_marvell ehci_marvell.167817: Marvell Orion EHCI
ehci_marvell ehci_marvell.167817: new USB bus registered, assigned bus number 2
ehci_marvell ehci_marvell.167817: irq 12, io base 0xf10a0100
ehci_marvell ehci_marvell.167817: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Loading I2C based RTC driver device interface.
Found TWSI-I2C with id: 0
No RTC found on the I2C bus
Freeing init memory: 356K
===INITRAMFS: =======================================INITRAMFS================================
===INITRAMFS: Initializing filesystem
===INITRAMFS: Mounting /proc
===INITRAMFS: Mounting /sys
===INITRAMFS: Populating /dev
===INITRAMFS: Mounting /dev/pts
===INITRAMFS: Product ID = '2Big'
===INITRAMFS: minRaidDevices=2
===INITRAMFS: maxRaidDevices=2
===INITRAMFS: Waiting for the master disk to spin up
===INITRAMFS: Waiting for 1 to 1 disks to spin up
===INITRAMFS: We finally have 2 disks, updating /dev
===INITRAMFS: Found available BootFS partition: /dev/sda7
===INITRAMFS: Normal boot, starting bootfs system array
===INITRAMFS: Starting bootfs RAID array (/dev/mmd: md0 stopped.
d0) with /dev/sda7
md: bind<sda7>
raid1: raid set md0 active with 1 out of 2 mirrors
===INITRAMFS: Mouting /dev/md0 on /root read only
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
===INITRAMFS: Mouting virtual filesystems
===INITRAMFS: Switching to bootfs, leaving initramfs
===BOOTFS: =======================================BOOTFS=================================
===BOOTFS: Initializing filesystem
===BOOTFS: Mounting /proc
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /sys
mount: /etc/mtab: Read-only file system
===BOOTFS: Populating /dev
===BOOTFS: Mounting /dev/pts
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /dev/shm
mount: /etc/mtab: Read-only file system
===BOOTFS: Warning: addBootfsComponents() /dev/sda7 is already part of /dev/md0, won't add it
===BOOTFS: addBootfsComponents() Adding /dev/sdb7 to /dev/md0
md: bind<sdb7>
RAID1 conf printout:
 --- wd:1 rd:2
 disk 0, wo:0, o:1, dev:sda7
 disk 1, wo:1, o:1, dev:sdb7
md: recovery of RAID array md0
md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: using 128k window, over a total of 7936 blocks.
===BOOTFS: Starting md1 (RootFS)
md: md0: recovery done.
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda7
 disk 1, wo:0, o:1, dev:sdb7
md: md1 stopped.
md: bind<sdb8>
md: bind<sda8>
md: md1: raid array is not clean -- starting background reconstruction
raid1: raid set md1 active with 2 out of 2 mirrors
md: resync of RAID array md1
md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
md: using 128k window, over a total of 176576 blocks.
md: md1: resync done.
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda8
 disk 1, wo:0, o:1, dev:sdb8
===BOOTFS: Starting md2 (Snapshots)
md: md2 stopped.
md: bind<sdb9>
md: bind<sda9>
raid1: raid set md2 active with 2 out of 2 mirrors
===BOOTFS: Starting md3 (Swap)
md: md3 stopped.
md: bind<sdb5>
md: bind<sda5>
raid1: raid set md3 active with 2 out of 2 mirrors
===BOOTFS: #### Running File System Check on Snapshot Partition (/dev/md2) ###
e2fsck 1.37 (21-Mar-2005)
/dev/md2: recovering journal
/dev/md2 has gone 49710 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/md2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/md2: 970/84480 files (0.2% non-contiguous), 7052/168656 blocks
#### Starting PatchManager using /dev/md1 and /dev/md2  ####
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
===BOOTFS: Creating base union /var/base from /var/original
===BOOTFS: Loading snapshots from /snapshots/snaps
unionfs: unionfs: new generation number 2
mount: /etc/mtab: Read-only file system
unionfs: unionfs: new generation number 3
mount: /etc/mtab: Read-only file system

   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/loglevel   [starting]
      initial/mountvirtfs   [starting]
      initial/edconf   [starting]
      dbus   [starting]
      bootmisc   [starting]
      mountfs   [starting]
      udev/filldev   [starting]
      udev/udevd   [starting]
      udev/mountdev   [starting]
      udev/set_hotplug   [starting]
      modules   [starting]
      hald   [starting]
      clock   [starting]
      dhcdbd   [starting]
      syslogd   [starting]
      klogd   [starting]
      swap   [starting]
      mountuserfs   [starting]
      usb   [starting]
      hostname   [starting]
      NetworkManager   [starting]
      NetworkManager/prepare   [starting]
      http   [starting]
      unionfs   [starting]
      mdadm   [starting]
      getty/1   [starting]
      crond   [starting]
      fan_controller   [starting]
      edconfd   [starting]
      recovery   [starting]
      snapshot   [starting]
   2% initial/loglevel   [done]     ( done in 44ms )
   5% initial/mountvirtfs   [done]     ( done in 213ms )

 initial/edconf start:
  Mounting /oldroot/snapshots/EDMINI
 
   8% udev/mountdev   [done]     ( done in 130ms )
  11% initial/edconf   [done]     ( done in 201ms )
  16% syslogd   [started]   ( pid: 964 )
  22% klogd   [started]   ( pid: 968 )
  25% unionfs   [done]     ( done in 228ms )
  27% NetworkManager/prepare   [done]     ( done in 404ms )
  30% hostname   [done]     ( done in 587ms )
  33% udev/udevd   [started]   ( pid: 977 )
  36% crond   [started]   ( pid: 974 )
  38% udev/set_hotplug   [done]     ( done in 193ms )
  41% modules   [done]     ( done in 2856ms )
  44% udev/filldev   [done]     ( done in 6607ms )
  50% getty/1   [started]   ( pid: 1320 )

 clock start:
  hwclock: can't open '/dev/misc/rtc': No such file or directory
 

 ** "/home/omouchet/trunk/src/initng/initng-0.6.10.2/plugins/service/initng_s  57% mountfs   [done]     ( done in 216ms )
      bootmisc   [SERVICE_START_DEPS_FAILED]
      hald   [DAEMON_START_DEPS_FAILED]
      http   [DAEMON_START_DEPS_FAILED]
      fan_controller   [DAEMON_START_DEPS_FAILED]
      dbus   [DAEMON_START_DEPS_FAILED]


 ** "/home/omouchet/trunk/src/initng/initng-0.6.10.2/plugins/critical/initng_critical.c", check_critical()  line:65:
 01:00:30 -- FAIL:   Service dbus failed, this is critical, going su_login!!
This is a sulogin offer,
you will be able to login for 2 times (now 0),
and on return initng will try continue where it was,
if the times go out, initng will launch
/sbin/initng-segfault on next su_login request.

Give root password for maintenance
(or type Control-D to continue): Starting md4 (User)


LaCix Linux release 2.2.3

Kernel 2.6.22.7 on an armv5tejl / ttyS0

LaCie-2big login:


Is rtc supposed to be part of Lacie system? Everything after rtc appears to fail loading. Are there any other partition images I could try?


Top
 Profile  
 
PostPosted: Sun Nov 22, 2015 1:59 am 
Offline

Joined: Fri Mar 28, 2014 7:23 pm
Posts: 4
Ok, I think I am good. I have booted parted magic with both drives connected to my desktop and cat /proc/partitions showed md1. After I mounted it, I removed the clock reference in bootmisc.i in etc/initng.

Seems to be working. Lacie Ethernat Agent found LaCie-2big.local with DHCP assigned IP and I was able to log in.

Thanks!


Top
 Profile  
 
PostPosted: Sun Nov 22, 2015 4:53 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5981
maloosheck wrote:
Is rtc supposed to be part of Lacie system? Everything after rtc appears to fail loading.
It think it should have, at least it's siblings the EdMini V2 and Networkspace v1 (bootlogs can be found in the wiki) have. And on your box the kernel tries to find one:
Code:
Loading I2C based RTC driver device interface.
Found TWSI-I2C with id: 0
No RTC found on the I2C bus
So I guess it's broken. A bit silly that the last services were marked to be dependent on the clock. On the other hand, why should you anticipate on hardware failure. On the third hand, nor the Networkspace neither the EdMini V2 seems to have a battery on the PCB. So what's the purpose of the rtc anyway?


Top
 Profile  
 
PostPosted: Wed Nov 25, 2015 5:00 am 
Offline

Joined: Fri Mar 28, 2014 7:23 pm
Posts: 4
Mijzelf wrote:
On the third hand, nor the Networkspace neither the EdMini V2 seems to have a battery on the PCB. So what's the purpose of the rtc anyway?


Well, I have not seen any rtc battery on my 2big pcb either. The clock.i script could probably be written better, but the hwclock command that fails this script is part of busybox, so I did not have much time researching. I guess the fact that you can sync time with the Lacie Ethernet Agent running PC and you have the 2big box constantly powered (and running, even with drives powered down) makes sense for no rtc on the board.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 2 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