Hi, I’m having a problem reaching a TS-1253U-RP. It cannot be found by the Qfinder Pro.
Here’s what I tried after removing all the drives in the system. The system can get into the BIOS without issue by pressing F2 / DEL and I can UEFI boot from a USB stick:
I followed the steps in NAS Recovery Guide for x86-based NAS | QNAP and copied the dom.img to the 492 MB DOM and restarted the system. (It gives 1 short beep around the BIOS time and 1 long beep after the BIOS time.)
I used a paper clip to press the small Reset button multiple times. Even after holding it down for 20 seconds, there are no beeps at the 3 or 10 second marks.
I can connect a USB keyboard and HDMI monitor and log in to the TS-1253U-RP. If I connect a network cable and type “ip a” then I see the IP address and I can ping it from a different machine. (But if I type http://[the ip address] or https://[the ip address] from the other machine, it’s not found, and Qfinder Pro does not find it either, and ssh can’t log in either.) If I disconnect the network cable from the TS-1253U-RP, then of course it cannot be pinged anymore from my other machine.
Following instructions from How to reset network & virtual switch setting via command line | QNAP - if I type /mnt/ext/opt/netmgr/netmgr.sh reset_all_settings_to_default, I get “No such file or directory.” If I type /etc/init.d/network.sh reset_network_config_to_default or /etc/init.d/network.sh clean-restart, I get a bunch of “sbin/getcfg: error while loading shared libraries: IibuLinux_Util.so.0: Cannot open shared object le: No such file or directory.”
Following instructions from qnap dot com (as a new user, I can only put 2 links and this is the 3rd) /da-dk/how-to/faq/article/how-to-reset-network-virtual-switch-setting-via-command-line, I get the same errors as before for the netmgr.sh and network.sh commands.
Following instructions from qnap dot com (as a new user I can only put 2 links and this is the 4th) /en/how-to/faq/article/how-to-set-up-a-direct-connection-test, Qfinder Pro still cannot find it.
I tried copying the dom.img again (same as step 1 in this list) but it still have the same errors when doing steps 4 and 5.
What can I try next? I can log in no problem so I assume the machine is working. Is there another way to reset the system from the command line? Thanks!
The errors indicating that getcfg and IibuLinux_Util.so.0 cannot be loaded usually suggest an issue with system files or libraries, potentially due to incomplete or incompatible restoration of the DOM image. Using an incomplete or non-compatible dom.img file could cause the system to experience startup and operational issues. Repeated unsuccessful restoration attempts may also indicate a problem with the DOM or hardware.
It seems that NAS Recovery Guide for x86-based NAS, Step 3/ Using the USB boot drive to recover the corrupted DOM is incomplete.
It’s recommended to submit a ticket via the QNAP Service Portal (Customer Service - QNAP), and a support engineer will assist you in changing the boot device to a USB device.
Hi @Yvette , thanks for your message. But I was able to change the boot device to a USB device by pressing F2 / DEL and I was able to UEFI boot from a USB stick.
I tried redownloading the image as @Regulus suggested, and I redid the copy of the dom.img twice (each time it takes around 30 sec to 1 min) but all the problems mentioned before persist. The libraries are still missing. I have a feeling the copy command didn’t actually work.
Is it possible that I accidentally put the DOM into read-only mode? Can I get it out of read-only mode?
The same post suggests to try dd if=/dev/zero of=/dev/sda count=200K and it works fine until 516 MB are copied (which is the approx size of the DOM). Transfer occurs at 5.3 MB/s which is reasonable. So in my case the DOM is fine.
I tried redownloading F_TS-X53U_20141125-1.2.8.img and it’s always the same problem. If even the reset button doesn’t work after installing the default firmware and I keep getting getcfg and IibuLinux_Util.so.0 cannot be loaded, then it’s obvious there’s something wrong with the image itself.
Could someone from Qnap please share an older or newer version of the image that worked or a corrected version of the image? Thanks!
If the USB DOM is good, there’s one more step that you need to update firmware to the latest version after perorming the firmware recovery. Still, it’s recommended to submit a support ticket for technical assistance =)
However, the F_TS-X53U_20141125-1.2.8.img image is not good. In addition to the forum post I mentioned last time, I found 2 more postings in the Polish Qnap forum about the image being bad.
It will be a real hassle to contact support to exchange it. Seeing that others have the same problem when they try to use this file, could you please ask support to test restoring that image onto a TS-453U or TS-853U or TS-1253U and then using the Qfinder Pro to try to connect to that image? They will see the problem and be able to reproduce the errors when they run /etc/init.d/network.sh. The image is not corrupt in the sense that it is a valid img file. But the img file is missing vital files required for the Qnap unit to work after the img file is copied to the dom.
So far, users with TS-453U or TS-853U or TS-1253U have all encountered this problem with this F_TS-X53U_20141125-1.2.8.img image and cannot connect to the Qnap using Qfinder Pro to properly update the firmware to the latest version after performing the firmware recovery.
@Yvette , I’d really appreciate it if you could please ask someone from the Qnap team to test restoring the https
download dot qnap dot com/Storage/tsd/fullimage/F_TS-X53U_20141125-1.2.8.img to a TS-453U or TS-853U or TS-1253U and then try to connect to the machine using Qfinder Pro. They will not be able to do it. And please ask them to run /etc/init.d/network.sh and they will see the “No such file or directory” / “Error while loading shared libraries” messages because the image is missing some important files.
Thank you very much for passing the message on to support, @Yvette . I really appreciate your help. Please let me know after they replace the bad image with a working image. Unfortunately, my NAS is completely unusable at the moment since I restored the bad F_TS-X53U_20141125-1.2.8.img image onto it.
@kifotib1421 As this issue cannot be reproduced in QNAP HQ, it is recommended to submit a ticket for RMA arrangement. QNAP local support team will recheck the DOM and image accordingly.
Could you please ask them what was the output they got when they ran /etc/init.d/network.sh using the download dot qnap dot com/Storage/tsd/fullimage/F_TS-X53U_20141125-1.2.8.img on a TS-453U or TS-853U or TS-1253U?
I’m trying to understand what the output is supposed to look like when it works correctly and compare it with when it does not work.
Hi @jln_brtn , unfortunately I couldn’t solve the issue.
In my case, the file on the Qnap site is most probably corrupt or otherwise incorrect, because multiple users reported the exact same issue on the exact same firmware on the Polish Qnap forum as I have linked above. And the instructions to restore the firmware are pretty simple and clear, so I think we are following the instructions correctly.
The device is out of warranty, so I’d have to pay quite a bit for the RMA. And it is large, so mailing it would be too expensive for me.
@Yvette and @Regulus, could you share how the support team checked the image please? Were they actually able to restore it successfully to a TS-1253U-RP? And could they share the checksum of the F_TS-X53U_20141125-1.2.8.img they were testing with so I can compare it with mine please? I have downloaded it 3 times and each time it’s the exact same issue as what has been reported by multiple other users in the Polish Qnap forum (error while loading shared libraries: IibuLinux_Util.so.0).
If they can correct the image, I’d really appreciate it because it’s too impractical for me to ship it back. The hardware itself is otherwise working fine and it’s a shame to not be able to use it due to the bad image file.
My problem as been solved by replacing the DOM storage. Huge thanks to the_dolbyman for the solution. I ordered this 8GB DOM from ebay.
I hope that will solve your problem too.
Hi @jln_brtn , unfortunately replacing the DOM and retrying the steps to restore the image didn’t solve it for me.
For good measure, I also tried writing the image to a USB stick and setting the Qnap to boot from the USB stick with the image. I got the exact same errors. This strongly suggests the F_TS-X53U_20141125-1.2.8.img image on the Qnap site is bad.
I ended up installing TrueNAS onto the larger sized DOM. So the DOM seems to be working just fine.
I’d prefer to use the Qnap software, but if it is corrupted, then that’s really not an option.
If @Yvette and @Regulus could share how the support team checked the image please, that would be greatly appreciated! Were they actually able to restore it successfully to a TS-1253U-RP? And could they share the checksum of the F_TS-X53U_20141125-1.2.8.img they were testing with so I can compare it with mine please? Even when I write to a new DOM or to a USB stick and boot from the USB stick, it’s the exact same issue as what has been reported by multiple other users in the Polish Qnap forum (error while loading shared libraries: IibuLinux_Util.so.0).
