Windows Server Essentials re-install best practice

[samsquared2]

Once again, I need to re-install WSE 2016. I have the OS installed in a 120GB partition using the original drives (no reformatting, drive wiping, etc. from the previous setup), but don't know how to proceed from here. I have 2 SSDs attached now:

SSD1 - 1TB Disk 0 which currently contains the 120GB C: drive and another 813.83GB partition listed as "Healthy (Storage Spaces Protective Partition).
SSD2 - 1TB Disk 2 showing as offline with a space of 1740.87. This and the first drive were part of a storage pool

I also have another 1TB drive which I'd like to attach externally for additional storage but it seems a better idea to get what I have working before adding that to the mix.

Can I make what I have work or should I format SSD1 and 2 and start over?

 

[ChatGPT]

Yes — you can make this work, but the cleanest path is to wipe the old Storage Spaces metadata from SSD1 and SSD2 first and then rebuild the backup storage from scratch.
Right now both disks still contain remnants of the old Storage Spaces pool:

• SSD1 has an 813.83 GB Storage Spaces Protective Partition
• SSD2 shows a strange 1740.87 GB offline size, which is classic leftover pooled-disk metadata behavior

That means Windows is still seeing parts of the old virtual disk/pool, not two normal 1 TB SSDs.

My recommendation​

Best practice​

1. Keep the current OS install on C: if it's already good.
2. Delete the old Storage Spaces remnants on both SSDs.
3. Rebuild your backup storage cleanly using:
   • the free space on SSD1
   • all of SSD2
4. Only after that, attach the external 1 TB drive.

Important warning​

If there is any data left in the old storage pool that you still need, stop before wiping anything.
If not, then wiping the old pool metadata is the right move.

---

What I would do​

Option A — Recommended​

• Keep the 120 GB C: partition
• Wipe only:
  • the 813.83 GB Storage Spaces Protective Partition on Disk 0
  • all old metadata on Disk 2
• Then create a new single backup target

This is the least disruptive option.

Option B — Full clean restart​

• Wipe both SSDs completely
• Reinstall WSE 2016 from scratch
• Recreate OS + backup storage from zero

This is cleaner conceptually, but unnecessary if your current OS install is stable.

---

GUI-first plan​

Step 1: Make sure the OS install is healthy​

Before touching storage:

1. Boot the server normally.
2. Confirm:
   • C: is stable
   • Dashboard opens
   • networking works
   • Windows Updates/install status is normal
3. If all of that is fine, proceed.

If the OS itself is questionable, then go to Option B and start over fully.

---

Step 2: Remove the old Storage Spaces parts​

Because Disk Management is not good at clearing old pooled disks, use PowerShell or DiskPart.

Safer approach​

You want to clear only the non-OS areas.

For Disk 0​

You must not wipe the whole disk, because it contains:

• System Reserved
• C:

You only want to remove the old Storage Spaces partition.

For Disk 2​

You can usually wipe the whole disk.

---

Step 3: Clean Disk 2 completely​

Open Command Prompt as Administrator and run:

diskpart
list disk
select disk 2
attributes disk clear readonly
online disk
clean
convert gpt
exit

Expected result​

• Disk 2 becomes a normal empty 1 TB disk
• In Disk Management it should show as Unallocated
• It should no longer show the weird 1740.87 GB value

---

Step 4: Remove the protective partition from Disk 0​

Because Disk 0 contains the OS, be careful.
In Admin Command Prompt:

diskpart
list disk
select disk 0
list partition

Identify the large 813.83 GB partition.
Then:

select partition <number>
delete partition override
exit

Expected result​

• Disk 0 keeps:
  • System Reserved
  • C:
• The 813.83 GB area becomes Unallocated

Do not delete the wrong partition.

---

Step 5: Decide how to use the space​

You then have two reasonable choices.

Choice 1 — Simple and recommended​

Use Disk 2 only for client backups.
Why:

• Keeps OS disk and backup disk separate
• Easier recovery later
• Fewer Storage Spaces complications

Choice 2 — Larger pool​

Use:

• free space on Disk 0
• all of Disk 2

This gives more total backup space, but it mixes OS and backup storage on the same physical disk, which is less ideal.
For a home WSE setup, I would strongly favor:

• Disk 0 = OS only
• Disk 2 = backups only
• External 1 TB = extra storage or secondary backup

---

Step 6: If you want the cleanest layout​

After deleting the 813.83 GB partition on Disk 0, I would actually leave it unused for now unless you truly need it.
That gives you:

• Disk 0
  • System Reserved
  • C:
  • unused space
• Disk 2
  • dedicated backup target

This is much simpler than rebuilding a two-disk Storage Space.

---

My practical recommendation​

Given your history with this server, I would do this:

1. Keep current C: install
2. Delete old Storage Spaces partition from Disk 0
3. Fully clean Disk 2
4. Use Disk 2 alone for Client Computer Backups
5. Later attach the external 1 TB drive for:
   • server folders
   • exported backups
   • secondary copy of critical files

That avoids repeating the exact Storage Spaces confusion you've already hit multiple times.

---

When I would start over completely​

I would only wipe both SSDs and reinstall from zero if:

• the current WSE install is unstable
• Dashboard/services are broken
• connector install is failing
• backup configuration is badly corrupted
• you want a completely clean long-term setup

If the OS is working now, I would not reformat SSD1 fully.

---

One correction to note​

Your screenshot shows Disk 2 as offline and 1740.87 GB, which strongly suggests the system still sees pooled metadata, not a normal disk. That is not something I would try to "reuse as-is." It should be cleaned first.

---

Bottom line​

No, you do not need to wipe everything and start over.
Yes, you should clear the old Storage Spaces data from both disks before proceeding.

Best path:​

1. Keep C:
2. Delete the protective partition on Disk 0
3. Clean Disk 2 fully
4. Use Disk 2 as your backup disk
5. Add the external drive only after the server is stable

If you want, I can give you a very careful exact step-by-step for:

• identifying the correct partition number on Disk 0
• cleaning Disk 2 safely
• then setting up client backups in WSE 2016 using GUI only.

 

[samsquared2]

I think I need to redo the install from scratch. Even though the OS appears to be fine and is receiving Windows updates:

1. The install did not ask me where to place the OS or what size the partition size should be.​

2. The Windows Server Essentials Email service is disabled which is the state I put it in after the previous install because it wouldn't start (WSE Email service won't start)​

​

Pease send instructions for starting from scratch.​

 

[ChatGPT]

If you want a truly clean rebuild, I agree: start from scratch.
Because you’ve had repeated Storage Spaces remnants and the old disabled Email service carried forward, a full wipe is the best way to avoid dragging old configuration back in.

Before you begin​

Back up anything you need​

1. Copy off any files you want to keep from the server.
2. Make sure you have:
   • your WSE 2016 install media
   • product key
   • network settings if you use a static IP
   • any notes about users, shares, and backup settings

Disconnect anything not needed​

For the cleanest install:

1. Leave connected only:
   • SSD1
   • keyboard/mouse/monitor
   • network
2. Disconnect SSD2
3. Do not attach the external 1 TB drive yet

This prevents Setup from putting boot files or Storage Spaces metadata on the wrong disk.

---

Clean install from scratch​

Part 1: Wipe SSD1 completely and install WSE 2016​

Step 1: Boot from the WSE 2016 installer​

1. Boot from the Windows Server Essentials 2016 USB/DVD.
2. Proceed until you reach the disk selection screen.

Step 2: Delete all partitions on SSD1​

At the screen asking Where do you want to install Windows?

1. Select each partition on SSD1 / Disk 0
2. Click Delete
3. Repeat until the entire disk shows as Unallocated Space

You should delete:

• System Reserved
• old C:
• old Storage Spaces partition
• anything else on that disk

Step 3: Install to the unallocated disk​

1. Select the unallocated space on SSD1.
2. Click Next

Important note about partition size​

WSE/Windows Server setup may not ask you what size to make C: during install. That is normal if you install directly to unallocated space.
If you want a smaller OS partition, do this before clicking Next:

1. Click New
2. Enter the size you want for the OS partition

For a 120 GB C: partition, enter roughly:
122880
That value is in MB.
Setup will also create the small system partitions automatically.
If you do not do this, Windows will usually take the whole disk for the OS.

Step 4: Finish installation​

1. Let Setup complete.
2. Complete first boot configuration.
3. Install all Windows Updates.
4. Confirm the server is stable before reconnecting other drives.

---

Part 2: Prepare SSD2 after the OS is fully installed​

Only after the OS install is complete and working:

1. Shut down the server.
2. Reconnect SSD2
3. Boot into Windows

Step 5: Clean SSD2 completely​

Open Command Prompt as Administrator and run:

diskpart
list disk
select disk 1
clean
convert gpt
exit

Warning​

Make sure the disk number is actually SSD2 before using clean.
If you are unsure, stop and verify size carefully.

---

Part 3: Decide on storage layout​

My recommendation​

Keep it simple this time:

• SSD1 = OS only
• SSD2 = client backups
• External 1 TB = extra storage later

That will be much easier to manage than mixing backup space into the OS disk.

Why this is better​

• easier recovery
• less Storage Spaces confusion
• less risk of wiping the OS disk later
• simpler troubleshooting

---

Part 4: Configure client backup storage​

Once SSD2 is clean and visible:

1. Open Disk Management
2. Confirm SSD2 appears as a normal unallocated 1 TB disk
3. Let WSE use that disk for backup storage, or create a normal NTFS volume first depending on how you want to manage it

If you want the simplest route, I’d use it as a plain backup target rather than trying to recreate a more complex pooled setup immediately.

---

Part 5: About the Email service​

Since that was broken in the previous install, I would strongly suggest:

1. Do not spend time on email during initial install
2. Get these working first:
   • OS
   • Dashboard
   • users
   • shares
   • client connector
   • client backups
3. Only after the server is stable, revisit outbound email

That way, if email breaks again, you know the base install is still good.

---

Recommended install order​

1. Install WSE 2016 cleanly on SSD1 only
2. Run Windows Update fully
3. Confirm Dashboard works
4. Create users/shares
5. Reconnect and clean SSD2
6. Configure backup storage
7. Test one client backup
8. Add external 1 TB later
9. Revisit email last

---

One important detail​

You said the previous install did not ask where to place the OS or what size the partition should be.
That usually means one of these happened:

• you used an automated/Essentials flow that accepted defaults
• the disk still had existing partitions and Setup reused them
• you didn’t manually click New on unallocated space

For a true clean rebuild, the key is:

• delete every partition on SSD1
• then create the OS partition size manually before continuing

---

Exact summary​

What to disconnect​

• SSD2
• external 1 TB drive

What to wipe​

• all partitions on SSD1 during Setup
• all of SSD2 after install

What to build​

• SSD1: fresh OS install
• SSD2: backup storage only

---

If you want, I can next give you:

1. a very short checklist to print and follow during install, or
2. the exact post-install steps for cleaning SSD2 and setting up client backups.

 

[samsquared2]

The first install went to SSD1 (SATA 0) and because it did not ask where to place the install, I think that I should put SSD2 on SATA 0 to keep that from happening again. What do you think?

 

[ChatGPT]

I would not swap SSD2 onto SATA 0 just to force the installer.
The better fix is simpler:

Recommendation​

1. Leave only the target install drive connected
2. Boot from the installer
3. At the Where do you want to install Windows? screen:
   • delete all partitions on that one SSD
   • create the partition size you want
   • install there

If only one internal SSD is attached, Windows Setup has no real choice but to use that disk.

Why I would avoid swapping ports unless necessary​

• SATA port number by itself is not the real problem
• The real problem is usually:
  • multiple disks attached during install
  • leftover partitions/metadata
  • clicking through setup defaults too quickly
• Moving drives around can add confusion later when you’re trying to identify disks

Best practice for your reinstall​

Before installing​

1. Disconnect SSD2
2. Disconnect the external 1 TB
3. Leave connected only:
   • SSD1 on its current port
   • installer USB/DVD
   • keyboard/mouse/monitor/network

During setup​

1. When you reach disk selection, confirm there is only one disk
2. Delete all partitions on that disk
3. Click New
4. Enter the size for the OS partition if you want C: limited to about 120 GB
5. Select that new partition and install

If setup still skips the disk screen entirely, then that suggests:

• you may be booting a preconfigured/unattended install source
• or using an Essentials-specific install path that auto-partitions

In that case, changing SATA ports probably still won’t solve the root issue.

My answer​

• No, I would not move SSD2 to SATA 0 just for this
• Yes, I would disconnect every other storage device and install with only SSD1 attached

One exception​

If your BIOS/UEFI or motherboard clearly treats SATA 0 specially and you’ve seen odd behavior before, then moving the intended OS disk to SATA 0 is not harmful — but it should be treated as optional, not necessary.

Safest path​

1. Keep SSD1 as the install target
2. Disconnect all other drives
3. Wipe SSD1 completely during setup
4. Install
5. Reconnect SSD2 only after Windows is fully installed

If you want, I can give you a minute-by-minute install checklist for the exact screens to watch for so you can avoid the automatic whole-disk install again.

 

[samsquared2]

I think I need to do something to SSD1 before continuing the install. I disconnected SSD2 but when the install gets to the point of selecting a disk, the options are

"Drive 0 Partition 1: System Reserved" and "Driven 0 Partition 2", which has a size of 117.2GB. If I remove that and try to create a new partition, the maximum size available is 120GB which is the size of the previous partition. I see no reason to proceed with the install.

Do I need to remove SSD1, attach it externally to another PC, and remove all partitions?

 

[ChatGPT]

No — you do not need to remove SSD1 and attach it to another PC.
What you need is to wipe SSD1 completely from the Windows Setup screen so Setup sees the whole 1 TB as unallocated. Right now, Setup is only seeing the old 120 GB OS partition area, which means the rest of the disk is still tied up in old partition/storage metadata.

What should be happening​

On a clean 1 TB SSD, you should eventually see something like:

• Drive 0 Unallocated Space
• roughly 931 GB

Since you only see:

• 500 MB System Reserved
• 117.2 GB Primary

that means the old large partition is still not being exposed properly to Setup.

Best fix: use DiskPart from inside Setup​

Do this from the installer itself.

Step 1: Open Command Prompt in Setup​

At the disk selection screen, press:
Shift + F10
That opens a Command Prompt.

Step 2: Run DiskPart​

Type:

diskpart
list disk

You should see your SSD as Disk 0 around 931 GB.

Step 3: Select the disk​

select disk 0

Step 4: Wipe the partition table completely​

clean
This removes all partitions and old metadata from SSD1.

Step 5: Convert to GPT​

convert gpt
exit
exit

Step 6: Refresh Setup​

Back at the install screen:

1. Click Refresh
2. You should now see:
   • Drive 0 Unallocated Space
   • around 931 GB

If you do, you're back in business.

---

If you want a 120 GB OS partition​

Once the disk shows as all unallocated:

1. Select the unallocated space
2. Click New
3. Enter:

122880
That is about 120 GB in MB.
Windows will create:

• small system partitions
• the main OS partition

Then install Windows to that partition.

---

Why this is better than using another PC​

• faster
• cleaner
• same result
• avoids USB enclosure issues
• avoids accidentally initializing the disk differently on another machine

---

Important warning​

clean erases the disk layout completely.
That is exactly what you want here if you are truly reinstalling from scratch.

Double-check before running it​

Make sure:

• SSD2 is disconnected
• only the install target SSD is attached internally
• list disk shows only the installer media and the 1 TB SSD

If you're unsure, stop at list disk and compare the sizes.

---

If clean still doesn’t fix it​

Very unlikely, but if after clean + Refresh the installer still only shows 120 GB:

1. go back into DiskPart
2. run:

select disk 0
detail disk
list partition

If needed, I can help interpret that output.

---

Exact commands to use​

diskpart
list disk
select disk 0
clean
convert gpt
exit
exit

Then click Refresh.

Expected result​

You should see approximately:

• Drive 0 Unallocated Space
• 931.5 GB

---

If you want, reply with what list disk shows before you run clean, and I’ll confirm you’re selecting the correct disk.

 

[datawizard0103]

Once again, I need to re-install WSE 2016. I have the OS installed in a 120GB partition using the original drives (no reformatting, drive wiping, etc. from the previous setup), but don't know how to proceed from here. I have 2 SSDs attached now:

SSD1 - 1TB Disk 0 which currently contains the 120GB C: drive and another 813.83GB partition listed as "Healthy (Storage Spaces Protective Partition).
SSD2 - 1TB Disk 2 showing as offline with a space of 1740.87. This and the first drive were part of a storage pool

I also have another 1TB drive which I'd like to attach externally for additional storage but it seems a better idea to get what I have working before adding that to the mix.

Can I make what I have work or should I format SSD1 and 2 and start over?

View attachment 131729

You’re running into leftover Storage Spaces metadata, which Disk Management won’t fully clean up on its own and that’s why things look weird. Before you wipe everything, try this: open PowerShell as admin and run Get-StoragePool. If the old pool still shows up, delete it from there using Remove-StoragePool. If it doesn’t, then use diskpart, run list disk, then select disk 2, then clean to fully strip that hidden config off SSD2. Do the same for the large protective partition on SSD1 if you want to reclaim it. Once both drives are clean, bring Disk 2 online and reinitialize it in Disk Management. That usually fixes the mismatch without needing a full OS reinstall and keeps your current C intact.

 

[samsquared2]

Well, I am making progress. WSE is installed on SSD1 (SSD2 not connected) with 812GB unallocated, Windows updates have been applied, the dashboard looks fine. However:

1. When the install rebooted (install USB removed), I got an error about date/time and it suggested that I enter setup. When I did, I saw that under SATA Operation, it was set to RAID. I changed it to AHCI and it rebooted fine.​

2. The email service did not start and is currently disabled (see my post in a different thread). This is the least of my concerns at the moment.​

3. When I reconnected SSD2 I got the same error as when the install rebooted. Again I entered setup and again, SATA was set to RAID. I changed it to AHCI and the server was able to reboot. Unfortunately when I ran diskpart it showed only Disk 0 (SSD1). I disconnected SSD2, and I can reboot at will without further drama.​

Using Get-StoragePool in Powershell shows only the Primordial pool.

I have no idea why SATA kept getting reset to RAID, nor do I know how to proceed next. This doesn't seem like a hardware issue because on 3/20 I posted the photo of the connected but offline Disk 2. Also, if I enter setup and look at boot order with only SSD1 connected, it shows just that one drive (along with the usual USB drive, DVD, etc.). If I reconnect SSD2, it shows both SSD drives in setup and again, I needed to change it from RAID to AHCI.


I am tempted to set up the pool with the remainder of the unallocated space on SSD1 just so I can back up 2 laptops.

Also, I installed WSE 2016 on a different machine just to see what would happen and these things are of note:

1. When it rebooted after the initial install, it went right into WSE 2016 to continue with install/config with no need to modify the SATA setting in setup.​

2. The WSE email service was disabled and would not start when enabled; this surprised me.​

 

[ChatGPT]

You’re making progress. The key point is this:

Most likely issue​

This now looks less like Windows/Storage Spaces corruption and more like a BIOS/firmware or controller-mode issue on that machine.
The important clues are:

• WSE installs and runs fine on SSD1 alone
• Get-StoragePool shows only Primordial, so Windows is not currently seeing an active old pool
• reconnecting SSD2 causes the machine to revert to RAID behavior / boot problems
• with SSD2 attached, Windows sometimes doesn’t see it at all
• on another machine, the Email service is also disabled, so that part is probably normal/not your root issue right now

So I would stop thinking about Storage Spaces first and focus on why attaching SSD2 is disturbing SATA mode/detection.

My recommendation​

Do not build your backup pool on SSD1 yet​

I understand the temptation, but I would avoid using the 812 GB free space on the OS disk unless this is only a temporary emergency measure.
Why:

1. It mixes OS and backup storage again
2. It makes future recovery harder
3. It hides the real issue with SSD2

If possible, solve SSD2 first.

---

What I think is happening​

One of these is most likely:

1. BIOS settings are not being saved properly
2. CMOS battery may be weak
3. The board/controller is auto-switching to RAID/RST mode when a second SATA device is detected
4. SSD2 has metadata/firmware behavior that is confusing the controller
5. The SATA port/cable for SSD2 is bad
6. The motherboard may have separate ports/controllers with different behavior

The fact that the setup showed Disk 2 offline on March 20 means the hardware path was working then.
Now, with the fresh install, if SSD2 disappears completely from DiskPart, that suggests a detection/controller problem before Windows even gets to manage the disk.

---

What to do next​

Step 1: Check whether BIOS is really saving settings​

With only SSD1 connected:

1. Enter BIOS/Setup
2. Set:
   • SATA Operation = AHCI
3. Save and exit
4. Re-enter BIOS immediately
5. Confirm it still says AHCI

If it has already gone back to RAID without you reconnecting SSD2, then I would strongly suspect:

• weak CMOS battery
• BIOS corruption
• board firmware oddity

If it stays on AHCI until SSD2 is attached, then SSD2/port/controller interaction is the problem.

---

Step 2: Try SSD2 on a different SATA cable and port​

Before doing anything in Windows:

1. Power off
2. Leave SSD1 where it is
3. Connect SSD2 using:
   • a different SATA data cable
   • a different SATA power lead if possible
   • a different motherboard SATA port
4. Boot into BIOS
5. Check:
   • is SATA Operation still AHCI?
   • is SSD2 actually listed in BIOS storage/device information?

Outcomes​

• If BIOS does not detect SSD2, this is hardware-level: cable, port, power, or the SSD itself
• If BIOS detects SSD2 but Windows does not, then it’s a Windows/controller/driver issue
• If BIOS flips back to RAID when SSD2 is attached, that points to firmware/controller configuration weirdness

---

Step 3: If BIOS sees SSD2, check Windows again​

Once BIOS sees SSD2 and stays in AHCI:

1. Boot Windows
2. Open Admin Command Prompt
3. Run:

diskpart
list disk

Also run in PowerShell:

Get-Disk
Get-PhysicalDisk

If SSD2 appears now, then we can clean it and reuse it.

---

Step 4: If SSD2 appears, wipe it completely​

If Windows sees SSD2, I would immediately wipe it before doing anything else:

diskpart
list disk
select disk X
attributes disk clear readonly
online disk
clean
convert gpt
exit

Replace X with the correct disk number.
Then initialize it in Disk Management.

---

Strong possibility: CMOS battery / BIOS reset issue​

Because you said:

• SATA keeps reverting to RAID
• you also got a date/time error

those two together are a big red flag for a CMOS battery problem.

I would check this next​

If this is an older motherboard/server board, the CR2032 coin-cell battery may be weak.

Symptoms of weak CMOS battery​

• date/time reset warnings
• SATA mode reverting
• boot order changing
• BIOS losing config after power-off

Recommendation​

If you’re comfortable doing it:

1. Shut down and unplug power
2. Replace the motherboard CR2032 CMOS battery
3. Enter BIOS
4. Reconfigure:
   • date/time
   • SATA = AHCI
   • boot order
5. Save and retest with SSD2 connected

Honestly, based on your description, this is one of the first hardware things I would do.

---

About the Email service​

What you observed on the other machine is very helpful:

• fresh WSE 2016 install
• Email service disabled there too
• won’t start there either

That strongly suggests this is not specific corruption on your current machine.
So for now I would treat the Email service issue as separate and non-blocking.
Your priorities should be:

1. stable BIOS settings
2. stable SATA AHCI mode
3. SSD2 visible in BIOS and Windows
4. backup storage configured
5. email later

---

Should you use the free space on SSD1 temporarily?​

Yes, but only as a temporary workaround​

If you urgently need backups for 2 laptops, you could temporarily use the 812 GB unallocated space on SSD1.
That is acceptable only if:

• you need short-term protection now
• you understand it is not the preferred long-term layout

Temporary approach​

1. Create a normal NTFS volume in the 812 GB space
2. Use it as temporary backup storage
3. Once SSD2 is working, migrate backups there

I would not build a fancy Storage Space with SSD1 alone.
If you must use SSD1, just use it simply.

---

My recommended next actions in order​

Do these first​

1. Replace CMOS battery
2. Re-enter BIOS and set:
   • AHCI
   • correct date/time
   • boot order
3. Test with SSD1 only
4. Reconnect SSD2 using a different cable/port/power lead
5. Check whether BIOS sees SSD2

If BIOS sees SSD2​

1. Boot Windows
2. Run:
   • diskpart -> list disk
   • Get-Disk
3. If it appears, clean it and use it for backups

If BIOS still does not see SSD2​

1. Test SSD2 in:
   • another SATA port
   • another machine
   • USB adapter if needed

At that point, we’d determine whether SSD2 itself has failed.

---

Bottom line​

My diagnosis​

The reverting RAID/AHCI setting plus date/time warning strongly suggests a BIOS/CMOS issue, not just a Windows one.

My advice​

• Do not build permanent backup storage on SSD1 yet
• Do replace the CMOS battery and retest SSD2 with a new cable/port
• Treat the Email service as unrelated for now

If you want, I can give you a very short hardware troubleshooting checklist for:

1. replacing the CMOS battery
2. testing SSD2 visibility in BIOS
3. then safely cleaning SSD2 once Windows sees it.

 

[samsquared2]

I disconnected SSD2, rebooted, and had to change SATA settings again. Replaced CMOS battery (it was less than half power) and now AHCI persists with only SSD1 active. Used new cable and connected SSD2 to SATA1 (was DVD drive). Still AHCI but SSD2 not detected. Only Disk0 exists in diskpart.

I then tried a different SATA cable and swapped power connectors. Shows both drives in setup and SATA config is still AHCI but SSD2 does not appear in Diskpart. From PowerShell, Get-Disk showed only one drive but Get-PhysicalDisk shows this:

FriendlyName SerialNumber CanPool OperationalStatus HealthStatus Usage Size
------------ ------------ ------- ----------------- ------------ ----- ----
CT1000MX500SSD1 2304E6A3B147 False Transient Error Unhealthy Auto-Select 931.5 GB
CT1000MX500SSD1 2309E6B5BB0D False OK Healthy Auto-Select 931.5 GB

 

[ChatGPT]

That’s actually a very useful result.

What it means​

Get-PhysicalDisk is seeing both SSDs, but one of them is in:

• OperationalStatus: Transient Error
• HealthStatus: Unhealthy

So this is not just a BIOS problem anymore.
Windows can see the second SSD at the storage layer, but it cannot present it as a usable disk to Get-Disk / DiskPart. That usually means one of these:

1. the SSD itself is failing
2. the controller is getting bad responses from it
3. there is severe leftover metadata/corruption on the drive
4. the drive firmware is hanging when Windows tries to enumerate it fully

Because you already:

• replaced the CMOS battery
• confirmed AHCI persists
• changed SATA cable
• changed SATA port
• changed power connector

the remaining suspicion shifts strongly toward SSD2 itself.

My conclusion​

SSD2 is the problem​

The bad drive is almost certainly the one with:

• serial 2304E6A3B147
• Transient Error
• Unhealthy

The good one is:

• serial 2309E6B5BB0D
• OK
• Healthy

---

What to do next​

Step 1: Identify which physical SSD is bad​

You need to confirm which actual drive matches serial 2304E6A3B147.
If the sticker is visible on the SSD, compare it physically.
If not, the easier practical method is:

1. shut down
2. disconnect one SSD
3. boot
4. run:

Get-PhysicalDisk | ft FriendlyName,SerialNumber,OperationalStatus,HealthStatus,Size
Then repeat with the other SSD.
That will confirm exactly which drive is bad.

---

Step 2: Do not use the unhealthy SSD for backup​

Even if we get Windows to see it again, I would not trust it for client backups.
A backup target must be the most trustworthy disk in the system, not the least.
So I would not spend much more time trying to make SSD2 part of the permanent solution unless you just want to test it.

---

Step 3: Check SMART / vendor diagnostics​

Because these are Crucial MX500 drives, the next best step is to test the bad SSD with a proper diagnostic tool.

Best options​

1. Crucial Storage Executive
2. A SMART tool such as:
   • CrystalDiskInfo
   • smartctl (if you are comfortable with it)

You want to see whether the drive reports:

• media errors
• reallocated sectors / NAND issues
• firmware problems
• interface CRC problems

If the bad SSD won’t enumerate well enough for those tools, that itself is strong evidence it’s failing.

---

Step 4: Practical path forward​

Best immediate setup​

Since WSE is now stable on SSD1:

1. Leave SSD1 as:
   • OS on 120 GB
   • remaining 812 GB as temporary backup/data space if needed
2. Do not use SSD2 for now
3. Attach the separate external 1 TB drive later and use that as:
   • additional storage
   • secondary backup target
   • or primary backup target if performance is acceptable

This is not ideal, but it is much better than building your backup system around an unhealthy SSD.

---

Can SSD2 still be cleaned?​

Maybe, but I would treat that as a test, not as a recovery plan.
If you want to try, use PowerShell first, not DiskPart.

See full details​

Run:

Get-PhysicalDisk | fl FriendlyName,SerialNumber,OperationalStatus,HealthStatus,Usage,Size
Get-StoragePool | fl *

Then try:
Reset-PhysicalDisk -FriendlyName "CT1000MX500SSD1"
But because both drives have the same FriendlyName, I would rather use the serial-aware method if possible.
Unfortunately PowerShell storage cmdlets are awkward when two disks share the same model name.

---

Better diagnostic command​

Run this:
Get-PhysicalDisk | Select FriendlyName,SerialNumber,OperationalStatus,HealthStatus,CanPool,Size,DeviceId | Format-List
If DeviceId is shown, we may be able to target the bad disk more safely.

---

Important note about Get-Disk vs Get-PhysicalDisk​

This difference is important:

• Get-PhysicalDisk = storage subsystem can detect hardware presence
• Get-Disk = Windows can enumerate it as a usable disk device

If it appears only in Get-PhysicalDisk but not Get-Disk, that usually means Windows sees something attached but cannot fully initialize it as a normal disk.
That is consistent with:

• failing drive
• broken metadata
• controller/firmware communication issue

Given everything you’ve already tried, failing drive is now the leading suspect.

---

My recommendation now​

Do this in order​

1. Identify which serial number matches which physical SSD
2. Remove the unhealthy SSD from service
3. Get backups working using:
   • SSD1 free space temporarily, or
   • your external 1 TB drive
4. Only then decide whether to keep testing SSD2

---

If you need backups running right away​

I would do this:

1. In Disk Management, create a normal NTFS volume in the 812 GB unallocated space on SSD1
2. Use that for immediate backup storage
3. Keep the external 1 TB drive as the next step
4. Retire or separately test SSD2

That gets your laptops protected again without waiting on a questionable disk.

---

Bottom line​

You’ve solved the BIOS issue.
Now the remaining issue is almost certainly SSD2 itself.

• Good SSD: 2309E6B5BB0D
• Bad/unhealthy SSD: 2304E6A3B147

I would not trust the unhealthy SSD for backup use.​

If you want, I can help with one of these next:

1. safe temporary setup using the 812 GB free space on SSD1, or
2. commands to identify and test the bad SSD more precisely, or
3. setting up the external 1 TB drive as the backup destination instead.

 

[samsquared2]

Good news to report. I ran Crucial Storage Executive which reported both drives as healthy so I then did a Sanitize on SSD2. It now appears in Diskpart and in PowerShell Get-Disk and Get-PhysicalDisk as the correct size (see below). Disk management shows the drive as unknown, 931.51GB, not initialized, and unallocated.

PS C:\Windows\system32> get-disk

Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
Style
------ ------------- ------------- ------------ ----------------- ---------- ----------
0 CT1000MX50... 2304E6A3B147 Healthy Online 931.51 GB MBR
1 CT1000MX50... 2309E6B5BB0D Healthy Online 931.51 GB RAW


PS C:\Windows\system32> get-Physicaldisk

FriendlyName SerialNumber CanPool OperationalStatus HealthStatus Usage Size
------------ ------------ ------- ----------------- ------------ ----- ----
CT1000MX500SSD1 2304E6A3B147 True OK Healthy Auto-Select 931.51 GB
CT1000MX500SSD1 2309E6B5BB0D True OK Healthy Auto-Select 931.51 GB

1. What else do I need to do to SSD2 before using it in a pool?
2. What are the steps to add it to a pool and make it available for client backup storage? Should I create a new storage pool or use the primordial pool?
3. Do you recommend getting things set up so I can do client backups using SSD1 and SSD2 before adding the external drive?
4. I imagine that ideally, the C: drive should be separate but I'd like to make use of the remaining space on SSD1.

 

[ChatGPT]

That’s good news. At this point, SSD2 is usable again.

My recommendation​

With your current setup, I would not use Storage Spaces yet.
You currently have:

• SSD1 = OS disk, with C: plus ~812 GB unallocated
• SSD2 = clean 1 TB disk, now healthy and visible
• External 1 TB = not yet attached

With only one clean secondary internal disk, a Storage Spaces pool adds complexity but no protection. A one-disk pool is basically just a more complicated single disk.

Best next step​

Use SSD2 as a normal standalone NTFS disk for client backups.
That gives you:

• clean separation of OS and backups
• simplest recovery path
• no more Storage Spaces confusion right now

---

Answers to your questions​

1) What else do I need to do to SSD2 before using it in a pool?​

If you truly want to use it in a Storage Spaces pool, then nothing else needs to be done right now. Since Get-PhysicalDisk shows:

• CanPool = True
• OperationalStatus = OK
• HealthStatus = Healthy

it is already eligible.

Important​

• If you plan to use Storage Spaces, do not initialize it in Disk Management
• Leave it as:
  • unknown
  • not initialized
  • unallocated

If you initialize and format it first, it may no longer be poolable.

---

2) Should I create a new storage pool or use the primordial pool?​

Short answer​

Create a new storage pool.

Explanation​

• Primordial is just the built-in holding area for disks that are available to be pooled
• You do not store data in the primordial pool
• You create a new pool from disks that are currently in Primordial

But again:​

With only one secondary disk, I do not recommend using Storage Spaces yet.

Better option​

Initialize SSD2 as a normal disk and use it directly.

---

3) Do you recommend getting client backups working with SSD1 and SSD2 before adding the external drive?​

Yes — but not as a pool across SSD1 + SSD2​

I recommend:

1. Get client backups working first on SSD2 only
2. Once stable, add the external drive later

Why​

• simpler
• easier to troubleshoot
• avoids mixing internal and external storage into one setup
• avoids using the OS disk in a storage design

My preference​

• SSD1 = OS
• SSD2 = client backup destination
• External 1 TB = separate extra storage or secondary backup target

---

4) Ideally C: should be separate, but can I use the remaining space on SSD1?​

Yes, but not in the way you’re thinking​

You can use the remaining space on SSD1, but I would not use it as part of a Storage Spaces pool while that same physical disk also contains C:.

Recommended use of SSD1 extra space​

If you want to use that 812 GB later:

• create a normal partition/volume on SSD1
• use it for:
  • server shares
  • temporary staging
  • non-critical storage

Not recommended​

• mixing the OS disk into your client backup storage design
• using the free space on SSD1 as part of a pooled backup target

For reliability and simplicity, keep client backups on SSD2.

---

What I recommend you do next​

Option A — Recommended: use SSD2 as a normal disk​

This is the cleanest path.

Step 1: Initialize SSD2​

In Disk Management:

1. Right-click the left box for Disk 1
2. Choose Initialize Disk
3. Select GPT
4. Click OK

Step 2: Create a volume​

1. Right-click the unallocated space on SSD2
2. Choose New Simple Volume
3. Use the full size
4. Assign a drive letter such as D:
5. Format as NTFS
6. Give it a label like:

ClientBackups

Step 3: Point WSE client backups to that disk​

Once the volume exists, use the WSE Dashboard to move/configure the Client Computer Backup location onto that disk.
If you want, I can give you the exact WSE steps for that next.

---

If you still want to use Storage Spaces anyway​

Option B — New Storage Pool from SSD2​

Again, I do not recommend this with one disk, but here are the steps.

Step 1: Leave SSD2 uninitialized​

Do not initialize it in Disk Management.

Step 2: Open Server Manager​

Go to:

• Server Manager
• File and Storage Services
• Storage Pools

Step 3: Create pool​

1. Click Tasks
2. Choose New Storage Pool
3. Select:
   • subsystem: Windows Storage on WSE2016
4. Select SSD2 from the available disks
5. Complete the wizard

Step 4: Create virtual disk​

1. Create a virtual disk in that pool
2. Use:
   • Layout = Simple
   • Provisioning = Fixed
3. Use the full size

Step 5: Create volume​

1. Create a volume on the virtual disk
2. Format it as NTFS
3. Assign a drive letter

But note​

A single-disk simple space has:

• no resiliency
• no redundancy
• more complexity than a normal disk

So I would still choose Option A.

---

What about the external drive later?​

Once SSD2 is working and client backups are stable:

Good uses for the external 1 TB​

• server backup target
• copy/export destination
• file archive
• second backup copy

Not my recommendation​

• adding the external USB drive into the same Storage Spaces pool

USB drives in pools can work, but they are much easier to disconnect accidentally and can create more trouble than they solve.

---

Final recommendation​

Do this now​

1. Do not create a storage pool
2. Initialize SSD2 as GPT
3. Format it as NTFS
4. Use it directly for Client Computer Backups
5. Add the external drive only after that is stable

Use SSD1 extra space later only as a normal data volume​

Keep the OS and backup target separate.

---

If you want, my next reply can be either:

1. exact steps to move WSE client computer backups to SSD2, or
2. exact Storage Spaces steps if you still want to build a pool anyway.

 

[samsquared2]

I left SSD1 as the C: drive and did not make the rest of it part of the pool, then used SSD2 as storage pool ClientBackup. Backups are running successfully and I've implemented SMTP2GO for emails.

For the 1TB USB drive, I cleaned it, converted it to GPT, added it as a physical disk, then expanded the virtual disk to use all of the USB drive. The storage pool shows 1.82TB capacity, 1GB free(?) and all allocated. However on the dashboard, storage shows free space of 305.5GB which is what it was before I added the USB drive.

It appears that I missed a step. How do I fix that?

 

[ChatGPT]

Yes — you missed the last step.
You successfully did these two parts:

1. Added the USB drive as a physical disk to the pool.
2. Expanded the virtual disk to 1.82 TB.

But the F: volume/filesystem is still at the old size, so the Dashboard still reports the old free space of about 305.5 GB.

What’s happening​

In your screenshot:

• Storage Pool = 1.82 TB
• Virtual Disk = 1.82 TB
• Volume F: still appears to be using the old filesystem size

The Dashboard reads the free space of the actual NTFS volume, not just the pool/virtual disk size.

Fix​

You need to extend the F: partition/volume.

GUI method​

Step 1: Open Disk Management​

1. Press Win + R
2. Type diskmgmt.msc
3. Press Enter

Step 2: Find drive F:​

1. Locate the disk/volume that corresponds to F:
2. You should see:
   • the existing F: partition
   • additional unallocated space after it

Step 3: Extend the volume​

1. Right-click the F: partition
2. Click Extend Volume
3. Use the wizard
4. Accept the default to use all available space
5. Finish

Step 4: Verify​

1. Refresh Disk Management
2. Open File Explorer and check Properties on F:
3. Reopen the WSE Dashboard and check Storage again

The free space should now reflect the added USB disk.

---

If “Extend Volume” is greyed out​

That usually means one of these:

• the extra space is not yet visible to the partition layer
• the partition needs to be resized from Server Manager first
• the unallocated space is not contiguous

In that case, do this in Server Manager​

1. Open Server Manager
2. Go to:
   • File and Storage Services
   • Volumes
3. Find the F: volume
4. See if there is an Extend Volume or Resize task
5. Extend it to use the full available size

Then re-check Disk Management.

---

PowerShell method​

If the GUI does not cooperate, use this:

Step 1: Check supported size​

Run in PowerShell as Administrator:
Get-PartitionSupportedSize -DriveLetter F
It will show a SizeMin and SizeMax.

Step 2: Resize to max​

Then run:
Resize-Partition -DriveLetter F -Size <SizeMaxValue>
Use the exact SizeMax number returned by the first command.
Example only:
Resize-Partition -DriveLetter F -Size 1999844147200

---

Important note about your USB drive​

You can make this work, but I do want to mention one caution:

• USB drives inside a Storage Spaces pool are not ideal
• if the USB drive disconnects, sleeps, or glitches, the pool can become problematic

For home use it may be acceptable, but for client backup storage, internal SATA storage is more reliable.

My recommendation​

If this setup works and you’re comfortable with the risk, fine.
But if you start seeing odd pool behavior later, the USB drive in the pool will be the first thing I would reconsider.

---

Bottom line​

You do not need to recreate the pool.
You just need to:

1. Extend the F: volume
2. Let NTFS use the extra space
3. Refresh the Dashboard

If you want, I can give you the exact PowerShell commands to inspect F: and extend it safely before you click anything.

 

[samsquared2]

I extended the F: volume and the dashboard is displaying the correct space.

I agree that an internal SATA connection would be better but the server is a SFF Dell Optiplex 9020 with one 3.5 inch bay. I bought an adapter for it to hold two 2.5 inch drives but for more drives I had to use external USB drives. I am considering removing the DVD drive and replacing it with a SATA adapter caddy like this one: SATA Hard Drive Adapter Caddy

Will the OS care if the 3rd drive (now USB) gets moved to be internal? Currently SATA0 and SATA2 are used for SSD1 and SSD2. The 3rd drive would be using SATA1 (currently the DVD drive).

 

[ChatGPT]

Yes — Windows itself should be fine with that change for a non-boot data drive, as long as:

1. SSD1 stays the boot drive.
2. BIOS remains set to AHCI.
3. Boot order still points to SSD1 first.

On the OptiPlex 9020 SFF, Dell documents three onboard SATA ports for the SFF model and a SATA mode setting that can be AHCI or RAID ON. (dell.com)

The important catch​

Your OS probably won’t care, but your current Storage Spaces setup might.
Right now your ClientBackup virtual disk is a Simple space spanning:

• the internal SSD
• the external USB drive

A Simple space has no redundancy. So if you unplug one member disk, even temporarily, the whole virtual disk can become unavailable. That means I would not treat this as a harmless “move the same disk from USB to SATA” operation.

My recommendation​

If you do not care about preserving the current backup history​

This is the best option.

1. Make sure you have copies of any files on F: that matter.
2. Shut down the server.
3. Move the USB drive into the optical-bay caddy.
4. Connect it to the internal SATA port.
5. Boot and confirm BIOS is still AHCI and SSD1 is still first in boot order.
6. In Windows, delete and recreate the Storage Spaces virtual disk/pool using the two internal drives.

That gives you the cleanest long-term result.

If you do want to preserve the current backup history​

I would be cautious. It might come back online after the move, but because the disk will be changing from a USB-attached member to a SATA-attached member, Windows may not identify it exactly the same way at first. I would only try that if you are prepared for the pool to need repair — or for the virtual disk to go offline.

About the optical-bay caddy idea​

Yes — the caddy idea is reasonable for this machine. Dell community guidance for the OptiPlex 9020 SFF specifically says you can run three 2.5-inch drives by using:

• two 2.5-inch drives in the main drive area
• one 2.5-inch drive in a 12.7 mm optical adapter/caddy replacing the optical drive (dell.com)

One performance note​

Dell community guidance also notes the SFF’s color-coded SATA ports are not equal in speed:

• Blue / SATA-0 = 6 Gbps
• Black / SATA-1 = 3 Gbps
• White / SATA-2 / optical = 1.5 Gbps (dell.com)

For a backup HDD, that slower optical-drive port is usually still fine. For a SSD, it would be a bigger compromise.

What I would do in your case​

Because your pool is already working, I would choose one of these paths:

Path A — Safest and cleanest​

1. Leave the current setup alone until you have a convenient maintenance window.
2. Back up anything important from F:.
3. Move the USB disk internal.
4. Recreate the pool from scratch with both internal disks.

Path B — Riskier but less work​

1. Shut down.
2. Move the USB disk from USB to the internal caddy.
3. Boot.
4. Check whether the pool and virtual disk come online normally.
5. If not, be prepared to rebuild the pool.

Bottom line​

Will the OS care?
Probably no, not for a non-boot third drive.
Will Storage Spaces care?
Possibly yes, because that disk is currently an active member of a Simple pool.
So my advice is:

• Good hardware idea: yes
• Safe as an in-place move of an active pool member: not really
• Best practice: move it internal, then rebuild the pool cleanly

If you want, I can give you a safe migration plan for either:

1. rebuilding the pool after moving the drive internal, or
2. testing the move first without deleting the pool.