NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Re: ReadyNas 516 More Command Timeout Headaches 2
I accidently Closed the post so I am reposting this due to my Nightmare- ReadyNas516, Latest Firmware/software- 6 disk NAS with 5 12TB Seagate Just Got done replacing 2 drives to get completely ...
Maxpower411 wrote:
Stephen - I guess the goal is to delete this admin directory?? Will this fix my problem?
Isn't the dir required, or will it build a new one?
Let me try again to explain this.
/home is a linux mount point. The system normally will remount /data/home onto /home. This is done with the same command you used to mount / onto /mnt.
/home itself is supposed to be empty. The NAS software has an error check for that, and in your case the error is triggering.
The only way to make the error go away is to delete all the files and folders in the original /home. Once the system is running, the remount of /data/home means you can't just go into /home to do that. I had you mount / onto /mnt, because /mnt will doesn't include the remounts.
The error is only a concern because of the space taken up by the spurious files and subfolders. It sounds like that is neglible in your case, but it would be good to clean it up.
So the system won't rebuild the folder, and it isn't needed. The real folder is /data/home/admin, and that won't be affected by the deletion in /mnt/home. Deleting /home/admin when the system is running would be a big mistake, as that is the same as /data/home/admin.
Maxpower411 wrote:
I belive it is possible that the admin directory cant be deleted until we delete the hidden dir, and the hidden file-just my best guess.
I don't think so, but I'm not certain what the problem actually is. I am wondering if it's actually a btrfs subvolume (which would be very odd, but conceivable). Let's wait until the resync is finished, and then pick it up again.
Thanks to Both of you Sandshark, and Stephen-
I can see the network on my pc so this is what I see:
If I goto admin folder, there is a hidden folder called .ssh, (I knew the period means hidden)
then inside of that folder there is a file named: ssh_authorized_keys. The file size of that
file is 0KB.
This is seen through the eyes of my network with the admin login, it shows always, the way my system is configured. (this is under my win 10 network area)
I am currently resyncing with ssh off I belive, very slow to even get into the admin of the network interface, so I will wait to finish the resync, before doing this.
I belive it is possible that the admin directory cant be deleted until we delete the hidden dir, and the hidden file-just my best guess.
Stephen - I guess the goal is to delete this admin directory?? Will this fix my problem?
Isn't the dir required, or will it build a new one?
I will follow your instructions as soon as the drive is done resyncing, everything slows to a crawl, just trying to login while resyncing (been looking at the entry page for about 5 minutes, just trying to log in.) so I wait !! (some of my networked drives are mapped as well) I was able to log in but wait, wait, and wait! Trying to see if I turned off ssh curently, not sure at this point.
Thanks for the help and patience from you both-
Jeff
Maxpower411 wrote:
Stephen - I guess the goal is to delete this admin directory?? Will this fix my problem?
Isn't the dir required, or will it build a new one?
Let me try again to explain this.
/home is a linux mount point. The system normally will remount /data/home onto /home. This is done with the same command you used to mount / onto /mnt.
/home itself is supposed to be empty. The NAS software has an error check for that, and in your case the error is triggering.
The only way to make the error go away is to delete all the files and folders in the original /home. Once the system is running, the remount of /data/home means you can't just go into /home to do that. I had you mount / onto /mnt, because /mnt will doesn't include the remounts.
The error is only a concern because of the space taken up by the spurious files and subfolders. It sounds like that is neglible in your case, but it would be good to clean it up.
So the system won't rebuild the folder, and it isn't needed. The real folder is /data/home/admin, and that won't be affected by the deletion in /mnt/home. Deleting /home/admin when the system is running would be a big mistake, as that is the same as /data/home/admin.
Maxpower411 wrote:
I belive it is possible that the admin directory cant be deleted until we delete the hidden dir, and the hidden file-just my best guess.
I don't think so, but I'm not certain what the problem actually is. I am wondering if it's actually a btrfs subvolume (which would be very odd, but conceivable). Let's wait until the resync is finished, and then pick it up again.
StephenB wrote:I don't think so, but I'm not certain what the problem actually is. I am wondering if it's actually a btrfs subvolume (which would be very odd, but conceivable). Let's wait until the resync is finished, and then pick it up again.
I think that when he originally went in and enabled SSH that the /data/home folder was not mounted at /home, so the OS created an actual admin folder (or maybe subvolume) in the real /home instead of the mounted one. Since user shares are normally subvolumes, it does make sense that maybe it is a subvolume, and that's what makes rm incapable of deleting it. But he also says there is still a hidden file in the folder that the rm didn't delete, so does the rm with those flags not delete invisible files and that's the real issue? Maybe add the -f option to force removal of the invisible file that maybe has something else keeping it from being deleted?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
