QNAP fails to reveal data corruption bug that affects all 4 bay and higher NAS devices

MAIN NAVIGATION

How To Fix / Mount RAID After 4.1.0 Firmware
We had a number devices have drives fail in quick succession — and on ALL of them, the ShadowProtect backups became corrupted in some way. Always back up your data. Hi Moogle, Glad to have helped. After continued verification and discussions, the team has now not only updated the release note to include this important fix:. Should I just go stright to 4. Please share this message with other resellers and end users so they can protect their data too.

QNAP Utilities


Commands are based on firmware version so you must check this first. Also be sure that you only type right commands You can copy these commands and right click on on putty to paste. One last thing, this is not Qnap global offical website and you can always request help from your local Qnap tech departman or offical global Qnap support team www. We can fix this kind of cases less than 10 minutes. See output of dmesg command below. Attached scsi generic sg19 type 0 [ Your email address will not be published.

You may use these HTML tags and attributes: Notify me of follow-up comments by email. Notify me of new posts by email. How To Start chkdsk Command" Document added; http: How To Fix" document extended; http: Never miss your favorite TV show again! Channel your music talent on the air Music Station: What Should I do? Given we had another copy of some of the files we were able to copy over the missing bits of the backup and restore the image chain to working order. In some cases, due to clients choice, there were no other copies of the backups and therefore the client lost their entire backup chain, and had to start backups from scratch again.

During the investigation with QNAP — it took QNAP over 2 months before they would configure StorageCraft backups and simulate the issue, that was despite the fact that we had replicated it on our test environment for them in advance. It was not until end of March that they reported back to us that they had found the issue and fixed it in firmware to be released in April.

They then further reported that they felt the issue was related to StorageCraft, however offered zero proof of this. I believe they felt the issue was related to StorageCraft only due to the fact that this was the program that highlighted the data was corrupt, and that if we had MD5 checksums of the word and other documents we could also have proven the corruption.

He reported that they too had seen a number of incidents where data corruption occurred on a QNAP NAS following a disk failure, however they too did not link the disk failure to the corruption until we brought them into the investigation.

A little googling shows that we are not alone and others are also experiencing similar issues. Look at this post here on Veeams forums where users report corruption after disk failure.

That makes me wonder if there are more issues with Linux based NAS devices out there that other vendors are seeing and not reporting. So — following the release of the updated firmware that fixed the problems, we scoured the release notes for advise that this indeed fixed a potential data corruption issue.

Nothing could be found then and even today, nothing is shown. We asked QNAP why they did not include this information as we really felt it was critical for ALL to upgrade to this fixed firmware given the potential data loss that could occur.

One can only wonder what other issues QNAP are fixing under the covers and not advising us about in their release notes. All in all we spent over hours investigating, proving and fixing this issue over the last 6 months, without even a thank you from them for the efforts expended.

However they have not done so and had not responded now for over a month until we prompted them a week ago, and now have gone silent again. I fear that they are too worried about public perception of their NAS to release what I see is critical information. In short, if you have any QNAP running a version before 4. No amount of data scrubbing will recover the data if you have a disk failure and have not upgraded to these versions at a minimum. Please share this message with other resellers and end users so they can protect their data too.

Read more about it here. While this is a none-official reply, I thank you for your team to have time investigate and highlight the issue to us. I also apology if you did not have a satisfied experience with our related support processes. As I have checked, we have already reviewing our release note draft with you, and we will improve and release it as soon as possible. It is confirmed that our storage system does cause hidden data integrity issue on parity block.

After the issue can be reproduced in our lab and is confirmed can cause data corruption along with Storage Craft Shadow Copy, we have now disabled it in all our released 4. Despite we have only received officially support request related to this issue from user that uses Storage Craft, we do agree with you that this option can potentially cause hidden data corruption under more general conditions when a RAID is in degraded mode, and should receive a higher level of attention and be addressed in the release note when fixed.

I thank you again for having this post, please kindly let me know if you have any further suggestion or find any other storage issue, and free feel to contact me directly by ripplewu qnap. We use ShadowProtect and have been fighting unexplained data corruption reported in ImageManager. I would upgrade either way to be sure. To be clear however, with my testing, the data is fine right up until a disk failure occurs, and it is at that point that the corruption occurs as the RAID software needs to recalc the missing data my terminology and it does so incorrectly.

If you have a QNAP and do not have a disk failure then the data is for the moment good. Thanks for taking the time to reply!

I appreciate your insight as well as that of the QNAP manager. End result is everyone wins. I am of the understanding that this bug would not affect RAID scrubbing process. I did not have any hdd failure during that period, but i did have stuff like — raid scrubbing — file system check after powercut.

Glad to have helped. Will post in next 24 hours. Jon — I have not yet completed it — will do so hopefully tonight. Work has been a bit crazy the last few days. Similarly to yours, they were not good. I created a case with QNAP first case online and second case from the NAS itself and support requested remote support to be enabled on the device.

After about a week they came back to me requesting access to be extended as it had expired. No other follow up emails or phone calls. Tired of waiting on them, and having to get it working again, I migrated the data off and destroyed the pool to get it fixed.

The second case was exactly like the first one — same issue, but this time I decided to wait a bit longer before fixing it myself, as I wanted to find the root cause for the error. After about two or three weeks I had no choice but workaround the issue myself and this time disable snapshot on the volumes. I had the opportunity to express my dissatisfaction on the survey after closing the case, but again never heard back from QNAP. As you mentioned QNAP support is really bad, and they do not care about the customer data.

I have had the pleasure of doing work with them and like your case, it took months to get correct information not a resolution because of lack of response and responsibility from QNAP support. I too have concerns about their support, but want to work with them to make it better if they are willing to do so.

After continued verification and discussions, the team has now not only updated the release note to include this important fix:. Such advice will include all the detail of an identified issue such affected products range, summary and suggested solutions and be announced on our website, sent to related distributors and promoted to related users as soon as released. While the team surly will move forward to understand how to more actively disclose an important fix and promote such information to our users, again me and the team thank your contribution to have this post and all the related efforts so that we can continue improve our processes to ensure the integrity of the data that users entrusted to our products.

Thanks for your good work! I have got a question: The first firmware was 4. Since then I updated the firmware to each new version 4. While I did this, there was installed firmware 4.


Leave a Reply

Qnap QXGG1T Single-Port (10Gbase-T) 10GbE Network Expansion Card, PCIe Gen3 x4, Low-Profile Bracket pre-Loaded, Low-Profile Flat Full-Height Brackets are Included. There’s no other way to put this, QNAP do not believe that a bug which risks corrupting your data on your QNAP NAS is worthwhile mentioning in their release notes at all. Qfinder Pro. Qfinder Pro (available for Windows, Mac and Ubuntu) allows you to quickly find and easily access all of the QNAP NAS on the same LAN.