Need to Upgrade Transmission from 2.92b to 2.93

[hvymetal86]

I hadn't seen any notice of it coming out but hadn't checked further than this thread so that's my fault. I found the post about donators and firmware updates and add-ons, successfully installed the new patch and just tried to login to the System Management > Setup > Firmware Interface page with my plugout account and got the following error on two attempts:

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

I wonder if it has anything to do with my plugout password being 100 characters long and having special characters... If it is I can just change/shorten it.

[Jocko]

Hi hvymetal86,

Currently, you have two issues but not linked.

First, when we implemented plugout account settings support, we did not think an user would use a so long password. Currently the password length is limited to 40 chars. With your current password, the firmware does not save your account settings and so you can not retrieve any package from plugout...

Currently, there is no way to fix it and you should change your password

The other issue is more annoying and seems to be an hardware issue. Indeed at each time you change some settings from the main setup menu, the firmware tries to synchronize the system clock (hardware datetime) with the software clock by using the hwclock command.

It seems your hardware clock is broken (may happen with a faulty capacitor). To valid that, please to post the output

Code: Select all

hwclock
dmesg|grep rtc -B 5 -A 5

[hvymetal86]

Haha, sorry about the password. I use a password manager so when I saw the forum said the limit was 100 I chose that. I've reset it to a 40 character one.

As for the commands, here was the output of both of them

Code: Select all

root@HvyMtlNAS:/ # hwclock
hwclock: can't open '/dev/misc/rtc': No such file or directory
root@HvyMtlNAS:/ # dmesg|grep rtc -B 5 -A 5
[    5.621534] aoe: AoE v85 initialised.
[    6.019037] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    6.025976] ata2.15: Port Multiplier 1.2, 0x11ab:0x4140 r193, 4 ports, feat 0x5/0x1f
[    6.042990] ata2.00: hard resetting link
[    6.369787] ata2.01: hard resetting link
[    6.629030] rtc-mv rtc-mv: internal RTC not ticking
[    6.634347] i2c /dev entries driver
[    6.639002] at24 0-0050: 512 byte 24c04 EEPROM, writable, 16 bytes/write
[    6.646260] uvcvideo: Unable to create debugfs directory
[    6.651891] usbcore: registered new interface driver uvcvideo
[    6.657613] USB Video Class driver (1.1.1)
--
[    6.837916] NET: Registered protocol family 5
[    6.843530] console [netcon0] enabled
[    6.847175] netconsole: network logging started
[    6.852454] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    6.859480] ata2.02: hard resetting link
[    6.864367] hctosys: unable to open rtc device (rtc0)
[    7.349304] ata2.03: hard resetting link
[    7.699071] ata2.01: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133
[    7.705573] ata2.01: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    7.739076] ata2.01: configured for UDMA/133
[    7.759067] ata2.02: ATA-9: ST2000DM001-1ER164, CC45, max UDMA/133


[Jocko]

Hi hvymetal86

I am sorry but these lines confirm my idea:

Code: Select all

[    6.629030] rtc-mv rtc-mv: internal RTC not ticking
[    6.864367] hctosys: unable to open rtc device (rtc0)


So the hardware clock is broken and for me it is not a software but hardware issue.

Fortunately, this issue does not prevent you from using the nas you just need to enable the Internet time option in the main setup menu. At each time you will change an option from the main setup menu you will get the hwclock warning but your changes will be saved.

To fix this issue, you should open the nas box and look at if you detect a damaged capacitor on the mainboard like this: viewtopic.php?f=27&t=2773&p=26577#p26577

[hvymetal86]

Just upgraded and Transmission 2.94 is working great. Thanks again for all the work you put into this. I'll probably open up the NAS at some point to confirm the capacitor issue, but I'm a bit gunshy about trying to replace it if so. I've never done board level repair before and if I mess it up all my data is gone unless I can find another 5bigv2...

[Jocko]

Hi

I've never done board level repair before and if I mess it up all my data is gone unless I can find another 5bigv2...

Please to note your NAS can run nicely without the hardware clock. Hardware clock is useful for debuging on nas booting (event are then rightly timestamp as soon as the kernel is loaded) or you do not want to use a network time server.
I have a 5big2 in the same state as yours for a long time without issue

[Lieven]

Hi,
I want to add my plugout login to fvdw-sl to install Web Explorer, but I get the error "could not update field :__FILE__, hwclock -w -u, err= 1" even though I already set the clock from NTP server. What do I do wrong?
I'm using an old edmini V2 and indeed the hardware clock will be defective.
Thank you.
Lieven

[hvymetal86]

In my case after I shortened my password from 100 characters to the max of 40, it saved it despite giving the clock error. If your password is already 40 chars or shorter you should start a new thread as it's a different issue.