As a precaution the Unity arrays has a set of drives that hold a copy of the code and are used as Vault drives, more specifically drives 0 to 4 of the DPE.
When the internal SSD is replaced on a Storage Processor, the system will then install the OS into the new M.2 SSD.
I hope that this information is useful, however if you have any other queries, please let me know by replying to this message.
After reviewing the details provided, when a SP is sent to proceed with a replacement, the system will not include an operating system installed.
The replacement component when shipped does not include the internal M.2 drive, PSU and other components. During the replacement procedure, the components from the old SP will be moved to the replacement unit.
Once the new SP is inserted, the system will run the regular checks to verify the status of the system, and if necessary firmware updates to the motherboard may be installed during the initial startup sequence, however the Operating system will not be re-installed.
I hope that this information is useful, however if you have further queries, please let us know by updating this thread.
Hi Ricardo, Thanks for the help, appriciate!! So where does the OE reside on a "new " SP, on the M.2 SSD. If so what happens when a M.2SSD fails and is replaced with new one ? Cheers, Vivek
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?
Thanks for the reply, so just go be clear, I can remove the drives the first 4 drives, use a 3rd party erasure tool to erase them, place it back in the Unity and it will boot?
After i wiped the first 4 drive and place them back in the chassis. i ran the reimage command but it fails to install. When it first boots i get @Failed to mount SSD with read-write permission! My guess is the reimage command isnt working after the first 4 vault drives are erase because of read write permissions. Anyone have any suggestions on show to get the backup image from the m.2 back on the first 4 drives after wiping them?
Are you using a recovery image and not an upgrade image? You may need to call phone support so they can login as root through the console and set the partition to read/write.
Ricardo_Lopes
14 Posts
2184
1
Posted July 5th, 2019 01:00
Hi @vivek_asml
Thank you for your reply.
As a precaution the Unity arrays has a set of drives that hold a copy of the code and are used as Vault drives, more specifically drives 0 to 4 of the DPE.
When the internal SSD is replaced on a Storage Processor, the system will then install the OS into the new M.2 SSD.
I hope that this information is useful, however if you have any other queries, please let me know by replying to this message.