NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Service management offline
hi ..Please help me on this am getting Service management is offine .unable to access my admin page .but i able to download logs. Am using Readynas 3312. I have data in this .I need that data too...
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/0x60On 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_USERIs 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: SUCCESSAfter 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: SUCCESSCan you give more details on what you were doing here?
Does RAIDar now show the volume is re-syncing?
Yes its showing the hard disk resync sign for extra harddrive ..which is re inserted again. But after some hours. total NAS is gon offline. not showing in raidar too..No ping of its IP also.
Hence after restart. Shows service management is offline. and repeats.
Did you take any action immediately before this happened (like change any share access)? Did it happen on a power cycle?
No root cause . Last scedule an Backup Job for NAS. that too stopped before NAS goes to offline.. its seems no track of intial prob.
Is SSH enabled on the NAS?
Yes
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?
- Nope....Sry ..SSH disabled.....and tried to access the NAS with only 1 drive ...which is removed in starting hdd5 and reinsert again to check the nas...there by I able to access the NAS without my volume raid 6.
And while enabling ssh..it's popup of volume to be present for enabling SSH.
Data is present..I able to see the all folders by accessing through Run \\ip command
Same time I tried of updating NAS firmware without volume.but the iso file not accepted the latest firmware. And tried with same version also..that package also not took. So dropped the scene.
IMW is not the account in NAS. Is the PC account where we access the NAS through IP.
Now NAS is running in 10 drive out of 12. Currently in Non redundant state .
Note : No drive misplaced in it place.
Nas status in Raidar : Management service is offline .
So How to login my Nas with my volume .So atleast I can take copy of my datas. And I do reset the device with new hdds.
Please kindly guide me.
Naveenkumar001 wrote:
Data is present..I able to see the all folders by accessing through Run \\ip command
So How to login my Nas with my volume .So at least I can take copy of my datas.Copy the data over the network using SMB.
If you use "private" home folders, you can get those files also over SMB using the NAS admin credentials. For instance, open CMD and enter
net use * /d /y net use z: \\nas-ip-address\data /u:admin nas-admin-passwordwill mount the full data volume (using the real NAS IP address and admin password of course).
Once the data is safe, we can move on the the other questions.
- The CMD cmnd isnt working..
By SMB.i can see the folders ...Can't able provide copy. Kept loading hrs..for an right click.
If possible please take remote desktop session.
Paid service is ok for me.if u able to help me on recover my data back.
Naveenkumar001 wrote:
If possible please take remote desktop session. Paid service is ok for me.if u able to help me on recover my data back.This is a user-to-user forum - I don't work for Netgear and don't provide direct support (just suggestions/advice)
Naveenkumar001 wrote:
The CMD cmnd isnt working..By SMB.i can see the folders ...Can't able provide copy. Kept loading hrs..for an right click.
Ok. Do you have experience with the linux command line? If you do, you could try using tech support mode,
Naveenkumar001 wrote:
The CMD cmnd isnt working.."Isn't working" isn't a particularly useful description. Are you getting an error message when you enter the command? If so, exactly what is it?
- System error 86
System error 1326
Username / password incorrect. Attached snap..please refer and suggest further pls - Nope I didn't....but I try .say what to do with Linux ..any CMD.?
I do...please suggest
Naveenkumar001 wrote:
Username / password incorrect.Are you sure the NAS is set up to use netgear1 as the admin password?
It is the default admin password for some older ReadyNAS, but not the default admin password for the 3312.
- Yes...Am sure.... I do diagnostic, able to download logs through this credentials only.
Naveenkumar001 wrote:
Yes...Am sure.... I do diagnostic, able to download logs through this credentials only.And when you enter this:
net use * /d /y net use z: \\192.168.5.12\data /u:admin netgear1you are getting the same password error?
Yes. Password is correct that is sure.
- Kindly help me on this...i need data...paid service..also pls suggest
Naveenkumar001 wrote:
Kindly help me on this...i need data...paid service..also pls suggestI'm not sure what to tell you to do.
You'd need to use ssh to try to resolve the btrfs errors - and the repair attempt would be very risky, and likely would require some experimentation. So not something easily done here.
RAID recovery software is the safest path. That would require using a Windows PC, and you'd need at least two USB enclosures to connect the disks. US cost would be about $400 for two 6 or 8 bay USB enclosures + $190 for a ReclaiMe software license. Plus you would need enough disk space to offload the files.
Access via support mode is still an option I've not seen suggested.
I was reluctant to suggest this until you used up all other options, but you could try an OS re-install. That should reset the admin password to password and hopefully will allow you to get to your data via SMB using the admin credentials with that password.
Just be sure not to accidently do a factory default.
Regardless of how you recover the files, those BTRFS errors may mean that you have some files corrupted, and you may not be able to tell which they are. And, of course, you're going to need some place to put all the files you download.
Hi i have accessed the Ready Nas through Serial Console via putty. So please provide me some commands so that i can mount data/ recover/ copy the files to destination. kindly lift me from here .
hi .,had done the OS reinstall by procedures. Same as u said Default password is set & IP default also set.
but not able to access via cmd net Use commands. Showing Password wrong only even with default password.
and i able to login via SMB. but the final folder is showing empty/blank. which i need to copy those files only.
in raidar screen - its in status of System starting up . for last one hour.
any other way pls.
shud i try tech support/ Volume read only boot modes. ??
Naveenkumar001 wrote:
Hi i have accessed the Ready Nas through Serial Console via putty. So please provide me some commands so that i can mount data/ recover/ copy the files to destination. kindly lift me from here .
Are you using telnet (NAS booted in tech support mode) or are you using ssh (NAS booted normally) to connect with putty?
Either way, you normally log in as root, NOT admin. With ssh, you use the NAS admin password.
If you are using ssh, are you seeing your shares when you enter ls -als /data ?
i had login as root and given the command. but nothing displays.
Am selecting Serial & telnet . as its connected to console comport. SSH is disable in NAS.without volume it cant be enabled.
shud i login same as tech support mode and try this command?
Naveenkumar001 wrote:
Am selecting Serial & telnet . as its connected to console comport. SSH is disable in NAS.without volume it cant be enabled.
Odd that the NAS let you connect with Telnet. I am wondering if it is in a recovery mode.
Rebooting in tech support mode makes sense. But the password for root is infr8ntdebug
There are several commands you'd need to run to manually mount the raid array.
rnutil chroot mdadm --assemble --really-force /dev/md127 /dev/sd[abcdefghijk]3 btrfs device scan mount /dev/md127 /dataThe NAS might not accept the syntax of the mdadm command. You might need to use /dev/sda3 /dev/sdb3 up to /dev/sdk3
I am thinking you will see errors. If you do, stop at that point and post the screen shot.
This is a bit confusing because you say you're using the serial (aka UART) port, but that wouldn't use Telnet, it would use Serial.
Yes Am selected Com3 with Baud rate 115200 . Telnet is default in Putty while clicking ok.
Dude..Check this
Naveenkumar001 wrote:
Dude..Check this
Did you connect using root and the password infr8ntdebug? The error you got with rnutil chroot suggests might not have done that (suggesting also that the NAS was not booted in tech support mode).
BTW, when you select serial in putty, then the protocol next to "other" is ignored. So you are not using telnet.
It is important to use the commands I give you, and stop if you get errors or cannot complete a step. These commands can make data recovery harder (or even impossible) if you don't enter them correctly.
OK, if he's connected via the serial port, I think he's not in debug mode -- at least I'm not aware that the console is active in debug mode. The console is active in normal mode with all the same requirements and capabilities of SSH.
No it doesn't asks me username and password while entered with serial.
entered root and got some other erron as attached. Now check this snap.
Is this a possitive sign?? shud wait for process to complete??
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
