1. I received an audible warning and the logs showed:
Log Entry: [Disk] There is a data transfer error on sector xxx of the slot 2 disk!
2. In addition the Storage Manager flagged the disk with a "red X" and the mouse over text "Deployment: Volume 1 (Data Transmission Error)
3. I ran the SMART Scan on the disk and it reported:
No error found (date time)
Log Entry: S.M.A.R.T quick scanning of Disk 2 result: completed without error.
4. I ran the Bad Block Scan and it reported:
No bad blocks found (date time)
Log Entry: [Disk Doctor] Badblock scanning of Disk 2 completed, 0 bad blocks found. (0/0/0 errors)
----
The scanning tools indicate the disk is working fine. However, the disk is still flagged with a "red X" and the buzzer still goes off with "Warning" enabled.
How do I clear the the disk back to NORMAL?
ASUSTOR - Data Transmission Error / Data transfer error on sector ...
-
- Posts: 6
- youtube meble na wymiar Warszawa
- Joined: Wed Apr 28, 2021 7:31 am
-
- Posts: 396
- Joined: Thu Apr 09, 2020 8:01 pm
Re: ASUSTOR - Data Transmission Error / Data transfer error on sector ...
Tried turning the NAS off, reseating the drives, and restarting?
-
- Posts: 6
- Joined: Wed Apr 28, 2021 7:31 am
Re: ASUSTOR - Data Transmission Error / Data transfer error on sector ...
> "Have you tried turning it off and on again?"
Lamest fix, but restarting did remove the warning.
Lamest fix, but restarting did remove the warning.
-
- Posts: 396
- Joined: Thu Apr 09, 2020 8:01 pm
Re: ASUSTOR - Data Transmission Error / Data transfer error on sector ...
If it works, it works.
-
- Posts: 4
- Joined: Mon Sep 02, 2019 9:41 pm
Re: ASUSTOR - Data Transmission Error / Data transfer error on sector ...
Replying to this old thread to validate that I had the same issue described above, Data Transmission Error detected on one of the drives in my array on Asustor AS5304T. The Array itself did not show degraded. I ran both a SMART scan and Disk Doctor, and found zero bad sectors. I could find no way of clearing out this error in the running NAS OS. The fix described in this thread of simply rebooting or shutting down and restarting the NAS, successfully cleared the error. I did not have to remove the affected drive from the tray or rebuild the array.