Re: ReadyNas 104, stuck in booting... after restart

dyerdj1 · ‎2015-08-27

Hey Guys,

A bought a new 4TB WD red drive 2 days back so i could copy the exiitsing data from the 2 4TB WDRed drives they were set up in a raid and then destroy that share to expand to 3 x 4TB in a JBOD setup.

Everything seemed to be working really well, all data copied correctly, destoyed the initial raid and then copied the files back but split between Disk 1 and 2 using 3 as a spare.

I have a feeling when i destroyed the orginal raid share, it has lost some READYNAS OS files or something as all APPs then disappeared and i was unable to see any Apps on the app page.

I then thought ok maybe a fresh restart is what it needs, after doing that the device now says booting..... and has been for quite a while, the power butting on flashing on and off steadily and the other light (to th left of the button) is almost constantly on with a few flickers every now and then.

Any ideas on how i can restore this?

Thanks in advance!

StephenB · ‎2015-08-27

The apps are stored on the data volume (default is /data/apps). So you did lose them when you destroyed the data volume.

Probably there should be a warning to uninstall/reinstall them (or a way to back up/restore /data/apps).

Since you still have your data, a factory reset would work. You can destroy the xraid volume before it is finished building, and recreate your data volumes. You might want to name the first one data (just in case an app assumes the path).

dyerdj1 · ‎2015-08-27

Thansk for the reply!

I forgot to mention in my post that after i destoryed the volumne i formatted and copied the data back.....

So i currently have 3 volumens D1, D2 and D3 which RAIDar says are all working fine, just the "Management service is offline" and the physical NAS itself just says "booting...."

I can access the NAS through putty easy enough and there is minimal going on, almost like it is just looking for something to run.....

Cheers

mdgm-ntgr · ‎2015-08-27

# journalctl -a | grep readynasd | tail -n 20

dyerdj1 · ‎2015-08-27

Aug 28 08:43:13 Elemental readynasd[1360]: readynasd started. (restarted=0)
Aug 28 08:43:13 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:13 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:13 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:13 Elemental readynasd[1367]: readynasd log started
Aug 28 08:43:13 Elemental readynasd[1367]: readynasd started. (restarted=0)
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:14 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:14 Elemental readynasd[1374]: readynasd log started
Aug 28 08:43:14 Elemental readynasd[1374]: readynasd started. (restarted=0)
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:14 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:14 Elemental readynasd[1381]: readynasd log started
Aug 28 08:43:14 Elemental readynasd[1381]: readynasd started. (restarted=0)
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:15 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service start request repeated too quickly, refusing to start.

dyerdj1 · ‎2015-08-27

Thanks for the replonse, output below.

Aug 28 08:43:13 Elemental readynasd[1360]: readynasd started. (restarted=0)
Aug 28 08:43:13 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:13 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:13 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:13 Elemental readynasd[1367]: readynasd log started
Aug 28 08:43:13 Elemental readynasd[1367]: readynasd started. (restarted=0)
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:14 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:14 Elemental readynasd[1374]: readynasd log started
Aug 28 08:43:14 Elemental readynasd[1374]: readynasd started. (restarted=0)
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:14 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:14 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:14 Elemental readynasd[1381]: readynasd log started
Aug 28 08:43:14 Elemental readynasd[1381]: readynasd started. (restarted=0)
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:15 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service start request repeated too quickly, refusing to start.

dyerdj1 · ‎2015-08-27

Thanks for the reply, have tried to post the log in here but keeps getting removed for some reason, here is a snippet.

ug 28 08:43:14 Elemental readynasd[1381]: readynasd log started
Aug 28 08:43:14 Elemental readynasd[1381]: readynasd started. (restarted=0)
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service: main process exited, code=dumped, status=11
Aug 28 08:43:15 Elemental systemd[1]: Unit readynasd.service entered failed state.
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service holdoff time over, scheduling restart.
Aug 28 08:43:15 Elemental systemd[1]: readynasd.service start request repeated too quickly, refusing to start.

mdgm-ntgr · ‎2015-08-27

# cat /var/log/frontview/initrd.log
# ls -lah /var/cores

dyerdj1 · ‎2015-08-27

Last login: Fri Aug 28 10:24:58 2015 from dyer.fritz.box
root@Elemental:~# cat /var/log/frontview/initrd.log
[2013/11/08 04:03:17] Factory default initiated due to new disks (no RAID, no partitions)!
[2013/11/08 04:03:34] Defaulting to X-RAID2 mode, RAID level 1
[2013/11/08 04:04:00] Factory default initiated on ReadyNASOS 6.0.4.
[2013/11/07 20:28:24] Updated from ReadyNASOS 6.0.4 to 6.1.4.
[2014/01/19 19:21:10] Updated from ReadyNASOS 6.1.4 to 6.1.5.
[2014/02/10 00:04:54] Updated from ReadyNASOS 6.1.5 to 6.1.6.
[2014/04/21 03:09:35] Updated from ReadyNASOS 6.1.6 (1391111179) to 6.1.7 (1396977042).
[2014/05/19 23:00:47] Updated from ReadyNASOS 6.1.7 (1396977042) to 6.1.8 (1398980083).
[2014/10/03 01:20:02] Updated from ReadyNASOS 6.1.8 (1398980083) to 6.1.9 (1409791183).
[2014/12/18 13:39:46] Updated from ReadyNASOS 6.1.9 () to 6.2.0 (ReadyNASOS).
[2015/03/15 23:17:38] Updated from ReadyNASOS 6.2.0 (ReadyNASOS) to 6.2.2 (ReadyNASOS).
[2015/05/10 15:16:19] Updated from ReadyNASOS 6.2.2 (ReadyNASOS) to 6.2.4 (ReadyNASOS).
[2015/08/23 02:39:46] Updated from ReadyNASOS 6.2.4 (ReadyNASOS) to 6.2.5 (ReadyNASOS).

root@Elemental:~# ls -lah /var/cores
total 3.7M
drwxr-xr-x 2 root root 4.0K Aug 24 03:30 .
drwxr-xr-x 19 root root 4.0K Aug 23 20:39 ..
-rw------- 1 root root 11M Aug 28 11:28 core-readynasd
-rw------- 1 root root 2.4M Aug 27 12:48 core-smbd

mdgm-ntgr · ‎2015-08-27

Thanks.

I have sent you a PM.

I would like the logs and the core-dump. The core dump will need to be compressed so it is small enough to be emailed.

mdgm-ntgr · ‎2015-08-27

O.K.

It turns out all the inodes are used on the 4GB OS partition. This probably means there are a lot of small files.

The OS partition being 74% full in terms of data is way too high too. It should be well under half full.

If you can't figure out from http://unix.stackexchange.com/questions/117093/find-where-inodes-are-being-used what is using it up I could have a look remotely at the system if you like.

mdgm-ntgr · ‎2015-08-27

Turns out Plex filled the inodes. Presumably an old version of the app.

BDC-M · ‎2015-09-09

As a Newbie to this forum, I am very disappointed on Netgear's apparent lack of concerted interest in my issues - Case #25715764. If I power the NAS down, accidentally hit restart on RAIDar or have a power failure, the Reboot idles along for 10 hours before the Power LIght stops flashing.Usally 30+ "NASOS is restartin"g every 19 minutes accordingly to the logs. All atempts to download logs have failed as per Case # above. First level support just fails to read the messages I send in any detail and relate to the Case history, repeatedly asking for the same information previously provided.

Overnight I have been promised a Level 2 Tech dialling into my NAS today but here we are 1 hour later than scheduled and no response. Maybe you can PM me and resole my issues.

BDC-M · ‎2015-09-09

That should be Case # 25717164.

mdgm-ntgr · ‎2015-09-10

The turnaround for support is best effort. You provided the necessarily details for escalation today. Once the support agent confirms the remote access is in place and escalates it (they would let you know before they escalate) one would expect that it may be a further day or so before the next level agent can look at the system. The time taken does vary depending on how busy the agent is that it is escalated to.

One of your disks has a huge ATA error count. I will PM you details of which disk this is. Please confirm that the disk was properly seated.

The huge ATA error count generally indicates a failed disk. You could test the disk using WD Data Lifeguard Diagnostics to confirm.

If you don't have a PC to test the disk, you could try using the NAS with just the other disk. If the other disk works fine regardless of which slot it is in then that would confirm that the disk with the huge ATA error count is bad.

BDC-M · ‎2015-09-10

When I attempt to execute Data Lifeguard it only sees C & D drives of my laptop, not either of the 2 drives in the NAS. How do I access them - thru Windows Explorer?

Thx

BDC-M

dyerdj1 · ‎2015-09-10

Hello BDC-M, sorry you have had such issues but I cannot disagree with you more. These guys were extremely helpful and quite quick considering the time difference here in NZ. In future please try not to post unrelated issues in an existing thread as you are just making it harder for the people looking for answers.
Cheers

BDC-M · ‎2015-09-10

So I have pulled out disk 2 and lo and behold the Log file will happily download to my PC. I will fwd this to Support for evaluation.