- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Encountered issue with 6.9.2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Encountered issue with 6.9.2
Been using RN314 for over a year, It has been working fine until this update. Noted that users were having issues with shares previously mounted after a few days, or could not mount them again after reboot. I was using and Underscore in the Device Name "ReadyNas_314" and after the upgrade the network could not be found any more, it seems it shortened it to just "ReadyNas". When I tried to remove the underscore and shorten the name a few days later when we could no longer mount shares at all, it would change in the frontview but return to old name after reboot. I logged in using ssh and found the hostname was correct but the hosts file still had the old name with the underscore. When I tried to vi the hosts file, got message that there was no "swap" available so I could not save any changes.
I checked the message log and found that there were errors rotating the logs and said it was out of space, I could not find any mounted drives that were anywhere near even 50% full, but I deleted two of the log files to make space and rebooted the unit from the command line.
After a reboot it seemed that the naming issue was resolved and I could vi the hosts file and fix that minor error, but we still had problems connecting to the shares.
I had created several groups of users and we have used them to access shares that had the group name assigned for access but, after installing 6..9.2 firmware update, users could no longer access shares that belonged to the group they were assigned to and I had to remove the group access to shares and assign access to each individual user.
I managed to get it all working again but it took me days to troubleshoot and get the unit to opeartional status again. I somebody else might find the information useful and of course maybe tech support can fix the firmware.
Bill
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
wrote:
I was using an underscore in the Device Name "ReadyNas_314"
Per the IETF RFCs, underscores aren't legal characters in hostnames. Netgear used to allow them anyway, but that behavior was recently changed.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
I understand the "Underscore" issue but I have been using it in Unix based systems for about 30 years and It worked fine in the previous firmware 6.9.1 and there was no mention of the changed behavior in the change notes. It would have been nice to know before implementing the new version.
Also that does not explain the other issue of the "swap" space crash and log space rotation issue.
And the fact that group access no longer works after the update, All the group access information seems to be intact and no signs of corruption, it just stopped working.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
wrote:
I understand the "Underscore" issue but I have been using it in Unix based systems for about 30 years and It worked fine in the previous firmware 6.9.1
Actually Netgear started enforcing the RFC character limits last April (in 6.7.1). Are you sure you upgraded from 6.9.1?
I agree it should have been in the release notes (and wasn't).
wrote:
Also that does not explain the other issue of the "swap" space crash and log space rotation issue.
And the fact that group access no longer works after the update, All the group access information seems to be intact and no signs of corruption, it just stopped working.
Understood. I think you'll need some analysis from Netgear on those.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
I have been unable to find a way to report the issue of Groups no longer working on 6.9.2 firmware update. Do you have to purchase support to report an issue???
Anybody know how to submit a bug report??
Thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
Which services are you running?
Which protocol are you using?
It would have been helpful to be able to have a look at the system before you reconfigured things.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
When the problems started a few days after the upgrade from 6.9.1 to 6.9.2, and yes I am sure of the previous version. I tried a few time to rename the ReadyNAS by removing the underscore. Each time I made the change and rebooted it after confirming the change was made, it reverted back to the original name after the restart. Thats when I realized something was wrong and I used an ssh login to start looking at what problems were occuring and found that there were the errors described in my original post.
The group logins that were failing are all using SMB and running windows 10, I looked at the logs thru an ssh login while trying to login with a group account and it showed a successful login for the user account and then a failure to login to mount the group share.
The only changes made were to add share access for each individual account to be added to each share since the group logins no longer worked.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
All partitions were less than 50% full,
Also, we are using several protocols including rsync, aft, http but the only ones using group logins are for Samba
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
Configuration changes that don't stick are often a symptom of a full root partition - that is why I asked about it. If you used df or du to assess the fullness, you might also try using the btrfs commands (which include metadata that df and du don't see). Worth checking, just in case - but probably not likely.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
root@ReadyNas314:/var/log/samba# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
udev 10240 4 10236 1% /dev
/dev/md0 4190208 974212 2818428 26% /
tmpfs 1015444 0 1015444 0% /dev/shm
tmpfs 1015444 3676 1011768 1% /run
tmpfs 507724 153816 353908 31% /run/lock
tmpfs 1015444 0 1015444 0% /sys/fs/cgroup
/dev/md127 3902166784 2234965652 1664549868 58% /data
/dev/md127 3902166784 2234965652 1664549868 58% /apps
/dev/md127 3902166784 2234965652 1664549868 58% /home
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
/dev/md0 is the root partition, and ~25% full is fairly typical for that.
As I said above btrfs filesystem df pathname gives more information than df.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
I don't quite get what is significantly different from the df command data, maybe it tells you something more. I will however keep in in mind for any future troubleshooting.
root@ReadyNas314:/var/log# btrfs filesystem df -k /
Data, single: total=3734400.00KiB, used=943748.00KiB
System, DUP: total=8192.00KiB, used=16.00KiB
Metadata, DUP: total=209472.00KiB, used=11056.00KiB
GlobalReserve, single: total=16384.00KiB, used=0.00KiB
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Encountered issue with 6.9.2
The btrfs fi df command splits up data and metadata usage and is much more accurate.