plonq: (Screen Punching Mood)
This is a follow-up to my post the other day where I mentioned that I was going to order some new hard drives to replace the one that was generating errors in my mirror. What I didn't show in that picture was that my boot drive was running at at about 95% capacity, and had been for the past couple of years. I would clean it up and get it down under 90%, but it would invariably start collecting clutter again.

On Saturday I put in a curb-side order for a new SSD boot drive, and two new data drives. I decided to replace the 256GB boot drive with a 1TB one, and the pair of 2TB data drives with a pair of 4TB drives because they were on sale to the point where they were practically giving them away.

Since I know that someone might ask, the SSD is a Samsung 860 EVO, and the mechanical drives are WD Blue.

My plan was to ... somehow clone the smaller boot drive over to the bigger one and then copy the data across from the failing RAID to one of the new drives, which I would let Windows mirror overnight.

Almost a full day later, I now know how to do it the next time, and can shave off oodles of time. I spent much of the day going through tutorials and installing various free tools before I finally found the combination that did what I needed.

The data drive should have been easy, but it ended taking almost as long to deal with as the boot drive. I mirrored over the data readily enough, but I couldn't get Windows to extend its partition to use the rest of the unallocated space on the disk. A couple of help sites recommended a free piece of partitioning software, but when I tried to get it to extend the partition, it got to the stage of expanding it and then did the equivalent of a shrug, and suggested that I should buck up for the pro version.

Frustrated, I bounced from help forum to help site before I finally found something useful on a Microsoft forum. The poster had the same problem as me, and the person responded asking them to confirm that it was set up as GPT and not MBR, since MBR would not let Windows 10 extend past 2GB. Sure enough, my drive was set up as MBR.

Google: Converting MBR to GPT in windows.
Google: Converting MBR to GPT in windows without losing data
Google: Converting MBR to GPT in windows without losing any data

After much digging, I discovered that one of the earlier tools I'd tested for cloning would also let me do that with a couple of mouse clicks. Sure enough, ten seconds later I had a GPT disk, and less than a minute later I had my data partition expanded to give me access to the full storage capacity.

I ended up having to clone my boot drive three times before I finally got it right. The first time I cloned it, the main partition and unallocated pace were not adjacent, so Windows would not let me extend the partition without converting the disk to a dynamic disk that would not boot.

After much research...

I cloned it again, but I told it to arrange the partitions in a different order so that the main partition and unused space were next to each other. I extended the partition and ... the computer refused to see it as a bootable drive.

After much more research...

I finally found a good article on pcmag.com that gave detailed instructions on how to clone your boot disk to a larger disk, and which two pieces of free software would do it for you.

Their process worked flawlessly on the first try, and when I swapped out the new SSD for the old one, my computer recognized it and booted into Windows. Not only do I have 77% free space on my boot drive now (versus 5%), but this new SSD is noticeably faster.

I just need to let my mirror rebuild overnight and I'm good to go for a few more years (until something else breaks).
plonq: (Kinda Bleah Mood)
Call it a brain fart, or a senior moment, but I had a minor moment of derp today.

In the aftermath of a significant power outage this morning (and by significant I mean the area it affected more than the time it was out), I started making my way through the house, resetting clocks and setting things back to normalcy.

One of the last things I tackled was the file server in the basement. It's going to need some attention soon because its fans are starting to make alarming sounds when the system first powers up. Once it has reached its operating temperature, it settles into a routine squeak and squeal, but for the first while it's quite a cacophony of disturbing noises. After the scare with the RAID on my main machine the other day, I thought it would not be a bad thing to check on the health of the RAID on our file server, since that is our main backup for everything.

I called up Disk Management in Windows, and was alarmed by what I saw. Below is the results from our file server, juxtaposed above the results from my machine upstairs.

One of these things is not like the other.

RAIDS

The moment I saw it showing as one drive reading as a single, basic partition, my inner alarm bells starting ringing furiously.

OMG! How long has the second drive been dead? Why have I never noticed any errors messages during boot-up?

I booted into the UEFI and things got even more confusing. I just could not resolve the drives it showed to the drives that I knew were in the computer. When I rebooted again to watch the statuses flash past, I noticed that it offered a options for interrupting the boot sequence to change settings.

And then I applied a mental palm to my face. The reason Windows was not seeing the RAID was because I was handling it in hardware; I'd installed a card for it when I built this backup machine because I didn't want to entrust our data to sometimes-flaky software RAID.

To my defence, it has been a few years since I built this machine.

August 2025

S M T W T F S
     12
3456789
10111213141516
171819202122 23
24252627282930
31      

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Feb. 5th, 2026 07:32 pm
Powered by Dreamwidth Studios