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
- Please post a summary in the Beta forum: viewforum.php?f=51
Note I may still be wrong, but it sounds suspiciously like a related issue to that supposedly fixed in the beta. Maybe one of the mods can take a look at your setup to verify - I made a mistake: I looked onto /etc/samba/smb.conf and shares.conf - but I should have been looking at /etc/frontview ... so I posted the wrong configuration. I'm sorry about that, but by using samba for a long time as my favorite fileserver I had not made up my mind to look anywhere else. "webroot" and "media" were the same empty directory, but disabling webroot didn't help, and renaming of the share is the one thing that could help me out of my datalessness.
- You just confirmed the issue is the one I referred to - usually you can rename the share back to media and the config is fixed. Don't know why not in your case. Please log in the beta forum as 4.2.20 should fix that issue and clearly it has not
- Thanks a lot sphardy!
This was exactly the problem that happened to me after upgrading Squeezecenter to version 7.7.1.
Now everything is working again! :-)
Thanks again!
Best Regards
/Rillekillesphardy wrote: 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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
