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

USB Recovery Failure (Reposting)

Steve89521
Aspirant

USB Recovery Failure (Reposting)

Not sure why this isn't showing up anywhere that I can see but trying again ...

Okay - At wit's end here - Applied update 6.10.2 to my RN102 and it worked on the OTHER unit I have - but this one appears to have bricked.

 

I had a good backup of the data - so that's not a problem - but the unit, when powering up holding the reset switch boots with all LEDs active - but when I attempt to cycle through the boot menu options - I can't get it to cycle through them.  All that lights after using backup button selection is "ACT" and "Power".

Then after attempting to build a USB recovery, and after starting the system successfully using USB recovery, the unit drops into "Tech Support" Mode (Firmware 6.2.4) with Serial: NONE000200000 and when I telnet into the unit there doesn't appear to be anything running that indicates that it's fixing flash, the disk, NOTHING.

This unit is (obviously) out of support so I'm kinda hosed without being able to do a factory reset.

The forums are unuseable because there's no discussion (at least in the open) about how do USE tech support mode to re-flash using the image I put on the recovery USB stick successfully.

I can see it when I telnet into the box and ls sysroot:

 

# ls -la

drwxr-xr-x 3 4096 Dec 31 1969 .

drwxrwxrwx 19 0 Dec 31 18:32 ..

-rwxr-xr-x 1 0 Feb 28 2016 NTGR_USBBOOT_INFO.txt

-rwxr-xr-x 1 76365824 Sep 23 2019 ReadyNASOS-6.10.2-arm.img

drwxr-xr-x 2 4096 Nov 4 2019 System Volume Information

-rwxr-xr-x 1 2729717 Dec 22 2017 initrd-recovery.gz

-rwxr-xr-x 1 3159060 Dec 1 2016 uImage-recovery

 

But not sure how to proceed from here

Any and all ideas for how to get this unstuck would be appreciated.

 

Thanks!

Model: RN102|ReadyNAS 100 Series 2- Bay
Message 1 of 10
StephenB
Guru

Re: USB Recovery Failure (Reposting)


@Steve89521 wrote:


Then after attempting to build a USB recovery, and after starting the system successfully using USB recovery, the unit drops into "Tech Support" Mode (Firmware 6.2.4) with Serial: NONE000200000 and when I telnet into the unit there doesn't appear to be anything running that indicates that it's fixing flash, the disk, NOTHING.


Were you upgrading from 6.2.4???

Message 2 of 10
Steve89521
Aspirant

Re: USB Recovery Failure (Reposting)

No - Just upgrading from the previous version to the latest update.

Model: RN102|ReadyNAS 100 Series 2- Bay
Message 3 of 10
mdgm
Virtuoso

Re: USB Recovery Failure (Reposting)

This is expected behaviour when recent USB Boot Recovery encounters an error (dropping to tech support mode and showing 6.2.4 as firmware version. I think not showing the correct serial in this state might be normal too, but not sure on that).

The output of
# dmesg
Would be interesting.

The internal flash could have failed.
Message 4 of 10
Steve89521
Aspirant

Re: USB Recovery Failure (Reposting)

Thanks for the hint of where to begin - Indeed after slogging through the output of dmesg (full output included below), here's what I found (abbreviated and highlighted flash init in red):

So I assume that's the root-cause and that replacement of the flash is in order (if possible)?

 

Thanks for any additional guidance you can provide.

 

--- Apparently - the forum doesn't permit attachment of text files (this is not helpful) 

Initializing cgroup subsys cpu
Linux version 3.0.101.RN_ARM.4 (jenkins@blocks) (gcc version 4.6.4 (Linaro GCC branch-4.6.4. Marvell GCC Dev 201310-2126.3d181f66 64K MAXPAGESIZE ALIGN) ) #1 Wed Apr 1 16:06:27 PDT 2015
CPU: Marvell PJ4Bv7 Processor [561f5811] revision 1 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Marvell Armada-370
[... Kernel Init Messages Removed]
Unpacking initramfs...
Freeing initrd memory: 2664K
PMU: registered new PMU device of type 0
Todo: mknod /dev/buttons c 253 0
WARNING: cooling threshold was triggered
Armada XP hwmon thermal sensor initialized.
futex hash table entries: 256 (order: -1, 3072 bytes)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.16)
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
Btrfs loaded
msgmni has been set to 247
async_tx: api initialized (async)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( crc32c )
mv_xor mv_xor.1: Marvell XOR: ( xor )
mv_xor mv_xor.2: Marvell XOR: ( cpy )
mv_xor mv_xor.3: Marvell XOR: ( fill cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xd0012000 (irq = 41) is a 16550A
console [ttyS0] enabled
loop: module loaded
ahci 0000:00:01.0: version 3.0
PCI: enabling device 0000:00:01.0 (0146 -> 0147)
ahci 0000:00:01.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
ahci 0000:00:01.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
scsi0 : ahci
scsi1 : ahci
ata1: SATA max UDMA/133 abar m512@0xe0010000 port 0xe0010100 irq 224
ata2: SATA max UDMA/133 abar m512@0xe0010000 port 0xe0010180 irq 224
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi2 : sata_mv
scsi3 : sata_mv
ata3: SATA max UDMA/133 irq 55
ata4: SATA max UDMA/133 irq 55
Rounding down aligned max_sectors from 4294967295 to 4294967288
mvSFlashInit ERROR: Unknown SPI flash device!
ERROR: sflash_probe - Failed to initialize the SFlash.
armada-nand armada-nand.0: Initialize HAL based NFC in 8bit mode with DMA Disabled using BCH 4bit ECC
armada-nand armada-nand.0: mvNfcInit() failed.
mv_eth_probe: port_mask=0x3, cpu_mask=0x1
0 - Base 0x00000000 , Size = 0x20000000.
4 - Base 0xf2000000 , Size = 0x02000000.
8 - Base 0xe0000000 , Size = 0x02000000.
9 - Base 0xf1100000 , Size = 0x00100000.
10 - Base 0xe2000000 , Size = 0x02000000.
11 - Base 0xf1200000 , Size = 0x00100000.
12 - Base 0xd0000000 , Size = 0x00100000.
14 - Base 0xf0000000 , Size = 0x01000000.
23 - Base 0xf5000000 , Size = 0x01000000.
25 - Base 0xc8010000 , Size = 0x00010000.
o 2 Giga ports supported
o SKB recycle supported (Enabled)
o NETA acceleration mode 1
o RX Queue support: 8 Queues * 512 Descriptors
o TX Queue support: 8 Queues * 512 Descriptors
o GSO supported
o GRO supported
o Receive checksum offload supported
o Transmit checksum offload supported
o Driver ERROR statistics enabled

o Loading network interface(s)

o Warning: GbE port 0 is powered off


o Port 1 is connected to Linux netdevice
giga p=1: mtu=1500, mac=d002be44
o eth0, ifindex = 2, GbE port = 1

bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
sky2: driver version 1.28
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.0: Marvell Orion EHCI
ehci_marvell ehci_marvell.0: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.0: irq 45, io base 0xfbb50100
ehci_marvell ehci_marvell.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ehci_marvell ehci_marvell.1: Marvell Orion EHCI
ehci_marvell ehci_marvell.1: new USB bus registered, assigned bus number 2
ehci_marvell ehci_marvell.1: irq 46, io base 0xfbb51100
ehci_marvell ehci_marvell.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
xhci_hcd 0000:01:01.0: xHCI Host Controller
xhci_hcd 0000:01:01.0: new USB bus registered, assigned bus number 3
Fresco Logic Linux Patch : 20
ata3: SATA link down (SStatus 0 SControl F300)
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
xhci_hcd 0000:01:01.0: xHCI Host Controller
xhci_hcd 0000:01:01.0: new USB bus registered, assigned bus number 4
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
i2c /dev entries driver
usb 1-1: new high-speed USB device number 2 using ehci_marvell
rtc-isl12057 0-0068: chip found, driver version 0.1
rtc (null): invalid alarm value: 1900-1-3 0:0:0
rtc-isl12057 0-0068: rtc core: registered rtc-isl12057 as rtc0
rtc-isl12057 0-0068: rtc power failure detected, please set clock.
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: ATA-9: WDC WD40EFRX-68WT0N0, 82.00A82, max UDMA/133
ata2.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
ata1.00: ATA-9: WDC WD40EFRX-68WT0N0, 82.00A82, max UDMA/133
ata1.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
ata2.00: configured for UDMA/133
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA WDC WD40EFRX-68W 82.0 PQ: 0 ANSI: 5
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) initialised: dm-devel@redhat.com
sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
scsi 1:0:0:0: Direct-Access ATA WDC WD40EFRX-68W 82.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB)
sd 1:0:0:0: [sdb] 4096-byte physical blocks
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Registered led device: backup
Registered led device: SATA1_PRESENT
Registered led device: SATA2_PRESENT
Registered led device: power
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
sdb: sdb1 sdb2 sdb3
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
IPv4 over IPv4 tunneling driver
sd 1:0:0:0: [sdb] Attached SCSI disk
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
802.1Q VLAN Support v1.8
Registering the dns_resolver key type
VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
HDD_pwrctl_init
SATA1 is detected.
SATA2 is detected.
Request the irq HDDpwrctrl success.
usb-storage 1-1:1.0: Quirks match for vid 090c pid 1000: 80000
scsi4 : usb-storage 1-1:1.0
registered taskstats version 1
rtc-isl12057 0-0068: setting system clock to 2000-01-03 21:50:53 UTC (946936253)
ata4: SATA link down (SStatus 0 SControl F300)
Freeing init memory: 164K
scsi 4:0:0:0: Direct-Access USB Flash Disk 1100 PQ: 0 ANSI: 4
sd 4:0:0:0: [sdc] 15663104 512-byte logical blocks: (8.01 GB/7.46 GiB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 4:0:0:0: [sdc] No Caching mode page found
sd 4:0:0:0: [sdc] Assuming drive cache: write through
sd 4:0:0:0: [sdc] No Caching mode page found
sd 4:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 4:0:0:0: [sdc] No Caching mode page found
sd 4:0:0:0: [sdc] Assuming drive cache: write through
sd 4:0:0:0: [sdc] Attached SCSI removable disk
pool #1: pkt_size=1536, buf_size=1632 - 8192 of 8192 buffers added
eth0: link up
eth0: started
eth0: no IPv6 routers present

 

 

Model: RN102|ReadyNAS 100 Series 2- Bay
Message 5 of 10
StephenB
Guru

Re: USB Recovery Failure (Reposting)


@Steve89521 wrote:

 

So I assume that's the root-cause and that replacement of the flash is in order (if possible)?

It looks like it's the root cause (though I don't have any direct experience with flash failures).

 

But the flash isn't replaceable.  Is the NAS still under warranty?  (three years for the original purchaser for the RN100 family).

 

Perhaps @JohnCM_S or @Marc_V can comment on whether there's anything paid support could do to try and bring the flash back to life.

Message 6 of 10
Steve89521
Aspirant

Re: USB Recovery Failure (Reposting)

The unit is no longer under warranty - but I do believe that if someone has some 'navigational' experience in identifying the replacement component on the mainboard, I can replace the flash myself.  I just haven't looked at it yet and have been reticent to spend much time on it if I don't need to.

If others have guidance, (and thank you for yours), I'll welcome it.

Model: RN102|ReadyNAS 100 Series 2- Bay
Message 7 of 10
Sandshark
Sensei

Re: USB Recovery Failure (Reposting)

No schematiics or board layout diagrams are available from Netgear.  You'll just have to look at the chips and figure it out by part number.  Then, you have to hope it's a common one available in single quantities and not a BGA (for which you are unlikely to have the equipment to replace). .

Message 8 of 10
Steve89521
Aspirant

Re: USB Recovery Failure (Reposting)

I guess this is the answer then: "Survey says: e-Waste the product"

Message 9 of 10
StephenB
Guru

Re: USB Recovery Failure (Reposting)


@Steve89521 wrote:

I guess this is the answer then: "Survey says: e-Waste the product"


Yes, unless @JohnCM_S or @Marc_V are willing to access the NAS remotely via tech support mode, and take a look as a courtesy. 

 

Though if the flash has failed, you'll need to replace the NAS.

Message 10 of 10
Top Contributors
Discussion stats
  • 9 replies
  • 1240 views
  • 0 kudos
  • 4 in conversation
Announcements