NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNas Pro -100
Acquired an Old ReadyNas pro 6 -100
it is running OS6 6.10.9
2GB memory and the 1.8ghz processor
Bios is version 1.6
I'd like to update the Bios to version 2.0 for the higher speed FSB memory and Xeon proc.
I've stepped through the various bios update pages and continue to fall short on loading the proper updates.
I've successfully uppacked the ROM files but when attempting the update or install the dmidecod and flashrom are not available.
nor is the libc6.i386.
I've attempted to update sources.lists via the old FTP debian Wheezer main non-free and the http://www.deb-multimedia.org
non of these pages appear to provide the updated information / install or I'm missing something along the way.
Any guidance would be very helpful as I've exhausted my knowledge of next possbile steps.
apt-get update
# apt-get install dmidecode flashrom - Unable to locate package dmidecode & flashrom
# apt-get install libc6-i386 - Unable to locate package libc6=i386
The command Sandshark (lsblk) provided does not function in Tech Support Mode.
FWIW, it was my suggestion. But good to know, as other users will likely run into this. Tech support Mode is missing a lot of commands.
I think in most cases the USB drive will be right after the last internal disk (so sde1 if there are 4 drives in the system), and the flash will be the one after that. But "most cases" isn't the same as all cases. sdc1 was the drive in Sandshark's writeup because he was testing on a Pro 2 (presumably with two drives installed).
But this might not be always true, and it is important to find the correct drive.
The write up provided by Sandshark was fully executed and the VPD file is now on the USB drive successfully.
Great!
15 Replies
The easiest way is to remove your volume with power off (marking drives to put them back as they were), use a spare drive to convert back to OS4.2.x, install the BIOS update package, convert back to OS6, then re-install your drives (again, with power off).
Thank you Sandshark . I'm looking at the old 2014 post from MDGM
Downgrade to RAIDiator-x86 from ReadyNAS OS | #notsupported | NETGEAR Communities
Is this the downgrade process you are referencing?
Thanks again for guidance as I don't have enough back ground to fully understand all the steps.
Yes, that process still works and it looks like the file is still there. If you haven't backed up your VPD file, you should also do that before converting back to OS6: Backup-and-restore-of-VPD-file-for-legacy-ReadyNAS-running-OS6/2253308.
Thank you again Sandshark. I was able to successfully downgrade to OS4, use an older version of Firefox, and access the admin page. Successfully loaded the proper BIOS and return the system back to OS 6 (6.9.5) Original drives are labeled and using 6.10.9. I see the VPD warning and instructions for back up / restore. I've attempted to follow the instructions before proceeding to 6.10.9 OS.
bin home lib64 opt run sysroot usr
dev init media proc sbin tmp var
etc lib mnt root sys usb
# mount /dev/sdd1 usb
mount: mounting /dev/sdd1 on usb failed: No such file or directory
I've been unable to mount the USB directory. ???
# mount /dev/sdd1 usb
mount: mounting /dev/sdd1 on usb failed: No such file or directorytry /usb
kind of perplexing to me :-)
mount /dev/sdd1 /usb
mount: mounting /dev/sdd1 on /usb failed: No such file or directory
# ls
bin home lib64 opt run sysroot usr
dev init media proc sbin tmp var
etc lib mnt root sys usb
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 4G 0 part
│ └─md0 9:0 0 4G 0 raid1 /
├─sda2 8:2 0 512M 0 part
│ └─md1 9:1 0 511.4M 0 raid1 [SWAP]
└─sda3 8:3 0 461.3G 0 part
└─md127 9:127 0 461.1G 0 raid1 /data
sdb 8:16 1 977.5M 0 disk
└─sdb1 8:17 1 972.7M 0 part /media/USB_FLASH_2
Base on this info would the commands be mount /dev/sdb1 mnt
then use mount /dev/sdc1 /usb
Base on this info would the commands be mount /dev/sdb1 mnt
then use mount /dev/sdc1 /usbThe boot flash is 256 MB. SDA is 500 GB (and clearly an internal disk, as is part of md0). SDB is 2 GB
So sdb1 is the USB drive. But you should also be seeing the boot flash, and you are not.
Are you sure you booted in tech support mode?
Good morning and thank you StephenB . The command Sandshark (lsblk) provided does not function in Tech Support Mode. I was able to run it during a SSH port 22 session. Entered Tech support mode and kept SDA as HDD, SDB would be flash and SDC would be USB. The write up provided by Sandshark was fully executed and the VPD file is now on the USB drive successfully.
Thank you Thank you! I really appreciate the assistance.
The command Sandshark (lsblk) provided does not function in Tech Support Mode.
FWIW, it was my suggestion. But good to know, as other users will likely run into this. Tech support Mode is missing a lot of commands.
I think in most cases the USB drive will be right after the last internal disk (so sde1 if there are 4 drives in the system), and the flash will be the one after that. But "most cases" isn't the same as all cases. sdc1 was the drive in Sandshark's writeup because he was testing on a Pro 2 (presumably with two drives installed).
But this might not be always true, and it is important to find the correct drive.
The write up provided by Sandshark was fully executed and the VPD file is now on the USB drive successfully.
Great!
Did you create the usb directory to which you are mounting it with mkdir usb?
Yes, once the proper drives were identified the writeup was followed and executed to the T. Thanks again!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
