Rant time.

So I just got bitten by the Black Friday deals that are flooding the internet and I got myself a shiny new Kingston HyperX 240GB SSD for cheaps. It’s rather quick actually, I got the following speeds below:


So yeah, half a gigabyte per second reads and writes! Noice. Sorry about the weird text issues, I have no idea why this happens when booting from a live USB (any ideas anybody?).

I thought, yay! Time to image over my OS’s and make them nice and fast. I thought to myself, 40GB for Linux and 200GB for Windows (I have a RAID5 array with Linux, and it doesn’t need as much room). So I used the article I made a short wile ago: Use Linux to move a Windows Installation to another drive! and got to work.

I started with Linux. I put Linux at the start of the drive and expanded it a bit from my 30GB SSD size to 40GB on the new SSD (just to make the numbers nice and round). I imaged it over and booted from the new SSD very easily (and much much quicker too). No problems thus far.

I shrunk my Windows 10 partition on my 500GB HDD down to something like 80GB so it wouldn’t take long to copy (and that it would fit on the SSD). It ended up taking sdd2 and sdd3 for the “Recovery” partition thing. Alright then, I’ll just boot the SSD again into Linux and do an update-grub! This seemed to work fine, with everything listed properly. I restarted and attempted to boot Windows 10.

…except it wasn’t to be. Just a white flashing bar and nothing else. I then remembered – ah, the Windows recovery thing needs to do a startup repair. Fair enough, I’ll boot my USB into the Windows 10 installer and chose to Repair my PC. All looked fine, went into Advanced and selected “Startup Repair”. It said it was “fixing issues” then got to about 30% then failed miserably, with nothing in the “log”. The next thing I tried was good old bootsect /fixmbr. Nope. All I did was kick GRUB out and make the entire drive unbootable. ARGH.

Back to the Linux install USB, run grub-install /dev/sda again. Except that wasn’t working either. It just said that it couldn’t find something to do with /cow. I figured it was a live USB thing, and remembered I still had a working copy of Linux on my 30GB SSD that I had unplugged.

I booted that up, and it loaded just fine, as if I had never touched it (and I hadn’t). I used that to fix the GRUB bootloader on the SSD, but I still could not get Windows 10 to start.

I did some poking around, and I discovered that Windows has to be at the start of the drive in order for it to boot properly.

What-the? WHY. There is no fathomable explanation why this should be the case. Linux works just fine no matter where the heck you plonk it on a disk. Why does Windows need to be so picky that it needs to be first in line once the disk is called up? I had a think – maybe it has something to do with Secure Boot? Oh no, that can’t be it. Linux works fine with Secure Boot and being on the disk anywhere. It’s times like these when I wonder why I bother with Windows anymore. I only use it for games really, and maybe a bit of programming.

So I’ve had to start over entirely from scratch. This time, I’ve put Windows 10 at the f***ing start of the drive. If it doesn’t work first time, it can rot on the hard drive where it was originally.

I’ll post back tomorrow with my conclusion. I’m not happy.

So something incredible just happened
Phew, everything worked out!

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.