Error 1002030001 Commit failed - Lost access to shares and account changes
Dear friends,
The issue is as follows; I can read from all my shares, but i cannot write to them (using Windows 10). Obviously this was not an issue before. I disconncted all my shares and try remapping them, but when i want to connect using credentials, windows gives an error.
When I go to the admin page of my nas, i also cannot change anything on the shares, any change i try to make gives the following error:
1002030001 - Commit failed
Also, I tried to delete some files via the admin browse page, rather than in windows on the mapped drive, but even there nothing happens. This is strange to me, as i am logged in to admin page with the actual Admin account.
Any change i try to make to either accounts or shares gives me the commit error i mentioned. I also cannot delete any data via the admin web interface. Coinsedently, i also lost any "apps" that were installed (like transmission) and if i go to the apps page to reinstall, it stays blank.
Something super fishy is going on and i cannot find an answer other than factory reset (eh, no) or contacting the support team (emailed them just now).
Snapshots are turned off, bit rot protection is turned on (but i cannot change any of those settings anyway...)
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
Hello yveZ79,
There is a possibility the OS partition got full for some reason that is the reason why any changes that are being made are not applying. Could please attach volume logs specially the one under df -h.
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
Hello yveZ79,
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution.
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
Howdy,
I have lost my volume now completely. Netgear tech looked at it and indeed the nas was on 95% capacity. It would have been great if the nas would give some sort of restrictions on you reaching a stage on which apparently it cannot function anymore.
All I can do now is pay for a recovery action, but this would cost 150 euros plus I need to have a storage unit available to copy the stuff to, as the nas was 15tb, this is not easy.
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
Hello yveZ79,
I do understand the frustration. If email alert is enabled and properly setup, the NAS will send email alert that the volume is reaching almost full. Also the NAS will generate logs that most of the volume space is used. The NAS is Network Attached Storage device and it is not backup solution. Best practice is to make sure you have a backup of the data save on the NAS if it is a cloud or offsite backup. As for your NAS in the future make sure to check the health of the hard drives and volume status every time you access the admin page.
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
Well sorry for being direct, but I think what you just said makes no sense at all. I agree only with the fact its not a back up. I saw that the volume was on 94% when I logged in. However , if th device needs to stay on -for example- max 92% usage, then this needs to be automated. Are users supposed to guess that 96% is actually already too much? Updates are generally not that big, so again, that does not hint to the fact we need more than 5% free space in order for the bad to work. The non-existing backup is on me, I'm not implying that's Netgears fault. I am saying that to me it sounds strange some critical requirement to remain operational is not automated, as in reserving x amount of space to ensure the device stays ok. That's the thing I am frustrated with. My volume is, sorry....was, 4 x 4TB, so 14.2TB effective...5% would mean approx 700GB....that sounds like a lot of space _needed_ to be reliably operational.
Anyways, just my thoughts....in the end, the back up is on me...but the 5% rule sounds strange to me.
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
Hello yveZ79,
On the email alerts and the logs it will tell the current volume data usage of the NAS and there is a suggestion to free up some space or add capacity. As for free space it is recommended to have around 10% to 15% of the total volume capacity.
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
Again, email alerts should not be a necessity to have your nas working. I logon daily to the admin page so not seeing the usage in an alert is not the issue. Let me try again; if it is needed (needed apparently, not recommended) to have x amount of % free, then this should be built in to the system, as in not allowing me to get to 96% because apparently then I can't use my device anymore...
I get where you're coming from, but this sounds more like a political answer then understanding the underlying issue. Now it's 10-15% in stead of 5&10% the guy on the phone told me. 15% of 15TB is alot (a LOT) of space to be needed.....
Re: Error 1002030001 Commit failed - Lost access to shares and account changes
@Retired_Member wrote: I get where you're coming from, but this sounds more like a political answer then understanding the underlying issue.
There is a threshold built into the snapshot processes that kicks in at 90% full. That will automatically delete snapshots in order to keep the file system healthy. That alone suggests this isn't political.
BTRFS free space is handled quite differently from ext - one difference is that metadata shares the same space pool as ordinary free space. You really don't want to run out of space for metadata. Whatever you might have been told on the phone, we do see problems here when the disk fullness exceeds 90%. I realize that looks like a lot of space, but the percentage matters more than the absolute amount.
I keep my own OS 6 systems below 85% utiltization. I'll let my older OS 4 NAS go higher, but generally want to limit them to 90%.
@Retired_Member wrote: Again, email alerts should not be a necessity to have your nas working.
They aren't, but I strongly recommend that you enable them.
