NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Sandshark's avatar
Sandshark
Sensei - Experienced User
Aug 31, 2022

Backup and restore of VPD file for legacy ReadyNAS running oS6

We have recently seen a rash of errors reported here on legacy machines upgraded to OS6 that are associated with a corrupt VPD (Vendor Product Data) file. This doesn't usually occur when the NAS is converted to OS6, but on a later update to OS6.10.x. This results in an unbootable unit, and USB recovery will not fix it. Thus, I have recognized that owners of legacy units running OS6 would be well served to backup their VPD for potential future recovery. Even if you're still running OS4.2.x, it's probably not a bad idea. Lots of users never run into this issue, but this is what you can do now in case it does affect you at some point.

 

The VPD is an encrypted file in the boot flash that contains the model and serial number of your NAS. It lets the OS know how to configure your unit, and it's probably encrypted to keep meddlers from messing with it and anyone from trying to create a "do it yourself ReadyNAS". Thus, it's unique to your unit and can't be re-created by anyone other than Netgear. While the forum mods have been helpful for many by creating a replacement, there is no guarantee they will be able to continue doing so.

 

Note that this is not applicable to native OS6 units -- they use another method to ID the hardware that's more robust.

 

In a standard boot (except in rack-mount units that use a USB drive for their flash), the boot flash is unavailable. But it is available in tech support mode in both OS4.2.x and OS6. The procedure is nearly the same for each, so this will cover both. If you are about to upgrade from OS4.2.x to OS6, then I recommend you back up your VPD first. If you have already completed the conversion, then do it before you apply another OS update.

 

For this, we'll save the VPD on a USB flash drive. It must be formatted as FAT, FAT32, or EXT with just one partition. Also make sure it doesn't have a boot sector. I recommend you have at least one file on it so you can properly ID that it's mounted. Note that I've tried with a couple flash drives, up to 32GB, with success.

 

Step one is to boot into tech support mode using the reset button boot menu. For units running OS4.2.x, do so with the USB drive already inserted. Start here to determine how to access the boot menu on your unit: ReadyNAS-ReadyDATA-Boot-Menu .

 

Now, you have to telnet into the unit. If you normally use a static IP assigned in the NAS, the NAS may not be at that address. If you reserve an address in your router, it should be. If it's not where you expect it to be, use RAIDar to determine the IP address. I use PUTTY for a telnet client, but you can use whatever you want to. Log in as user root with password infr8ntdebug.

 

If you are running OS6 and didn't boot with the USB inserted, insert it now.

 

If your unit is a 2-drive unit (as was the Pro2 I tested this on), the two hard drives will be /dev/sda and /dev/sdb. Then /dev/sdc will be the unit flash and /dev/sdd will be the USB drive. If you have more drives (actual drives, not empty slots), they'll be the next two (so sdg and sdh on a 6-drive unit). We'll be mounting the first partition of each.

 

On an OS6 machine, you have to move to the root directory: CD /

 

Now you can mount the internal flash: mount  /dev/sdc1  mnt (or whatever is the right sd_1 device for your NAS).
Verify the contents of flash are there: ls  mnt will return something like this:

csums.md5     kernel.up     root.tlz      version.txt
initrd.gz     ldlinux.sys   supplmnt.tlz  vpd
kernel        memtest       syslinux.cfg

 

It'll be a bit different on an OS6 unit, but the big thing is that vpd is there.

 

Next, we'll make a directory to which we can mount the USB, do the mount, and check that it worked:

mkdir  usb
mount  /dev/sdd1  usb  (again, or appropriate sd_1 device for your NAS)
ls  usb

 

This is where having something already on the USB helps. You'll see it in the results.

 

Now, we just copy the VPD. If you're backing up, do cp  /mnt/vpd  /usb. If recovering, do the opposite: cp  /usb/vpd  /mnt and verify with ls  usb or ls  mnt.

 

Then unmount the USB with umount  usb and remove the USB drive. Now you can do a normal boot.

 

Put a copy of the file somewhere you'll not misplace it. On the NAS itself is OK only if you also do a backup that'll include it and can be accessed without the NAS. When you need it, you won't have access to the NAS.

 

Note that I don't recommend you use this method to backup and restore anything else. Leave that to USB recovery.

 

If anyone knows how to mount a USB drive not present at boot on OS4.2.x, please add that information. I gave up trying since I had a work-around.  If added afterward, it shows up in dmesg, but not /dev.

 

If you only found this because you already lost your VPD, I don't recommend you copy one from another identical machine and you absolutely should not from another machine type. They'll end up showing the same serial number or worse.  Ask the mods to help you create and install a replacement.

33 Replies

Replies have been turned off for this discussion
  • After happily recovering my Ultra 6 and then getting it back on version 6.9.5 Hotfix 1, as per the new owner's wish, I've selected to be notified on LTS updates only. I think main reason is to be able to expand storage beyond the current 6 * 4 TB.
    It keeps offering me 6.9.6 and I've followed your advice to backup VPD. Would you consider 6.9.6 a relatively safe version to upgrade to, just to get rid of the reminders or just keep cancel the update reminders to remain on 6.9.5 Hotfix 1? I notice you say the corruption happens mostly with 6.10.x releases...

    • Sandshark's avatar
      Sandshark
      Sensei - Experienced User

      I've been running 6.9.6 for about 2 years.  I'm not a first adopter on my main and backup NAS, I have a couple "sandbox" NAS for that.  But given how long it's been since the LTS string got any security update, I'm likely to move to 6.10.8 on all.  I think others have been running it long enough that's it's proven stable.

  • a couple things that weren't clear to me, as someone who'd never used telnet before:

    -after logging in, i got a "#" symbol, which apparently means you're connected.

    -I wasn't sure how to get disk info to display (i.e. dev/sda, dev/sdb, etc) so after googling (and finding this page https://linuxhandbook.com/linux-list-disks) i used sfdisk to confirm devices id's for the remaining commands.

    Again I'm the last person you should get telnet info from, but it worked for me. More notes on the telnet aspect of the vpd backup here: https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Best-firmware-for-RNDP2000-after-OS6-upgrade/m-p/2393107

     

    also https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/PuTTY-connection/m-p/1497551

  • While i have not been to a linux command prompt in  years none of these articles tell me how to mount the firmware mount location on the dead NAS?? 

     

    I have been able to telnet in to the dead NAS but i can't for the life of me figure out what is the proper command to mount the drive so I can copy the VPD file from another NAS.

     

    dmesg | grep -i 'disk'
    [    0.000000] RAMDISK: [mem 0x7f6a6000-0x7fffffff]
    [    3.168449] sd 0:0:0:0: [sda] Attached SCSI disk
    [    3.486127] sd 1:0:0:0: [sdb] Attached SCSI disk
    [    3.788597] sd 2:0:0:0: [sdc] Attached SCSI disk
    [    4.088025] sd 3:0:0:0: [sdd] Attached SCSI disk
    [    5.146077] sd 4:0:0:0: [sde] Attached SCSI disk
    [    5.405128] sd 5:0:0:0: [sdf] Attached SCSI disk
    [    8.367613] scsi 6:0:0:0: Direct-Access     SanDisk  Cruzer           7.01 PQ: 0 ANSI: 0 CCS
    [    8.368022] scsi 7:0:0:0: Direct-Access     SMI      USB DISK         1100 PQ: 0 ANSI: 0 CCS
    [    8.379228] sd 6:0:0:0: [sdg] Attached SCSI removable disk
    [    8.380757] sd 7:0:0:0: [sdh] Attached SCSI removable disk
    # mount -t tmpfs -o size=2048M tmpfs /media/ramdisk
     
    # mount
    rootfs on / type rootfs (rw,size=2013636k,nr_inodes=503409)
    proc on /proc type proc (rw,noatime,nodiratime)
    sysfs on /sys type sysfs (rw,noatime,nodiratime)
    devpts on /dev/pts type devpts (rw,noatime,nodiratime,mode=600,ptmxmode=000)
     
     
    # cat /etc/fstab
    # /etc/fstab: static file system information.
    #
    # <file system> <mount pt>     <type>   <options>         <dump> <pass>
    /dev/root       /              ext2     rw,noauto         0      1
    proc            /proc          proc     defaults          0      0
    devpts          /dev/pts       devpts   defaults,gid=5,mode=620   0      0
    tmpfs           /dev/shm       tmpfs    mode=0777         0      0
    tmpfs           /tmp           tmpfs    defaults          0      0
    sysfs           /sys           sysfs    defaults          0      0
    #
     
    some simple command to find the location where the corrupt VPD file is would be helpful 🙂
    • StephenB's avatar
      StephenB
      Guru - Experienced User

      tsdampier wrote:
      While i have not been to a linux command prompt in  years none of these articles tell me how to mount the firmware mount location on the dead NAS?? 
       
      some simple command to find the location where the corrupt VPD file is would be helpful 🙂

       

      How many hard drives are installed?

       

      Normally the hard drives start with sda, and you'd try the ones after them.  For instance, if you have 4 disks installed, you'd start with sde1, and see if that is the correct one.

      • tsdampier's avatar
        tsdampier
        Aspirant

        Six drives as it states in the info above.  It was in a XRAID Raid 5 array.  All my devices are the same configurations.  Some a few different model numbers but overall the same architecture. 

         

        Thanks

  • Great procedural document.  I'm using it to backup the VPD file on my new (to me) ReadyNas Pro 6 and have run into a problem.  I added the SSH enable addon and it works fine in normal boot mode.  When I boot into Tech support I can't SSH to the box (connection refused) to back up the VPD file and then proceed with the 4.2.x to OS 6 upgrade.  Anyone ever run into this and be able to lend some experience on how to get around it?

    • Sandshark's avatar
      Sandshark
      Sensei - Experienced User

      In Tech Support mode, you use Telnet, not SSH.

      • taceto12's avatar
        taceto12
        Apprentice

        Oh crap, dumb mistake. I should have payed more attention to the posts in this thread.  I'm caught up now and Thanks!

  • my apologies if this has been mentioned, but when telnet'ing on to the machine in tech support mode on a pro 6, once we scroll to 'tech support' mode (showing on screen, is there a button to confirm the option, or does it boot to tech support mode eventually once scrolled to the option from the boot menu?

     

    also, do we specify a specific port when entering parameters in putty in order to telnet?

     

    at the moment, i see 'tech support' on the screen, i enter the ip in telnet/putty, leave the port to the default shown, after hitting enter, the putty title bar with show the ip, but a dialogue box pops up saying connection timed out, which leads me to believe either its not in the correct mode, or the connection settings are incorrect

     

    any light shed on this would be appreciated

     

    many thanks

    • rodnaaaaay's avatar
      rodnaaaaay
      Aspirant

      sorry, just an update due to not being able to edit the post

       

      i missed the bit that says i press 'reset' button once correct mode is selected - sno then it booted in debug mode.. but in that mode doesnt seem to connect to the lan (no activity lights) and also cannot ping the IP, nor does raidar pick it up on a scan any longer

       

      still get the same 'network error - connection timed out' on putty

    • StephenB's avatar
      StephenB
      Guru - Experienced User
      rodnaaaaay wrote:

      but when telnet'ing on to the machine in tech support mode on a pro 6, once we scroll to 'tech support' mode (showing on screen, is there a button to confirm the option, or does it boot to tech support mode eventually once scrolled to the option from the boot menu?

      Instructions for tech support mode are on pages 28-29 here:

      rodnaaaaay wrote:

      also, do we specify a specific port when entering parameters in putty in order to telnet?

      Select "other" using the radio buttons, and select telnet in the pulldown on the right.  That will set also set the port correctly (to port 23).  Enter the IP address in the appropriate field.

       

      rodnaaaaay wrote:

      i missed the bit that says i press 'reset' button once correct mode is selected - sno then it booted in debug mode.. but in that mode doesnt seem to connect to the lan (no activity lights) and also cannot ping the IP, nor does raidar pick it up on a scan any longer

      If you just boot up normally, does RAIDar find the NAS?

      • rodnaaaaay's avatar
        rodnaaaaay
        Aspirant

        thanks for the response

         

        yes its currently up and functioning as normal, its just when its in tech support mode that it cant find the NAS

         

        ill try what you suggested now and report back

    • StephenB's avatar
      StephenB
      Guru - Experienced User
      rodnaaaaay wrote:

      i enter the ip in telnet/putty, leave the port to the default shown, after hitting enter, the putty title bar with show the ip, but a dialogue box pops up saying connection timed out, which leads me to believe either its not in the correct mode, or the connection settings are incorrect

      Did you follow my instructions (using my screenshot as a guide)?  As I already said, you need to select "other" as the protocol choice, and then select Telnet from the pulldown.

       

       

      rodnaaaaay wrote:

      is there a button to confirm the option, or does it boot to tech support mode eventually once scrolled to the option from the boot menu?

      Did you read the instructions in the link I posted?  Note step 6:

      • When the status display screen shows the boot mode you need, press and release Reset
        button to confirm your boot menu selection.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More