NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

SteveInReno's avatar
SteveInReno
Aspirant
Aug 11, 2018

ReadyNAS 4220: errors creating shares, creating folders, etc... Nothing working.

Model = ReadyNAS 4220

Firmware = v6.9.3

Issue: Unable to create new folders in any share; unable to create new shares

 

Issue began a couple weeks ago; AD users with rights (they are actually domain admins) *and* local administrative account get errors indicating insufficient rights to create new folders.  Attempted to create new shares with various names; getting errors indicating share name is invalid or already in use (not the case).  Attempted to change rights on existing shares; getting completely useless error indicating "commit failed".  Available space is 11.x terabytes out of 36 terabytes.  Also attached are the log output from the ReadyNAS.  Factory reset of the unit isn't an option; we need to be able to fix whatever the problem is.  Google searches of this and related issues yield nothing of use.

 

Attached is image of all three error for different issues described above; unable to upload logs because this board won't accept it.  The "labels" required at the right of this post have nothing to do with the error; no clue why I can't enter relevant labels.

 

Thanks.

Steve

3 Replies

Replies have been turned off for this discussion
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired

    Note that you can't create a share with the same name as a user/group.

     

    You can send your logs in (see the Sending Logs link in my sig)

    • SteveInReno's avatar
      SteveInReno
      Aspirant

      MDGM, thanks for replying.  I've emailed the logs per your request.

       

      And as I mentioned in my post, I have tried creating shares that do not already exist with the same name.

      Steve

      • mdgm-ntgr's avatar
        mdgm-ntgr
        NETGEAR Employee Retired

        Thanks for the logs.

         

        In kernel.log and systemd-journal.log you can see

         

        Aug 11 09:07:47 nas kernel: BTRFS: device label 43f68d0a:data devid 1 transid 207817 /dev/md127
        Aug 11 09:10:10 nas kernel: BTRFS info (device md127): checking UUID tree
        Aug 11 09:10:51 nas kernel: BTRFS error (device md127): parent transid verify failed on 26603622694912 wanted 185320 found 207817
        Aug 11 09:10:51 nas kernel: BTRFS error (device md127): parent transid verify failed on 26603622694912 wanted 185320 found 207817
        Aug 11 09:10:51 nas kernel: BTRFS warning (device md127): Skipping commit of aborted transaction.
        Aug 11 09:10:51 nas kernel: BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure
        Aug 11 09:10:51 nas kernel: BTRFS info (device md127): forced readonly
        Aug 11 09:10:52 nas kernel: BTRFS info (device md127): delayed_refs has NO entry

         

        The filesystem has gone read-only.

         

        Backup, verify backup, factory default (wipes all data, settings, everything), restore from backup could well be the best way forward here. You could contact support but I would expect that they would recommend the same thing.

NETGEAR Academy

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

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More