NVX - Stuck Booting - Upgrade to 4.2.18(x86)

[Jupiter1]

Download the new 4.2.18 image, upload and upgrade within the FrontView.

Reboot.

Then stuck booting several hours.

Use SSH to check the /var/log/messages, as belows:

Jupiter:/var/log# tail messages
Jul 26 00:48:25 Jupiter kernel: ata1: EH complete
Jul 26 00:48:25 Jupiter kernel: ata2.00: configured for UDMA/133
Jul 26 00:48:25 Jupiter kernel: ata2: EH complete
Jul 26 00:48:25 Jupiter kernel: ata3.00: configured for UDMA/133
Jul 26 00:48:25 Jupiter kernel: ata3: EH complete
Jul 26 00:48:25 Jupiter kernel: Adding 524272k swap on /dev/md1.  Priority:-1 extents:1 across:524272k
Jul 26 00:48:25 Jupiter kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
Jul 26 00:48:25 Jupiter kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
Jul 26 00:48:29 Jupiter syslogd 1.4.1#18: restart.
Jul 26 00:53:03 Jupiter kernel: [Hardware Error]: Machine check events logged

So, what's going on?

I've tried the Skip Checking FS mode, but no effect. Plz help.

[Jupiter1]

And no permission to run the mcelog command.

[PapaBear1]

Open an online tech support case with Netgear. Apparently the upgrade process was corrupted in some manner. When you get the case #, edit your first post and add the case # to the subject line.

Do you have a current and complete backup?

[Jupiter1]

@papabear

I don't have a backup cause the NAS is the last backup.

The great and strange news, the system is up now. I'm confused.

[PapaBear1]

The fact that it is back up is good news. The fact that you consider the the NAS as the backup is not. You have just had a close call, and I would advise you to take heed unless you really want to joint the "Lost Data" club.

Every ReadyNAS manual warns that the ReadyNAS should not be considered a backup device. RAID is a technique to combine multiple disks into a single volume and provide some redundancy so the volume can survive a disk failure. Once you then replace the failed disk, it should re-establish the array and continue. However, if you had a dual drive failure, or a failure in the unit, or catastrophic failure or theft of device, where would your data be?