Drives "locked" after being in NV. HELP!!!

i put them back in the nv and they work fine.

Need unlock this drive
Checking BUSY....
Send SECURITY UNLOCK command
Wait completion
Security unlock command succeed
hdc: WDC WD740GD-00FLA1, hdc: enable ATAEXT,security=7
hde: WDC WD740GD-75FLA0, hde: enable ATAEXT,security=0
Need unlock this drive
Checking BUSY....
Send SECURITY UNLOCK command
Wait completion
Security unlock command succeed
hdg: WDC WD740GD-00FLA0, hdg: enable ATAEXT,security=7
Need unlock this drive
Checking BUSY....
Send SECURITY UNLOCK command
Wait completion
Security unlock command succeed

why would it set a password on the drives? :roll:
it obviously IT did it because it's able to unlock it. ive tried every thing i can think of for a password on the drives, mac address, default admin password

hdc: WDC WD740GD-00FLA1, hdc: enable ATAEXT,security=7 
hde: WDC WD740GD-75FLA0, hde: enable ATAEXT,security=0 

Security value is from IDENTIFY DEVICE word 128
bit 0: Security supported?
bit 1: Security enabled?
bit 2: Security locked?
bit 3: Security frozen?
...

From the log, 1st 3rd and 4th drive are locked, 2nd drive is not locked.
This can only happen when user aborts XRAID build, because we only
lock drives for XRAID build(Initial and Expansion). Drives will be unlocked
when build finishes.

If there is no data on these disks yet, you can build XRAID
with unlocked 2nd drive first, shutdown and then and all locked drives in,
system will then erase all 3 locked drives and then unlock it.

You may unlock disk yourself, the procedure would be:
1. Unlock drive using user password first.
2. Disable password using admin password.
The passwords we use for admin and user both are:

for i=0:15
         password[i] = 0xbeef + i; // 2-byte short word
We use big-endian while Intel uses little-endian, so password
on PC may be: 0xefbe, 0xf0be, ... Sorry for picking up beef as password. 

Let me know if you have any problems. I am going to ask our software
engineers to prepare a service package to unlock drives accidentally
locked by us.

ahh. now that i think about it the power did flicker during that and i didn't have it on the ups at that time. it probably rebooted during this, i will try this when i get home.

this worked. thanks. i wasn't able to use the passwords you provided with the unlock command via the mhdd hard drive disk. but doing the xraid and expanding them worked well, the password(s) are gone.

codegrinder wrote:
this worked. thanks. i wasn't able to use the passwords you provided with the unlock command via the mhdd hard drive disk. but doing the xraid and expanding them worked well, the password(s) are gone.

Thanks for update. Although the chance of hitting this problem is very
low, we will make sure that a disk can be used in PC if it can be used
in ReadyNAS in future release(i.e. Guarantee the same problem will not
happen)

cool. thanks for your help, and thank Brian, i think thats what his name was :oops: , for his help to. he was great about calling back with updates and stuff. most of the time when you get support they blow you off as user error.