Forum Discussion

Aspirant

Mar 11, 2024

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

Guru - Experienced User

Mar 11, 2024

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?

britesc

Aspirant

Mar 12, 2024

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 error

total 16

...

263 0 drwxr-xr-x 1 AUser users 712 Feb 23 2023 AUser
? ? d????????? ? ? ? ? ? admin

If 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 😎

StephenB
Guru - Experienced User
Mar 12, 2024
britesc wrote:

If I ssh in then I get the following from /home

admin@Donkey:/home$ ls -lisa
ls: cannot access 'admin': Input/output error

total 16

...

263 0 drwxr-xr-x 1 AUser users 712 Feb 23 2023 AUser
? ? d????????? ? ? ? ? ? admin

Normally 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.
- Sandshark
  Sensei
  Mar 12, 2024
  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.
  - britesc
    Aspirant
    Mar 12, 2024
    MHi,
    
    Once again thanks for the replies.
    I will change share permissions.
    I have ordered a new 2TB drive, compatible with the existing as I noted msadm -D /dev/md0 was reporting /dev/sdc as removed. Having checked that the drives are physically fitted correctly I am assuming that sdc is not behaving itself 😉
    Additionally the RAID is marked as Read Only.
    If the change of HDD resolves the problem I will report back
    
    Many thanks,
    
    jB 😎