QNAP firmware issues : Major file system bug

[SuperMario]

Hey all,

I see that some people have had a "we've replicated the problem" message from QNAP, well, I've heard that before and we'll see. Let's remember that customers are still waiting for the promised fix to the NMP-1000 Youtube issue - and that hasn't appeared yet, so I'm reluctant to believe anything that QNAP might say unofficially.

I haven't had any response from them since late last week. I really do hope that they have, though, so I'll keeping my fingers crossed, but going off past experience, I won't hold my breath.

A little update: I wiped the TS-859 with the sanitized data set and tried to copy the contents of the TS-1079 across to back up as much as we could. I reversed the copy process this time, in that I copied all the multimedia files first and then I copied the remaining data, and low and behold, it repeatedly stalls bad enough that we can't even complete the copy operation. The data is mostly the same, just I didn't randomize the filenames or file sizes as it is our "backup" in case the TS-1079 drops more drives and kills this volume, too.

So we're going to have to find some way to copy the rest of the data to another machine just to ensure we have a full backup of the rest of the data on the TS-1079, but it proves that the same data when filename extensions are left intact has the issue, but not when they're changed.

Simon: How about QNAP actually post some information to this thread letting all of your customers know what the ** is going on? What is the root cause of the problem? If your engineers have replicated the issue as it has claimed to other people, then how about providing an explanation to your customers? How about informing your customers of when we can expect a fix to appear?

Mario.

[schumaku]

Let's remember that customers are still waiting for the promised fix to the NMP-1000 Youtube issue - and that hasn't appeared yet,

Nope my friend - while I (like many others) not happy with its scope - NMP-1000 v1.2.0 Build 1013 was released to beta on 12 October - and is playing Youtube well, certainly the big majority where the Codec is supported by the chipset.

[AdrianW]

Simon: How about QNAP actually post some information to this thread letting all of your customers know what the ** is going on? What is the root cause of the problem? If your engineers have replicated the issue as it has claimed to other people, then how about providing an explanation to your customers? How about informing your customers of when we can expect a fix to appear?

I'd really like to see some real information on the problem and some idea when a fix will be available. Saying things like "we're sure we'll find a solution" isn't very reassuring.

In 17 days it will be one entire year since I originally posted about my problem with stalls when copying to my 859

[SuperMario]

Let's remember that customers are still waiting for the promised fix to the NMP-1000 Youtube issue - and that hasn't appeared yet,

Nope my friend - while I (like many others) not happy with its scope - NMP-1000 v1.2.0 Build 1013 was released to beta on 12 October - and is playing Youtube well, certainly the big majority where the Codec is supported by the chipset.

All I can see for download for the NMP-1000 is "NMP-1000 v1.2.0 Build0309 PAL v1.2.0 Build0309 PAL" dated the 2011/03/11.

I was told by QNAP that I'd be informed when there was a beta, of which they told me about a test version for the NMP-1000P - but that's a different unit and nothing since then.

Do you have a link for this beta version, I'd love to finally be able to use the NMP-1000 for what I bought it for. Right now, it;s just another QNAP product that I've wasted my time and money on.

EDIT: I just found that there was an embedded link in schumaku's original post (the blue text). I didn't even know that thread existed. I'll grab it now and test it tonight, thanks schumaku.

EDIT#2: ** typical. The update doesn't work (I have a pal version unit) - it finds the update and after loading it says "Update failed!". ** brilliant work QNAP. I'll refrain from posting about the NMP-1000 as it isn't relevant to this thread, but it needs to be said that if this is the quality of their FW updates, I now really have doubts about QNAP's ability to do anything properly.

Mario.

[peterjaman]

First time on to this forum and first time realising i have the same issues...

I use the ts-412 (3.5.1) 4 x 2tb WD drives, as my back up device and a media played for our iTunes media centre, we have just under 5.5tb of date made up of back-up data from 4 macs in the house (2.2tb). The rest is made up of movie, music and photo files (3tb +)... In total over 15m files in 3m folders.

Over the last week i have noticed iTunes had some issues syncing with the media library and on Friday it came to a hold and would no longer sync. Any device i also tried to sync to it had the same problem...would just stall and hang. Sometimes it would start up and sync a couple of files, but then just stop and hang again... Till it got to the point where it timed out and crashed.

I figured this was an iTunes issue so i called support and we spend 3 hours on the phone troubleshooting (QNAP...you could learn from Apple support...3 hours on the phone with different escalation levels till i was connected to a expert in Sweden, who spent a good 40 minutes trying different things...this costs me $300AUD for 3 years when i bought my mac).

Anyway, what we worked out was that if we tried to copy files to the 412 it would just stall...a 4mb file took 4 minutes to copy. We tried network tests we tried isolation tests and the final test was not copying anything to the drive but just moving files on the drive...from the downloads directory to the multimedia directory. A 180mb file took 29 minutes. This was done directly from the QNAP file manager browser window and the files were moved within the QNAP's directories...so there is no outside moves or transfers.

After reading this thread i tried deleting files...guess what...presto everything works again.
The file transfers work and iTunes syncs again. Sounds rather obvious to me there is a problem here...
Im not a tech in any way, I'm just a guy that knows enough to setup a half decent 1gb home network with a few basic gb switches and some mac gear. But if i can read this after having the problem and take from it there is a solution that means you remove files from the drive and then it works...i would have though people a little smarter then me with this sort of stuff should see it rather obviously.

Thanks for your help fellow Aussie...SuperMario (and people positively adding to the tread). Im sorted for now and will monitor it to make sure the problem doesn't happen again. Wlil i buy that second QNAP i now need considering this one is just about full...no F****'ing way.
Appreciate the thread...its been interesting reading to say the least...

[AdrianW]

If you're following this thread - you need to read the first post: here, which has been updated by QNAPSimon with some info re: the linux kernel.

[spid]

If you're following this thread - you need to read the first post: here, which has been updated by QNAPSimon with some info re: the linux kernel.

This is good news, even if it takes some weeks as stated in the post.
Hopefully i can keep the amount of files down until the new firmware is out.

[SuperMario]

Thanks for posting an update for everyone, Simon.

I've been away traveling on business for the past 2 weeks, so it's good to see that the root cause has finally been reproduced and identified by QNAP. Even better that there has been some public confirmation of the issue.

Do you have a rough timeline for when we will see a fix? I think quite a few people would be willing to test a potential fix, as I know we'd like to be able to get back to actually using the units properly ASAP.

Mario.

[Yeroon]

this seems to be related to several other posts on this forum.

http://forum.qnap.com/viewtopic.php?f=25&t=35355
http://forum.qnap.com/viewtopic.php?f=25&t=31693


Hopefully the kernel update will solve them.
Like SuperMario i'm waiting for a solution for more than a year now.

[q20]

New firmware out; same kernel, though.

[~] # uname -r
2.6.33.2

[bobertuk]

New firmware out; same kernel, though.

[~] # uname -r
2.6.33.2

If you take a look at the first post in this thread, you will see a statement from QNAP that the new kernel will be added after firmware version 3.5.2

Bob

[TonyPh12345]

They confirmed it also affects 3.5.2. They didn't say it'd be fixed on the first release after it.. So, it might not be fixed until 3.5.9!

[forkless]

Fair enough it isn't fixed in 3.5.2 yet as it was in beta before the kernel issue was confirmed but I sure may hope that it will be in the next round of updates. -)

[broz]

Is it hard to update the kernel?

[forkless]

Define hard. For QNAP probably not but that is not the issue while this is taking a while. They need create new firmwares for all their models and run tests (to make sure there are no other issues that surface) before pushing them out publicly.

Like indicated at the start of the thread it would take some weeks to get through the process.