Migrating from dead ts-451+ to 464: unable to decrypt

Hey everyone
My ts-451+ died. I opted to replace it with a ts-464.
I tried to keep the disks in order, but failed to actually label them…
On first boot of the 464 I had the 4 disks in the drive bays.
The volume group was visible in the UI, but it was “locked”.
I’ve tried all of the password combinations I can imagine I would’ve set… but none of them work.

I guess I’m wondering, is it possible I put the drives in the wrong order? How can I tell?
Or to put it another way, is it possible to put the disks in the wrong order and still have qnap find the volume group, but unable to decrypt the disk?

If you had the drives encrypted but forgot the password, you will have a bad time…I hope you have usable backups

That’s the thing, I don’t think I forgot the password. I set it two months ago.
So, I’m wondering if it is possible to get the order of the disks wrong that might lead to disk password not being decrypt-able?
I have a partial backup…

I also have a script that’s trying to brute force the disk… sigh
Basically, read a dictionary and echo PASS | cryptsetup open /dev/mapper/vg1-lg1 NAME && echo PASS && exit

Disk order should not matter on CAT2 devices…If in doubt open a ticket with QNAP. Try pruning the password at 12 or 16 char (there was issues with this in the past)

Good call out on length, thanks!

Did that fix your issue ?

i updated my script to truncate down to 12, 16, and 20
running it now
fingers crossed :nervous:

Instead of bruteforcing, try to decrypt your disks via GUI with your known password, but reduce that to the first 12 or 16 characters. (That’s what I meant)

there are a few possibilities
so, it’s safer to let brute take a swing
i won’t have to keep juggling which combo has or has not been attempted

hi flah00,

On the faulty unit, have you tried resurrecting it using the guides in the following videos to fix a common L.PC clock issue:

I"ve been running a TS-451+ for an addition few years using this fix and it might help you buy some time to figure out how to access and transfer the data from you encrypted drives.

Thanks for the suggestion.
I tried connecting, without soldering, the two pins. But the faulty system then began to exhibit symptoms is lpc death, such as all disk lights on when nothing’s in the bays, would not get past post. Removing the resistor allowed the system to pass post and drop into grub again, because of the missing dom.
The faulty system couldn’t use dsl to boot either. USB keyboard issues and a missing knoppix filesystem.

I bit the bullet, reencrypted the disks on the new system and restored from partial backup. :cry:

C’est la vie

I had the exact same problem and bought the TS-464. Fortunately my drives were labeled and the transition was seamless for me. However, I do question the reliability of QNAP hardware. After a two weeks my TS-464 failed to power on. They did repair it under the warranty. Also I do keep backups.

That processor issue was also on Synology NAS and Cisco, etc …all processors of that generation were affected, so not only QNAP