ReadyNas 104, stuck in booting... after upgrade to 6.6 from 6.4.2

[sokol_44]

Automatic update from  6.4.2 to 6.6 ( i think 6.6.0)

Stuck at "booting 99%", SSH and SMB works.

Logged and service readynas wont start:

# systemctl status readynasd
● readynasd.service - ReadyNAS System Daemon
   Loaded: loaded (/lib/systemd/system/readynasd.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit-hit) since Sun 2017-01-22 13:15:00 CET; 3 weeks 6 days ago
 Main PID: 3229 (code=dumped, signal=SEGV)
   Status: "Importing DB"

Jan 22 13:15:00 mls-nas1 systemd[1]: readynasd.service: Failed with result 'core-dump'.
Jan 22 13:15:00 mls-nas1 systemd[1]: readynasd.service: Service hold-off time over, scheduling restart.
Jan 22 13:15:00 mls-nas1 systemd[1]: Stopped ReadyNAS System Daemon.
Jan 22 13:15:00 mls-nas1 systemd[1]: readynasd.service: Start request repeated too quickly.
Jan 22 13:15:00 mls-nas1 systemd[1]: Failed to start ReadyNAS System Daemon.
Jan 22 13:15:00 mls-nas1 systemd[1]: readynasd.service: Unit entered failed state.
Jan 22 13:15:00 mls-nas1 systemd[1]: readynasd.service: Failed with result 'start-limit-hit'.

I have core and strace of this process..

[mdgm-ntgr · Accepted solution]

A factory reset was a rather drastic step to take. I have sent you a PM.

[mdgm-ntgr]

How full is the root volume?

# df -h
# df -i

You can confirm the firmware version:

# cat /etc/os_version

Do you have any apps installed? If so, which ones?

[sokol_44]

Additional mount is for backup where i try to move everything in case i need hard reset.

# df -h
Filesystem                  Size  Used Avail Use% Mounted on
udev                         10M  4.0K   10M   1% /dev
/dev/md0                    4.0G  906M  2.9G  24% /
tmpfs                       249M     0  249M   0% /dev/shm
tmpfs                       249M  452K  248M   1% /run
tmpfs                       125M  732K  124M   1% /run/lock
tmpfs                       249M     0  249M   0% /sys/fs/cgroup
/dev/md127                  5.5T  3.2T  2.4T  58% /data
/dev/md127                  5.5T  3.2T  2.4T  58% /home
/dev/md127                  5.5T  3.2T  2.4T  58% /apps
192.168.1.17:/mnt/hbz1/all  2.6T  732G  1.9T  28% /mnt/freenas

~# df -i
Filesystem                     Inodes IUsed      IFree IUse% Mounted on
udev                            63154   440      62714    1% /dev
/dev/md0                        65536 18474      47062   29% /
tmpfs                           63590     1      63589    1% /dev/shm
tmpfs                           63590   580      63010    1% /run
tmpfs                           63590    24      63566    1% /run/lock
tmpfs                           63590     9      63581    1% /sys/fs/cgroup
/dev/md127                          0     0          0     - /data
/dev/md127                          0     0          0     - /home
/dev/md127                          0     0          0     - /apps
192.168.1.17:/mnt/hbz1/all 3978873730 25656 3978848074    1% /mnt/freenas

#  cat /etc/os_version
ReadyNASOS!!version=6.6.1,time=1482880160,arch=arm,descr=ReadyNASOS

# ls -l /data/.apps
total 0
drwxr-xr-x 1 root  root   52 Jun 26  2014 APPGENIE
dr-xr-xr-x 1 root  root    0 Jun 18  2014 DO_NOT_DELETE
drwxr-xr-x 1 admin admin 124 Aug 28  2014 phpsysinfo
drwxr-xr-x 1 root  root   92 Nov 10  2014 rsyslog-app
drwxr-xr-x 1 root  root  132 Apr 16  2015 smbplus
drwxr-xr-x 1 admin admin 128 Jul 12  2015 tftpr6

Also i had instalet "btsync" & "transmission", and i instaled from command line "mc", "screen" and for some timre "tor".

[sokol_44]

So....

After a week without answer i decided to try factory reset.

Now i have box stuck at 99% Booting without SSH access 😞

Lucky i have coppied `core-readynasd` if somebody wants to help me with that problem 😕

Help......

[mdgm-ntgr · Accepted solution]

A factory reset was a rather drastic step to take. I have sent you a PM.

[sokol_44]

It was probably memory problem, it was solved by RMA and new chasis (with computer)