2Big Network New install bugs - clock issues mostly

[danyboy666]

I'm separating stuff from the last topic since there are some issue with the NAS not related to RAID

cat boot.log

Code: Select all

root@fvdwsl-base:/ # cat boot.log
start boot log
detect and set platform
2big1
UIMAGE-3142-2BIG1-6
2big1
 mount dev/pts
update dev nodes
booting using sda1 root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = 2big1
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Wed Nov 16 12:00:00 UTC 2011
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'xor.ko' not found
create temporary group file
configure loopback network interface
setting reboot and standby
2big1
rebootd-isp1
2big1
standbyd-isp1
starting php based setup routines step 1

 * Starting udevd...                                     [ OK ]
 * Found XML database configuration file...      [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Updating Disks database...
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /etc/finc/logError.finc on line 23

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /etc/finc/logError.finc on line 23
                         [ OK ]
 * Starting mount of volumes...
   - Mounting volume Vol-A:  [ OK ]
   - Mounting volume Vol-:  [ OK ]
 * Finishing mount of volumes...                 [ OK ]

Warning: Illegal string offset 'volid' in /etc/finc/exthddfunc_wait_allmountExtHdd.finc on line 83
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ]
 * Configuring LAN interface...                  [ OK ]
 * Initializing Timezone...                      [ OK ]
 * Starting web server...                                [ OK ]
 * Starting mount of internal USB ...
 * Finishing mount internal USB ...      [ OK ]
 * Configuring Disks...                                  [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Configuring System Users...
        Root password: use default password
        Set users
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /etc/finc/logError.finc on line 23
, linux and samba accounts       [ 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 mount of remote shares...
 * Finishing mount shares...                     [ OK ]
 * Starting NTP client...                                [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 16.1
    built on: Oct 01 2015

    LAN IP address: 192.168.121.85 (static)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
LED settings
else loop1 finished
rcS finished


this warning comes up three times on the boot.log

Code: Select all

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /etc/finc/logError.finc on line 23

ps.: I have a couple bugs i'm not sure if it's fvdw related.
- I can't setup the time from the web interface from Chrome "Current System Status: could not update field :__FILE__, hwclock -w -u, err= 1" Whenever i hit the accept button. I,ve also tried with Microsoft Edge (IE) but with the same result "could not update field :__FILE__, hwclock -w -u, err= 1".

Code: Select all

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

dmesg | grep -i rtc
[    2.564503] rtc-rs5c372 0-0032: can't read registers
[    2.569526] rtc-rs5c372: probe of 0-0032 failed with error -5
[    2.627790] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)


- I can't empty the "set clock from internet time server (NTP) field when it is checked
- The button labelled [...] next to "Set Time Zone: /UTC" doesn't respond at all. What was is suppose to acheive?
edit: this was fixed after i've reinstalled the 16.1 firmware but i still get "Current System Status: could not update field :__FILE__, hwclock -w -u, err= 1"

but system date is correct though

Code: Select all

date
Sun Dec 20 17:48:01 EST 2015


The only reason i can see for this is that there is no RTC on the PCB...

- When i try to shut down the NAS from the web interface it reboot instead of shuting down
- I can't use the tuggle button on the back of the NAS the shut down the unit. Unresponsive unless i unplug the power supply.

[Jocko]

AFAIK, 2big1 should support RTC.

Your issue comes from here

Code: Select all

[    2.558676] i2c /dev entries driver
[    2.564503] rtc-rs5c372 0-0032: can't read registers
[    2.569526] rtc-rs5c372: probe of 0-0032 failed with error -5

As fvdw-sl 16.1 uses a new kernel version, may be there is a bug here. I think fvdw will be able to help you.

[fvdw]

it should look like this (output from another 2big1 user)

Code: Select all

[   15.376062] i2c /dev entries driver
[   15.384798] rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.6
[   15.396877] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0


let me think about this

[fvdw]

you have a strange 2big1, according to my knowledge these devices should have 64 MB ram, yours seems to have 128 MB :scratch

Anyhow there is no reason why the rtc should not be loaded. I will ask another board member having a 2big1 for his dmesg output with kernel #6

[danyboy666]

Sorry to cause so much confusions :P I'll post more logs and test results if needed

[danyboy666]

You are right :

Code: Select all

cat /proc/meminfo
MemTotal:         125788 kB
MemFree:           39528 kB
MemAvailable:     103828 kB
Buffers:            8416 kB
Cached:            63648 kB
SwapCached:            0 kB
Active:            34576 kB
Inactive:          42744 kB
Active(anon):       5360 kB
Inactive(anon):     5408 kB
Active(file):      29216 kB
Inactive(file):    37336 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:        514076 kB
SwapFree:         514076 kB
Dirty:               508 kB
Writeback:             0 kB
AnonPages:          5308 kB
Mapped:            12280 kB
Shmem:              5460 kB
Slab:               4888 kB
SReclaimable:       2564 kB
SUnreclaim:         2324 kB
KernelStack:         480 kB
PageTables:          444 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      576968 kB
Committed_AS:      41856 kB
VmallocTotal:     892928 kB
VmallocUsed:       21524 kB
VmallocChunk:     856572 kB


Code: Select all

cat /proc/cpuinfo
processor       : 0
model name      : Feroceon rev 0 (v5l)
Features        : swp half thumb fastmult edsp
CPU implementer : 0x41
CPU architecture: 5TEJ
CPU variant     : 0x0
CPU part        : 0x926
CPU revision    : 0

Hardware        : LaCie 2Big Network
Revision        : 0000
Serial          : 0000000000000000


[danyboy666]

AFAIK, 2big1 should support RTC.

Your issue comes from here

Code: Select all

[    2.558676] i2c /dev entries driver
[    2.564503] rtc-rs5c372 0-0032: can't read registers
[    2.569526] rtc-rs5c372: probe of 0-0032 failed with error -5

As fvdw-sl 16.1 uses a new kernel version, may be there is a bug here. I think fvdw will be able to help you.

I did not see any battery onboard that's why i was guessing there were no RTC.

I think this NAS is different from other 2Big Network 1. This would explain the model version "2BIGV2NAS". I've made sure that it was indeed a 2Big Network 1 before doing anythin with it. cpuinfo output does comfirm it is too. Another thing i'm sure about is the u-boot version 1.1.4. Also fvdw pointed out that it had 128MB memory instead of the usual 64MB. This NAS as been nothing but a pain in the *** since i've got it.... Every recovery attemps i've made to restore the original firmware enede up in failures. I did try over 20 times multiple ways with multiple images none of them worked. It was even thought originaly to be completely dead when i got it from my old job where i was network tech. The box has been sitting in pieces in my inventory for almost two years before i'd try my luck with it again.

[uelpenich]

The box has been sitting in pieces in my inventory for almost two years before i'd try my luck with it again.

You are shure it is a 2big 1? Not a 2big1 housing with a 2big2 pcb?

How many positions has the switch on the rear?
* Three (off | auto | on)? it is a 2big 1.
* Two (off | on)? it is a 2big2.

[danyboy666]

Code: Select all

How many positions has the switch on the rear? 
* Three (off | auto | on)? it is a 2big 1.

I'm sure. Also it was verified and confirmed with the model 2BIGV2NAS / LAC301421U on LaCie support as being a 2Big Network 1.

There seem to be another revision of this 2Big v1. Maybe it somewhere along as what you've just mentionned but cpuinfo does confirm it to be 2Big Network 1. Altough they might have use a V2 PCB but with a V1 CPU.