Updating SCOS on Dell CT-SCV2080

I am in the process of decommissioning an older Dell SCV2080 and I thought it might be a good opportunity to try to update the Storage Center Operating System (SCOS) as the unit is being decommissioned.

When I had this unit in production, its function was mainly to retain backups. As it has aged, support expired and getting replacement drives started to become a challenge. The drives are firmware locked by Dell and purchasing drives online was always a gamble for compatibility reasons. In 2023, I replaced this unit with a new Dell PowerVault ME5084 so I figured that now is a good opportunity to play around with this SCV2080.

When it was used in production and without any support, I couldn’t risk doing these software updates as I had no guidance from Dell or access to the files. The SCOS software used in this article was from the SCV2020 unit that I was able to obtain when troubleshooting with Dell on a previous active ticket. As both storage arrays are part of the SCV2000 series, I wanted to try to update the SCOS on this unit and see if it would take.

Files:

https://mega.nz/file/4NBhFSRD#ACr-GiZkPxfAmGNurTVDNrW3NpFuiNWl33BfI19Smh8

The SCV2080 in question has 171TB of raw space across 47 4TB disk (3.64TB recognized). The operating system is an older SCOS version of 7.1.12.2. To manage this storage center, I have had to use an older version of Dell Storage Manager (DSM) (2018 R1.10, build 18.1.10.171).

Since I’ve replaced this unit with a much newer and larger SAN and this one is being decommissioned, I wanted to try to update the SCV2080 using my guide found below:

https://tweakmyskills.com/dell-compellent-storage-center-scos-upgrade-guide

Before we begin, I’m far from a Dell Storage engineer and if something goes haywire, it is no loss to me as this unit will no longer be used for any of our workloads. Use this guide with caution as I take no responsibility for any problems or challenges that you make encounter along the way.

With that out of the way, I started off by unzipping the SCOS R07.03.20.019.10, which is closest to my current version, to a folder on my desktop that will be running the update from.

I launched DSM, I went into Settings –> SupportAssit option. I disabled SupportAssist and enabled the Configure Update Utility and pointed the IP to that of my desktop that will be running the Dell Storage Center Update Utility. This is where the SCOS updates will be pulled from.

Afterwards, I launched the Dell Storage Center Update Utility from my desktop, pointed the Distro Directory to the location of the unzipped SCOS files. I then pressed the START button to begin validation of the files.

Now going back into DSM, I will manually check for updates and this is what I see:

DSM detects the available SCOS update from my transmit client. I will select the Apply all updates option since I don’t have any services that would be impacted. I will begin the upgrade and see how it works out. I’ll be sure to update my post as I work through the following SCOS:

  • R07.03.20.019.10
  • R07.04.21.004.02
  • R07.05.10.012.01

Edit 1:

I couldn’t perform the update because the Dell Storage Manager client (2018 R1.10, build 18.1.10.171) was too old for the new SCSO version. I upgraded the DSM client from 2018 R1.10 to 2018 R1.20 and restarted the update.

That had worked as it is asking me for the Admin password now.

After about 10-15 minutes, the update completed successfully.

Logging back into DSM, I see this message.

Its possible this is a new feature that we didn’t know of due to the outdated SCOS, or it was disabled and this version informs us of this.

Next, I will try to update to SCOS: R07.04.21.004.02

Back on my desktop, I changed the Distro Directory in the Storage Center Update Utility to point to the SCOS version that I will work on deploying next (R07.04.21.004.02). Make sure to unzip all of the files.

I see the following message in the info log stating the version was validated.

Starting the update the same way as before, it looks like it will run. If it does error out, it may be due to the DSM software version.

Lets see how it goes…

Edit 2:

Just as I thought, I will need to update DSM.

I have version 20.1.2.14 so I will try that.

With DSM 2020 R1.2, the update is now starting to run.

While this upgrade is running, it did provide an error but the process was still running. This update took the longest because I mistakenly left the Selected Installation Type set as Non-Service Affecting.

After a bit of time, the update completed.

The last and final upgrade will be to version R07.05.10.012.01.

I unzipped the folder contents and mounted the files with the Storage Center Update Utility.

I went back into DSM and checked for updates. Below is the final update available and pending. This time I made sure to select Apply all updates – service affecting.

I let DSM do its thing and after a bit of time, the completed message was showing and the final SCOS update was installed.

That is pretty much it for the updates. I am not sure if the SCV2000 series has newer updates than 7.5.10.12.

This is a bit of an involved process if you don’t have an active support contract so I hope this can help somebody out there. It was a fun exercise and something I’ve wanted to do for a while.

Thank you reading this.

Dell Compellent Storage Center SCOS Upgrade Guide

The purpose of this guide is to provide clarity on the process of updating the Storage Center Operating System (SCOS) on Dell Compellent Storage Center SANs.

This guide focuses on updating the Dell SCOS by using the Dell Storage Center Update Utility (SCUU). None of the work should be performed without an active Dell service contract. Performing this work without Dell support/contract may put your SAN at risk if you are unable to recover or restore functionality.

If this is a production device, make sure to schedule a 2-8 hour maintenance window. Allocate more time than needed incase you require troubleshooting and support from Dell.

My instructions have been based on my experience of performing three large updates to bring an outdated SAN up to the most recent SCOS version. I am not responsible/liable for any work that viewers of this article perform or follow. Everything is done at your own risk. If you choose to follow this guide, you are taking your own risk and I do not provide any support on this matter.

Files:

https://mega.nz/file/4NBhFSRD#ACr-GiZkPxfAmGNurTVDNrW3NpFuiNWl33BfI19Smh8

With that out of the way, today we will be working with a Dell Compellent Storage Center SCV2020 which contains two controllers and 24 disks.  My unit has an active support contract with Dell and I’ve performed a few of these upgrades in the past with the guidance of a Dell Storage Engineer.

Usually performing updates on Dell Compellent SANs can be done via the Actions Menu within the Dell Storage Manager (DSM) client and the Check for Updates option. Seen Below.

From my experience, a Dell SAN that is far out of date will not offer you these updates. Usually Dell Support needs to ‘allow’ them to be pushed out to your SAN via SupportAssist but I believe that really outdated units need to be manually updated with the Dell SCUU tool in order to bring them up to a specific version. This may be due to the size of updates or the risk of going from unsupported and outdated version to the latest. I’m not sure and I don’t have an answer so take this with a grain of salt.

SANs like many other infrastructure devices do require system updates for device compatibility, bug fixes and security patches. Often these updates will include potential firmware updates for the SAN controllers and drives and are critical for smooth functionality and computability within a SAN.

With the Dell Storage Centers, if they haven’t been updated for a while, they cannot be managed by more recent versions of Dell Storage Managers (DSM). You will receive a message indicating that the OS of the SAN is outdated. As of this writing (April 2023), the latest DSM is at 2020 R1.10 Release, dated Aug 19, 2022.

Here is an example of that. I have Dell Storage Manager (DSM) 2018 R1.20 installed but the SCOS version is 6.6.11.9. The application is newer than the SCOS version and it does not allow me to manage the SAN. This is due to the DSM application being far too new and not compatible with the 6.6.11.9 SCOS version.

The solution? Try to find a 2016 version of DSM, such this 2016 R3.20 Release.

Within my environment, I use DSM to manage the a few Compellent SANs within one DSM interface. Having all of the SANs on the same SCOS compatibility version as the DSM allows for this to happen.

The SCV2020 that I’m working on initially was at SCOS version 6.6.11.9.6. The most current SCOS version is 7.5.10.12.1. To upgrade the SAN, I’ve had to fumble my way through different Dell DSM versions and SCOS updates.

For example, while going through a few updates, I ran into this message.

Basically I was trying to apply SCOS update 7.4.21.4.2 by using DSM 2018 R1.20. DSM allows upgrades to certain levels of SCOS. Newer versions of SCOS that supersede the DSM version is not allowed. You need to always be ahead with DSM but not too far ahead. This is the problem with not being on top of updates with Dell Compellent SANs.

Now you may ask, If I have a Dell Support Contract, why won’t I just reach out to them? Great question! This unit is overseas and requires me to contact Dell International Support. The international support line has had me redirected to Desktop support a few times despite me selecting enterprise storage, so I decided to tackle this unit on my own.
If something would have come up that requires immediate support, I would have gone through the phone channels and escalation to get support.

With all of that out of the way, lets perform the final update for my Dell SCV2020 from SCOS version 7.3.20.19 to 7.5.10.12.1 by using DSM 2018 R1.20.

Although I’ve mentioned it earlier about the incorrect DSM version, I will try to update to the latest Dell SCOS version with the DSM 2018 R1.20. This will not work but I wanted to show you everything I’ve encountered with these manual updates.

First, you need to obtain the following files:

  • Dell Storage Center Operating System (SCOS) version you want to upgrade to
    • Usually you need to get this from Dells FTP, which is provided with a username and password from Dell support
  • Dell Storage Center Update Utility (SCUU), found here.
    • SCUU guide if you need it, here.
  • Dell Storage Manager (DSM) client
    • 2018 R1.20 – Here
    • 2020 R1.10 – Here

In my case after installing DSM (2018), SCUU and I have my SCOS images, we are going to launch the SCUU tool.

A few things to keep in mind. The workstation that you are working on will be the endpoint IP. This is the IP and the port (9005) that the Compellent will use to connect to your device to perform updates. This is required as we will be turning off SupportAssist to allow the updates to be handled locally and not from Dell.

Click on the Distro Directory button and select the extracted Dell SCOS update you are running. In my case, I’ve extracted the R07.05.10.012.01 zip and pointed the directory to the folder. You can review other options in the Tools menu but the defaults have worked fine for me.

Click on the green Start button. This will begin to validate and prepare the SCOS update to be provided to the SAN. We have yet to configure the Compellent to search for the available update.

At this time, nothing should update at all from my experience. We are only preparing the update on a plate for the SAN to eat it once we bring it out to its table.

Now, launch your DSM version. For me, I am launching the DSM 2018 R1.20 version.

With DSM logged into the SAN, click on the Edit Settings menu and select SupportAssist on the bottom left side.

Click on the Turn off Support Assist option. This will enable the DSM application to point to a different Update Utility Host.

Put a checkmark into the Enabled box for the Configure Update Utility option.
The Update Utility Host or IP address should be the IP that the Dell SCUU tool with the SCOS is waiting on. Make sure the port is 9005 (default).

Once done, click Apply and OK.

Now we will have the DSM application search for the available update. Click on the Actions option then select System and then Check for Update.

Once DSM detects the available update presented by SCUU, you will see something along these lines.

Confirm that the current and new Storage Center versions are what you expect.

You can select the option to download now and install or download now and install later. I will use the first option.

For installation type, as my SAN is not technically in production, I will apply all updates which is service affecting. Yours may differ and you may only need non-service impacting updates. Review the columns of the Update Package Components section. You can see which updates are required and which ones are service affecting. Make your decision based on your business requirements.

As I have redundant controllers in my SAN, this allows me to reboot when necessary without impacting the SAN connectivity, if required.

To recap. I’m installing updates right away and applying all updates.

I pressed OK to initiate the update and voila, this message comes up.

I need to update my DSM from 2018 R1.20 to 2020 R1.10 to be able to install this latest SCOS update.

BRB…

Latest DSM is installed

Now onto the final update. The process is the same. The settings should already be prefilled but its best to validate by going back into SupportAssist and making sure SupportAssist = off and Configure Update Utility = Enabled with the SCUU host IP and port entered.

I’m going back in to check for the available update. Everything remains the same as before.

I am going to OK and the update will start. You may be prompted to enter in your Compellent user credentials.

The Update Available screen seen above will change to Update in Progress and DSM will refresh the window every 30 seconds with the status.

Although the update said it would take 1+ hour to complete, for me it was done in about 30 minutes.

We can confirm that the DSM client sees the latest version installed.

We need to go back in and enable SupportAssist, which is recommended if you have an active Support Contract.

Take a look at the Alerts and Logs tabs and make sure you don’t see anything looks to be critical or service impacting. The Summary tab will also have a brief overview of the SAN health status.

Usually I will reach out to the Dell Support Team and have them review the latest SupportAssist logs and SAN status to make sure everything is functional and there are no alerts or errors that stand out to them.

Go back to the SCUU tool and stop it from sharing the SCOS image. You can now close the application completely. The process isn’t fairly complicated but the challenge is getting the Dell SCOS versions from the Dell FTP. Once you have those, you should be able to make your way through updating the SAN.

Now, all of this has been performed on the Dell Compellent Storage Center units. I am not sure if the PowerVault line will use the same SCOS software. I’d imagine so but that is not a definte answer.

I should have a Dell MD3200 in a few months to play around with that is outdated so I will perform a few tests and create a new post.

That pretty much concludes the process of updating the Dell Compellent SCOS by using the SCUU tool.

Thanks for reading.

What I’ve been up to recently

Since my last relevant post regarding the HP ML150 G6, I’ve been thinking about how to tackle my education on iSCSI/NFS in my home lab environment and also replace my againg 10 year old NAS.

Lets take a step back and let me explain my storage history. About 10 years ago when I beginning to get into IT career wise, I decided to purchase an HP EX490 Mediasmart Server. This little nifty box was one of HP’s products to get their foot into the door of the home NAS market, but the EX490 was a bit more than just a regular NAS.

The EX490 had:

  • Socketed CPU, so upgrading the processor was possible (Intel Celeron 450 2.2Ghz)
  • Upgradable memory (2GB DDR2 but still…)
  • Windows Home Server v1 (based on Server 2003)
  • Toolless drive cages
  • 4 drive bays
  • 10/100/1000 Ethernet
  • 4 USB 2.0 ports and 1 eSATA port

This unit was great when it launched and I did enjoy it what it did for me. Although, the OS was already outdated on the launch of the server, shortly after WHS v2 was released. I didn’t bother changing the OS due to the hassle and my data so stuck with the ancient v1 release.

I’ve kept this little box full with Western Digital Green 2TB drives, which have performed flawlessly over 10 years without any failures. I still have them and will post SMART data in anther post.

The EX490 was and still is a great little unit for the tasks it was designed for but we can all agree that those specs are on the light side even a few years ago. It can still handle file serving needs in 2019 for somebody that doesn’t have high requirement so I will try to find a new owner for this little box.

About a year or two after owning this HP EX490, I did upgrade the EX490 from 2GB to 4GB of memory, using the following make and model RAM: Patriot Memory PSD24G8002 Signature DDR2 4GB CL6 800MHz DIMM, PC2 6400

I also had the EX490 upgraded from it’s slow Intel Celeron 450 to a Intel E8400 CPU around that time. Look at how both CPUs compare using CPU-World here. I’ve always wanted to purchase the Intel Q9550s but back then the CPU was fairly pricey and the E8400 I had laying around from past desktop builds.

With the memory and cpu upgraded, I did notice the increase in performance and continued using the NAS for a few more years.

About 4 years ago, bored and having the want to tinker with the EX490, I finally decided to purchase the Intel Q9550s from eBay. The processor arrived and it was immediately installed. The performance bump from the E8400 to the Intel Q9550s wasn’t very noticeable for me but I was able to check that off my list. See the comparison here.

Anyways, that is my real first exposure to a home NAS/server unit, purchased sometime around 2009-2010. I have since collected more data and I’ve been on the hunt to replace the aging EX490.

I’ve toyed with the idea of a custom NAS or enterprise SAN (LOLZ) since that is really the closest thing I can somewhat relate to from my work enviroment. I didn’t know much about Terramaster, QNAP or Synology so I started searching around to try and find out which manufacturer will provide me a scalable yet powerful and quality unit. My needs were quite basic really;

  • Store my personal data, photos and videos from over the years. No brainer
  • Storage for all my Linux ISOs…
  • Capable of iSCSI and NFS storage that I could integrate with my HP ML150 G6 to practice storage configurations.
  • 2-4 NICs so I could do NIC teaming and practice failover.

So on April 12th, I purchased the Synology DS1618+. The fancy matte black unit arrived and I was really excited. I compared many of the Synology units, from the DS918+ all the way to the ridiculously priced DS1819+.

I’ve played around with the DS1618+, setting a 4x2TB SHR1, Btrfs configuration for my personal data and 2x3TB RAID-1 EXT4 for what I wanted to use for datastores for VMware. I liked the OS, it was nice and basic. I was a bit surprised that enabling ‘advanced’ mode in the Synology control panel seemed to have displayed up a few more items, but everything still looked fairly basic. Regardless, it looks like a polished OS overall.

What sat wrong with me was the hardware. The processor was decent and the memory capability with ECC capable RAM is fantastic but I didn’t feel that what I paid (1100.00 CAD) was worth it. About two weeks after receiving the Synology, I noticed QNAP had a few nicer offerings. I looked at a few modes and noticed that the hardware features of QNAP are much better than Synology. Doing some searches on Google, most user’s that have used both platforms have the same opinion. Synology for the OS and updates, QNAP for the hardware. Multiple QNAP units incoporate PCIe slots (one or two) but also have intergrated 10Gb NICs. I wanted to like the Synology, so I looked at the bigger brother, the DS1819+. I don’t really want 8 bays but for scalability and being able to have a hot spare and SSD for caching (or SSD’s for VM’s) is a benefit.

The DS1618+ was starting to look like something I was going to return. Browsing on Amazon, I was surprised to see the massive total price difference between the DS1618+ and the DS1819+. My DS1618+ cost me about $1107.xx Canadian currency. The DS1819+ sells for about $1333.xx + tax, which brings it to a total of about $15xx.xx Canadian dollars.

$400.00 bucks for another 2 bays? No way Jose.

So I actively searched for a comparable but better(in my eyes) QNAP unit. I’ve looked at a few which met some of my requirements, such as the QNAP TS-932x, TVS-951X or the TS-963X. I love how they are 9-bay, have 10Gb integrated but for some reason something didn’t appeal to me.

I kept searching and I found one that looked like a small price increase over the DS1618+ but still cheaper than the DS1819+ and had more capabilities and features. The QNAP TS-873. This seems to tick off all my wants. 4 NICs, 8-bay, lower cost than the Synology unit but much better in hardware. The only real downfall I see is that the CPU uses a bit more power (15W more normal use vs the DS1618+) but the overall gains from it at the price point leave Synology in the dust (IMO of course).

Now people will say that the QNAP OS isn’t as refined as the Synology unit. Sure I get that, but that is something that QNAP can improve over the years. The hardware, well I’m stuck with for the period I plan to keep this unit for.

I am not purchasing a NAS to use at home for 2-3 years. I am looking to get something for the long haul. My HP EX490 operated pretty reliably for nearly 10 years and thankfully I had no failures.

Last night I placed an order for the TS-873 and I am excited to see what this unit holds. I did have two QNAP NAS (TS-EC879U-RP) at work so I have some familiarity of the OS already. I say did because one of them randomly failed out of the sudden. Thankfully I was able to use the other one to retrieve my data from the drives. Qnap support was pretty poor and slow. Oh well.

Anyways, that’s the gist of my storage history for the past 9-10 years. I know RAID and the number of bays are NOT backup, so fear not. Any critical data will be uploaded to Backblaze under a personal account. Their pricing seems fairly good and the general feedback about them looks to be positive.

What do you think? Do you think I made a wise choice? What do you look for when purchasing a NAS?

Thanks!