Forum Discussion

Sensei

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 c...

tsdampier

Aspirant

Dec 10, 2024

There is nothing to compare the factory reset just plainly zero outs the file size 🙂 So basically i know the new file is correct as it is not zero bytes 😉

the problem I see is the consistency of the labeling on the product is poor at best. I have two that say RND-6B with a diskless code of RNDP6000.

Then I have a readynas Business Pro which is back up and running with the correct non zero byte vpd file. This unit actually says Business pro on the front of it but nothing to the effect on the label underneath 😉 Underneath it is listed as a RNDP6350-100NAS.

I have the one which was always fine which is also listed underneath as RNDP6350-100NAS but does not say Business Pro on the front.

The two that have RND-6B on the bottom, one is fine the other is the one which is stuck in this loop. This is the one's who match on the bottom but the one of them is the one still broken 🙂

Perhaps I need to wait until the OS6 usb recovery finishes before replacing the VPC file?

StephenB

Guru - Experienced User

Dec 10, 2024

tsdampier wrote:

Underneath it is listed as a RNDP6350-100NAS.

So this is the -100xxx hardware. NAS is the code for North America - other geographies have different suffixes. It is not the same as the -200xxx. No idea if the VPD from a -200 system can be applied to a -100 system. But is seems likely that it would fail.

If you can't find the full part number on your working NAS, you can download the full log zip file and look at boot_info.log.

The -100 systems will have

loader:	RNDP6000-V1

The -200 systems will have

loader:	RNDP6000-V2

tsdampier
Aspirant
Dec 10, 2024
On the bottom of the one that is working it says RNDP6350-100NAS and the bootloader is RNDP6000-V2
So once again this is not consistent across their products and really is different per serial number range and when the product was manufactured 🙂 Note: One of them says ReadyNAS Business Pro on the front of the unit. And I now have a working VPD file for that one.

The other unit that says RNDP6350-???NAS also but shows nothing in the boot loader section boot_info.log 🙂 The label on the bottom is unreadable with the version NAS unfortunately 🙂 This one is also working no issues and never had the corrupt VPD problem.

For the one that is not working - I am not sure where that log file is located to download it using the telnet tech support boot 😉 It is one of the RND-6B on the bottom and RNDP6000 as the model number which is a diskless model.

The VPD file I put on this non-working one is from the same unit that has the same info on the bottom exactly except the serial number/mac addresses 🙂 So if that is supposed to work then this has nothing to do with the RNDP6350's as they are both running no issues.

As always open to suggestions but I have tried a bunch of permutations and suspect this will not work until I get a new real VPD file for it 😞
Sandshark
Sensei
Dec 10, 2024
The very earliest Pro6 did have a different motherboard. Maybe the one you can't get working has that.
Sandshark
Sensei
Dec 18, 2024
I wanted to add a couple of notes to update this thread.

In the original message, I recommend against using the vpd from another unit. While that still applies to dissimilar hardware, it's not an issue with similar hardware any longer because of the lack of ReadyCloud and Netgear support.

VPDs from a Pro BE, Pro Pioneer, Pro6, and Ultra6Plus (but NOT an Ultra6) are interchangeable, except maybe for the earliest units. There is an early version of the motherboard that I have read about here in the forum, and I do not know if the vpd is the same, as I've never had one.

Pro4 and Ultra4 are interchangeable, as are Pro2 and Ultra2.

And if you are running OS6, I've found an easier way to access the flash. From SSH, issue rnutil toggle_flash and now you can see it from SSH. It still needs to be mounted. Note that, as far as I can tell, it doesn't actually toggle, it just turns it on (not back off the second time it's issued), so best to re-boot and protect the flash once you're finished with the backup.