I'm upgrading (read: replacing) my mediaserver with another machine but when I plug in the storage drive (a 2TB seagate drive) suddenly the OS gets corrupt (installed on a 120GB Kingston SSD) and I can no longer boot from it. What's even more confusing is that the SSD is not visible in BIOS when the seagate is installed.
Some info needed before this next part:
- Windows 7 was installed on the old mediaserver
- Windows 10 was installed on the new mediaserver
- Windows 7 is installed on this 3rd computer I'm about to talk about.
When I plug both these drives into computer#3 with Windows 7, it doesn't get corrupt and I can view both drives. The SSD is browsable, but the Seagate drive is only visible from the diskmanager. Here's where I found the actual problem. It's apparently a 'recoverypartition', even though I've never installed an OS on it. It's only one simple partition taking up the whole drive only for storage.
When plugging it back into the old mediaserver, it boots up just fine and I can browse the storagedrive like normal. It's still thought of as a'recoverypartition' and I believe it's in some way locked to this particular installation.
I've never encountered this before, how did it happen and how can I fix it? I don't have a spare 2TB drive to do a backup on so I can repartition it.
Some info needed before this next part:
- Windows 7 was installed on the old mediaserver
- Windows 10 was installed on the new mediaserver
- Windows 7 is installed on this 3rd computer I'm about to talk about.
When I plug both these drives into computer#3 with Windows 7, it doesn't get corrupt and I can view both drives. The SSD is browsable, but the Seagate drive is only visible from the diskmanager. Here's where I found the actual problem. It's apparently a 'recoverypartition', even though I've never installed an OS on it. It's only one simple partition taking up the whole drive only for storage.
When plugging it back into the old mediaserver, it boots up just fine and I can browse the storagedrive like normal. It's still thought of as a'recoverypartition' and I believe it's in some way locked to this particular installation.
I've never encountered this before, how did it happen and how can I fix it? I don't have a spare 2TB drive to do a backup on so I can repartition it.