NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Detected increasing command timeouts errors
1. Have a ReadyNAS 316 that I have been running for many years without any odd ball issues. Recently I swapped out a 4TB Seagate HDD for a 12TB Seagate HDD. After a few weeks, it started generating "...
Marc_V wrote:
If the issue still persist, it would be good to turn to check to turn off the NAS, remove the drives and label them accordingly and insert a spare disk on the slot where the 12TB is located. It will initiate a setup using the spare disk, once done we'll be able to check if it will give the same error and the NAS might need a hardware check.
A related test is to turn off the NAS, and switch the slots of the 8 TB drive and the 12 TB drive. Then reboot and see if the problem moves.
It would also be useful to download the full log zip file, and look for disk / btrfs errors in system.log and kernel.log. It is possible that errors with other disks might be triggering the command timeouts. Also look in disk_info.log, as there could be other SMART errors that aren't generating alerts.
Marc_V wrote:
... or by plugging in the 12TB drive on your PC and run Seatools ...
I'd suggest Seatools for this (connecting with either USB or SATA). If there is an issue with the RMA'd disk, it will be simpler to exchange it again if you have a Seatools failure code.
FWIW, Acronis Drive Monitor won't actually test the disk. It will look at the SMART stats (which can be handy), but that's all it does.
Mark_V, A new 12TB drive gave me the original "increasing command timeouts errors". All other drives have been running well for some time, no errors from the system or SMART error counts. Then on RMA 12TB HDD that I received and inserted (returning the original 12TB drive) ...after a few weeks....the RMA replacement 12TB drive started reporting the "increasing command timeouts errors" just like the original NEW HDD. I will downloand the full logds tomorrow and review. To me at first pass it seems like a 12TB drive NAS OS cache flush handling issue.
Checked the system.log and kernel.log for any btrfs errors. Nil reported. System log make no references. Kernel log has btrfs log entries, but none reporting with "error".
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
