Hi,Readynas 422Firmware 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 devices via windows ready cloud app). 6 Shares one each only they access an one shared they all access.The shares are created localy, not via ready cloud (luckily!) been working perfectly for over a year, got a call friday morning to say it had stopped working and they could access anything.Looked on ready cloud and it said no device asigned to account, so I visited site and loged onlocaly as admin to find ready cloud had switched it self off. in doing so, it had deleted all the cloud users. so when I switched it back on I then had to manualy re add the accounts and set there permisions again. The only logical answer in my head would have been someone to guess the admin password and create the havoc, but the time it happened in the monring no one was onsite, I am the only person who knows the password which I created and a reset isnt an option as it emails my corporate wmail which they dont hav access to. I also note a worying disk notification for drive 2 which has neevr appeared before and not since, and both drives show as healthy. Ive downlaoded full logs but of note was as follows (Appologies its in reverse order) Id really apreciate some feedback or sugestions on what it could be! Thanks Sep 19, 2020 00:00:11 Snapshot: Snapshot c_1600470007 was successfully created for share or LUN shared.Sep 19, 2020 00:00:11 Snapshot: Snapshot c_1600470007 was successfully created for share or LUN salesadmin.Sep 19, 2020 00:00:11 Snapshot: Snapshot c_1600470007 was successfully created for share or LUN Quality_Assurance_Shared.Sep 19, 2020 00:00:10 Snapshot: Snapshot c_1600470007 was successfully created for share or LUN production_manager.Sep 19, 2020 00:00:09 Snapshot: Snapshot c_1600470007 was successfully created for share or LUN Removedforweb.Sep 19, 2020 00:00:09 Snapshot: Snapshot c_1600470007 was successfully created for share or LUN Removedforweb.Sep 19, 2020 00:00:07 Snapshot: Snapshot c_1600470007 was successfully created for share or LUN accounts.Sep 18, 2020 12:28:59 Disk: Disk in channel 2 (Internal) changed state from RESYNC to ONLINE.Sep 18, 2020 12:28:59 Volume: Volume data health changed from Degraded to Redundant.Sep 18, 2020 12:28:59 Volume: Volume data is resynced.Sep 18, 2020 08:14:16 System: Antivirus scanner definition file was updated to 59.25931.Sep 18, 2020 07:54:52 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:51 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:50 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:48 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:47 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:46 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:45 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:44 Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.Sep 18, 2020 07:54:03 Volume: Resyncing started for Volume data.Sep 18, 2020 07:53:52 System: ReadyNASOS background service started. Sep 18, 2020 07:53:52 Disk: Detected high spin retry count: [1048577] on disk 2 (Internal) [TOSHIBA HDWD120, 78GKEE6CS]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy.Sep 18, 2020 07:53:51 Volume: Volume data is Degraded.Sep 18, 2020 07:53:49 System: ReadyNASOS service or process was restarted.Sep 18, 2020 06:59:33 System: ReadyNASOS background service started.Sep 18, 2020 06:59:32 Volume: Volume data is Degraded.Sep 18, 2020 06:59:30 System: ReadyNASOS service or process was restarted.Sep 18, 2020 06:47:46 Volume: Resyncing started for Volume data.Sep 18, 2020 06:47:37 System: ReadyNASOS background service started.Sep 18, 2020 06:47:35 Volume: Volume data is Degraded.Sep 18, 2020 06:47:33 System: ReadyNASOS service or process was restarted.Sep 18, 2020 06:44:30 Volume: Volume data is Degraded.Sep 18, 2020 06:44:28 System: ReadyNASOS service or process was restarted.Sep 18, 2020 06:41:02 Volume: Volume data is Degraded.Sep 18, 2020 06:41:00 System: ReadyNASOS service or process was restarted.Sep 18, 2020 06:39:07 Volume: Volume data is Degraded.Sep 18, 2020 06:39:05 System: ReadyNASOS service or process was restarted.

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.

Forum Discussion

Peajonathanca14

Aspirant

Sep 20, 2020

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 devices via windows ready cloud app).

6 Shares one each only they access an one shared they all access.

The shares are created localy, not via ready cloud (luckily!)

been working perfectly for over a year, got a call friday morning to say it had stopped working and they could access anything.

Looked on ready cloud and it said no device asigned to account, so I visited site and loged onlocaly as admin to find ready cloud had switched it self off. in doing so, it had deleted all the cloud users. so when I switched it back on I then had to manualy re add the accounts and set there permisions again.

The only logical answer in my head would have been someone to guess the admin password and create the havoc, but the time it happened in the monring no one was onsite, I am the only person who knows the password which I created and a reset isnt an option as it emails my corporate wmail which they dont hav access to. I also note a worying disk notification for drive 2 which has neevr appeared before and not since, and both drives show as healthy.

Ive downlaoded full logs but of note was as follows (Appologies its in reverse order)

Id really apreciate some feedback or sugestions on what it could be!

Thanks

Sep 19, 2020 00:00:11		Snapshot: Snapshot c_1600470007 was successfully created for share or LUN shared.
Sep 19, 2020 00:00:11		Snapshot: Snapshot c_1600470007 was successfully created for share or LUN salesadmin.
Sep 19, 2020 00:00:11		Snapshot: Snapshot c_1600470007 was successfully created for share or LUN Quality_Assurance_Shared.
Sep 19, 2020 00:00:10		Snapshot: Snapshot c_1600470007 was successfully created for share or LUN production_manager.
Sep 19, 2020 00:00:09		Snapshot: Snapshot c_1600470007 was successfully created for share or LUN Removedforweb.
Sep 19, 2020 00:00:09		Snapshot: Snapshot c_1600470007 was successfully created for share or LUN Removedforweb.
Sep 19, 2020 00:00:07		Snapshot: Snapshot c_1600470007 was successfully created for share or LUN accounts.
Sep 18, 2020 12:28:59		Disk: Disk in channel 2 (Internal) changed state from RESYNC to ONLINE.
Sep 18, 2020 12:28:59		Volume: Volume data health changed from Degraded to Redundant.
Sep 18, 2020 12:28:59		Volume: Volume data is resynced.
Sep 18, 2020 08:14:16		System: Antivirus scanner definition file was updated to 59.25931.
Sep 18, 2020 07:54:52		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:51		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:50		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:48		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:47		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:46		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:45		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:44		Account: User 'USER ID REMOVED FOR WEB PUBLISHING' was deleted.
Sep 18, 2020 07:54:03		Volume: Resyncing started for Volume data.
Sep 18, 2020 07:53:52		System: ReadyNASOS background service started.

Sep 18, 2020 07:53:52		Disk: Detected high spin retry count: [1048577] on disk 2 (Internal) [TOSHIBA HDWD120, 78GKEE6CS]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy.
Sep 18, 2020 07:53:51		Volume: Volume data is Degraded.
Sep 18, 2020 07:53:49		System: ReadyNASOS service or process was restarted.
Sep 18, 2020 06:59:33		System: ReadyNASOS background service started.
Sep 18, 2020 06:59:32		Volume: Volume data is Degraded.
Sep 18, 2020 06:59:30		System: ReadyNASOS service or process was restarted.
Sep 18, 2020 06:47:46		Volume: Resyncing started for Volume data.
Sep 18, 2020 06:47:37		System: ReadyNASOS background service started.
Sep 18, 2020 06:47:35		Volume: Volume data is Degraded.
Sep 18, 2020 06:47:33		System: ReadyNASOS service or process was restarted.
Sep 18, 2020 06:44:30		Volume: Volume data is Degraded.
Sep 18, 2020 06:44:28		System: ReadyNASOS service or process was restarted.
Sep 18, 2020 06:41:02		Volume: Volume data is Degraded.
Sep 18, 2020 06:41:00		System: ReadyNASOS service or process was restarted.
Sep 18, 2020 06:39:07		Volume: Volume data is Degraded.
Sep 18, 2020 06:39:05		System: ReadyNASOS service or process was restarted.

Sandshark
Sep 22, 2020
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.

6 Replies

Replies have been turned off for this discussion

Sandshark
Sensei - Experienced User
Sep 22, 2020
It appears it's related to the problems with Drive 2, though I don't know exactly why. Perhaps the re-sync was tying up to many assets and made ReadyCloud fail in some way. I would certainly not let those errors on Drive 2 continue to grow.
JohnCM_S
NETGEAR Employee Retired
Sep 22, 2020
Hi Peajonathanca14,

Were you able to check if there is green check mark on both Internet and Service when NAS gets disconnected from ReadyCLOUD?

It will be best to check the health of disk 2 since you already received a warning for impending disk failure You may check disk_info.log.

Regards,
- Peajonathanca14
  Aspirant
  Sep 22, 2020
  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
  - Sandshark
    Sensei - Experienced User
    Sep 22, 2020
    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.