I got myself an SSD the other day. I disconnected my HDD and went about installing Windows 7 onto the SSD. Once it was complete I simply reconnected my HDD and everything was fine. I moved my Desktop and Downloads folders to the HDD as well as Program Files. Basic things you do when you get an SSD.
Everything was fine this way for a couple of days. Then I decided to check out some things so I booted to a gparted USB stick and was inspecting the partitions. I noticed that the HDD had the typical Windows system/recover/whatever 100 MB partition as the first partition. (I skipped the creation of this partition on the SSD). Since it was left over from the old Windows install on the HDD I decided to remove it and expand the second partition to recover the space. Once all of this was done, Windows would no longer boot. I would get to a black screen (some odd colored pixels would blink around across the top of the screen) and nothing would ever happen. If I disconnected the HDD and booted just from the SDD everything went fine (except that it complained about not finding D: where the Desktop and such were located.) Odd.
I rebooted in Safe Mode and saw that there was no D: in My Computer. I opened Disk Management and saw that the drive was being seen by Windows but there was no drive letter assigned so I assigned D: to it again and rebooted. Same black screen with pixels. I rebooted to safemode and this time it wouldn't load, either. I think this is because I assigned the drive letter and now Windows is trying to read whatever from the drive and getting hung up again.
I booted back into gparted a few times to inspect but nothing seemed out of place until I noticed that on the HDD there was only one partition and it was sdb2. There was no sdb1 so I dropped into the terminal and did an fdisk -l and saw that there was indeed no sdb1 on that drive. I mounted sdb2 and saw that all of the files were still there and fully accessible. Doing a check on the drive showed no errors.
Before I left the house this morning I set gparted to shrink sdb2 and recreate sdb1 hoping that Windows as just freaking out since the only partition on the drive was #1 and there was no #0 partition.
Does this seem plausible? I won't be home to see if it worked for some hours. If all else fails I'm going to try to copy all of the files on sdb2 to an external hard drive, but I'd rather just fix whatever is wrong with the HDD now that's preventing Windows from booting.
Everything was fine this way for a couple of days. Then I decided to check out some things so I booted to a gparted USB stick and was inspecting the partitions. I noticed that the HDD had the typical Windows system/recover/whatever 100 MB partition as the first partition. (I skipped the creation of this partition on the SSD). Since it was left over from the old Windows install on the HDD I decided to remove it and expand the second partition to recover the space. Once all of this was done, Windows would no longer boot. I would get to a black screen (some odd colored pixels would blink around across the top of the screen) and nothing would ever happen. If I disconnected the HDD and booted just from the SDD everything went fine (except that it complained about not finding D: where the Desktop and such were located.) Odd.
I rebooted in Safe Mode and saw that there was no D: in My Computer. I opened Disk Management and saw that the drive was being seen by Windows but there was no drive letter assigned so I assigned D: to it again and rebooted. Same black screen with pixels. I rebooted to safemode and this time it wouldn't load, either. I think this is because I assigned the drive letter and now Windows is trying to read whatever from the drive and getting hung up again.
I booted back into gparted a few times to inspect but nothing seemed out of place until I noticed that on the HDD there was only one partition and it was sdb2. There was no sdb1 so I dropped into the terminal and did an fdisk -l and saw that there was indeed no sdb1 on that drive. I mounted sdb2 and saw that all of the files were still there and fully accessible. Doing a check on the drive showed no errors.
Before I left the house this morning I set gparted to shrink sdb2 and recreate sdb1 hoping that Windows as just freaking out since the only partition on the drive was #1 and there was no #0 partition.
Does this seem plausible? I won't be home to see if it worked for some hours. If all else fails I'm going to try to copy all of the files on sdb2 to an external hard drive, but I'd rather just fix whatever is wrong with the HDD now that's preventing Windows from booting.
Facebook
Twitter
Instagram