Service management offline

---

Naveenkumar001 wrote:

>>> Is SSH enabled on the NAS?

Yes

---

I suggest accessing the NAS with ssh, and then check that your data is there (ls -als /data).

The logs show that the volume is mounted, but I am seeing unexplained BTRFS timeouts:

Feb 20 10:53:40 DHTL-TP1-NAS kernel: INFO: task btrfs-transacti:4250 blocked for more than 200 seconds.
Feb 20 10:53:40 DHTL-TP1-NAS kernel:       Tainted: P           O    4.1.30.x86_64.1 #1
Feb 20 10:53:40 DHTL-TP1-NAS kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 20 10:53:40 DHTL-TP1-NAS kernel: btrfs-transacti D ffff88021321bd68     0  4250      2 0x00000000
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  ffff88021321bd68 ffffffff88e2c4a0 ffff880265f08fc0 ffff88026fc147c0
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  ffffffff88e2c8d8 ffff88026fc147c0 ffff88021321c000 ffff880265d8f1f0
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  ffff880265d8f1f0 0000000000000000 ffff88026644b370 ffff88021321bd88
Feb 20 10:53:40 DHTL-TP1-NAS kernel: Call Trace:
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff88a4f1e2>] schedule+0x32/0x80
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff882e62df>] wait_current_trans.isra.34+0x9f/0x100
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff8809c8c0>] ? add_wait_queue+0x60/0x60
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff882e7e58>] start_transaction+0x2c8/0x550
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff882e8142>] btrfs_attach_transaction+0x12/0x20
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff882e4d0b>] transaction_kthread+0x7b/0x240
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff882e4c90>] ? open_ctree+0x24b0/0x24b0
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff88082bb4>] kthread+0xc4/0xe0
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff88082af0>] ? kthread_freezable_should_stop+0x60/0x60
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff88a523d2>] ret_from_fork+0x42/0x70
Feb 20 10:53:40 DHTL-TP1-NAS kernel:  [<ffffffff88082af0>] ? kthread_freezable_should_stop+0x60/0x60

On SMB access, I am seeing a lot of errors that look like this:

[2025/02/20 16:12:33.035542,  2] ../source3/auth/auth.c:315(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [IMW] -> [IMW] FAILED with error NT_STATUS_NO_SUCH_USER

Is IMW an account that should exist on the NAS?

You are running very old firmware (6.6.0 - released in 2016).  You appeared to make an attempt to update to 6.10.10 on 19 Feb

Feb 19 2025 17:04:49 INFO:UPLOAD_IMAGE: _filename_=ReadyNASOS-6.10.10-x86_64.zip _filesize_=90385981
Feb 19 2025 17:04:50 INFO:GET_REMOTE_INFO: name=ReadyNASOS version=6.10.10 size=90783744 md5=b2f2ee74b9bbf269d449490b24b370fe arch=x86_64
Feb 19 2025 17:04:50 INFO: arch=x86_64 personality= sysinfo->personality=1
Feb 19 2025 17:04:50 INFO:UPLOAD_IMAGE: Checking file for md5... 
Feb 19 2025 17:04:50 INFO:CHECK_MD5_SUM: local=b2f2ee74b9bbf269d449490b24b370fe remote=b2f2ee74b9bbf269d449490b24b370fe
Feb 19 2025 17:04:50 INFO:CHECK_MD5_SUM: MD5 OK! Create link in /etc/.flash_update -> .flash_update_file
Feb 19 2025 17:04:50 INFO:UPLOAD_IMAGE: Write info to .flash_update_info... 
Feb 19 2025 17:04:50 INFO:UPLOAD_IMAGE: SUCCESS

After that you appear to have downgraded back to 6.6.0

Feb 19 2025 17:29:10 INFO:UPLOAD_IMAGE: _filename_=ReadyNASOS-6.6.0-x86_64.img _filesize_=63207424
Feb 19 2025 17:29:10 INFO:GET_REMOTE_INFO: name=ReadyNASOS version=6.6.0 size=63207424 md5=aec396425a099a22e0fc4f43bbe6ac69 arch=x86_64
Feb 19 2025 17:29:10 INFO: arch=x86_64 personality= sysinfo->personality=1
Feb 19 2025 17:29:10 INFO:UPLOAD_IMAGE: Checking file for md5... 
Feb 19 2025 17:29:10 INFO:CHECK_MD5_SUM: local=aec396425a099a22e0fc4f43bbe6ac69 remote=aec396425a099a22e0fc4f43bbe6ac69
Feb 19 2025 17:29:10 INFO:CHECK_MD5_SUM: MD5 OK! Create link in /etc/.flash_update -> .flash_update_file
Feb 19 2025 17:29:10 INFO:UPLOAD_IMAGE: Write info to .flash_update_info... 
Feb 19 2025 17:29:10 INFO:UPLOAD_IMAGE: SUCCESS

Can you give more details on what you were doing here?