NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Backup NAS 2 USB HDD stops unforeseeable after 500 GB
Having bought a new usb hdd 5 TB a few months ago and set up this device as backup device for the NAS 516. The first full backup worked fine. During the last weeks the nas run incremental backups da...
Having checked the whole setup including format and cable I could identify a malfunction of the power adapter of the hdd which caused the backup errors.
There has been a loose contact in the 12 volt power adapter. I changed the adapter and the backup run properly and ended succesful without interruption.
Surprisingly the brand new power adapter was delivered with a malfunction.
Thank you to you all for your helpful and kind recomendations - I have learned a lot regarding doing backups properly.
No, haven't activated auto-eject. Haven't this activated in my other backup job either. For this job I am using the same model of usb hdd and it works fine.
I am using the same type of usb hdds for the two backup jobs: 5 TB WD Model WDBWLG0050HBK-EESN
I bought two of them, one last year, the recent hdd which causes the problems in February this year.
My understanding is - not 100 % sure - that the WD 5 TB Elements is NO SMR drive. Nothing mentioned re SMR neither in the invoice of the hdd nor on the packing. I have read that that SMR drives have to deal with massive reduction of data transfer rate during longer data transfer processes.
TT_DE wrote:
No, haven't activated auto-eject. Haven't this activated in my other backup job either. For this job I am using the same model of usb hdd and it works fine.
I understand that it works most of the time. But turn on auto-eject - your symptoms result from the "dirty" bit being set on the USB drive.
TT_DE wrote:
My understanding is - not 100 % sure - that the WD 5 TB Elements is NO SMR drive.
The reason I mentioned it is that SMR drives need to do a lot of post-processing when you write data (because when you write track X, it corrupts track X+1). That could be a contributing factor.
But I also believe that the WD elements is PMR.
StephenB wrote:
TT_DE wrote:No, haven't activated auto-eject. Haven't this activated in my other backup job either. For this job I am using the same model of usb hdd and it works fine.
I understand that it works most of the time. But turn on auto-eject - your symptoms result from the "dirty" bit being set on the USB drive.
Thx for the hint. Turning on auto eject means that I have to restart the NAS daily to reconnect the USB HDD ?
Otherwise I could not run incremental back up daily. could I?
But how could this "dirty bit" occur during a running backup? Backup starts properly and suddenly stops after having transferred more than 500 GB?
TT_DE wrote:My understanding is - not 100 % sure - that the WD 5 TB Elements is NO SMR drive.
The reason I mentioned it is that SMR drives need to do a lot of post-processing when you write data (because when you write track X, it corrupts track X+1). That could be a contributing factor.
But I also believe that the WD elements is PMR.
Thank You.Seems to be the identical issue like this one: https://community.netgear.com/t5/Backing-up-to-your-ReadyNAS/After-backup-Destination-is-read-only/m-p/960340#M10182
TT_DE wrote:
Thx for the hint. Turning on auto eject means that I have to restart the NAS daily to reconnect the USB HDD ?
Otherwise I could not run incremental back up daily. could I?
I was thinking that you were removing the drive after the backup was finished - is that correct?
If you are removing it, then your procedures don't change. If you are generally leaving it in place, then leave auto-eject off, but make sure you make you do eject it from the web ui before you remove the drive.
TT_DE wrote:
But how could this "dirty bit" occur during a running backup? Backup starts properly and suddenly stops after having transferred more than 500 GB?
The dirty bit is a consequence of removing the drive unexpectedly. The backup failure itself might be unrelated.
Though your response makes me wonder if the drive is being unexpectedly disconnected in the middle of the backup somehow. Is it possible that the USB cable or power connector is loose on the drive?
StephenB wrote:
TT_DE wrote:Thx for the hint. Turning on auto eject means that I have to restart the NAS daily to reconnect the USB HDD ?
Otherwise I could not run incremental back up daily. could I?
I was thinking that you were removing the drive after the backup was finished - is that correct?
If you are removing it, then your procedures don't change. If you are generally leaving it in place, then leave auto-eject off, but make sure you make you do eject it from the web ui before you remove the drive.
TT_DE wrote:
But how could this "dirty bit" occur during a running backup? Backup starts properly and suddenly stops after having transferred more than 500 GB?
The dirty bit is a consequence of removing the drive unexpectedly. The backup failure itself might be unrelated.
Though your response makes me wonder if the drive is being unexpectedly disconnected in the middle of the backup somehow. Is it possible that the USB cable or power connector is loose on the drive?
No - the USB HDD stays conected via the USB 3 port at the backside of the NAS device.
Yep, will leave auto-eject off and I am generally use the UI eject option.
No - I am not aware of any cable connection problem neither power mir data cable. Checked this as first when problem occured.
Seems to me that ther eis no plausible explanation yet what causes this problem.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
