Page 4 of 39

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Thu Sep 07, 2017 9:46 pm
by michele.merlini
same issue here! disk 3 .
error messages: "Host: Disk 3 failed." - "Host: Disk 3 unplugged." - "A drive has been detected but is inaccessible. Please check it for faults."

anyway my nas found a new firmware version 4.3.3.0299 Build 2017090116 .
Updating right now. i'll let you know if it solves!

_________________________________________
here is the change log

QTS 4.3
QTS 4.3.3.0299 Build 20170901

[Important Notes]
- When QTS 4.3.x is installed on NAS models running on 64-bit Intel and AMD processors, some applications may not be supported. To check if installed apps on your NAS are compatible with QTS 4.3.x, download the QTS 64-bit compatibility tool and install it on your current QTS build. (https://download.qnap.com/QPKG/CF64_0.1-1114.qpkg.zip)

[New Feature]
- Twonky Server 8.3 is now a built-in feature for the following NAS models that have serial numbers beginning with Q16 (or smaller numbers):
TS-x63U-RP, TS-x63U, TS-x53U-RP, TS-x53U, TS-x51U, TS-x79 Pro, TVS-x71T, TVS-x71, TVS-x63+, TVS-x63, TS-x63, TVS-x63, TS-x53A, TBS-x53A, TS-x53 Pro, TS-x53S Pro (formerly known as the SS-x53 Pro), TS-x53mini, TS-x51+, TS-x51, TS-x51S, TS-x51C, TS-x31P, TS-x31+, TS-x31, HS-x51+, HS-x51, TVS-x70, TS-x70 Pro, TS-x70, TS-x69 Pro, TS-x69L, IS-400 Pro, TS-x21, TS-x21U, TS-x20, TS-x20U, TS-x19P II, TS-x19P+, TS-x19P, TS-x19, TS-x19U II, TS-x19U+, TS-x19U, TS-x12U, TS-x12-E, TS-x12P, and TS-x12.
- Added a message to remind users that the performance of domain controllers may be affected if the system memory is less than 2 GB.
- Added support for connecting to the Internet via PIX-MT100 LTE USB dongle.

[Fixed Issues]
- Fixed a vulnerability in the Linux kernel that could be exploited to circumvent the stack guard page (CVE-2017-1000364). This fix is available to all NAS models that support QTS 4.3.3.
- Updated the version of MariaDB to 5.5.57 to fix multiple vulnerabilities.
- Updated the version of PHP to 5.6.31 to fix multiple vulnerabilities.
- Fixed multiple command injection vulnerabilities.
- Updated the version of the Portable UPnP SDK (libupnp) to 1.6.22 to fix a vulnerability that could allow for unauthorized modification to arbitrary files (CVE-2016-6255) and a heap overflow vulnerability that could be exploited to execute arbitrary code or cause a denial of service (CVE-2016-8863).
- Fixed a command injection vulnerability in Media Library to prevent unauthorized remote command execution.
- Users could not copy files to a mounted shared folder after installing Container Station on the TS-870.
- Users can now perform and complete McAfee antivirus scan jobs.
- The details of users would not be displayed in "Control Panel" > "Privilege" > "User Groups" when the group name contained certain characters.
- The configuration buttons in "Control Panel" > "Privilege" > "Domain Security" would be incorrectly disabled after users joined the NAS to a domain and then updated the QTS version to 4.3.3.
- Performing I/O tests on the TS-EC1279U would cause the NAS to randomly restart.
- Installing and using Container Station on the TS-EC1679U would cause the NAS to run out of memory and then restart.
- Users could not access folders with circular symbolic links via AFP.
- File Station could not correctly display the properties of Qsync files or folders.
- When users synced the same shared folder to two devices using two accounts, some synced files would be missing on one of the devices.
- Duplicate files might appear in the destination folder when users uploaded a large number of files to the synced shared folder.
- Qsync could not sync the files in a shared folder if the option "Only admin can create files/folders" was enabled for its parent folder.
- On the TS-431X, the clock speed of the CPU was not correctly displayed in "System Information".
- Active Directory users could not access the previous versions of a shared folder on Windows.
- Active Directory users would not be immediately blocked from or logged out of Qsync after the NAS left an - Active Directory domain.
- Remote controls might not function correctly after the NAS woke up from the S3 Sleep Mode.
- Users could not complete upload tasks when uploading large files to Amazon Drive.
- Users could not join the NAS to an Active Directory domain if SMB1 was disabled on the Active Directory server.
- The NAS occasionally could not connect to the Internet after users created a virtual switch with the system default gateway.
- The network configuration of the Thunderbolt Bridge would revert from a static IP address to an automatic IP address after users restarted the NAS.
- Backup Station could not correctly display the time left, the transfer speed, or the job status of RTRR FTP jobs in the "Job Status and Logs".
- After uploading files from a Mac to a NAS shared folder, users could not transfer the files to Windows 7 or Windows Server 2008.
- Fans would rotate at an abnormally high speed after users set the fans to the Quiet Mode and then restarted the NAS.
- After restarting the NAS when migrating the folder to an encrypted folder, users could not access a shared folder via SMB.
- The settings of the primary DNS server would not be correctly configured when Domain Controller was enabled.
- Antivirus scan jobs could not be completed if users uploaded renamed virus definition files.
- Non-admin users could not run NAS-to-NAS backup jobs on Backup Station.
- Users could not back up the files in certain paths to an external storage device using USB One Touch Copy.
- Duplicate users would appear as user groups after administrators granted folder permissions to domain users via Windows ACL.
- Using Rsync commands on a command line interface would cause errors after users updated the version of QTS to 4.3.3.0238.
- Administrators could not grant users permission to access the NAS via SSH if their usernames contained a whitespace character.
- Users could not enable RAID Scrubbing again if they did not modify the previous RAID Scrubbing schedule.
- Users could not select the highest SMB version on the TS-x31, TS-x28, and TAS-x68 series.
- The Control Panel interface would take longer to respond when users added a large number of IP addresses to the blacklist or whitelist.
- Users could not access the NAS running certain QTS versions when using Firefox 54.0.1 and Java 8 Update 144 - (32-bit).
- The option to specify snapshot reserved space was available during QTS installation on the NAS models that do not support snapshot features.
- Some NFS shared folders would not be mounted after users restarted the NAS.
- StarWind iSCSI Initiator would stop responding when accessing the iSCSI targets after users updated the QTS version to 4.3.3.
- An error about default gateway configuration would occur when users signed in to myQNAPcloud if VLAN was enabled and static IP address was used for a network interface.
- Users could not remotely access the NAS via CloudLink when the access control permission in myQNAPcloud was set to "Private".
- Users were unable to install Let's Encrypt on myQNAPcloud after installing QTS SSL Certificate.
- After taking snapshots for shared folders and then updating the QTS version to 4.3.3, users could not access the previous versions of shared folders on Windows via SMB

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Thu Sep 07, 2017 10:39 pm
by dolbyman
why waste all the space with the (publicly available) changelog?

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sat Sep 09, 2017 2:51 pm
by whoslistening
The problem is back. This is after updating to the most recent firmware (4.3.3.0299). I've replaced all four drives with brand new WD Reds, so it's definitely not the drive.

I have submitted a ticket but since my device is out of warranty, I'm not sure what resolution I'm going to get.

I must say I'm quite disappointed with QNAP on this, and it's making me look at just getting another brand.

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 12:59 am
by bvandeering
Hello i have a TS-415A I have four 3TB western digital RED HDD's. I had a disk fail got a replacement from WD, it failed got another replacement it failed got another replacement this time I ran the WD disk checker on the drive both quick tests and extended tests pass fine but again the drive fails on the rebuild and the NAS removes drive 3 from the array. Is there any thing that i am doing wrong? I am going to test out the current failed HD to see if show any errors now. I created a support case and QNAP reviewed the logs I sent and they confirmed read write errors but with this many drives?
Thanks Bob

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 3:29 am
by MrVideo
You need to search the forum. You also need to list your software version and build date.

There was an issue with disks 3/4 being "unplugged" from the NAS. A later version of software fixed it.

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 7:03 am
by whoslistening
I'm on the most recent version and the problem still exists.

2017/09/01
4.3.3.0299

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 9:00 am
by MrVideo
Open a QNAP helpdesk support ticket and report it.

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 9:06 am
by whoslistening
If you look at my previous post, you'll see that I've already done that.

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 4:09 pm
by MrVideo
Oops, sorry. Right you are.

Another Unhappy QNAP User with Drive 3 WD red disk problems

Posted: Sun Sep 10, 2017 4:31 pm
by JWChris
I have a TS-669 Pro with WD 4 terrabyte disks and following a firmware update about a week ago have had a very similar issue. Drive 3 failed and I had to rebuild the RAID with the remaining 5 disks.
Disk 3 was initially just set to spare and pronounced healthy but having carried out a full scan on it it has failed that and has now been set to Abnormal.
I have ordered a replacement drive which has not yet arrived so haven't yet raised a log with QNAP but research on here is convincing me that the problem is probably with them and not with my drive.
I am also concerned about the loss of data/ data scrubbing issue reported elsewhere.
I was going to buy a new QNAP to give me a second back up and more resilience as my 669 Pro has been very reliable for several years but I am also now concerned about the reliability and response of QNAP. I am holding off on a new NAS purchase until I am sure what is going on but my faith in my TS 669 Pro has been lost.
I think QNAP will lose a lot of business if they don't sort out what is going on quickly and issue full information.

Re: Another Unhappy QNAP User with Drive 3 WD red disk problems

Posted: Sun Sep 10, 2017 5:09 pm
by CylonCenturion
JWChris wrote:I have a TS-669 Pro with WD 4 terrabyte disks and following a firmware update about a week ago have had a very similar issue. Drive 3 failed and I had to rebuild the RAID with the remaining 5 disks.
Disk 3 was initially just set to spare and pronounced healthy but having carried out a full scan on it it has failed that and has now been set to Abnormal.
I have ordered a replacement drive which has not yet arrived so haven't yet raised a log with QNAP but research on here is convincing me that the problem is probably with them and not with my drive.
I am also concerned about the loss of data/ data scrubbing issue reported elsewhere.
I was going to buy a new QNAP to give me a second back up and more resilience as my 669 Pro has been very reliable for several years but I am also now concerned about the reliability and response of QNAP. I am holding off on a new NAS purchase until I am sure what is going on but my faith in my TS 669 Pro has been lost.
I think QNAP will lose a lot of business if they don't sort out what is going on quickly and issue full information.


What drives are in use?

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 5:53 pm
by JWChris
Disks 1,2, 4, 5 & 6 running RAID5 with 52% of reduced storage capacity of 14.43 TB being used
Disk 3 marked as Abnormal

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Sun Sep 10, 2017 9:49 pm
by bomberman447
I have a TS-451 with 4x WD Red 5TB and drive one keeps doing this as well. Has happened about four times now starting in July. No SMART issues on the drive (Drive 1), plug back in, rebuild then a few weeks later it happens again. I have not been using it continuously though, only really on weekends just to check for issues.

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Mon Sep 11, 2017 8:35 am
by MrVideo
JWChris wrote:Disks 1,2, 4, 5 & 6 running RAID5 with 52% of reduced storage capacity of 14.43 TB being used
Disk 3 marked as Abnormal

Software version and build date? Model of the HDDs? With 5, or more, disks in a RAID, you should be using RAID6, not RAID5.

I hope you have been doing backups.

Re: "Disk Failed", then "Disk Unplugged" errors

Posted: Mon Sep 11, 2017 8:47 am
by MrVideo
bomberman447 wrote:I have a TS-451 with 4x WD Red 5TB and drive one keeps doing this as well. Has happened about four times now starting in July. No SMART issues on the drive (Drive 1), plug back in, rebuild then a few weeks later it happens again. I have not been using it continuously though, only really on weekends just to check for issues.

Software version and build date?

This issue has been hitting some model's drives 3 & 4. You are not fitting the pattern, as it is drive 1.

Open a QNAP helpdesk support ticket.