Failed to update firmware

Questions about SNMP, Power, System, Logs, disk, & RAID.
Post Reply
IMeMyself
New here
Posts: 2
Joined: Sat Sep 24, 2022 6:26 pm

Failed to update firmware

Post by IMeMyself »

I've had the same issue on a TS-431P, with 1 small SSD, 1x 8TB, 2x2TB.

Model:
TS-431P
Current firmware version:
4.3.6.0923
Date:
2019/04/25

I've done a "Reset Settings", then followed the SSH procedure to upgrade the firmware, here's the log:

Code: Select all

[~] # mkdir /mnt/HDA_ROOT/update
mkdir: Cannot create directory `/mnt/HDA_ROOT/update': File exists
[~] # rm -rf /mnt/update
[~] #  rm -f /tmp/update_process
<S-131P_231P_431P_X31+_X31K_20220419-4.5.4.2012-work.img
[~] # ln -sf /mnt/HDA_ROOT/update /mnt/update
<lic/TS-131P_231P_431P_X31+_X31K_20220419-4.5.4.2012-work.img
cksum=3424970820
UBI device number 1, total 1728 LEBs (219414528 bytes, 209.2 MiB), available 172                                                                                                                                                             0 LEBs (218398720 bytes, 208.3 MiB), LEB size 126976 bytes (124.0 KiB)
Set volume size to 218398720
Volume ID 0, size 1720 LEBs (218398720 bytes, 208.3 MiB), LEB size 126976 bytes                                                                                                                                                              (124.0 KiB), dynamic, name "tmp", alignment 1
Using 120-bit encryption - (QNAPNASVERSION4)
len=1048576
model name = TS-X41
version = 4.5.4
IS_STORAGE_V2
TS131K_u-boot.bin
TS131K_u-boot.bin.cksum
TS131K_u-boot.bin.sign
TS131P_u-boot.bin
TS131P_u-boot.bin.cksum
TS131P_u-boot.bin.sign
TSX31AK_u-boot.bin
TSX31AK_u-boot.bin.cksum
TSX31AK_u-boot.bin.sign
TSX31K_u-boot.bin
TSX31K_u-boot.bin.cksum
TSX31K_u-boot.bin.sign
TSX31P+_u-boot.bin
TSX31P+_u-boot.bin.cksum
TSX31P+_u-boot.bin.sign
TSX41_u-boot.bin
TSX41_u-boot.bin.cksum
TSX41_u-boot.bin.sign
boot/
config/
eeprom_1.38_AL212-1700_OB_1G_V2.bin
eeprom_1.38_AL212-1700_OB_1G_V2.bin.cksum
eeprom_1.38_AL212-1700_OB_1G_V2.bin.sign
eeprom_1.39_AL212-1400_OB_1G.bin
eeprom_1.39_AL212-1400_OB_1G.bin.cksum
eeprom_1.39_AL212-1400_OB_1G.bin.sign
fw_info
fw_info.conf
i2cget
i2cset
libcrypto.so.1.0.0
libssl.so.1.0.0
rootfs2.ubi
rootfs2.ubi.cksum
rootfs2.ubi.sign
u-boot.bin
u-boot.bin.cksum
u-boot.bin.sign
uImage
[Firmware Update] System update failed. Firmware file format error. Error code: FW004
I don't want to loose all data so I'd rather avoid reinitialization to solve the issue..
FSC830
Experience counts
Posts: 2043
Joined: Thu Mar 03, 2016 1:11 am

Re: Failed to update firmware

Post by FSC830 »

IMeMyself wrote: Sat Sep 24, 2022 6:31 pm ...
I don't want to loose all data so I'd rather avoid reinitialization to solve the issue..
There exists an easy solution for not loosing data, its called "backup"!
Everyone, who do not taking care about backup should be aware that data can be gone in multiple ways:
Damage of NAS by fire, water, criminals, accident, ... whatever
NAS can be stolen, NAS can be hacked (if exposed to internet),...

There are numerous options to loose data. An error when updating is only one of many!
So everyone who has no backup will loose data, some sooner, some later!

A backup is always a copy of data at external devices, best stored at an external site!

Regards
IMeMyself
New here
Posts: 2
Joined: Sat Sep 24, 2022 6:26 pm

Re: Failed to update firmware

Post by IMeMyself »

FSC830 wrote: Sat Sep 24, 2022 6:48 pm
A backup is always a copy of data at external devices, best stored at an external site!

Regards
Thanks for your answer, I should rephrase: I would like a solution that does not involve wiping the storage devices in the NAS.
I already have onsite and offsite backups, as a matter of fact, this NAS contains a lot of backups.

Actually I would like to avoid is having to setup again the NAS too (I have all of the files on the NAS in other places, but not organized the same way).
FSC830
Experience counts
Posts: 2043
Joined: Thu Mar 03, 2016 1:11 am

Re: Failed to update firmware

Post by FSC830 »

In that case you are at the sunny side of data :DD .
FW004? As far as I remember this **could** be can error due a lack of capacity in partiton the firmware is stored.
But I am not sure about this.

Regards

Edit: Found some posts in German user forum with FW004 when updating from v4.3.x to 4.4.1.
As a solution was posted to do the updates step by step (if not the latest previous firmware is installed).
User avatar
dolbyman
Guru
Posts: 35275
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Failed to update firmware

Post by dolbyman »

IMeMyself wrote: Sat Sep 24, 2022 6:31 pm I've had the same issue on a TS-431P, with 1 small SSD, 1x 8TB, 2x2TB.

[...]
Please do not post in 4 year old threads..I will move these posts into a sepperate topic and close this thread

Original thread
viewtopic.php?f=25&t=144471
Post Reply

Return to “System & Disk Volume Management”