NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Limerick_fr
Aug 28, 2020Guide
CIFS needs to be restarted or ReadyNAS needs to be rebooted
Hi all, For many months now, I have been using SyncBackPro to backup files (mirroring) from computer to my ReadyNAS Ultra 2 with no issues. Since few days, without any change anywhere, automa...
Limerick_fr
Aug 28, 2020Guide
Ok, thanks Sandshark for the info.
So upgrading to OS6 means starting from scratch again... Even to rebuild the Raid 1 again I believe.
As I am not a super geek and I did this setup few years back (and lost a bit of brain cells and memory in the meantime), I will propbably postponed this upgrade, at least until I solve this CIFS daily issue.
bedlam1
Aug 28, 2020Prodigy
- Limerick_frAug 28, 2020Guide
Thank you bedlam1.
I had found this tuto form StephenB, but the links to the files are dead... especially PREPR4TOR6_0.1-x86.bin
And 4 years after this thread, I believe I should use ReadyNASOS-6.10.3-x86_64.img instead of R4toR6_6.9.3.bin?
Perhaps will I go for that upgrade but not before I fix this CIFS issue (or if it is part of the solution...)
- StephenBAug 28, 2020Guru - Experienced User
Limerick_fr wrote:
Thank you bedlam1.
I had found this tuto form StephenB, but the links to the files are dead... especially PREPR4TOR6_0.1-x86.bin
I can send you the instructions later on (with working links).
But the main thing right now is to get the NAS running again.
- Limerick_frAug 29, 2020Guide
StephenB wrote:But the main thing right now is to get the NAS running again.
Yes absolutely.
Well it's running, but the CIFS doesn't work anymore after a nightly shutdown and daily startup. Like this morning for example. I sometimes have to turn CIFS OFF then ON. But not this morning... :smileysurprised:
This morning I symply had to run the process again and it worked...
Very weird...
However as you advised yesterday, I dropped the log.zip to Mark. Standing by for his feedback.
And for the upgrade to OS6, I think I have found everything here, from you StephenB. Thanks !
- StephenBAug 29, 2020Guru - Experienced User
If you don't have a backup of the NAS, then I suggest making a backup of the NAS while you are waiting.
One thing I now suggest for people converting their 4.2.x systems is increasing the RAM. Some folks have run into out-of-memory issues post-conversion, as the memory requirements have crept up some over the years.
You can upgrade your Ultra 2 to 2 GB (it has one memory slot). That will match the memory in the OS-6 equivalent (the RN312). The Crucial CT25664BC1067 and the Kingston KVR1333D3S8S9 modules are both reported as working by other forum members, and both are inexpensive. You can do this upgrade either before or after conversion. I'd do it first myself (but after your CIFS problem is resolved, as upgrading the RAM likely will result in Netgear denying support).
Also, if you want to ensure your bios is up-to-date, it is easier to update it before you convert. The latest BIOS for the Ultra 2 is from the 2nd of November 2011. You can see the bios version looking at bios_ver.log in your log zip. If you want to update it (OS-6 conversion doesn't require it), you install http://www.readynas.com/download/addons/x86/4.2/BIOS_Update_Package_0.5-x86.bin as an add-on.
- Limerick_frAug 30, 2020Guide
Thank you again StephenB for all these valuable information.
I will follow each of your advices as soon as I have the feedback from Mark regarding the logs.
I am afraid he might not see a lot because I discovered yesterday that it seems to be a random issue, despite it has been the same behaviour for the last 2 or 3 weeks.
Standing by then for the moment.
- Limerick_frSep 07, 2020Guide
Hi StephenB,
So, I followed your advice!
1- Made a full backup on attached USB3 drive. Took almost one full day for only 300Gb! (From few Kb/s to a maximum 5Mb/s)
2- Upgraded the RAM to 2Gb with the Crucial CT25664BC1067
3- Updated the BIOS (from v1.4 to v1.8) with BIOS_Update_Package_0.5-x86.bin as an add-on
4- Installed PREP4TOR6_0.1-x86. bin as an add-on
5- Upgraded the OS to R4toR6_6.9.5.bin with the GUI upgrade feature
6- Updated the OS to ReadyNASOS-6.10.3-x86_64 using the automatic upgrade feature.
Everything went well and I am happy to discover a 21st century GUI... :D
A bit surprise however to see how long it will take to Sync: about 60 hours for a 1Tb RAID1! Don't remember that it was so long when I initially confirgured it 6 or 7 years ago.
I wonder if I have to wait until it is finished before putting the data back in place in the share folders...
Something I can't manage to do is to have a successful test for the outgoing email using Gmail.
I used the default setup which is said to be OK and also tried with 587 as smtp server with TLS enabled. No joy.
It was the same with OS4.
Regarding the initial issue with CIFS, I haven't received any feedback from Marc for the logs, however, I told him that after 2 or 3 weeks with this problem, evrything went back to normal without changing anything...
Thank you for your valuable input to upgrade to OS6 !
Lim.
- Limerick_frSep 07, 2020Guide
EDIT previous message: I have found the solution regarding the Alert emails => allow less secure apps in google
- StephenBSep 07, 2020Guru - Experienced User
I'm glad it worked out.
Limerick_fr wrote:
A bit surprise however to see how long it will take to Sync: about 60 hours for a 1Tb RAID1! Don't remember that it was so long when I initially confirgured it 6 or 7 years ago.
I wonder if I have to wait until it is finished before putting the data back in place in the share folders...
It shouldn't be taking that long. You might want to download the log zip file, and look at the smart stats in disk_info.log. Though the estimates aren't always correct.
You can use the NAS during sync, but it will slow things down.
- Limerick_frSep 07, 2020Guide
It seems that I am not allowed to post anymore.
I have been trying to answer StephenB at least 10 times, including the log he mentionned as a code, and despite my post is displayed in the thread as 18 of 18 (before the current 18, of course :smileywink:), it is removed as soon as I go back to the forum...:smileyfrustrated:
Don't know what's going on. Never had this in any other forums I have been using. Could it be because I copy the log report in code </> ???
EDIT: this post is accepted. Why my previous is being displayed at first in that current thread then deleted once I am back in the forrum ???
A try to copy the log report below:
Device: sda Controller: 0 Channel: 0 Model: WDC WD10EZRX-00A8LB0 Serial: WD-WMC1U6975282 Firmware: 01.01A01W Class: SATA Sectors: 1953525168 Pool: data PoolType: RAID 1 PoolState: 1 PoolHostId: 5e24a8c0 Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 34 Start/Stop Count: 19726 Power-On Hours: 45374 Power Cycle Count: 2810 Load Cycle Count: 219847 Device: sdb Controller: 0 Channel: 1 Model: WDC WD10EZRX-00A8LB0 Serial: WD-WMC1U6973907 Firmware: 01.01A01W Class: SATA Sectors: 1953525168 Pool: data PoolType: RAID 1 PoolState: 1 PoolHostId: 5e24a8c0 Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 32 Start/Stop Count: 19731 Power-On Hours: 45374 Power Cycle Count: 2810 Load Cycle Count: 219886
- StephenBSep 07, 2020Guru - Experienced User
Limerick_fr wrote:
Never had this in any other forums I have been using. Could it be because I copy the log report in code </> ???
EDIT: this post is accepted. Why my previous is being displayed at first in that current thread then deleted once I am back in the forrum ???
Likely something in the post triggered the spam filter.
Limerick_fr wrote:
A try to copy the log report below:
Device: sda Controller: 0 Channel: 0 Model: WDC WD10EZRX-00A8LB0 Serial: WD-WMC1U6975282 Firmware: 01.01A01W Class: SATA Sectors: 1953525168 Pool: data PoolType: RAID 1 PoolState: 1 PoolHostId: 5e24a8c0 Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 34 Start/Stop Count: 19726 Power-On Hours: 45374 Power Cycle Count: 2810 Load Cycle Count: 219847 Device: sdb Controller: 0 Channel: 1 Model: WDC WD10EZRX-00A8LB0 Serial: WD-WMC1U6973907 Firmware: 01.01A01W Class: SATA Sectors: 1953525168 Pool: data PoolType: RAID 1 PoolState: 1 PoolHostId: 5e24a8c0 Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 32 Start/Stop Count: 19731 Power-On Hours: 45374 Power Cycle Count: 2810 Load Cycle Count: 219886
The disks look healthy. Is the sync still going slowly?
- SandsharkSep 08, 2020Sensei - Experienced User
I have seen cases where drive caching is turned off during sync. Another user reported it here, and I observed it during an experiment (for something else). I have no idea why, and it seems to uniquely happen for RAID1.
From SSH you can use hdparm -i /dev/sda and hdparm -i /dev/sdb and see if you see DriveCache=enabled. If it's not, there are some warnings about turning it on "on the fly", but the other user and I did so successfully. Use hdparm -W /dev/sda and hdparm -W /dev/sdb.
- Limerick_frSep 08, 2020Guide
Thank you Sandshark for your help but I will have to make some search as I am not used to SSH and don't how to use it.
In the mean time here is where I am with syncing. The good thing is that I am over 50% now :smileyvery-happy:
- SandsharkSep 08, 2020Sensei - Experienced User
Sometimes the original estimate is wrong and it shortens as the process progresses. Hopefully, that's the case with yours.
- Limerick_frSep 08, 2020Guide
Sandshark wrote:Sometimes the original estimate is wrong and it shortens as the process progresses. Hopefully, that's the case with yours.
Well in fact I started the Syncing yesteray morning. So we are at a bit of over 30 hours non stop running.
Yes it is a bit unreliable as it has just decrease to 28 hours remaining...
- Limerick_frSep 09, 2020Guide
Hi All,
So a little wrap up to conclude this thread.
No more CIFS problem, even before upgrading to OS6. Strange issue during 3 weeks that disappeared by itself.
Very nice idea to upgrade to OS6 with increasing the RAM from 1 to 2Gb.
Syncing estimation is finally quite reliable. 60 hours estimated, started on Monday 8am, finished on Wednesday 6pm : 58 hours.
I did not use SSH as I was not sure of how to proceed. It was just a matter of patience letting the NAS running 24H a day.
Also backing up and restoring data was very long: over 24 hours for 300GB, each way...
But everything seems to run nicely now and very happy of the move.
Best to all,
Lim.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!