Unsolved
This post is more than 5 years old
2 Intern
•
308 Posts
0
2917
January 25th, 2017 17:00
Unity System Drive
Unity System Drive
Unity System Drive (Used be called Vault drive)
Detailed Information
Question:
Is there any difference between Unity System Drive (used be called Vault) and VNX system drive (Vault Drive)?
Are there any concerns when creating user pool on Unity system drive (Vault Drive)?
Answer:
About system drive (Vault Drive) …. Write cache is used M.2 SSD in Unity so system drive (Vault Drive) will not be used. That is why unlike VNX, Unity can create Pools in system drive (Vault Drive). But Unity system information still resides in the first 4 drives (same as VNX) and used 107GB per drive. So amount of space can be used for pool is smaller than non vault drive. Also note that upon drive failure on system drive (Vault Drive) you need to copy back manually after rebuild to put User data back on same drive. (If they wish to)
Author: Aya Saito
sm3013
1 Rookie
•
43 Posts
0
July 25th, 2022 08:00
Ok so I'm getting requests to wipe the first 4 drives to ensure all of the data is gone and let the next user worry about reinstalling what ever goes on the first 4 drives on the Unity that have the yellow sticker. If those are erased can the M.2 reimage from the back end by using the svc_reimage command after they are erased or is the unit bricked at this point? I'm trying to keep the item functional after removing all data but and some people are satisfied with the svc_initial command and want the drives wiped. I was thinking wiping the first 4 drives and then reimaging it from the m.2 would take care of the issue.