Factory Reset a Dell sc4020 with no serial console user password

Create a USB Stick with MSDOS partition and a single ascii file name "unlock.py" or unlock.phy (cant remember) and insert "unlock Admin" without the quotes into the controller lead. After a couple of seconds you can login by using the default password "mmm".

 

Regards,

Joerg

the default password is "mmm" ?

>Yes thats the default

 

Regards,
Joerg

The factory reset i found is as follows below. However when I list all the files I find all kinds of files and logs that don't look like they belong if it was a true factory reset where all logs, config files, backup configs, snapshots, phone home logs etc. etc. etc. On a side note we are getting rid of this unit so I know the powers that be wont want to spend any more money on getting a contract for a support ticket so any help would be great. I listed as small sample directories/files below as well that caused me to scratch my head and believe this isn't a true factory reset.

Restore Controllers to Factory Settings
Clear HSN, VPD and Configuration
 Open SecureCRT or Putty session to the serial ports of the 2 controllers to be restored.
 Login to each controller.
If not previously changed the production default login is:
Login: Admin Password:mmm
 From the CLI prompt on the top controller enter:
>shellaccess developer
>platform init hsn set 0
>platform vpd set ssn=0
>platform vpd set assetTag=0
>cs purge all
>disk global clobberall
>platform bmc set source DHCP
>-reset
 From the CLI prompt on the bottom controller enter:
>shellaccess developer
>platform init hsn set 0
>cs purge all
>disk global clobberall
> platform bmc set source DHCP
>-reset
 Both controllers will reset and initialize to the safemode promp

firmware/compellent_06_07_40_012 80257 17605524 11/16/2017 20:18:23 11/16/2017 20:18:45
firmware/tinybsd_06_07_40_012.tar 80258 47037440 11/16/2017 20:18:45 11/16/2017 20:19:42
firmware/platform/chassis_bbuc_9_5_0000.ima 80260 131072 06/21/2017 22:11:12 06/21/2017 22:11:12
firmware/platform/chassis_bbuc_9_5_0000.ima.md5 80263 33 08/18/2017 20:14:35 08/18/2017 20:14:35
firmware/platform/chassis_bios_0_7_0002.ima 80265 4325376 06/21/2017 22:11:12 06/21/2017 22:11:12
firmware/platform/chassis_bios_0_7_0002.ima.md5 80266 33 08/18/2017 20:14:35 08/18/2017 20:14:35
firmware/platform/chassis_cpld_7_0_000E.ima 80267 131072 06/21/2017 22:10:18 06/21/2017 22:10:18
firmware/platform/chassis_cpld_7_0_000E.ima.md5 80268 33 08/18/2017 20:14:35 08/18/2017 20:14:35
firmware/platform/chassis_manifest.txt 80270 104 08/18/2017 20:14:35 08/18/2017 20:14:35
firmware/platform/chassis_manifest1.txt 80271 104 08/18/2017 20:14:35 08/18/2017 20:14:35
firmware/platform/chassis_root_2_8_000F.ima 80272 33554432 06/21/2017 22:11:12 06/21/2017 22:11:12
firmware/platform/chassis_root_2_8_000F.ima.md5 80273 33 08/18/2017 20:14:35 08/18/2017 20:14:35
firmware/platform/Yafu.ini 80274 19465 06/21/2017 22:10:18 06/21/2017 22:10:18
firmware/platform/chassis_firmware.tgz 1525116 18110626 11/20/2017 22:13:26 11/20/2017 22:13:26
firmware/platform/chassis_firstbootdone.txt 80275 0 11/28/2017 02:33:56 11/16/2021 17:15:24
firmware/compellent_06_05_20_018 80261 13062160 07/28/2015 15:34:59 07/28/2015 15:35:14
firmware/tinybsd_06_05_20_018.tar 80262 33631744 07/28/2015 15:35:50 07/28/2015 15:36:30
firmware/compellent_QSA4_0_0_27.bin 1525117 12901237 11/20/2017 22:13:27 11/20/2017 22:13:27
firmware/compellent_QSA4_0_0_11.bin 80264 12870887 07/28/2015 15:40:47 07/28/2015 15:41:02
firmware/compellent_QSA4_0_0_22.bin 80269 12884672 11/16/2017 20:31:04 11/16/2017 20:31:23
firmware/compellent_fw_070211004_b.tgz 1525116 18110626 11/20/2017 22:13:26 11/20/2017 22:13:26
firmware/tinybsd_07_02_11_004.tar 1525122 56734720 11/20/2017 22:13:27 11/20/2017 22:13:28
firmware/compellent_07_02_11_004 1525128 24173468 11/20/2017 22:13:29 11/20/2017 22:13:29
logs/qrq.log 882820 0 05/04/2015 19:36:46 05/04/2015 19:36:46
logs/syslog.0 882837 412706 11/16/2021 17:05:17 11/16/2021 17:18:32
logs/syslog.1 882836 166473 11/16/2021 16:53:26 11/16/2021 17:05:17
logs/syslog.2 882834 396309 11/16/2021 13:44:43 11/16/2021 16:53:26
logs/appwatchdogd_timeout.curr 882818 105421 11/10/2017 22:12:09 11/15/2017 00:01:36
logs/syslog.3 882839 85495 11/16/2021 12:36:44 11/16/2021 13:44:43
logs/syslog.4 882848 165023 11/16/2021 12:32:24 11/16/2021 12:36:44
logs/syslog.5 882847 72808 11/15/2021 20:54:52 11/16/2021 12:32:24
logs/emailManager.log 882822 0 11/18/2017 19:25:25 11/18/2017 19:25:25
logs/syslog.6 882846 178855 11/15/2021 20:50:33 11/15/2021 20:54:52
logs/syslog.7 882843 57725 11/15/2021 20:48:56 11/15/2021 20:50:33
logs/syslog.8 882842 165285 11/15/2021 20:44:37 11/15/2021 20:48:56
logs/syslog.9 882835 42311 11/15/2021 20:43:01 11/15/2021 20:44:37
logs/phoning_appwatchdogd_timeout.log.ffffffff.gz 882849 89759 11/08/2021 15:58:37 11/08/2021 15:58:37
logs/appwatchdogd_timeout.log.0 882851 5699 11/15/2021 17:45:20 11/15/2021 19:09:35
logs/appwatchdogd_timeout.log.1 882850 17097 11/15/2021 13:41:18 11/15/2021 13:43:11
logs/appwatchdogd_timeout.log.2 882844 683609 11/12/2021 14:52:00 11/12/2021 15:33:43
phoned_home/asyncsignalsafe.log 882824 2990 09/24/2017 23:01:58 11/10/2017 21:58:11
phoned_home/appwatchdogd_timeout.log 882817 181037 10/04/2017 23:38:06 10/26/2017 00:06:20
phoned_home/logFile.gz 6 46006 11/28/2017 02:04:00 11/28/2017 02:04:00
phoned_home/smartctl.txt 882821 4504 08/17/2019 02:55:42 08/23/2019 02:55:54
phoned_home/appwatchdogd_timeout.log.0.gz 882840 117439 03/26/2019 00:00:00 03/26/2019 00:00:

 

 

 

Hello sm3013,

 

A factory reset would need a call into support so that we can capture the license & some other important data before reset.

Support is the only ones who can reset the system as there are quite a few steps that have to be done correctly to ensure that all data is removed. I'll note your steps look good for SC4020 systems prior to SCOS 6.7

We can certainly allow community input from anyone that has done it on their own.

What is the procedure to capture the license before reseting? I only have access to the __safemode__ account on serial CLI. 

Thank you,

Hi,

 

If it's in regard to obtain the license file for your SC4020, I've responded to you here: https://dell.to/3A7nzSz

 

I'll leave this post for public comment if there is any further information provided.