× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973

Re : ReadyNas OS 6.6.0 upgrade failed and break NAS

J_Balcer
Aspirant

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

@BarcaXtreme Your situation seems almost identical to mine. I've formatted USB drives with default settings (that is FAT32 and blocksize 4096), tried 10 different ones and almost immediately after their initialization on the NAS, the LCD screen displayed "Failed!".

 

@mdgm-ntgr I left the NAS powered on for over 10 minutes and it was still flashing Power and Backup lights. I had to pull the plug to power it down. BTW I got RMA and on Monday my unit goes to the service.

Model: RN10400|ReadyNAS 100 Series 4- Bay (Diskless)
Message 26 of 40
BarcaXtreme
Aspirant

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

Hi, yes. I've created the drives according to the How do I use the USB Recovery Tool on my ReadyNAS OS 6 storage system?

All are FAT32 formatted. I've checked the drives after running the app and the correct files on on the USB drive. 

 

I've left the NAS on for over 10 min and both the Power and Backup lights just keep flashing. It doesn't power off at any point. The message on the screen doesn't change either. "Boot from USB Failed!"

Message 27 of 40
adrien60
Tutor

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

I searched in logs files, but i don't see anything between the time the NAS shut down for 6.6 upgrade, and the time it boot up to install 6.5.2 in recovery.

 

It looks like it doesn't start to install 6.6.0, and it fail with error "do_exit+8ec" message displayed on the LCD.

Model: RN104|ReadyNAS 100 Series
Message 28 of 40
adrien60
Tutor

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

I managed to plug a serial console to the RN104, and here is what I have on boot :

 

 


BootROM 1.08
Booting from NAND flash


General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20)
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0001
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:56:14) Marvell version: v2011.12 2014_T2.0p1
06/23/2015 ReadyNAS-104 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:            0x1feef000:0x1ff9f514
       BSS:             0x1ffef8a0
       Stack:           0x1f9eeef8
       Heap:            0x1f9ef000:0x1feef000

NAND:  (ID 0xf1ad)      128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000000160000

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII0 Phy
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   egiga0, egiga1 [PRIME]
Power On!

FDT loaded successfully
Delay 7s then power on another group of HDDs 1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x200000, size 0x400000
 4194304 bytes read: OK

NAND read: device 0 offset 0x800000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.1.30.armada.1
   Created:      2016-09-22  23:39:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3595632 Bytes = 3.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
   Image Name:   initramfs
   Created:      2016-09-27   0:56:45 UTC
   Image Type:   ARM Linux RAMDisk Image (lzma compressed)
   Data Size:    3291883 Bytes = 3.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x01000000
   Loading Kernel Image ... OK
   Loading Ramdisk to 1f6ca000, end 1f9edaeb ... OK
   Using Device Tree in place at 01000000, end 010068e5
Updating device tree successful

Starting kernel ...


Starting the boot process...
Detected system type: RN104
Loading kernel modules...done
UBI device number 0, total 920 LEBs (116817920 bytes, 111.4 MiB), available 9 LEBs (1142784 bytes, 1.1 MiB), LEB size 126976 bytes (124.0 KiB)
[    7.993559] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    7.993559]
[    8.002752] CPU: 0 PID: 1 Comm: init Tainted: P           O    4.1.30.armada.1 #1
[    8.010269] Hardware name: Marvell Armada 370/XP (Device Tree)
[    8.016167] [<c0015cd0>] (unwind_backtrace) from [<c0011f38>] (show_stack+0x10/0x18)
[    8.023958] [<c0011f38>] (show_stack) from [<c06bb964>] (dump_stack+0x78/0x9c)
[    8.031219] [<c06bb964>] (dump_stack) from [<c06b74a0>] (panic+0x94/0x208)
[    8.038142] [<c06b74a0>] (panic) from [<c0025f20>] (do_exit+0x8f0/0x930)
[    8.044881] [<c0025f20>] (do_exit) from [<c0026020>] (do_group_exit+0x48/0xbc)
[    8.052150] [<c0026020>] (do_group_exit) from [<c002f108>] (get_signal+0x330/0x62c)
[    8.059845] [<c002f108>] (get_signal) from [<c06b6f94>] (do_signal+0x7c/0x350)
[    8.067104] [<c06b6f94>] (do_signal) from [<c001191c>] (do_work_pending+0xa4/0xbc)
[    8.074712] [<c001191c>] (do_work_pending) from [<c000f46c>] (work_pending+0xc/0x20)
[    8.181265] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    8.181265]

Message 29 of 40
adrien60
Tutor

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

I tried 6.6.0 RC1 and RC2, same kernel panic...

Model: RN104|ReadyNAS 100 Series
Message 30 of 40
adrien60
Tutor

Re : ReadyNas OS 6.6.0 upgrade failed and break NAS

I tried to remove all disks, but the result is the same.
So it means the kernel panic occurs before loading what is on disks.
So that can't be caused by an installed app...
Message 31 of 40
adrien60
Tutor

Re : ReadyNas OS 6.6.0 upgrade failed and break NAS

I tried to put a spare disk, install 6.5.2, Factory reset, all is OK.
Then upgrade to 6.6.0, same error again.
Message 32 of 40
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS


@adrien60 wrote:

I managed to plug a serial console to the RN104, and here is what I have on boot :

 


Wow. I didn't expect that to be tried, but that output is useful.

Message 33 of 40
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

adrien60's system is fixed.

Message 34 of 40
BarcaXtreme
Aspirant

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

Guess that leaves me. I was considering an OS reinstall from the boot menu since I still haven't been able to make it work from a USB drive

 

Message 35 of 40
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

I don't think an OS Re-install will resolve this. I have sent you a PM.

Message 36 of 40
Brauni
Aspirant

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

Hi,

 

i have exact the same problem. Nothing of the solutions here work for me.

 

Please help.

Message 37 of 40
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

Hi Brauni,

 

so you also get the do_exit+8ec error? I have sent you a PM.

Message 38 of 40
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

O.K. So Brauni and BarcaXtreme get "Boot from USB failed!" no matter which USB keys they try.

 

Please make sure you are using e.g. FAT32 and are using the MBR (Master Boot Record partition scheme).

 

All the USB keys failing seems to suggest hardware failure.

 

If the NAS can boot from USB as in adrien60's case then this should be fixable remotely.

Message 39 of 40
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas OS 6.6.0 upgrade failed and break NAS

If your hardware has failed and an RMA is needed then you should use a scratch disk (must not be from your array) to upgrade the firmware on the replacement NAS following the recommended upgrade path. Then after verifying it has come up fine on 6.6.0 power down, remove the scratch disk and move your disks across keeping the order the same.

 

I'm locking this thread. It's best if new examples of this problem should they occur are discussed in new threads so it is easier to track, especially as this thread already has an accepted solution.

Message 40 of 40
Top Contributors
Discussion stats
  • 39 replies
  • 5947 views
  • 2 kudos
  • 6 in conversation
Announcements