NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
britesc
Mar 11, 2024Aspirant
ReadyNas524X - Lost admin Home Folder !!!
Hi, Running ReadyNas 524X 6.10.10 Although I can login as admin, it appears that the admin home folder is not accessible anymore. Is there anything I can do to try attempt recovery? Like chkds...
StephenB
Mar 11, 2024Guru - Experienced User
britesc wrote:
Running ReadyNas 524X 6.10.10
Although I can login as admin, it appears that the admin home folder is not accessible anymore.
If you navigate into home, are you seeing admin there?
- britescMar 12, 2024Aspirant
Hi,
Thanks for the replies.
If I ssh in then I get the following from /home
admin@Donkey:/home$ ls -lisa
ls: cannot access 'admin': Input/output errortotal 16
...
263 0 drwxr-xr-x 1 AUser users 712 Feb 23 2023 AUser
? ? d????????? ? ? ? ? ? adminIf I use the webgui and look at the shares I get a list of users of which admin is 1 of them.
If I then click on admin I get a progress bar that does not end and a rotating cog icon that continues for ever.
If this was NTFS I would say that the MBR File Descriptor has gone, but should be recoverable using various OS and 3rd party tools.
As this is a Debian derivative Linux I think that there is an inode problem.
Firstly is the RAID 5 constructed using mdadm in which case I would try some msadm tools etc.
If not any idea how the raid is constructed.
Thanks and kind regards,
jB đ
- StephenBMar 12, 2024Guru - Experienced User
britesc wrote:
If I ssh in then I get the following from /home
admin@Donkey:/home$ ls -lisa
ls: cannot access 'admin': Input/output errortotal 16
...
263 0 drwxr-xr-x 1 AUser users 712 Feb 23 2023 AUser
? ? d????????? ? ? ? ? ? adminNormally it is recommended to log in as root when using ssh. But I do see my admin folder when I log as admin on a system running 6.10.10. Note this is an RN102, not an x86 NAS.
FWIW, the file system is btrfs, so no inodes. The home folder is actually on the data volume (you are accessing it via a mount point). You could try running btrfs check --force /dev/md127 (logging in as root) and see if that finds anything. If you try this, be careful not to access the data volume while the check is running. Otherwise you might crash.
- SandsharkMar 12, 2024Sensei
Your permissions for AUser are not what I expect. Normal, they should be rwx------. Having you been making permissions changes with SSH? I don't specifically know how that could cause this error, but it's not a good idea. And if it wasn't you who made the change, I wonder if it's related.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!