Ya know, I think you’re either the unluckiest person around, or you’re just plain making stuff up! :smileyvery-happy:
For one thing, you do NOT have the same issue. The OP said that his drive’s SUPERBLOCK got corrupted by the NAS Client. That is impossible. Samba doesn’t do BLOCK LEVEL access to files. NFS doesn’t even do that. These protocols are FILE-LEVEL protocols. They do not have access to BLOCK-LEVEL data.
File corruption IS possible, but quite unlikely the Hub is responsible. I don’t care how often you say it’s 100% the Hub. Nothing you’ve indicated proves anything. You’re succombing to a logical fallacy known as “Post Hoc Ergo Propter Hoc.”
I won’t say it’s impossible, but I can say that I have ALWAYS given my Live Hub Read / Write access to the NAS, and not a single issue with file corruption.
Your own statement even tends to indicate it was NOT the Hub:
the FIledate changed and it was exactly the Time where i granted Write Access to the Hub
Unless you told the Hub to access a file at the SAME SECOND you changed the priviledges, then the NAS did something all on its own. You’re suggesting that the Hub is just sitting there watching a file and waiting to gain write-access to it, and the instant it gains access, it wrote something. That’s not how the Hub works.
From the sound of it, you’re saying that it’s almost 100% reproducible problem.
I would love to see real evidence: A Wireshark capture of this event occurring.