Windows 10: Attempted to put OS on SSD, now I have two boot volumes.

I tried to transfer my Windows 10 over to a newly formatted SSD but it said the disk size was too small (250 GB SSD). After this error I followed this youtube video to install Windows onto my SSD without using a USB boot.

The problem is that I wanted to just put the OS onto the SSD, nothing else but it looks like I now have 2 volumes to choose from when booting up; The HDD with windows on it (with all my files/games) and the SSD with only the OS installed. The problem with the SSD volume is that none of my stuff is on it, it made me create a new account and all my files from my HDD are gone unless I boot into the HDD.

Was I supposed to migrate my stuff over to the SSD as well? Its a pretty small SSD so I don't think Ill be able to migrate all the files. I'm not too sure what to do as I want to keep all my files from my HDD and just use the SSD for the OS. Am I doing something wrong, or did I miss a step somewhere?

submitted by /u/estrangier
[link] [comments]

:)

 

MBR of RAID volume overwritten, OS fails to boot. Help.

I've screwed up, big time.

My machine has a RAID 0 of two 500GB drives. The resulting volume stores my Windows XP installation. Its contents are vital. I installed an additional 80GB IDE HDD to install Kubuntu. During Kubuntu's setup, those 500GB drives were displayed as is, and not as the resulting volume. I was able to make sure the right drive (hdc, that 80 GB HDD) was partitioned and formatted, but the grand screwup came where in the "finalise" step, you have to specify where the boot-loader has to be installed. This option was hidden in a seperate dialog that comes up on clicking an "advanced" button somewhere. Well...the installer wrote the boot loader to (hda), the first member of the RAID 0 volume, when the installer doesn't recognise the volume itself and only its member disks.

Windows doesn't boot, neither does Kubuntu (shows Grub error 15). I need a way to recover data from the volume. I'm hoping the volume's contents are intact, though its MBR is gone. How do I boot Windows?

I can't use a WinXP boot floppy made from another system, since the boot floppy won't recognise a RAID volume. Should I boot the machine with the Windows XP install CD + AHCI driver floppy and install the OS without formatting the volume, so at least I could safely move my files to another drive even if the resulting OS is unstable? Ideas please.

 

64Gb SSD for OS or 2Tb HDD for storage ?!

I suggest that you get the 2tb for storage. SSDs are only useful if you want to boot things fast like OS and programs. I actually suggest you get both if you have that many movies.

 

After hard reset, OS disk showing no volumes/partitions

Hi everyone,

I've searched high and low on Google for the specific issue that I'm having, but I can't seem to figure this out.

About a year ago, I built my own computer. I have my OS (Windows 10) installed on a Plextor M6 256 SSD. Today, for about the fourth time in a year, my computer became unresponsive during normal use. After a forced hard reset, I was taken to a black screen with the 0xc00000e error, telling me that a required device was inaccessible. After a quick Google search, I found many answers saying that this problem was because of a corrupted boot record.

I followed the steps recommended by Microsoft. First, I attempted automated startup recovery. This didn't work. Then I attempted to use bootrec to fix the problem. This resulted in the tool telling me that no Windows installations were detected.

I decided then to open diskpart. The disk itself was detected, but whenever I listed volumes, nothing showed up for that disk. No partitions or volumes were listed.

I've since recovered the drive by flashing a Clonezilla image that I had as a backup, so everything is up and running now. However, I am curious as to why this problem keeps happening. I've downloaded the diagnostic tools from Plextor for my disk, and it says that everything is fine. I've also run a Windows memory diagnostic, which has returned no errors.

My assumption is that the hard reset is causing some kind of partition table corruption. But, that still leaves the issue of why the computer is freezing up to begin with unsolved. Any suggestions/possible causes to investigate would be much appreciated!