- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Not sure about kernel.up, though it appears match kernel in the flash (both size and checksum). So that could be ok.
You could of course try copying root.tlz onto the flash. But there might be a way to check (and spare) bad sectors, which might make sense to do first. Maybe wait for others to chime in, as they might have advice on that.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
According to @mdgm in PM, the kernel.up is for 32 bit architecture and needs to be renamed to kernel in case of manual extraction. This would explain why it matches a different hash to the one listed. Same-same but different.
I've noticed while doing some more looking around, there's a /lib64/ folder on the first raid partition, making me think that an update to the x64 version of 4.3.21 was attempted, if not to OS 6, unless it's meant to be there just because.
I can't get badblocks to run when chroot'd into the raid partition, output below. I believe it's because of the file being for x64 architecture.
root@22N294RA00187:/# ls -la lib64
total 2176
drwxr-xr-x 2 root 0 4096 Sep 16 03:31 .
drwxr-xr-x 22 root 0 4096 Sep 23 04:27 ..
-rwxr-xr-x 1 root 0 131576 Jan 29 2015 ld-2.7.so
lrwxrwxrwx 1 root 0 9 Sep 16 03:31 ld-linux-x86-64.so.2 -> ld-2.7.so
lrwxrwxrwx 1 root 0 15 Sep 16 03:31 libblkid.so.1 -> libblkid.so.1.0
-rw-r--r-- 1 root 0 48848 Sep 19 2014 libblkid.so.1.0
-rwxr-xr-x 1 root 0 1498416 Jan 29 2015 libc-2.7.so
lrwxrwxrwx 1 root 0 11 Sep 16 03:31 libc.so.6 -> libc-2.7.so
lrwxrwxrwx 1 root 0 17 Sep 16 03:31 libcom_err.so.2 -> libcom_err.so.2.1
-rw-r--r-- 1 root 0 12352 Sep 19 2014 libcom_err.so.2.1
lrwxrwxrwx 1 root 0 13 Sep 16 03:31 libe2p.so.2 -> libe2p.so.2.3
-rw-r--r-- 1 root 0 28816 Sep 19 2014 libe2p.so.2.3
lrwxrwxrwx 1 root 0 16 Sep 16 03:31 libext2fs.so.2 -> libext2fs.so.2.4
-rw-r--r-- 1 root 0 283168 Sep 19 2014 libext2fs.so.2.4
-rwxr-xr-x 1 root 0 130197 Jan 29 2015 libpthread-2.7.so
lrwxrwxrwx 1 root 0 17 Sep 16 03:31 libpthread.so.0 -> libpthread-2.7.so
lrwxrwxrwx 1 root 0 25 Sep 16 03:31 libreadynas_lgpl.so.0 -> libreadynas_lgpl.so.0.1.1
-rwxr-xr-x 1 root 0 11896 Mar 2 2010 libreadynas_lgpl.so.0.1.1
lrwxrwxrwx 1 root 0 12 Sep 16 03:31 libss.so.2 -> libss.so.2.0
-rw-r--r-- 1 root 0 24432 Sep 19 2014 libss.so.2.0
lrwxrwxrwx 1 root 0 14 Sep 16 03:31 libuuid.so.1 -> libuuid.so.1.2
-rw-r--r-- 1 root 0 16112 Sep 19 2014 libuuid.so.1.2
root@22N294RA00187:/# badblocks -v /dev/sde1
badblocks: error while loading shared libraries: libreadynas_lgpl.so.0: cannot open shared object file: No such file or directory
root@22N294RA00187:/#
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
@frankie0p wrote:
According to @mdgm in PM, the kernel.up is for 32 bit architecture and needs to be renamed to kernel in case of manual extraction.
FWIW, I was thinking that might be the case - but definitely something that needed to be confirmed before touching that file in the flash.
@frankie0p wrote:
I've noticed while doing some more looking around, there's a /lib64/ folder on the first raid partition, making me think that an update to the x64 version of 4.3.21 was attempted, if not to OS 6, unless it's meant to be there just because.
You must mean 4.2.31 (there is no 4.3.x firmware). But I don't see how the 4.2.31 x64 firmware would have been applied, since the install should autodetect that the NVX is a 32 bit machine.
I haven't seen details of exactly what happens to the OS partition if you attempt to upgrade an NVX to OS-6. But I'd think there would be far more stuff wrong if OS-6 binaries put in the root folder.
So I'm thinking it's "meant to be there just because" it was just easier to populate some folders that weren't used on 32-bit machines.
I guess you could try seeing if badblocks is available w/o the chroot. Or just try to replace root.tlz, and see if it works.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
@StephenB wrote:I guess you could try seeing if badblocks is available w/o the chroot. Or just try to replace root.tlz, and see if it work.
I did look for it in the tech support root but I dont think it's included in busybox. I tried smartctl but the flash module doesn't support selftest logging either. At this point I think the best thing I can do is indeed attempt to copy the new root.tlz over, as the flash itself being bad is pretty much a terminal illness.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Out of curiosity, @aldospa, would you be able to see if upgrading to OS6 on your device has had any of the effects listed in the thread?
Only attempt if you're not to bothered about the fate of the NAS and you feel comfortable doing so, obviously. I'm just interested to see what the attempted upgrade has done to the OS.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Frankie,
Managed to get my serial console working and found that I can only see a command prompt when booting from the USB recovery stick. However the USB recovery stick is not performing the fix, but when I boot from the USB I at least get to a command prompt. The key text from the console is when I use the USB recovery tool end in the following text
Could not find external boot flash!
ERROR: Could not find external flash device!!
/bin/ash: can't access tty; job control turned off
#
then ran
# uname -a
Linux (none) 2.6.37.3.RNx86_32.1.1 #1 Fri Mar 11 15:29:27 PST 2011 i686 unknown
and ran
# cat /etc/os_version
cat: can't open '/etc/os_version': No such file or directory
went further and looked to mount my flash which was coming up as sde1
# cat /proc/partitionsmajor minor #blocks name8 0 1953514584 sda8 1 2490240 sda18 2 2097152 sda28 3 1948693584 sda38 16 1953514584 sdb8 17 4194304 sdb18 18 524288 sdb28 19 1948793912 sdb38 32 1953514584 sdc8 33 2490240 sdc18 34 2097152 sdc28 35 1948693584 sdc38 48 1953514584 sdd8 49 4194304 sdd18 50 524288 sdd28 51 1948793912 sdd38 64 125440 sde8 65 125333 sde18 80 1981952 sdf
# ls
bin dev lib sbin tmp
boot_flash etc proc sys usr
data init root sysroot var
Creating a mount point for the internal flash
# mkdir /mnt
# mount /dev/sde1 /mnt
Going into the internal Flash
# cd mnt
# pwd
/mnt
Looking at the contents of the internal flash
# ls
CSUMS.MD5 KERNEL MEMTEST SUPPLMNT.TLZ VERSION.TXT
INITRD.GZ LDLINUX.SYS ROOT.TLZ SYSLINUX.CFG VPD
# ls -aldrwxr-xr-x 2 0 0 16384 Jan 1 1970 .drwxr-xr-x 17 0 0 0 May 8 13:15 ..-rwxr-xr-x 1 0 0 128 Apr 30 01:51 CSUMS.MD5-rwxr-xr-x 1 0 0 4454994 Apr 30 01:51 INITRD.GZ-rwxr-xr-x 1 0 0 3040368 Aug 4 2017 KERNEL-r-xr-xr-x 1 0 0 12424 Jun 22 2010 LDLINUX.SYS-rwxr-xr-x 1 0 0 169600 Aug 4 2017 MEMTEST-rwxr-xr-x 1 0 0 61039715 Apr 30 01:51 ROOT.TLZ-rwxr-xr-x 1 0 0 650860 Aug 4 2017 SUPPLMNT.TLZ-rwxr-xr-x 1 0 0 532 Aug 4 2017 SYSLINUX.CFG-rwxr-xr-x 1 0 0 42 Aug 4 2017 VERSION.TXT-rwxr-xr-x 1 0 0 512 Aug 3 2011 VPDit appears my attempt to move to OS6 has modified the following files on my flash area-rwxr-xr-x 1 0 0 3040368 Aug 4 2017 KERNEL-rwxr-xr-x 1 0 0 169600 Aug 4 2017 MEMTEST-rwxr-xr-x 1 0 0 650860 Aug 4 2017 SUPPLMNT.TLZ-rwxr-xr-x 1 0 0 532 Aug 4 2017 SYSLINUX.CFG-rwxr-xr-x 1 0 0 42 Aug 4 2017 VERSION.TXTSo I’m now looking for a way to get my device re-flashed to reverse the files above. It seems we all need a new tool other than the USB recovery tool. For me I need to find a virtual window 7 machine to be able to produce it USB recovery tool. Even now though it is still not working for me to reflash the ReadyNAS NVX but at least I have a command prompt.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Can anyone help reflash my Readynas NVX
after an atttempt to move to OS6 found out the Readynas NVX is a 32 bit machine that is not supported
(1) From the firmware file RAIDiator-x86-4.2.31 i get the checksums are
% cat csums.md5
3b149aa715d8c09491439f9240285ca2 initrd.gz
d3af676e47ee06ed1c3bcf9b22f35341 kernel
8cf6bab4b104fc5b869aeb8585849b24 kernel.up
26acb3351b52a61f3480533a1fd89b9c memtest
2f6e4d8775717a54ac3d074e527c3209 root.tlz
9de4bac1de70732b8f7bb4e8fe0397c9 supplmnt.tlz
aea8b2361c563250478a687d16f38b6a syslinux.cfg
fac783aa9c70094c2c63850ac6286983 version.txt
with dates
-rw-r--r--@ 1 aldospadaccini staff 57370624 24 May 2017 RAIDiator-x86-4.2.31
-rw-r--r-- 1 aldospadaccini staff 354 23 May 2017 csums.md5
-rw-r--r-- 1 aldospadaccini staff 1718218 23 May 2017 initrd.gz
-rw-r--r-- 1 aldospadaccini staff 3731456 23 May 2017 kernel
-rw-r--r-- 1 aldospadaccini staff 3040368 23 May 2017 kernel.up
-rwxr-xr-x 1 aldospadaccini staff 169600 23 May 2017 memtest
-rw-r--r-- 1 aldospadaccini staff 48031517 23 May 2017 root.tlz
-rw-r--r-- 1 aldospadaccini staff 650860 23 May 2017 supplmnt.tlz
-rwxr-xr-x 1 aldospadaccini staff 532 23 May 2017 syslinux.cfg
-rw-r--r-- 1 aldospadaccini staff 42 23 May 2017 version.txt
% cat version.txt
RAIDiator!!version=4.2.31,time=1495520166
(2) on the Readynas NVX after a USB recovery boot I get on the Flash
# mkdir /mnt
# mount /dev/sde1 /mnt
# cd mnt
# ls -al
drwxr-xr-x 2 0 0 16384 Jan 1 1970 .
drwxr-xr-x 17 0 0 0 May 8 23:16 ..
-rwxr-xr-x 1 0 0 128 Apr 30 01:51 CSUMS.MD5
-rwxr-xr-x 1 0 0 4454994 Apr 30 01:51 INITRD.GZ
-rwxr-xr-x 1 0 0 3040368 Aug 4 2017 KERNEL
-r-xr-xr-x 1 0 0 12424 Jun 22 2010 LDLINUX.SYS
-rwxr-xr-x 1 0 0 169600 Aug 4 2017 MEMTEST
-rwxr-xr-x 1 0 0 61039715 Apr 30 01:51 ROOT.TLZ
-rwxr-xr-x 1 0 0 650860 Aug 4 2017 SUPPLMNT.TLZ
-rwxr-xr-x 1 0 0 532 Aug 4 2017 SYSLINUX.CFG
-rwxr-xr-x 1 0 0 42 Aug 4 2017 VERSION.TXT
-rwxr-xr-x 1 0 0 512 Aug 3 2011 VPD
with checksum
# cat CSUMS.MD5
f3990a6e51a4af81861c5d6adca19ef9 initrd.gz
0fb4d3019e0e77ce578694dea23df8d7 kernel
82059e5c1ec6307fa8cc660761644ac8 root.tlz
# cat VERSION.TXT
RAIDiator!!version=4.2.31,time=1495520166
it seems the files on the ReadyNAS Flash need to be updated to the ones in the RAIDiator-x86-4.2.31 firmware archive.
Is it just a straight copy onto the flash drive via another usb?
I'm thinking to mount the Usb Recovery to get a command prompt and mount as follows:
# mkdir /mnt_internal_flash
# mount /dev/sde1 /mnt_internal_flash
Then insert another USB into the Readynas with a copy of the 7zz extract contents from the firmware file RAIDiator-x86-4.2.31. Then mount and copy as follows
# mkdir /mnt_anotherusb
# mount /dev/sdf1 /mnt_anotherusb
Finally copy the files across
# cp /mnt_anotherusb/* /mnt_internal_flash/
Is this the right way to go to refresh the ReadyNas NVX?
Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Morning all, happy Monday.
Ladies and Gentlemen, we got him.
I copied over the firmware manually, performed a factory reset and now the NAS is happily doing a resync. I'll post the telnet log file below that shows the steps for copying over the FW image.
22N294RA00187 login: root
Password:
# start_raid.sh
mdadm: /dev/md/0 has been started with 4 drives.
mdadm: /dev/md/1 has been started with 4 drives.
mdadm: /dev/md/2 has been started with 4 drives.
# mount /dev/md0 /sysroot
# ls sysroot
USB dev home lib64 opt root tmp
bin etc initrd lost+found proc sbin usr
c frontview lib mnt ramfs sys
# mount --bind /proc /sysroot/proc
# mount --bind /dev /sysroot/dev
# mount --bind /dev/pts /sysroot/dev/pts
# mount --bind /sys /sysroot/sys
# chroot /sysroot /bin/bash
root@22N294RA00187:/# mkdir /mnt/flash
root@22N294RA00187:/# mkdir /mnt/usb
root@22N294RA00187:/# cat /proc/partitions
major minor #blocks name
8 0 1953514584 sda
8 1 4194304 sda1
8 2 524288 sda2
8 3 1948793912 sda3
8 16 1953514584 sdb
8 17 4194304 sdb1
8 18 524288 sdb2
8 19 1948793912 sdb3
8 32 1953514584 sdc
8 33 4194304 sdc1
8 34 524288 sdc2
8 35 1948793912 sdc3
8 48 1953514584 sdd
8 49 4194304 sdd1
8 50 524288 sdd2
8 51 1948793912 sdd3
8 64 125440 sde
8 65 125333 sde1
8 80 3911648 sdf
8 81 3911008 sdf1
9 0 4193268 md0
9 1 1048448 md1
9 2 5846378112 md2
root@22N294RA00187:/# mount /dev/sde1 /mnt/flash
root@22N294RA00187:/# mount /dev/sdf1 /mnt/usb
root@22N294RA00187:/# ls -la -R /mnt
/mnt:
total 28
drwxr-xr-x 4 root 0 4096 Sep 27 02:11 .
drwxr-xr-x 22 root 0 4096 Sep 23 04:27 ..
drwxr-xr-x 2 root 0 16384 Jan 1 1970 flash
drwxr-xr-x 3 root 0 4096 Jan 1 1970 usb
/mnt/flash:
total 52398
drwxr-xr-x 2 root 0 16384 Jan 1 1970 .
drwxr-xr-x 4 root 0 4096 Sep 27 02:11 ..
-rwxr-xr-x 1 root 0 354 Aug 18 2017 CSUMS.MD5
-rwxr-xr-x 1 root 0 1718218 Aug 18 2017 INITRD.GZ
-rwxr-xr-x 1 root 0 3040368 Aug 18 2017 KERNEL
-r-xr-xr-x 1 root 0 12424 Oct 1 2009 LDLINUX.SYS
-rwxr-xr-x 1 root 0 169600 Aug 18 2017 MEMTEST
-rwxr-xr-x 1 root 0 48031517 Aug 18 2017 ROOT.TLZ
-rwxr-xr-x 1 root 0 650860 Aug 18 2017 SUPPLMNT.TLZ
-rwxr-xr-x 1 root 0 532 Aug 18 2017 SYSLINUX.CFG
-rwxr-xr-x 1 root 0 42 Aug 18 2017 VERSION.TXT
-rwxr-xr-x 1 root 0 512 Feb 27 2011 VPD
/mnt/usb:
total 52408
drwxr-xr-x 3 root 0 4096 Jan 1 1970 .
drwxr-xr-x 4 root 0 4096 Sep 27 02:11 ..
-rwxr-xr-x 1 root 0 354 Sep 24 00:29 CSUMS.MD5
-rwxr-xr-x 1 root 0 1718218 Sep 24 00:29 INITRD.GZ
-rwxr-xr-x 1 root 0 3040368 Sep 24 00:29 KERNEL
-rwxr-xr-x 1 root 0 12424 Sep 24 00:29 LDLINUX.SYS
-rwxr-xr-x 1 root 0 169600 Sep 24 00:29 MEMTEST
-rwxr-xr-x 1 root 0 48031517 May 23 2017 ROOT.TLZ
-rwxr-xr-x 1 root 0 650860 Sep 24 00:29 SUPPLMNT.TLZ
-rwxr-xr-x 1 root 0 532 Sep 24 00:29 SYSLINUX.CFG
drwxr-xr-x 2 root 0 4096 Jun 6 2019 System Volume Information
-rwxr-xr-x 1 root 0 42 Sep 24 00:29 VERSION.TXT
-rwxr-xr-x 1 root 0 512 Sep 24 00:29 VPD
/mnt/usb/System Volume Information:
total 16
drwxr-xr-x 2 root 0 4096 Jun 6 2019 .
drwxr-xr-x 3 root 0 4096 Jan 1 1970 ..
-rwxr-xr-x 1 root 0 76 Jun 27 2019 IndexerVolumeGuid
-rwxr-xr-x 1 root 0 12 Jun 6 2019 WPSettings.dat
root@22N294RA00187:/# cp /mnt/flash/ROOT.TLZ /mnt/usb/copyofROOT.TLZcorrupt
root@22N294RA00187:/# ls -la -R /mnt
...
/mnt/flash:
total 52398
drwxr-xr-x 2 root 0 16384 Jan 1 1970 .
drwxr-xr-x 4 root 0 4096 Sep 27 02:11 ..
-rwxr-xr-x 1 root 0 354 Aug 18 2017 CSUMS.MD5
-rwxr-xr-x 1 root 0 1718218 Aug 18 2017 INITRD.GZ
-rwxr-xr-x 1 root 0 3040368 Aug 18 2017 KERNEL
-r-xr-xr-x 1 root 0 12424 Oct 1 2009 LDLINUX.SYS
-rwxr-xr-x 1 root 0 169600 Aug 18 2017 MEMTEST
-rwxr-xr-x 1 root 0 48031517 Aug 18 2017 ROOT.TLZ
-rwxr-xr-x 1 root 0 650860 Aug 18 2017 SUPPLMNT.TLZ
-rwxr-xr-x 1 root 0 532 Aug 18 2017 SYSLINUX.CFG
-rwxr-xr-x 1 root 0 42 Aug 18 2017 VERSION.TXT
-rwxr-xr-x 1 root 0 512 Feb 27 2011 VPD
/mnt/usb:
total 99316
drwxr-xr-x 3 root 0 4096 Sep 27 02:13 .
drwxr-xr-x 4 root 0 4096 Sep 27 02:11 ..
-rwxr-xr-x 1 root 0 354 Sep 24 00:29 CSUMS.MD5
-rwxr-xr-x 1 root 0 1718218 Sep 24 00:29 INITRD.GZ
-rwxr-xr-x 1 root 0 3040368 Sep 24 00:29 KERNEL
-rwxr-xr-x 1 root 0 12424 Sep 24 00:29 LDLINUX.SYS
-rwxr-xr-x 1 root 0 169600 Sep 24 00:29 MEMTEST
-rwxr-xr-x 1 root 0 48031517 May 23 2017 ROOT.TLZ
-rwxr-xr-x 1 root 0 650860 Sep 24 00:29 SUPPLMNT.TLZ
-rwxr-xr-x 1 root 0 532 Sep 24 00:29 SYSLINUX.CFG
drwxr-xr-x 2 root 0 4096 Jun 6 2019 System Volume Information
-rwxr-xr-x 1 root 0 42 Sep 24 00:29 VERSION.TXT
-rwxr-xr-x 1 root 0 512 Sep 24 00:29 VPD
-rwxr-xr-x 1 root 0 48031517 Sep 27 02:13 copyofROOT.TLZcorrupt
...
root@22N294RA00187:/# rm -f /mnt/flash/ROOT.TLZ
root@22N294RA00187:/# cp /mnt/usb/ROOT.TLZ /mnt/flash/ROOT.TLZ
root@22N294RA00187:/# date
Mon Sep 27 02:16:20 UTC 2021
root@22N294RA00187:/# ls -la -R /mnt
...
/mnt/flash:
total 52398
drwxr-xr-x 2 root 0 16384 Sep 27 02:15 .
drwxr-xr-x 4 root 0 4096 Sep 27 02:11 ..
-rwxr-xr-x 1 root 0 354 Aug 18 2017 CSUMS.MD5
-rwxr-xr-x 1 root 0 1718218 Aug 18 2017 INITRD.GZ
-rwxr-xr-x 1 root 0 3040368 Aug 18 2017 KERNEL
-r-xr-xr-x 1 root 0 12424 Oct 1 2009 LDLINUX.SYS
-rwxr-xr-x 1 root 0 169600 Aug 18 2017 MEMTEST
-rwxr-xr-x 1 root 0 48031517 Sep 27 02:15 ROOT.TLZ
-rwxr-xr-x 1 root 0 650860 Aug 18 2017 SUPPLMNT.TLZ
-rwxr-xr-x 1 root 0 532 Aug 18 2017 SYSLINUX.CFG
-rwxr-xr-x 1 root 0 42 Aug 18 2017 VERSION.TXT
-rwxr-xr-x 1 root 0 512 Feb 27 2011 VPD
/mnt/usb:
total 99316
drwxr-xr-x 3 root 0 4096 Sep 27 02:13 .
drwxr-xr-x 4 root 0 4096 Sep 27 02:11 ..
-rwxr-xr-x 1 root 0 354 Sep 24 00:29 CSUMS.MD5
-rwxr-xr-x 1 root 0 1718218 Sep 24 00:29 INITRD.GZ
-rwxr-xr-x 1 root 0 3040368 Sep 24 00:29 KERNEL
-rwxr-xr-x 1 root 0 12424 Sep 24 00:29 LDLINUX.SYS
-rwxr-xr-x 1 root 0 169600 Sep 24 00:29 MEMTEST
-rwxr-xr-x 1 root 0 48031517 May 23 2017 ROOT.TLZ
-rwxr-xr-x 1 root 0 650860 Sep 24 00:29 SUPPLMNT.TLZ
-rwxr-xr-x 1 root 0 532 Sep 24 00:29 SYSLINUX.CFG
drwxr-xr-x 2 root 0 4096 Jun 6 2019 System Volume Information
-rwxr-xr-x 1 root 0 42 Sep 24 00:29 VERSION.TXT
-rwxr-xr-x 1 root 0 512 Sep 24 00:29 VPD
-rwxr-xr-x 1 root 0 48031517 Sep 27 02:13 copyofROOT.TLZcorrupt
...
root@22N294RA00187:/# mount
/dev/sde1 on /mnt/flash type vfat (rw)
/dev/sdf1 on /mnt/usb type vfat (rw)
root@22N294RA00187:/# umount /dev/sde1
root@22N294RA00187:/# umount /dev/sdf1
root@22N294RA00187:/# mount
root@22N294RA00187:/# exit
exit
# mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/md0 on /sysroot type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
proc on /sysroot/proc type proc (rw,relatime)
tmpfs on /sysroot/dev type tmpfs (rw,relatime,size=10240k,mode=755)
devpts on /sysroot/dev/pts type devpts (rw,relatime,mode=600)
sysfs on /sysroot/sys type sysfs (rw,relatime)
# umount /sysroot/sys
# umount /sysroot/dev/pts
# umount /sysroot/dev
# umount /sysroot/proc
# mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
# poweroff -f
My thanks to all who helped.
The punchline: Last night I got an email from Netgear customer service saying a case had been opened for me and that I needed to provide my information again. "Missed it by that much."
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Frankie,
Thanks so much for your solution. In my case my disks have been removed but still need to correct the flash. My thoughts are the following will work. Do you agree it sound like you just need to copy the files to the internal flash. I think I read that the kernel.up file in the RAIDiator-x86-4.2.31 is for the 32bit version and applicable to the ReadyNas NVX. the kernel.up file needs to be renamed to kernel and this one uploaded to the flash.
My history and proposed solution below seems similar to yours.
==================
Can anyone help reflash my Readynas NVX. After an attempt to move to OS6 found out the Readynas NVX is a 32 bit machine that is not supported
(1) From the firmware file RAIDiator-x86-4.2.31 i get the checksums are
% cat csums.md5
3b149aa715d8c09491439f9240285ca2 initrd.gz
d3af676e47ee06ed1c3bcf9b22f35341 kernel
8cf6bab4b104fc5b869aeb8585849b24 kernel.up
26acb3351b52a61f3480533a1fd89b9c memtest
2f6e4d8775717a54ac3d074e527c3209 root.tlz
9de4bac1de70732b8f7bb4e8fe0397c9 supplmnt.tlz
aea8b2361c563250478a687d16f38b6a syslinux.cfg
fac783aa9c70094c2c63850ac6286983 version.txt
with dates
-rw-r--r--@ 1 aldospadaccini staff 57370624 24 May 2017 RAIDiator-x86-4.2.31
-rw-r--r-- 1 aldospadaccini staff 354 23 May 2017 csums.md5
-rw-r--r-- 1 aldospadaccini staff 1718218 23 May 2017 initrd.gz
-rw-r--r-- 1 aldospadaccini staff 3731456 23 May 2017 kernel
-rw-r--r-- 1 aldospadaccini staff 3040368 23 May 2017 kernel.up
-rwxr-xr-x 1 aldospadaccini staff 169600 23 May 2017 memtest
-rw-r--r-- 1 aldospadaccini staff 48031517 23 May 2017 root.tlz
-rw-r--r-- 1 aldospadaccini staff 650860 23 May 2017 supplmnt.tlz
-rwxr-xr-x 1 aldospadaccini staff 532 23 May 2017 syslinux.cfg
-rw-r--r-- 1 aldospadaccini staff 42 23 May 2017 version.txt
% cat version.txt
RAIDiator!!version=4.2.31,time=1495520166
(2) on the Readynas NVX after a USB recovery boot I get on the Flash
# mkdir /mnt
# mount /dev/sde1 /mnt
# cd mnt
# ls -al
drwxr-xr-x 2 0 0 16384 Jan 1 1970 .
drwxr-xr-x 17 0 0 0 May 8 23:16 ..
-rwxr-xr-x 1 0 0 128 Apr 30 01:51 CSUMS.MD5
-rwxr-xr-x 1 0 0 4454994 Apr 30 01:51 INITRD.GZ
-rwxr-xr-x 1 0 0 3040368 Aug 4 2017 KERNEL
-r-xr-xr-x 1 0 0 12424 Jun 22 2010 LDLINUX.SYS
-rwxr-xr-x 1 0 0 169600 Aug 4 2017 MEMTEST
-rwxr-xr-x 1 0 0 61039715 Apr 30 01:51 ROOT.TLZ
-rwxr-xr-x 1 0 0 650860 Aug 4 2017 SUPPLMNT.TLZ
-rwxr-xr-x 1 0 0 532 Aug 4 2017 SYSLINUX.CFG
-rwxr-xr-x 1 0 0 42 Aug 4 2017 VERSION.TXT
-rwxr-xr-x 1 0 0 512 Aug 3 2011 VPD
with checksum
# cat CSUMS.MD5
f3990a6e51a4af81861c5d6adca19ef9 initrd.gz
0fb4d3019e0e77ce578694dea23df8d7 kernel
82059e5c1ec6307fa8cc660761644ac8 root.tlz
# cat VERSION.TXT
RAIDiator!!version=4.2.31,time=1495520166
it seems the files on the ReadyNAS Flash need to be updated to the ones in the RAIDiator-x86-4.2.31 firmware archive.
Is it just a straight copy onto the flash drive of the files extracted from the firmware file?
I'm thinking to mount the Usb Recovery to get a command prompt and mount as follows:
# mkdir /mnt_internal_flash
# mount /dev/sde1 /mnt_internal_flash
Then insert another USB into the Readynas with a copy of the 7zz extract contents from the firmware file RAIDiator-x86-4.2.31. Then mount and copy as follows
# mkdir /mnt_anotherusb
# mount /dev/sdf1 /mnt_anotherusb
# cp /mnt_anotherusb/* /mnt_internal_flash/
Is this the right way to go?
Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
@aldospa wrote:it seems the files on the ReadyNAS Flash need to be updated to the ones in the RAIDiator-x86-4.2.31 firmware archive.
Is it just a straight copy onto the flash drive of the files extracted from the firmware file?
kernel in the 4.2.31 image is the 64 bit kernel. So you'd need to copy kernel.up (the 32 bit kernel) in the image to kernel in the flash. Plus copy the other two.
Either way is potentially risky, but I think I'd start by simply copying the three files, and not attempting the USB recovery.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
It sounds to me like you were trying to use the OS6 USB recovery tool, not the legacy one. But since you were able to get it running via other means, that's now moot.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Managed to mount my two USB and copied the firmware files to the internal flash which fixed my system. The only issue is that I lost ssh access so performed a factory reset. At the moment all my browser are not able to load the front view webpage due to certificate errors. Not sure how to fix this.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
I use firefox, when it shows a certificate error it also says "Advanced Options", when I select that I can select to "continue despite the risk" or something, than it lets you view the web page. If your browser doesn't allow continuing, I suggest googling for a workaround or use a different browser.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
@frankie0p wrote:
I use firefox, when it shows a certificate error it also says "Advanced Options", when I select that I can select to "continue despite the risk" or something, than it lets you view the web page. If your browser doesn't allow continuing, I suggest googling for a workaround or use a different browser.
Current FireFox won't behave that way with 4.x or 5.3 systems, because it has dropped support for TLS 1.0. The legacy systems will now give you an "ssl verision or cipher mismatch" error, and there is no way to work around that with FireFox or Chrome. IE will still connect, as will Edge in IE mode.
There are two workarounds - add-ons for 4.2.x and 5.3.x systems are available thanks to @WhoCares_ at rnxtras.com.
There are no add-ons for 4.1 systems, but you can make a simple mod to allow access to the admin interface with http - which is not encrypted. That allows access, but of course there is lower security.
You can also use on older browser version - mozilla has all the old versions of FireFox available for download. FireFox 94.0.2 certainly will connect (I've tried it), some slightly newer versions might also.
https://community.netgear.com/t5/New-ReadyNAS-Users-General/Workaround-for-ERR-SSL-VERSION-OR-CIPHER... gives more information on all of this.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Not sure what to tell you, worked for me. Might have applied the workaround in the past and forgotten about it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Thanks for the help. Im now able to boot post a usb recovery but it seems we have messed up the EEPROM data and now front view is without buttons. Its blank as per the attached.
Think this is known issue but not can't find the solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
@aldospa wrote:Thanks for the help. Im now able to boot post a usb recovery but it seems we have messed up the EEPROM data and now front view is without buttons. Its blank as per the attached.
Think this is known issue but not can't find the solution.
Fixing the EEPROM requires Netgear's help, so I am tagging the mods ( @Marc_V and @JeraldM )
What status is RAIDar giving you now? https://kb.netgear.com/20684/ReadyNAS-Downloads#raidar
Have you tried clearing the browser cache?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
That display can be from one of two things I know of: You used really old firmware to USB recover, so you have to use IE in compatibility mode to see the proper display or a messed up SAMBA configuration file. Have you tried another factory default since the USB recovery? That should clear up the SAMBA issue, if that's the problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Thanks I've used the USB recovery firmware
RAIDiator!!version=4.2.31,time=1495520166
and also done a factory reset.
It sound like help generating a VPD file
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
You did a factory reset after the USB recovery? A USB recovery doesn't do one automatically, and if you did a reset from a corrupted flash prior to USB recovery, then the image installed during the reset was likely corrupted.
Does a valid model and serial number show up in RAIDar? If so, it's not a VPD problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to Boot or Factory Reset ReadyNAS NVX Pioneer (RNDX400E)
Checked Raidar and there is not model number or serial so that confirms a VPD file issue. So just need to wait for assistance directly for who know how to fix that. Thanks for your help.
- « Previous
-
- 1
- 2
- Next »