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

Forum Discussion

SGT_Oldy's avatar
SGT_Oldy
Aspirant
Nov 19, 2019
Solved

Could not delete share due to snapshot deletion failure, Code 1004030000 OS6

I have a ReadyNAS 316 OS 6.10.2 with 3x2TiB + 3x4TiB disks so currently at 12TiB. Seem to have a problem with one of my share folders. I am unable to delete a share due to a snapshot deletion error as mentioned in the title.

 

First noticed the problem when I was changing out two of the 2Tb disks with 4Tb disks. One of the disks was BOB, so sent it back. Was prio to that at 2,2,2,2,4,4 was attempting to go 2,2,4,4,4,4 but got stuck at three each 2&4 disks.

 

 

 

Yes, I saw there were several similar mentions of this in the forum but none gave me the solution. 

 

 

 

Currently I see I have:

 

5.32 TB Data,

 

5.97 TB Free,

 

1.42 TB Snapshots, (although there are NO snapshots on the system) and the one share (was Archive, renamed OldChive in an attempt to delete that way) I am unable to delete shows it is currently...

 

 

 

16,777,216.0Tb in size. 

 

 

 

I am attempting to migrate all data off the NAS onto drives--if I can get enough disks together to save it all--so to be able to reformat but would like to find the right answer. 

 

 

 

1) shows I have 1.42Tb of snapshots but have no snapshots.

 

2) have a share showing data consumed is well over 1K% the size of the whole NAS, and I am unable to delete the thing.

 

 

 

I don't want to go the route of SSH for warranty sake, although I don’t think it matters anymore, but will if someone can walk me through a little.

 

 

 

Ask anything you want to know if it helps get to the answer.

 

 

 

Oldy

  • Clearly the file system for the data volume has become corrupted somehow.  The most conservative approach is to do a factory default, rebuild the NAS, and restore the data from backup.

     

    If you purchased the NAS (new) between 1 June 2014 and 31 May 2016, then you have lifetime chat support at my.netgear.com.   You could try using that if you have it.

     

    SSH is another possibility - using it to manually delete the snapshots and share.  You'd log in as root, using the NAS admin password.

     

    You can list the btrfs subvolumes (e.g., shares and snapshots) with btrfs subvolume list /data

     

    Then you can manually delete the ones you want to get rid of with  btrfs subvolume delete <path>

     

    You need to use the full name in the path (e.g., it needs to start with /data/OldChive ).  When deleting snapshots you need to delete each one independently (something like /data/OldChive/.snapshots/XX/snapshot for each one).

     

10 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User

    Clearly the file system for the data volume has become corrupted somehow.  The most conservative approach is to do a factory default, rebuild the NAS, and restore the data from backup.

     

    If you purchased the NAS (new) between 1 June 2014 and 31 May 2016, then you have lifetime chat support at my.netgear.com.   You could try using that if you have it.

     

    SSH is another possibility - using it to manually delete the snapshots and share.  You'd log in as root, using the NAS admin password.

     

    You can list the btrfs subvolumes (e.g., shares and snapshots) with btrfs subvolume list /data

     

    Then you can manually delete the ones you want to get rid of with  btrfs subvolume delete <path>

     

    You need to use the full name in the path (e.g., it needs to start with /data/OldChive ).  When deleting snapshots you need to delete each one independently (something like /data/OldChive/.snapshots/XX/snapshot for each one).

     

    • SGT_Oldy's avatar
      SGT_Oldy
      Aspirant

      Hey  StephenB 

       

      First things first, you said the file system is become corrupted, any idea why or how to prevent it happening again?

       

      Onto the current situation...

      Thanks... not fixed yet but better understanding. You told me to use "btrfs subvolume list /data" to see what it was I could not before and to know what to delete. 

       

      I used that and found:

      ID 287 gen 245200 top level 285 path OldChive/.snapshots    (and / or)
      ID 9439 gen 242748 top level 287 path OldChive/.snapshots/99/snapshot

       

      Being hidden I could not see it before, so YEAH! now I can see what I want to delete. So I did cd data/OldChive/.snapshots

      and entered this line

       

      root@XXNASXX:/data/OldChive/.snapshots# rm -rf 99/

      but from there I got about a bajillion lines listing each dir and file and

       

      rm: cannot remove '99/snapshot/(each dir and each file of the dir)': Read-only file system

      I tried to use the Admin page to try to change the permissions, as well as windows file expoloer but that did nothing helpful. I then used Google to find the Linux command to change the dir and files from R to RW.  However, chmod is not part of the OS, and I could not find any other commands.

       

      If this was a Cisco, Dell, or even a dammed Brocade switch or router I could command line that thing with no problem, but I am not as good with Linux as I wish I was.

       

      I looked back at my purchase info, I bought a diskless system off of Newegg on EXACTLY 5/31/2016. I will try during the day instead of evening to use the chat support, however do you know if they will be upset that I have accessed via SSH already? I have this NAS at home btw, maybe I am strange, but I like tech stuff lol.

       

       

       

       

      • Sandshark's avatar
        Sandshark
        Sensei - Experienced User

        If the NAS has made the file system read-only, then it has detected something it thinks could go catestrophically wrong if you write more to it.  There is really no way around that that I have found than backing up the data while you can, doing a factory default, and re-building.

    • SGT_Oldy's avatar
      SGT_Oldy
      Aspirant

      StephenB Hey, I somehow clicked on my first reply to you as the "solution" do you know how to fix that?

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        I'm glad you figured it out.  Subvolumes look like ordinary folders, but they aren't - and as you found, rm can't delete them.

         

        It might be good to also run a balance.  That will scan the allocated data and metadata.  It will also consolidate more free space.

         


        SGT_Oldy wrote:

        Hey, I somehow clicked on my first reply to you as the "solution" do you know how to fix that?


        Yes, I've undone that, so you can pick a different post.

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