Stuck booting... after updating to RAIDiator-x86-4.2.31 firmware

[steezynas]

Spoiler

My Readynas NVX was running fine until I updated to RAIDiator-x86-4.2.31 firmware in frontview. Now it is stuck booting.... I have all data backed up, but would still like to get this booting again.

[steezynas]

I booted into Tech Support mode and I do not appear to have any overly large log files that I can see. I have also tried OS Reinstall mode as well. Any suggestions other than a factory reset? 

[StephenB]

How full was the OS partition?

Did you try the boot option to skip the volume check?

If the OS partition is ok, and skipping the volume check doesn't help, then I suggest testing the disk drives in a Windows PC using vendor tools.  Use Seatools for Seagate; Lifeguard for Western Digital.

Alternatively, see if the NAS boots with disk 1 removed.  If there is no change, you can power down, and try reinserting disk 1 and removing disk 2.  Repeat until you've tried all the slots.

Note it is possible to manually mount the data volumes in tech support mode - but that won't help you get the system booting normally, and you don't need to off-load data.  So I wouldn't bother with that.

[steezynas]

RAIDar shows all disks healthy. Skipping volume check also stays stuck booting.... I know you say not to bother, but the way I was able to back up all my data was after mounting it in tech support mode. I can also see the os partition. It only shows approx 700MB of the 4GB used. I mounted my disks with:

# start_raid.sh

# mount /dev/md0 /sysroot

# mount --bind /proc /sysroot/proc
# mount --bind /dev /sysroot/dev
# mount --bind /dev/pts /sysroot/dev/pts

# chroot /sysroot /bin/bash

# vgscan
# vgchange -a y

# mount -o ro /dev/c/c /c

I will try pulling a disk to see if that helps. The fact that my raid mounted fine and I was able to extract all data should indicate the disks are okay, no?

[StephenB]

---

@steezynas wrote:

I will try pulling a disk to see if that helps. The fact that my raid mounted fine and I was able to extract all data should indicate the disks are okay, no?

---

Yes, though you might check with smartctl.

Also, the boot problem could be related to some OS volume corruption - not necessarily the data volume.

[steezynas]

I have the OS partition booted. Anything particular to look for? Tried booting earlier with 1 disk removed at a time, no luck. 

[StephenB]

---

@steezynas wrote:

I have the OS partition booted. Anything particular to look for? Tried booting earlier with 1 disk removed at a time, no luck. 

---

See how full the root is (df / -h and df / -i)

[steezynas]

# df -h
Filesystem Size Used Available Use% Mounted on

tmpfs 10.0M 0 10.0M 0% /dev
/dev/md0 4.0G 781.8M 3.0G 20% /sysroot
tmpfs 10.0M 0 10.0M 0% /sysroot/dev

[StephenB]

---

@steezynas wrote:

# df -h
Filesystem Size Used Available Use% Mounted on

tmpfs 10.0M 0 10.0M 0% /dev
/dev/md0 4.0G 781.8M 3.0G 20% /sysroot
tmpfs 10.0M 0 10.0M 0% /sysroot/dev

---

This shows that the OS partition isn't full - though if you are running ReadyDLNA you should also check the inodes with the -i option.

What add-ons do you have installed?  Have you installed or updated anything with ssh?

[steezynas]

# df -P
Filesystem 1024-blocks Used Available Capacity Mounted on
tmpfs 10240 0 10240 0% /dev
/dev/md0 4185780 800536 3175532 20% /sysroot
tmpfs 10240 0 10240 0% /sysroot/dev

# df -i
Filesystem Inodes Used Available Use% Mounted on
tmpfs 129009 142 128867 0% /dev
/dev/md0 65536 30772 34764 47% /sysroot
tmpfs 129009 142 128867 0% /sysroot/dev

Don't really have many add-ons. Didn't change anything other then updating from .28 to .31 and this problem began. I've used ssh in the past. 

At this point, a factory reset wouldn't be that big of a deal, as I managed to save my data. But I'd prefer not having to spend the time recopying it all back to the nas if I could just fix the booting issue. 

I have usb to ttl cable. I notice there is a serial port on the back. Is it possible to watch it boot up via that? Or perhaps a log file of what's happening on boot?w

[steezynas]

# df -P
Filesystem 1024-blocks Used Available Capacity Mounted on
tmpfs 10240 0 10240 0% /dev
/dev/md0 4185780 800536 3175532 20% /sysroot
tmpfs 10240 0 10240 0% /sysroot/dev

# df -i
Filesystem Inodes Used Available Use% Mounted on
tmpfs 129009 142 128867 0% /dev
/dev/md0 65536 30772 34764 47% /sysroot
tmpfs 129009 142 128867 0% /sysroot/dev

Don't really have many add-ons. Didn't change anything other then updating from .28 to .31 and this problem began. I've used ssh in the past. 

At this point, a factory reset wouldn't be that big of a deal, as I managed to save my data. But I'd prefer not having to spend the time recopying it all back to the nas if I could just fix the booting issue. 

I have usb to ttl cable. I notice there is a serial port on the back. Is it possible to watch it boot up via that? Or perhaps a log file of what's happening on boot?

[steezynas]

My response seems to keep being deleted, I'm not sure why, but I'll post it one more time.

# df -P
Filesystem 1024-blocks Used Available Capacity Mounted on
tmpfs 10240 0 10240 0% /dev
/dev/md0 4185780 800536 3175532 20% /sysroot
tmpfs 10240 0 10240 0% /sysroot/dev

# df -i
Filesystem Inodes Used Available Use% Mounted on
tmpfs 129009 142 128867 0% /dev
/dev/md0 65536 30772 34764 47% /sysroot
tmpfs 129009 142 128867 0% /sysroot/dev

Don't really have many add-ons. Didn't change anything other then updating from .28 to .31 and this problem began. I've used ssh in the past. 

At this point, a factory reset wouldn't be that big of a deal, as I managed to save my data. But I'd prefer not having to spend the time recopying it all back to the nas if I could just fix the booting issue. 

I have usb to ttl cable. I notice there is a serial port on the back. Is it possible to watch it boot up via that? Or perhaps a log file of what's happening on boot?