NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Problem with access via CIFS, NFS works fine
Hello
perhaps someone is so kind to help me with a problem which really makes me mad: I've got a ReadyNAS Ultra 2, some weeks ago I resetted the Ultra to factory default while installing 2 2TB HDs. I formatted the as Raid 0 to get really fast 4 Tb ... (not recommended, but my decision). Everything worked out fine, I filled half of the space with Videos, I accessed all of the files via CIFS from PCs (Windows 7, Windows XP, Windows Vista, 2 Netgear EVA - 8000 and 9150) here in the LAN, some Linux-Machines got access via NFS to that folder too. The Ultra goes down every night at 1 am, and comes up agein at 4:30 am.
This morning suddenly the media-share on my windows machine was absolutely empty though the Web-UI tells me still 53% of diskspace are being used. Checking out what happened no PC got any files or dirs via CIFS. But I'm a little glad to see all my files via NFS, so I could get them back to my local machines or servers, but when I do so, I will return the Ultra and replace it with a cheap 2-disk-usb-box and make a share on a fileserver. This would not be elegant but it would work, not only today but also tomorrow. The elegant way would be to get the Ultra running again via CIFS...
Thanks in advance
loddar61
perhaps someone is so kind to help me with a problem which really makes me mad: I've got a ReadyNAS Ultra 2, some weeks ago I resetted the Ultra to factory default while installing 2 2TB HDs. I formatted the as Raid 0 to get really fast 4 Tb ... (not recommended, but my decision). Everything worked out fine, I filled half of the space with Videos, I accessed all of the files via CIFS from PCs (Windows 7, Windows XP, Windows Vista, 2 Netgear EVA - 8000 and 9150) here in the LAN, some Linux-Machines got access via NFS to that folder too. The Ultra goes down every night at 1 am, and comes up agein at 4:30 am.
This morning suddenly the media-share on my windows machine was absolutely empty though the Web-UI tells me still 53% of diskspace are being used. Checking out what happened no PC got any files or dirs via CIFS. But I'm a little glad to see all my files via NFS, so I could get them back to my local machines or servers, but when I do so, I will return the Ultra and replace it with a cheap 2-disk-usb-box and make a share on a fileserver. This would not be elegant but it would work, not only today but also tomorrow. The elegant way would be to get the Ultra running again via CIFS...
Thanks in advance
loddar61
14 Replies
Replies have been turned off for this discussion
- Running 4.1.19? Sounds like you've hit a CIFS configuration issue many have reported that should be fixed in 4.2.20
Check the beta forum for a beta release of 4.2.20 - Thanks for the quick answer. I gave 4.2.20-T4 a try, but it didn't change the behavior. I guess I should copy my data as fast as the NAS can deliver it ...
- I strongly suspect the issue is the one I described - in which case, no your data is not at risk, the problem is that the CIFS server has an incorrect parameter - a bug Netgear introduced in 4.2.19. (Though a complete backup is *always* to be recommended)
You can verify if this truly is the the issue by performing a "Config Backup" (Frontview >> System >> Config Backup). This will generate a zip file with all of the data related to your setup, one of the files being called "Shares.conf". In that file you should check for a share called "media" being configured to access "/c/media" as follows:[media]
path = /c/media
comment = "Media Server Share"
If your path is not set to "/c/media" then my diagnosis is correct.
A common workaround to correct this is to rename your media share in Frontview, and then rename it back to "media" - this typically corrects the the config file, and 4.2.20 should prevent the fault happening again.
FYI: The NFS setup is separate to CIFS and so unaffected by this issue which is why you can access the data over NFS - Here is what I found ...
[media]
comment = "Media Server Share"
path = "/c/media"
public = 1
writeable = 1
oplocks = 1
admin users = "admin","Administrator"
force create mode = 0666
create mask = 0666
force directory mode = 0777
directory mask = 0777
perhaps the biggest issue is the entry "admin users" - that I don't know from my own smb.conf
Thanks very much for your help (in the meantime 3 machines are copying my data ...) - Then it appears I was completely wrong - the path is clearly correct. In which case I would recommend you contact tech support
The admin users configuration is correct - the built-in admin user always has full access to all shares - Thank you very much for your patient help.
I have had a readyNAS replaced by the support 2 weeks ago, the old one had a hardware problem (no boot at all). When putting in my hd I lost all the data on it (1 TB of videos and music, all my DVDs and CDs ...). So I'm warned and back up the data _before_ I contact support. I guess they will advice me to set the box to factory default ... loddar61 wrote: When putting in my hd I lost all the data on it (1 TB of videos and music, all my DVDs and CDs ...)
You are aware that is by design and not a fault? And how other non-ReadyNAS devices work also? Inserting a disk adds that disk to the RAID array and so must delete any content on the disk- probably it was my fault - thats true. But I thought, that putting a ReadyNAS-formatted disk into a new box would show up my old configuration - and I was wrong. Anyway the data were lost, which was frustrating because of having spent so much time and processing power in ripping my CDs into flac and my DVDs into mkv. So I won't make the same mistake again :)
btw. I renamed media into media1 and can access my files again. renaming the share back to media made them disappear again... perhaps I just should change all the shares on the clients here and everything is good ... - If renaming the share solves the issue - then it would appear that maybe I was not so far off the mark.
If you are content to rename the share, then that would seem to be a good workaround - but you may still wish to log a tech support case as perhaps 4.2.20 has not fully fixed the issue as hoped and Netgear need to know thatI thought, that putting a ReadyNAS-formatted disk into a new box would show up my old configuration
Depends how you do it. If you hot-add, then your disk will *always* be wiped as this is the action to replace a disk, typically after a failure. Cold-add with no other disk installed and you should see your old configuration & data sphardy wrote: If renaming the share solves the issue - then it would appear that maybe I was not so far off the mark.
If you are content to rename the share, then that would seem to be a good workaround - but you may still wish to log a tech support case as perhaps 4.2.20 has not fully fixed the issue as hoped and Netgear need to know that
I will do so - that firmware has beta status, and i will try to give netgear everything, they need to know about that issue, whatever it is.sphardy wrote: Depends how you do it. If you hot-add, then your disk will *always* be wiped as this is the action to replace a disk, typically after a failure. Cold-add with no other disk installed and you should see your old configuration & data
I added it cold, but I tried before to mount the hd on a linux machine, perhaps I did it the wrong way and destroyed the partition table myself. Today I just know, something went wrong which was not too funny for me, and I will act with more caution in future :)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
