NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
System: ReadyNASOS service or process was restarted.
Morning all, Model: ReadyNAS 3138 OS: Firmware 6.10.4 Hotfix 1 Problem: Dreaded System: ReadyNASOS service or process was restarted. error (similiar error messages to https://community.netgear.c...
duhden wrote:
- my gut tell me that it is something misconfigured with mdadmin (x-raid) as I know that it requires a restart to begin the expansion
Normally it doesn't require a restart to begin expansion.
I'd look in the logs for disk-related errors. Or just test the drives in a Windows PC with vendor tools (seatools for seagate; lifeguard for western digital). Personally I do test my drives before I put them into the NAS - first running the long non-destructive test, and then the ful erase/write zeros test.
I'm not too sure where my rather lenghty reply from Sunday disappeared too. It was here, but now I don't see any additional replies to the thread...
I'd look in the logs for disk-related errors. Or just test the drives in a Windows PC with vendor tools (seatools for seagate; lifeguard for western digital). Personally I do test my drives before I put them into the NAS - first running the long non-destructive test, and then the ful erase/write zeros test.
So, over the weekend I took the time to run the "Long Generic" test run on all four of the new 12 TB drives. They all passed. I think we can rule out hardware
I've started rebuilding the NAS from scratch (again)
- Factory reset with just one old 300 GB drive (it complained about no redundancy)
- Added first 12 TB drive - Flex Raid mirrored the 300 GB as expected, leaving the rest of the 11.5 TB as orphaned
- Once mirror completed, pulled original 300 GB and added second tested 12TB drive. It complained about redunancy until the 300 GB was mirrored. It then expanded, to a mirror or 12 TB and synced that. It just finished. Everything so far is as expected as I now have a 12TB mirrored (raid 1) volume.
I'm still feeling that there is something (some type of cron job?) related to expansion that is causing the OS to restart.
I'm also still confused as to why the NAS was trying to resilver a mirror (a term I had to look up) when I completed the initial factory reset with four identical 12 TB drives. There shouldn't have been any mirror activities - just raid 5.
Any other suggesions of config files to review or tasks to run would be mos welcomed.
Doug
"Just RAID5" isn't "mirror" exactly, but it does have redundancy that requires a RAID sync (aka, re-silver), even if all the drives are empty. In other words, the NAS was doing exactly what it was supposed to do after the factory default. The NAS will give you access to the volume before it completes that process so you can do more with it, including adding files, though that will slow down the sync. With 12TB drives, that sync will take a while.
But it won't take nearly as long as the process you are now needlessly doing adding one drive at a time and doing a re-sync with every addition that will take longer for each drive added. At this point, you can probably still do another factory default and wait for it to sync just the once in less time than to complete the process of adding drives individually.
Hi Sandshark - thanks for the reply
Sandshark wrote:But it won't take nearly as long as the process you are now needlessly doing adding one drive at a time and doing a re-sync with every addition that will take longer for each drive added. At this point, you can probably still do another factory default and wait for it to sync just the once in less time than to complete the process of adding drives individually.
Agreed 100% The first time that I did a factory reset, that is exactly what I did. I put all four new drives in, completed a factory reset, started copying files back as it resynced (which took the better part of the day) and then several hours after it finished I was back to the original issue of the OS restarting every X minutes.
Everything else aside, i need to find out why the OS is restarting making the NAS unusable!
duhden wrote:
Sandshark wrote:
But it won't take nearly as long as the process you are now needlessly doing adding one drive at a time and doing a re-sync with every addition that will take longer for each drive added. At this point, you can probably still do another factory default and wait for it to sync just the once in less time than to complete the process of adding drives individually.
Agreed 100% The first time that I did a factory reset, that is exactly what I did. I put all four new drives in, completed a factory reset, started copying files back as it resynced (which took the better part of the day) and then several hours after it finished I was back to the original issue of the OS restarting every X minutes.
Everything else aside, i need to find out why the OS is restarting making the NAS unusable!
FWIW, I have had disks pass the long generic test, but fail the full erase test. So I always run them both before I use disks in the NAS.
One avenue that might be more flexible is to switch to flexraid and create 4 jbod volumes. That won't require any resyncs. If the restarts still occur, then you can can remove one disk (destroying the volume) and see if the problem disappears. Then re-insert and move onto the next. If they don't, then try the factory default again, and see if you get the same result as before.
I'm wondering if your system is effected by the C2000 CPU flaw - if so the timing might be coincidental. Did Netgear ever reach out to you about that? https://kb.netgear.com/000037344/Service-Note-for-RN3130-RN3138-WC7500-and-WC7600v2
https://kb.netgear.com/000037344/Service-Note-for-RN3130-RN3138-WC7500-and-WC7600v2
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
