So my first idea was to get the debug logs off it, it seemed like mostly jibberish it just said in the OTA section that Firmware flashing failed. Same log like 6 times over. So i was like whatever Ill just reset and lose all my data, thanks alot WD for forcing us to update firmware for a device that wont update easily in the first place -_- anyway I reset and it was all f’ed up so i did some googling and figured it was probably my port forwarding, so i decided to just throw it in the DMZ, it says firmware update found, 4 hours later it still hadnt updated so im like who knows maybe it glitched again, i check the logs and its the same failure to flash the firmware i guess I dunno im not a linux guy, so i reset again and now its just sitting there updating the firmware. I mean since when does a firmware update for a device like this take hours or days. Im getting pissed
a 700 dollar device should not need major unstated changes to my router settings just to download and flash a update in the first place. Ill let it hang here updating for a day or two but then im done, i am fairly tech savvy, this should not be this hard
I don’t own the device you have but, have you already looked at this?
Yea i mean ive seen it its just whenever i check my debug logs it always shows that its failing to flash the firmware for some reason as far as i can tell. It says firmware update found now that ive put it in the DMZ of my router but its just kinda sitting there, going on several hours now after that last reset attempt. I mean i guess ill see but im just pissed that they made this necessary in more ways than 1 and i lost all my data. This is basically just like a 1 month old device now and its never successfully updated firmware. I mean hell they couldve at least put some obvious alert to tell me it needs to be port forwarded still in the first place and not expect me to just figure that out, and again since its not flashing im not even certain thats the problem at least in entirety.
Seems like you could have or should have returned or backup the device before everything gone south. The OTA and smartctl log which are part of the debug_logs is the first place to look. It doesn’t take a ‘Linux guy’ to read the error logs. The second place to look is to file a case with WD support. The third place to look is to post the OTA log and smartctl log as this person did.
Yea I only recently became aware that i wasnt on the latest firmware and i was too busy working to really do anything about it. I guess since it says it found a firmware update itll hopefully eventually flash but from what the internet says that could take like 1 to 7 days. if it isnt updated in a week i guess ill try to update it at a family members house. beyond that I dont know what to do.
[DEBUG][install_a.cpp:main():837]argc:5
[DEBUG][install_a.cpp:main():838], argv[0]=fw_update
[DEBUG][install_a.cpp:main():838], argv[1]=-r
[DEBUG][install_a.cpp:main():838], argv[2]=-v
[DEBUG][install_a.cpp:main():838], argv[3]=9.4.0-191
[DEBUG][install_a.cpp:main():838], argv[4]=/tmp/otaclient/fwupdate/install.img
[DEBUG][install_a.cpp:main():841]opt_str=(null) , tgt_dev=(null), compress_srting=(null)
[DEBUG][install_a.cpp:main():853]package file path: /tmp/otaclient/fwupdate/install.img
[INFO][install_a.cpp:main():870]
Firmware update called on: Sun Mar 26 10:47:48 2023
[INFO][install_a.cpp:main():871]from=220
[INFO][install_a.cpp:main():873]to=191
[INFO][install_a.cpp:main():918]Reading boot config.
[INFO][install_a.cpp:wd_read_boot_config():325][INFO] bstate = 0, bna= 0, nbr = F
[DEBUG][src/rtk_main.cpp:rtk_burn_rtkimg_from_usb():1180]prtkimgdesc->tarinfo.tarfile_path:/tmp/otaclient/fwupdate/install.img
[INFO][src/rtk_tar.cpp:parse_tar():117]@parse_tar /tmp/otaclient/fwupdate/install.img 35
[INFO][src/rtk_tar.cpp:parse_tar():137]tarfile_path:/tmp/otaclient/fwupdate/install.img, tarfile_size: 259481600 Bytes (253400 KB)
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():51]hash_value :
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():54]0x00
[DEBUG][src/rtk_tar.cpp:rtk_dump_hash_value():56]
[DEBUG][src/rtk_tar.cpp:parse_tar():185]filename = KDP/
filesize = 0 ( 0KB), ustarin = ustar
[DEBUG][src/rtk_tar.cpp:parse_tar():185]filename = KDP/sata.dtb
filesize = 46818 ( 45KB), ustarin = ustar
[DEBUG][src/rtk_imgdesc.cpp:fill_rtkimgdesc_file():2622]KDP/sata.dtb can’t be figured
[DEBUG][src/rtk_tar.cpp:parse_tar():185]filename = KDP/bluecore.audio
filesize = 913312 ( 891KB), ustarin = ustar
[DEBUG][src/rtk_imgdesc.cpp:fill_rtkimgdesc_file():2622]KDP/bluecore.audio can’t be figured
[DEBUG][src/rtk_tar.cpp:parse_tar():185]filename = KDP/system.bin
filesize = 239390720 (233780KB), ustarin = ustar
[DEBUG][src/rtk_imgdesc.cpp:fill_rtkimgdesc_file():2622]KDP/system.bin can’t be figured
[DEBUG][src/rtk_tar.cpp:parse_tar():185]filename = KDP/sata.uImage
filesize = 14926336 (14576KB), ustarin = ustar
[DEBUG][src/rtk_imgdesc.cpp:fill_rtkimgdesc_file():2622]KDP/sata.uImage can’t be figured
[DEBUG][src/rtk_tar.cpp:parse_tar():185]filename = KDP/linux.root.cpio.gz_pad.img
filesize = 4194304 ( 4096KB), ustarin = ustar
[DEBUG][src/rtk_imgdesc.cpp:fill_rtkimgdesc_file():2622]KDP/linux.root.cpio.gz_pad.img can’t be figured
[DEBUG][src/rtk_tar.cpp:parse_tar():185]filename = config.txt
filesize = 443 ( 0KB), ustarin = ustar
[DEBUG][src/rtk_imgdesc.cpp:fill_rtkimgdesc_file():2503]Got config.txt
[DEBUG][src/rtk_tar.cpp:parse_tar():162]tar magic error
[INFO][src/rtk_config.cpp:rtk_load_config():586]
[Load configuration]
[INFO][src/rtk_config.cpp:rtk_load_config():606]ro.hardware = pelican, persist.wd.device_type = pelican.
[INFO][src/rtk_config.cpp:rtk_load_config():635] cbr = B
[INFO][src/rtk_config.cpp:rtk_load_config():639]
gPartitionAB(reflash part) = A
[INFO][src/rtk_burn.cpp:rtk_extract_file():4730]
Extract config.txt file into /tmp/config.txt…
[INFO][src/rtk_burn.cpp:rtk_extract_file():4732]tarfile_offset:0x0f774600 (443 Bytes = 0 KB)
[INFO][src/rtk_burn.cpp:rtk_extract_file():4758]extract config.txt from /tmp/otaclient/fwupdate/install.img
[INFO][src/rtk_burn.cpp:rtk_extract_file():4778]extract ok
[Part list]
efs part_name mount_point efs filename min_size
(22) rootfs (5) 0
(36) etc (5) 0
(24) cache (5) 0
(25) data (5) 0
(26) system (5) 0
(27) systemB (5) 0
(23) res (5) 0
(28) (6) 0
(29) (6) 0
(30) (6) 0
(31) (6) 0
(32) (6) 0
(33) (6) 0
(34) (6) 0
(35) (6) 0
[Part list]
efs part_name mount_point efs filename min_size
(22) rootfs (5) 0
(36) etc (5) 0
(24) cache (5) 0
(25) data (5) 0
(26) system (5) 0
(27) systemB (5) 0
(23) res (5) 0
(28) (6) 0
(29) (6) 0
(30) (6) 0
(31) (6) 0
(32) (6) 0
(33) (6) 0
(34) (6) 0
(35) (6) 0
[Part list]
efs part_name mount_point efs filename min_size
(22) rootfs (5) 0
(36) etc (5) 0
(24) cache (5) 0
(25) data (5) 0
(26) system (5) 0
(27) systemB (5) 0
(23) res (5) 0
(28) (6) 0
(29) (6) 0
(30) (6) 0
(31) (6) 0
(32) (6) 0
(33) (6) 0
(34) (6) 0
(35) (6) 0
[Part list]
efs part_name mount_point efs filename min_size
(22) rootfs (5) 0
(36) etc (5) 0
(24) cache (5) 0
(25) data (5) 0
(26) system (5) 0
(27) systemB (5) 0
(23) res (5) 0
(28) (6) 0
(29) (6) 0
(30) (6) 0
(31) (6) 0
(32) (6) 0
(33) (6) 0
(34) (6) 0
(35) (6) 0
[DEBUG][src/rtk_config.cpp:fill_yn_install_dtb():470]fill_yn_install_dtb(y)(1)
[LOG][src/rtk_config.cpp:fill_yn_install_dtb():470]fill_yn_install_dtb(y)
[DEBUG][src/rtk_config.cpp:fill_yn_update_etc():471]fill_yn_update_etc(y)(1)
[LOG][src/rtk_config.cpp:fill_yn_update_etc():471]fill_yn_update_etc(y)
[DEBUG][src/rtk_config.cpp:fill_var_install_avfile_count():497]fill_var_install_avfile_count(0)(1)
[LOG][src/rtk_config.cpp:fill_var_install_avfile_count():497]fill_var_install_avfile_count(0)
[DEBUG][src/rtk_config.cpp:fill_var_reboot_delay():502]fill_var_reboot_delay(5)(1)
[LOG][src/rtk_config.cpp:fill_var_reboot_delay():502]fill_var_reboot_delay(5)
[DEBUG][src/rtk_config.cpp:fill_var_efuse_key():507]fill_var_efuse_key(0)(1)
[LOG][src/rtk_config.cpp:fill_var_efuse_key():507]fill_var_efuse_key(0)
[DEBUG][src/rtk_config.cpp:fill_var_secure_boot():506]fill_var_secure_boot(0)(1)
[LOG][src/rtk_config.cpp:fill_var_secure_boot():506]fill_var_secure_boot(0)
[INFO][src/rtk_config.cpp:add_firmware():242]Before Add firmware(GOLDRootFS), filename(KDP/gold.root.sata.cpio.gz_pad.img), target(0x02200000)
[INFO][src/rtk_config.cpp:add_firmware():256]Add firmware(GOLDRootFS), filename(KDP/gold.root.sata.cpio.gz_pad.img), target(0x02200000)
[INFO][src/rtk_config.cpp:add_firmware():242]Before Add firmware(kernelDT), filename(KDP/sata.dtb), target(0x01f00000)
[INFO][src/rtk_config.cpp:add_firmware():256]Add firmware(kernelDT), filename(KDP/sata.dtb), target(0x01f00000)
[INFO][src/rtk_config.cpp:add_firmware():242]Before Add firmware(kernelRootFS), filename(KDP/linux.root.cpio.gz_pad.img), target(0x02200000)
[INFO][src/rtk_config.cpp:add_firmware():256]Add firmware(kernelRootFS), filename(KDP/linux.root.cpio.gz_pad.img), target(0x02200000)
[INFO][src/rtk_config.cpp:add_firmware():242]Before Add firmware(linuxKernel), filename(KDP/sata.uImage), target(0x03000000)
[INFO][src/rtk_config.cpp:add_firmware():256]Add firmware(linuxKernel), filename(KDP/sata.uImage), target(0x03000000)
[INFO][src/rtk_config.cpp:add_firmware():242]Before Add firmware(audioKernel), filename(KDP/bluecore.audio), target(0x01b00000)
[INFO][src/rtk_config.cpp:add_firmware():256]Add firmware(audioKernel), filename(KDP/bluecore.audio), target(0x01b00000)
[INFO][src/rtk_config.cpp:add_partition():317]Add partition command system /system ext4 KDP/system.bin 838860800
[INFO][src/rtk_config.cpp:add_partition():329]Before Add partition(system), mount_point(/system), filesystem(ext4:4), size(838860800)
[INFO][src/rtk_config.cpp:add_partition():389]Add partition(system), mount_point(/system), filesystem(ext4:4), size(838860800)
[INFO][src/rtk_config.cpp:rtk_load_config():767]pelican doesn’t match with hw-list.
[DEBUG][src/rtk_main.cpp:rtk_burn_rtkimg_from_usb():1189]fill_rtk_part_list_by_config(-1) fail
[DEBUG][install_a.cpp:main():1036]rtk_burn_rtkimg_from_usb(-3)
[INFO][install_a.cpp:main():1047]
install time:2 seconds
[INFO][install_a.cpp:main():1048]DHC install_a (JH version), date:Jan 4 2021, time:13:28:40 REV:969406M
[INFO][install_a.cpp:main():1062]
=== FLASHING FAIL ===
[FAIL][install_a.cpp:main():1239]
=== INSTALL FAIL ===
[INFO][install_a.cpp:append_ota_history_to_log():536]
OTA history:
Fw_updater version 2.7.3-2 called at 2023-03-26.10:47:48
from 220 to 191
OTA FAILED
I am getting the same failed firmware update log since March, 23rd and opened a case via Support. Unfortunately no response regarding the resolution but just some automated replies from the support agent till now. Probably I will not get a real response in the upcoming days.
I wonder whether the problem is related with CGNAT service forced by the ISP. If so, then I will be getting the same problem on the next rounds too. With a simple download & install option, they could have eliminated such problems/complaints?
This will be my last purchase from WD due to the lack of support and poor SW capabilities.
After receiving the below Customer Support response:
As per the shared logs, The data in the volume is corrupt. you can backup the data, carry out a full factory reset (data destructive) and setup the unit again to see if the firmware can be updated successfully.
I decided to go over the Debian+OMV installation as discussed in https://community.wd.com/t/install-debian-on-wd-my-cloud-home/250061/22 section.
Now, I have a Deb10+OMV5 installed device in 10 mins and started to transfer my backups to the new setup. Everything seems working properly. I think, I don’t have to deal with the helpless Support once more till they can provide a better service instead of joggling with the useless messages.
I am happy now 
hello, i have the same issue.
Could i ask you a really simple question (i am new to the software you are using)?
debian is an OS while OMV is a personal cloud, but i dind’t understood how you saved data. After the new OS installation OMV is able to read the data ALREADY in the nas? I must find a way to extrac that datas…
TY
I did not get the data as I was using the unit only for 5 days. I had all my backups and I made a fresh install. I believe you can get the data from the disks by taking out the drives from the unit bays, mount them on a linux based OS (you can set one on a VM platforms Win or Mac) as they are EXT4 partitions. Or you can purchase or find free SW which can read EXT4.
