NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Readynas 422, Firmware 6.10.2, Deleted its self from Ready Cloud
Hi, Readynas 422 Firmware 6.10.2 6 Users (default local admin account) 5 cloud created users used to log in to the server localy for onsite PC's and remotely for Ready cloud access on personal...
Your log shows the drive had to go through re-sync because the NAS dropped it from the array. Re-sync has been known to take too much CPU time and cause problems with ongoing processes, including the main NAS process readynasd, though I really would not expect that on a series 400 unit. But if something did interfere with the ReadyCloud process or another critical one, there is no telling what the fallout might be.
Hi John,
Thanks for the reply.
The odd thing is this, The NAS has been connected to both ReadyCloud and onedrive for over a year and working fine with no issues at all.
When I checked it following the faliure, it was still shown online and conected to onedrive, it was just the readycloud feature which had turned itself off.
Ive put the disk log from the other day below, the second disk does look a little unhealthy considering they were both installed new at the same time!
I think its a WD drive from memory so Ill get a replacmenet on order for it. The question is though, why a failing disk would cause it to disconect from ready cloud. It was not an internet conectivity issue, the NAS just completly removed itself to the point where the account the NAS was assigned to still existed, but when I logged in remotely initialy it didnt show as offline but instead showed the account as not having any devices linked to it.
Would you agree the second drive looks like it needs replacing as below?
Thanks for your responce.
-------------------------------------------------
Device: sdb
Controller: 0
Channel: 0
Model: TOSHIBA HDWD120
Firmware: MX4OACF0T
Class: SATA
RPM: 7200
Sectors: 3907029168
Pool: data
PoolType: RAID 1
PoolState: 1
PoolHostId: a451c72
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 14
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 35
Start/Stop Count: 17
Power-On Hours: 5042
Power Cycle Count: 16
Load Cycle Count: 46
-------------------------------------------------
Device: sda
Controller: 0
Channel: 1
Model: TOSHIBA HDWD120
Firmware: MX4OACF0T
Class: SATA
RPM: 7200
Sectors: 3907029168
Pool: data
PoolType: RAID 1
PoolState: 1
PoolHostId: a451c72
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 1048577
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 36
Start/Stop Count: 22
Power-On Hours: 5042
Power Cycle Count: 17
Load Cycle Count: 53
Your log shows the drive had to go through re-sync because the NAS dropped it from the array. Re-sync has been known to take too much CPU time and cause problems with ongoing processes, including the main NAS process readynasd, though I really would not expect that on a series 400 unit. But if something did interfere with the ReadyCloud process or another critical one, there is no telling what the fallout might be.
Are any of the drives SMR drives? I had a nearly total lock-up on my NAS during a scrub, which includes a re-sync, after I swapped a drive for one of the newer SMR WD reds. Several processes had "backed up", being unable to get access to the drives. I had no other fall-out, but I noticed in time and paused the scrub long enough for the backed up processes to complete. Otherwise, I shutter to think what might have happened. I have backup, but the restoration process would not be fun.
Sandshark wrote:
Are any of the drives SMR drives?
The HDWD120 is also known as the P300, and Toshiba recently disclosed that it is an SMR drive.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
