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

RN204 can't start

Alein
Aspirant

RN204 can't start

Hi,

I have a problem with RN204.

 

Something is wrong with USB, I am not soure what. but this is log.

 

 

Annapurna Labs stage 2: stage2_eth3_ram_loader v1.49.9
Executing next!
Annapurna Labs stage 2: stage2.5_loader v1.49.9
SPD I2C Address:00000050
Executing next!


Stage 3 2013.10-alpine_spl-1.49.d-00659-ge082932 (Nov 19 2014 - 16:21:12)

DRAM: 2 GiB
EEPROM Revision ID = 32
Device ID = a212
Device Info: AL21200-1400
Loading DT to 00100000 (16813 bytes)...
Board config ID: Netgear NAS RN20x
SRAM agent up: agent_wakeup v1.49
Loading U-Boot to 00100000 (401888 bytes)...
Executing U-Boot...


U-Boot 2013.10-alpine_db-1.49 (Jan 08 2016 - 10:41:23)
01/08/2016 ReadyNAS-200 V1.1

Annapurna Labs
Board: Alpine Development Board
I2C: ready
DRAM: 2 GiB
eeprom_per_device_init: no valid information found!
power_init_board: EEPROM per device information is not valid - using defaults!
Board config ID: Netgear NAS RN20x
dt_based_init: ETH params initialization failed!
ac_adapter_plug_in = 1
NAND: 128 MiB
00:01.0 - 1c36:0001 - Network controller
00:03.0 - 1c36:0001 - Network controller
00:04.0 - 1c36:0011 - Cryptographic device
00:05.0 - 1c36:0021 - Base system peripheral
00:09.0 - 1c36:0031 - Mass storage controller
PCIE_0: Link up. Speed 5GT/s Width x1
01:00.0 - 1b21:0612 - Mass storage controller
PCIE_1: Link up. Speed 5GT/s Width x1
02:00.0 - 1b6f:7052 - Serial bus controller
In: serial
Out: serial
Err: serial
Net: , al_eth1 [PRIME], al_eth3
mn=01, hr=00, dt=00
!!!!AC-failure!!!!
Power On!
SERDES 2, p4, pma, reg[13][4:4] <= 0x00
SERDES 2, p4, pma, reg[15][2:0] <= 0x02
Found 0 Disks!
Hit any key to stop autoboot: 0
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
(Re)start USB...
USB0: Register 8000450 NbrPorts 8
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
Annapurna Labs stage 2: stage2_eth3_ram_loader v1.49.9
Executing next!
Annapurna Labs stage 2: stage2.5_loader v1.49.9
SPD I2C Address:00000050
Executing next!

 

I can't  flash this unit with new FW. It looks fine, but after restart problem is like in 1st log

 

Annapurna Labs
Board: Alpine Development Board
I2C: ready
DRAM: 2 GiB
eeprom_per_device_init: no valid information found!
power_init_board: EEPROM per device information is not valid - using defaults!
Board config ID: Netgear NAS RN20x
dt_based_init: ETH params initialization failed!
ac_adapter_plug_in = 0
NAND: 128 MiB
00:01.0 - 1c36:0001 - Network controller
00:03.0 - 1c36:0001 - Network controller
00:04.0 - 1c36:0011 - Cryptographic device
00:05.0 - 1c36:0021 - Base system peripheral
00:09.0 - 1c36:0031 - Mass storage controller
PCIE_0: Link up. Speed 5GT/s Width x1
01:00.0 - 1b21:0612 - Mass storage controller
PCIE_1: Link up. Speed 5GT/s Width x1
02:00.0 - 1b6f:7052 - Serial bus controller
In: serial
Out: serial
Err: serial
Net: , al_eth1 [PRIME], al_eth3
mn=01, hr=00, dt=00
Power On!
SERDES 2, p4, pma, reg[13][4:4] <= 0x00
SERDES 2, p4, pma, reg[15][2:0] <= 0x02
Found 0 Disks!
Hit any key to stop autoboot: 0
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
(Re)start USB...
USB0: Register 8000450 NbrPorts 8
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
reading uImage-recovery
3746824 bytes read in 1992 ms (1.8 MiB/s)
reading initrd-recovery.gz
2733998 bytes read in 1462 ms (1.8 MiB/s)
gpio: pin 33 (gpio 33) value is 1
## Booting kernel from Legacy Image at 08000000 ...
Image Name: Linux-4.1.7.alpine.1
Created: 2015-09-25 18:43:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3746760 Bytes = 3.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08800000 ...
Image Name: initramfs
Created: 2016-12-21 6:08:04 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 2733934 Bytes = 2.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 07000000
Booting using the fdt blob at 0x7000000
Loading Kernel Image ... OK
reserving fdt memory region: addr=0 size=100000
Loading Ramdisk to 0189d000, end 01b3876e ... OK
Using Device Tree in place at 07000000, end 07008bd3

Starting kernel ...

pci 0002:00:00.0: can't enable device: BAR 0 [mem 0x00000000-0x00000fff] not claimed
pci 0002:00:00.0: Error enabling bridge (-22), continuing
pci 0002:01:00.0: can't enable device: BAR 0 [mem 0xe8000000-0xe8007fff 64bit] not claimed
Start to run USB Recovery...
Get systype=rn204
Searching for external boot flash device...sda
UBI device number 0, total 800 LEBs (101580800 bytes, 96.9 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
Internal flash attached
Searching for internal boot flash device...mtd rootfs: ubi0_0
Erasing 128 Kibyte @ 5e0000 -- 100 % complete
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
Writing data to block 16 at offset 0x200000
Writing data to block 17 at offset 0x220000
Writing data to block 18 at offset 0x240000
Writing data to block 19 at offset 0x260000
Writing data to block 20 at offset 0x280000
Writing data to block 21 at offset 0x2a0000
Writing data to block 22 at offset 0x2c0000
Writing data to block 23 at offset 0x2e0000
Writing data to block 24 at offset 0x300000
Erasing 128 Kibyte @ 3e0000 -- 100 % complete
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
Writing data to block 16 at offset 0x200000
Writing data to block 17 at offset 0x220000
done
reboot: Power down
õAnnapurna Labs stage 2: stage2_eth3_ram_loader v1.49.9
Executing next!
Annapurna Labs stage 2: stage2.5_loader v1.49.9
SPD I2C Address:00000050
Executing next!

 

 

Any idea what I can do about it?

 

Model: RN204|ReadyNAS204
Message 1 of 14
JennC
NETGEAR Employee Retired

Re: RN202 can't start

Hello Alein,

 

What exactly is happening when you try to use the USB ports of the NAS? Are you trying to use it to backup some data? Please give more details of the problem aside from the logs.

 

Regards,

Message 2 of 14
Alein
Aspirant

Re: RN202 can't start

Hi,

Well, you didn't specify how I use USB front port.

 

So from beginning.

 

I am trying start NAS, I can not. I am getting error

 

[Thu May 11 19:01:29.803 2017] Starting the controller
[Thu May 11 19:01:29.803 2017] USB XHCI 1.00
[Thu May 11 19:01:29.804 2017] scanning bus 0 for devices... 1 USB Device(s) found
[Thu May 11 19:01:29.929 2017] scanning usb for storage devices... 0 Storage Device(s) found
[Thu May 11 19:01:29.991 2017] ** Bad device usb 0 **

 

So, I am trying to reinstall OS, or factory default. But after I am in boot many, I am not able to change options, there is only factory default, but I can not push it father. However, I am able to start NAS with recovery USB connected, and then NAS is recognizing it and trying to flash.

 

[Thu May 11 19:03:44.313 2017] U-Boot 2013.10-alpine_db-1.49 (Jan 08 2016 - 10:41:23)
[Thu May 11 19:03:44.313 2017] 01/08/2016 ReadyNAS-200 V1.1
[Thu May 11 19:03:44.328 2017]
[Thu May 11 19:03:44.328 2017] Annapurna Labs
[Thu May 11 19:03:44.328 2017] Board: Alpine Development Board
[Thu May 11 19:03:44.344 2017] I2C: ready
[Thu May 11 19:03:44.344 2017] DRAM: 2 GiB
[Thu May 11 19:03:44.376 2017] eeprom_per_device_init: no valid information found!
[Thu May 11 19:03:44.376 2017] power_init_board: EEPROM per device information is not valid - using defaults!
[Thu May 11 19:03:44.424 2017] Board config ID: Netgear NAS RN20x
[Thu May 11 19:03:44.509 2017] dt_based_init: ETH params initialization failed!
[Thu May 11 19:03:44.524 2017] ac_adapter_plug_in = 0
[Thu May 11 19:03:44.618 2017] NAND: 128 MiB
[Thu May 11 19:03:46.376 2017] 00:01.0 - 1c36:0001 - Network controller
[Thu May 11 19:03:46.456 2017] 00:03.0 - 1c36:0001 - Network controller
[Thu May 11 19:03:46.456 2017] 00:04.0 - 1c36:0011 - Cryptographic device
[Thu May 11 19:03:46.456 2017] 00:05.0 - 1c36:0021 - Base system peripheral
[Thu May 11 19:03:46.456 2017] 00:09.0 - 1c36:0031 - Mass storage controller
[Thu May 11 19:03:46.500 2017] PCIE_0: Link up. Speed 5GT/s Width x1
[Thu May 11 19:03:46.500 2017] 01:00.0 - 1b21:0612 - Mass storage controller
[Thu May 11 19:03:46.674 2017] PCIE_1: Link up. Speed 5GT/s Width x1
[Thu May 11 19:03:46.674 2017] 02:00.0 - 1b6f:7052 - Serial bus controller
[Thu May 11 19:03:46.674 2017] In: serial
[Thu May 11 19:03:46.674 2017] Out: serial
[Thu May 11 19:03:46.674 2017] Err: serial
[Thu May 11 19:03:46.674 2017] Net: , al_eth1 [PRIME], al_eth3
[Thu May 11 19:03:46.692 2017] mn=11, hr=00, dt=00
[Thu May 11 19:03:47.892 2017] Power On!
[Thu May 11 19:03:49.113 2017] SERDES 2, p4, pma, reg[13][4:4] <= 0x00
[Thu May 11 19:03:49.113 2017] SERDES 2, p4, pma, reg[15][2:0] <= 0x02
[Thu May 11 19:03:49.128 2017] Found 1 Disks!
[Thu May 11 19:03:49.128 2017] Hit any key to stop autoboot: 0
[Thu May 11 19:03:49.238 2017] bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
[Thu May 11 19:03:49.253 2017] (Re)start USB...
[Thu May 11 19:03:49.253 2017] USB0: Register 8000450 NbrPorts 8
[Thu May 11 19:03:49.253 2017] Starting the controller
[Thu May 11 19:03:49.269 2017] USB XHCI 1.00
[Thu May 11 19:03:49.269 2017] scanning bus 0 for devices... 2 USB Device(s) found
[Thu May 11 19:03:50.207 2017] scanning usb for storage devices... 1 Storage Device(s) found
[Thu May 11 19:03:50.300 2017] reading uImage-recovery
[Thu May 11 19:03:52.288 2017] 3746824 bytes read in 1991 ms (1.8 MiB/s)
[Thu May 11 19:03:52.288 2017] reading initrd-recovery.gz
[Thu May 11 19:03:53.748 2017] 2733998 bytes read in 1461 ms (1.8 MiB/s)
[Thu May 11 19:03:53.810 2017] gpio: pin 33 (gpio 33) value is 1
[Thu May 11 19:03:53.826 2017] ## Booting kernel from Legacy Image at 08000000 ...
[Thu May 11 19:03:53.826 2017] Image Name: Linux-4.1.7.alpine.1
[Thu May 11 19:03:53.826 2017] Created: 2015-09-25 18:43:37 UTC
[Thu May 11 19:03:53.843 2017] Image Type: ARM Linux Kernel Image (uncompressed)
[Thu May 11 19:03:53.843 2017] Data Size: 3746760 Bytes = 3.6 MiB
[Thu May 11 19:03:53.843 2017] Load Address: 00008000
[Thu May 11 19:03:53.843 2017] Entry Point: 00008000
[Thu May 11 19:03:53.843 2017] Verifying Checksum ... OK
[Thu May 11 19:03:54.265 2017] ## Loading init Ramdisk from Legacy Image at 08800000 ...
[Thu May 11 19:03:54.265 2017] Image Name: initramfs
[Thu May 11 19:03:54.280 2017] Created: 2016-12-21 6:08:04 UTC
[Thu May 11 19:03:54.296 2017] Image Type: ARM Linux RAMDisk Image (lzma compressed)
[Thu May 11 19:03:54.296 2017] Data Size: 2733934 Bytes = 2.6 MiB
[Thu May 11 19:03:54.296 2017] Load Address: 00000000
[Thu May 11 19:03:54.296 2017] Entry Point: 00000000
[Thu May 11 19:03:54.296 2017] Verifying Checksum ... OK
[Thu May 11 19:03:54.579 2017] ## Flattened Device Tree blob at 07000000
[Thu May 11 19:03:54.595 2017] Booting using the fdt blob at 0x7000000
[Thu May 11 19:03:54.595 2017] Loading Kernel Image ... OK
[Thu May 11 19:03:55.166 2017] reserving fdt memory region: addr=0 size=100000
[Thu May 11 19:03:55.182 2017] Loading Ramdisk to 0189d000, end 01b3876e ... OK
[Thu May 11 19:03:55.668 2017] Using Device Tree in place at 07000000, end 07008bd3
[Thu May 11 19:03:55.715 2017]
[Thu May 11 19:03:55.715 2017] Starting kernel ...
[Thu May 11 19:03:55.715 2017]
[Thu May 11 19:04:01.169 2017] pci 0002:00:00.0: can't enable device: BAR 0 [mem 0x00000000-0x00000fff] not claimed
[Thu May 11 19:04:01.169 2017] pci 0002:00:00.0: Error enabling bridge (-22), continuing
[Thu May 11 19:04:01.169 2017] pci 0002:01:00.0: can't enable device: BAR 0 [mem 0xe8000000-0xe8007fff 64bit] not claimed
[Thu May 11 19:04:02.045 2017] Start to run USB Recovery...
[Thu May 11 19:04:02.123 2017] Get systype=rn204
[Thu May 11 19:04:02.204 2017] Searching for external boot flash device...sdb
[Thu May 11 19:04:07.298 2017] UBI device number 0, total 800 LEBs (101580800 bytes, 96.9 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
[Thu May 11 19:04:07.313 2017] Internal flash attached
[Thu May 11 19:04:07.391 2017] Searching for internal boot flash device...mtd rootfs: ubi0_0
[Thu May 11 19:04:07.813 2017] Writing internal nand flash device...Erasing 128 Kibyte @ 0 -- 0 % complete Erasing 128 Kibyte @ 20000 -- 7 % complete Erasing 128 Kibyte @ 40000 -- 14 % complete Erasing 128 Kibyte @ 60000 -- 21 % complete Erasing 128 Kibyte @ 80000 -- 28 % complete Erasing 128 Kibyte @ a0000 -- 35 % complete Erasing 128 Kibyte @ c0000 -- 42 % complete Erasing 128 Kibyte @ e0000 -- 50 % complete Erasing 128 Kibyte @ 100000 -- 57 % complete Erasing 128 Kibyte @ 120000 -- 64 % complete Erasing 128 Kibyte @ 140000 -- 71 % complete Erasing 128 Kibyte @ 160000 -- 78 % complete Erasing 128 Kibyte @ 180000 -- 85 % complete Erasing 128 Kibyte @ 1a0000 -- 92 % complete Erasing 128 Kibyte @ 1a0000 -- 100 % complete
[Thu May 11 19:04:14.140 2017] Writing data to block 0 at offset 0x0
[Thu May 11 19:04:14.140 2017] Writing data to block 1 at offset 0x20000
[Thu May 11 19:04:14.155 2017] Writing data to block 2 at offset 0x40000
[Thu May 11 19:04:14.171 2017] Writing data to block 3 at offset 0x60000
[Thu May 11 19:04:14.186 2017] Writing data to block 4 at offset 0x80000
[Thu May 11 19:04:14.218 2017] Writing data to block 5 at offset 0xa0000
[Thu May 11 19:04:14.249 2017] Writing data to block 6 at offset 0xc0000
[Thu May 11 19:04:14.264 2017] Writing data to block 7 at offset 0xe0000
[Thu May 11 19:04:14.296 2017] Writing data to block 8 at offset 0x100000

 

Message 3 of 14
Alein
Aspirant

Re: RN202 can't start

[Thu May 11 19:04:14.296 2017] done
[Thu May 11 19:04:14.311 2017] Erasing 128 Kibyte @ 0 -- 0 % complete Erasing 128 Kibyte @ 20000 -- 2 % complete Erasing 128 Kibyte @ 40000 -- 4 % complete Erasing 128 Kibyte @ 60000 -- 6 % complete Erasing 128 Kibyte @ 80000 -- 8 % complete Erasing 128 Kibyte @ a0000 -- 10 % complete Erasing 128 Kibyte @ c0000 -- 12 % complete Erasing 128 Kibyte @ e0000 -- 14 % complete Erasing 128 Kibyte @ 100000 -- 16 % complete Erasing 128 Kibyte @ 120000 -- 18 % complete Erasing 128 Kibyte @ 140000 -- 20 % complete Erasing 128 Kibyte @ 160000 -- 22 % complete Erasing 128 Kibyte @ 180000 -- 25 % complete Erasing 128 Kibyte @ 1a0000 -- 27 % complete Erasing 128 Kibyte @ 1c0000 -- 29 % complete Erasing 128 Kibyte @ 1e0000 -- 31 % complete Erasing 128 Kibyte @ 200000 -- 33 % complete Erasing 128 Kibyte @ 220000 -- 35 % complete Erasing 128 Kibyte @ 240000 -- 37 % complete Erasing 128 Kibyte @ 260000 -- 39 % complete Erasing 128 Kibyte @ 280000 -- 41 % complete Erasing 128 Kibyte @ 2a0000 -- 43 % complete Erasing 128 Kibyte @ 2c0000 -- 45 % complete Erasing 128 Kibyte @ 2e0000 -- 47 % complete Erasing 128 Kibyte @ 300000 -- 50 % complete Erasing 128 Kibyte @ 320000 -- 52 % complete Erasing 128 Kibyte @ 340000 -- 54 % complete Erasing 128 Kibyte @ 360000 -- 56 % complete Erasing 128 Kibyte @ 380000 -- 58 % complete Erasing 128 Kibyte @ 3a0000 -- 60 % complete Erasing 128 Kibyte @ 3c0000 -- 62 % complete Erasing 128 Kibyte @ 3e0000 -- 64 % complete Erasing 128 Kibyte @ 400000 -- 66 % complete Erasing 128 Kibyte @ 420000 -- 68 % complete Erasing 128 Kibyte @ 440000 -- 70 % complete Erasing 128 Kibyte @ 460000 -- 72 % complete Erasing 128 Kibyte @ 480000 -- 75 % complete Erasing 128 Kibyte @ 4a0000 -- 77 % complete Erasing 128 Kibyte @ 4c0000 -- 79 % complete Erasing 128 Kibyte @ 4e0000 -- 81 % complete Erasing 128 Kibyte @ 500000 -- 83 % complete Erasing 128 Kibyte @ 520000 -- 85 % complete Erasing 128 Kibyte @ 540000 -- 87 % complete Erasing 128 Kibyte @ 560000 -- 89 % complete Erasing 128 Kibyte @ 580000 -- 91 % complete Erasing 128 Kibyte @ 5a0000 -- 93 % complete Erasing 128 Kibyte @ 5c0000 -- 95 % complete Erasing 128 Kibyte @ 5e0000 -- 97 % complete Erasing 128 Kibyte @ 5e0000 -- 100 % complete
[Thu May 11 19:04:14.498 2017] Writing data to block 0 at offset 0x0
[Thu May 11 19:04:14.514 2017] Writing data to block 1 at offset 0x20000
[Thu May 11 19:04:14.514 2017] Writing data to block 2 at offset 0x40000
[Thu May 11 19:04:14.514 2017] Writing data to block 3 at offset 0x60000
[Thu May 11 19:04:14.514 2017] Writing data to block 4 at offset 0x80000
[Thu May 11 19:04:14.530 2017] Writing data to block 5 at offset 0xa0000
[Thu May 11 19:04:14.530 2017] Writing data to block 6 at offset 0xc0000
[Thu May 11 19:04:14.561 2017] Writing data to block 7 at offset 0xe0000
[Thu May 11 19:04:14.576 2017] Writing data to block 8 at offset 0x100000
[Thu May 11 19:04:14.608 2017] Writing data to block 9 at offset 0x120000
[Thu May 11 19:04:14.639 2017] Writing data to block 10 at offset 0x140000
[Thu May 11 19:04:14.654 2017] Writing data to block 11 at offset 0x160000
[Thu May 11 19:04:14.686 2017] Writing data to block 12 at offset 0x180000
[Thu May 11 19:04:14.717 2017] Writing data to block 13 at offset 0x1a0000
[Thu May 11 19:04:14.732 2017] Writing data to block 14 at offset 0x1c0000
[Thu May 11 19:04:14.764 2017] Writing data to block 15 at offset 0x1e0000
[Thu May 11 19:04:14.779 2017] Writing data to block 16 at offset 0x200000
[Thu May 11 19:04:14.810 2017] Writing data to block 17 at offset 0x220000
[Thu May 11 19:04:14.842 2017] Writing data to block 18 at offset 0x240000
[Thu May 11 19:04:14.857 2017] Writing data to block 19 at offset 0x260000
[Thu May 11 19:04:14.888 2017] Writing data to block 20 at offset 0x280000
[Thu May 11 19:04:14.920 2017] Writing data to block 21 at offset 0x2a0000
[Thu May 11 19:04:14.935 2017] Writing data to block 22 at offset 0x2c0000
[Thu May 11 19:04:14.966 2017] Writing data to block 23 at offset 0x2e0000
[Thu May 11 19:04:14.998 2017] Writing data to block 24 at offset 0x300000
[Thu May 11 19:04:15.013 2017] Writing data to block 25 at offset 0x320000
[Thu May 11 19:04:15.044 2017] Writing data to block 26 at offset 0x340000
[Thu May 11 19:04:15.076 2017] Writing data to block 27 at offset 0x360000
[Thu May 11 19:04:15.091 2017] Erasing 128 Kibyte @ 0 -- 0 % complete Erasing 128 Kibyte @ 20000 -- 3 % complete Erasing 128 Kibyte @ 40000 -- 6 % complete Erasing 128 Kibyte @ 60000 -- 9 % complete Erasing 128 Kibyte @ 80000 -- 12 % complete Erasing 128 Kibyte @ a0000 -- 15 % complete Erasing 128 Kibyte @ c0000 -- 18 % complete Erasing 128 Kibyte @ e0000 -- 21 % complete Erasing 128 Kibyte @ 100000 -- 25 % complete Erasing 128 Kibyte @ 120000 -- 28 % complete Erasing 128 Kibyte @ 140000 -- 31 % complete Erasing 128 Kibyte @ 160000 -- 34 % complete Erasing 128 Kibyte @ 180000 -- 37 % complete Erasing 128 Kibyte @ 1a0000 -- 40 % complete Erasing 128 Kibyte @ 1c0000 -- 43 % complete Erasing 128 Kibyte @ 1e0000 -- 46 % complete Erasing 128 Kibyte @ 200000 -- 50 % complete Erasing 128 Kibyte @ 220000 -- 53 % complete Erasing 128 Kibyte @ 240000 -- 56 % complete Erasing 128 Kibyte @ 260000 -- 59 % complete Erasing 128 Kibyte @ 280000 -- 62 % complete Erasing 128 Kibyte @ 2a0000 -- 65 % complete Erasing 128 Kibyte @ 2c0000 -- 68 % complete Erasing 128 Kibyte @ 2e0000 -- 71 % complete Erasing 128 Kibyte @ 300000 -- 75 % complete Erasing 128 Kibyte @ 320000 -- 78 % complete Erasing 128 Kibyte @ 340000 -- 81 % complete Erasing 128 Kibyte @ 360000 -- 84 % complete Erasing 128 Kibyte @ 380000 -- 87 % complete Erasing 128 Kibyte @ 3a0000 -- 90 % complete Erasing 128 Kibyte @ 3c0000 -- 93 % complete Erasing 128 Kibyte @ 3e0000 -- 96 % complete Erasing 128 Kibyte @ 3e0000 -- 100 % complete
[Thu May 11 19:04:15.232 2017] Writing data to block 0 at offset 0x0
[Thu May 11 19:04:15.232 2017] Writing data to block 1 at offset 0x20000
[Thu May 11 19:04:15.232 2017] Writing data to block 2 at offset 0x40000
[Thu May 11 19:04:15.247 2017] Writing data to block 3 at offset 0x60000
[Thu May 11 19:04:15.247 2017] Writing data to block 4 at offset 0x80000
[Thu May 11 19:04:15.263 2017] Writing data to block 5 at offset 0xa0000
[Thu May 11 19:04:15.294 2017] Writing data to block 6 at offset 0xc0000
[Thu May 11 19:04:15.325 2017] Writing data to block 7 at offset 0xe0000
[Thu May 11 19:04:15.341 2017] Writing data to block 8 at offset 0x100000
[Thu May 11 19:04:15.372 2017] Writing data to block 9 at offset 0x120000
[Thu May 11 19:04:15.403 2017] Writing data to block 10 at offset 0x140000
[Thu May 11 19:04:15.419 2017] Writing data to block 11 at offset 0x160000
[Thu May 11 19:04:15.450 2017] Writing data to block 12 at offset 0x180000
[Thu May 11 19:04:15.481 2017] Writing data to block 13 at offset 0x1a0000
[Thu May 11 19:04:15.497 2017] Writing data to block 14 at offset 0x1c0000
[Thu May 11 19:04:15.528 2017] Writing data to block 15 at offset 0x1e0000
[Thu May 11 19:04:15.559 2017] Writing data to block 16 at offset 0x200000
[Thu May 11 19:04:15.575 2017] Writing data to block 17 at offset 0x220000
[Thu May 11 19:04:15.606 2017] Writing data to block 18 at offset 0x240000
[Thu May 11 19:04:15.637 2017] Writing data to block 19 at offset 0x260000
[Thu May 11 19:04:15.653 2017] Writing data to block 20 at offset 0x280000
[Thu May 11 19:04:15.686 2017] Writing data to block 21 at offset 0x2a0000
[Thu May 11 19:04:15.701 2017] Writing data to block 22 at offset 0x2c0000
[Thu May 11 19:04:15.733 2017] Writing data to block 23 at offset 0x2e0000
[Thu May 11 19:04:15.764 2017] Writing data to block 24 at offset 0x300000
[Thu May 11 19:04:15.779 2017] Writing data to block 25 at offset 0x320000
[Thu May 11 19:04:27.457 2017] done
[Thu May 11 19:04:27.661 2017] reboot: Power down

 

 

After start, whole problem is starting from beginning.

 

I was trying to remove USB recovery during boot, and I was able to get some command line, but without success doing something usefully.

 

I also was able to stop boot, and get some env variables.

 

All logs I will send you on priv, as there is serial number.

Message 4 of 14
StephenB
Guru

Re: RN202 can't start


@Alein wrote:

 

 

All logs I will send you on priv, as there is serial number.


https://kb.netgear.com/21543/How-do-I-send-all-logs-to-ReadyNAS-Community-moderators

Message 5 of 14
Alein
Aspirant

Re: RN202 can't start

Done

e-mail topic like on forum

"RN204 can't start"

Message 6 of 14
mdgm-ntgr
NETGEAR Employee Retired

Re: RN202 can't start

I can see in your console log that it booted into debug mode at some point. Can you boot it back into that and then PM me the 5-digit number that you then get in RAIDar?

Message 7 of 14
Alein
Aspirant

Re: RN202 can't start

Hi,

At the end of the log  I was trying to boot from your image, but there was not 5 digits code.

 

WARN halted endpoint.

 

One time I took out pendrive with oryginal image during boot before it starts writing image to flash, but I get on screen 

 

DEBUG: $PORT

$IP Recovery

 

[Thu May 11 19:19:30.154 2017] Get systype=rn204
[Thu May 11 19:19:30.213 2017] Searching for external boot flash device...Could not find external boot flash!
[Thu May 11 19:19:51.849 2017] ERROR: Could not find external flash device!!  | disconnected USB with oryginal image
[Thu May 11 19:19:51.864 2017] Booting into debug mode...
[Thu May 11 19:19:51.942 2017] udhcpc (v1.21.1) started

 

 

 

So, what else I can do?

 

 

 

Message 8 of 14
Alein
Aspirant

Re: RN202 can't start

By Raidar you mean external application? not OS6 LCD,console?

 

https://www.downloads.netgear.com/files/GDC/READYNAS-COMMON/RAIDar_6.3.0.exe

 

If yes, I will try after work

 

Message 9 of 14
StephenB
Guru

Re: RN202 can't start


@Alein wrote:

By Raidar you mean external application? not OS6 LCD,console?

 

 


That is what he means.  It's possible the code is also on the LCD console - I've never looked to see.

Message 10 of 14
Alein
Aspirant

Re: RN202 can't start

That is all what I am getting

 

2017.05.12 17-12-55.jpg

 

 

 

 

U-Boot 2013.10-alpine_db-1.49 (Jan 08 2016 - 10:41:23)
01/08/2016 ReadyNAS-200 V1.1

Annapurna Labs
Board: Alpine Development Board
I2C: ready
DRAM: 2 GiB
eeprom_per_device_init: no valid information found!
power_init_board: EEPROM per device information is not valid - using defaults!
Board config ID: Netgear NAS RN20x
dt_based_init: ETH params initialization failed!
ac_adapter_plug_in = 0
NAND: 128 MiB
00:01.0 - 1c36:0001 - Network controller
00:03.0 - 1c36:0001 - Network controller
00:04.0 - 1c36:0011 - Cryptographic device
00:05.0 - 1c36:0021 - Base system peripheral
00:09.0 - 1c36:0031 - Mass storage controller
PCIE_0: Link up. Speed 5GT/s Width x1
01:00.0 - 1b21:0612 - Mass storage controller
PCIE_1: Link up. Speed 5GT/s Width x1
02:00.0 - 1b6f:7052 - Serial bus controller
In: serial
Out: serial
Err: serial
Net: , al_eth1 [PRIME], al_eth3
mn=11, hr=00, dt=00
Power On!
SERDES 2, p4, pma, reg[13][4:4] <= 0x00
SERDES 2, p4, pma, reg[15][2:0] <= 0x02
Found 1 Disks!
Hit any key to stop autoboot: 0
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
(Re)start USB...
USB0: Register 8000450 NbrPorts 8
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
reading uImage-recovery
3746824 bytes read in 1992 ms (1.8 MiB/s)
reading initrd-recovery.gz
2733998 bytes read in 1461 ms (1.8 MiB/s)
gpio: pin 33 (gpio 33) value is 1
## Booting kernel from Legacy Image at 08000000 ...
Image Name: Linux-4.1.7.alpine.1
Created: 2015-09-25 18:43:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3746760 Bytes = 3.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08800000 ...
Image Name: initramfs
Created: 2016-12-21 6:08:04 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 2733934 Bytes = 2.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 07000000
Booting using the fdt blob at 0x7000000
Loading Kernel Image ... OK
reserving fdt memory region: addr=0 size=100000
Loading Ramdisk to 0189d000, end 01b3876e ... OK
Using Device Tree in place at 07000000, end 07008bd3

Starting kernel ...

pci 0002:00:00.0: can't enable device: BAR 0 [mem 0x00000000-0x00000fff] not claimed
pci 0002:00:00.0: Error enabling bridge (-22), continuing
pci 0002:01:00.0: can't enable device: BAR 0 [mem 0xe8000000-0xe8007fff 64bit] not claimed
Start to run USB Recovery...
Get systype=rn204
Searching for external boot flash device...Could not find external boot flash!
ERROR: Could not find external flash device!!
Booting into debug mode...
udhcpc (v1.21.1) started
grep: /etc/resolv.conf: No such file or directory
Sending discover...
Sending discover...
Sending discover...
No lease, failing
udhcpc (v1.21.1) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 172.26.12.238...
Lease of 172.26.12.238 obtained, lease time 2592000
deleting routers
route: SIOCDELRT: No such process
adding dns 172.26.12.151
adding dns 172.26.10.151
Hostid: 117AD994
/bin/ash: can't access tty; job control turned off
/ #

Message 11 of 14
Alein
Aspirant

Re: RN202 can't start

I had an idea to use 202 unit. After factory defaults I was trying to boot from new disk in 204 unit. but it seems that 204 unit has older OS. I can not downgrade 202, so is there an option to install OS from PC? or force 204 to boot from disk even if flash OS is older?

 

Message 12 of 14
mdgm-ntgr
NETGEAR Employee Retired

Re: RN202 can't start

Ah I forgot that custom USB was for older ARM units (RN100/RN2120) and based on 6.2.4.

Message 13 of 14
Alein
Aspirant

Re: RN202 can't start

ok, So what is next. What I can do?

Message 14 of 14
Top Contributors
Discussion stats
  • 13 replies
  • 5882 views
  • 0 kudos
  • 4 in conversation
Announcements