hwclock error

hwclock error

Postby wd9895 » Sun Nov 24, 2019 9:30 pm

New HDD in 2big network 2
FW 18.2 is on the drive already
When storing new colors of interface the error occurs:

could not update field :__FILE__, hwclock -w -u, err= 1

root@2big2:/ # hwclock
hwclock: can't open '/dev/misc/rtc': No such file or directory
root@2big2:/ # hwclock -w -u
hwclock: can't open '/dev/misc/rtc': No such file or directory

root@2big2:/ # dmesg|grep rtc -B 5 -A 5
[ 25.954294] aoe: AoE v85 initialised.
[ 26.063255] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 26.070338] ata2.15: Port Multiplier 1.1, 0x197b:0x2352 r1, 2 ports, feat 0x0/0x8
[ 26.084894] ata2.00: hard resetting link
[ 26.443945] ata2.01: hard resetting link
[ 27.013250] rtc-mv rtc-mv: internal RTC not ticking
[ 27.018571] i2c /dev entries driver
[ 27.023530] at24 0-0050: 512 byte 24c04 EEPROM, writable, 16 bytes/write
[ 27.030676] uvcvideo: Unable to create debugfs directory
[ 27.037263] usbcore: registered new interface driver uvcvideo
[ 27.042986] USB Video Class driver (1.1.1)
--
[ 27.250869] NET: Registered protocol family 5
[ 27.256222] console [netcon0] enabled
[ 27.259868] netconsole: network logging started
[ 27.265186] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 27.272877] sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8
[ 27.278451] hctosys: unable to open rtc device (rtc0)
[ 27.286059] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 27.291403] md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
[ 27.331308] EXT4-fs (sdb7): mounting ext3 file system using the ext4 subsystem
[ 27.346164] EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
[ 27.353887] VFS: Mounted root (ext3 filesystem) readonly on device 8:7.

Any hint ?
wd9895
Donator Supporter
Donator Supporter
 
Posts: 255
Joined: Fri Jun 10, 2011 1:49 pm
Location: Hamburg, Germany

Re: hwclock error

Postby fvdw » Sun Nov 24, 2019 10:47 pm

think you already found the issue,
[ 27.013250] rtc-mv rtc-mv: internal RTC not ticking

hwclock is broken, sometimes it can be repaired by repairing a leaking capacitor

a search on the form using this string "could not update field :__FILE__, hwclock" give you many topics, most of them are related to older lacie like 5big and 2big version1
Seems now the v2 start to have this problem. But The nas doesn't need it it will function also without it
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: hwclock error

Postby wd9895 » Sun Nov 24, 2019 11:15 pm

I'm going to dismantle the box in the next few days.
Shouldn't be a problem if this is a capacitor.

I'll also look after the fan which is really annoying.
Modern Harddisks do not produce so much temperature as the ones 10 years ago.
wd9895
Donator Supporter
Donator Supporter
 
Posts: 255
Joined: Fri Jun 10, 2011 1:49 pm
Location: Hamburg, Germany

Re: hwclock error

Postby wd9895 » Wed Nov 27, 2019 6:38 pm

Another observation:
The hardware clock runs even without a synchronisation and when the NAS is switched off.
No reset on 1/1/20xx

Anyhow I will replace the capacitors but I don't feel confident about it.
wd9895
Donator Supporter
Donator Supporter
 
Posts: 255
Joined: Fri Jun 10, 2011 1:49 pm
Location: Hamburg, Germany

Re: hwclock error

Postby fvdw » Wed Nov 27, 2019 7:27 pm

Hwclock is different from system time. Maybe you have set in webinterface to synchronize time with internet.

Replacing capacitor is tricky as soldering on a multilayer board is risky. It is a super capacitor that acts as battery.

Note. there is no real need to fix it
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands


Return to Lacie 2Big Network vs2

Who is online

Users browsing this forum: No registered users and 5 guests