- Joined
- Oct 30, 2008
- Messages
- 1,768 (0.29/day)
System Name | Lailalo |
---|---|
Processor | Ryzen 9 5900X Boosts to 4.95Ghz |
Motherboard | Asus TUF Gaming X570-Plus (WIFI |
Cooling | Noctua |
Memory | 32GB DDR4 3200 Corsair Vengeance |
Video Card(s) | XFX 7900XT 20GB |
Storage | Samsung 970 Pro Plus 1TB, Crucial 1TB MX500 SSD, Segate 3TB |
Display(s) | LG Ultrawide 29in @ 2560x1080 |
Case | Coolermaster Storm Sniper |
Power Supply | XPG 1000W |
Mouse | G602 |
Keyboard | G510s |
Software | Windows 10 Pro / Windows 10 Home |
Okay so I'm looking for ideas. The last week has been hell. Switched my FX over to Ryzen and Windows 10 decided to go nuts. Critical errors at startup. Nothing would fix it. Part of this was likely due to the wonky system I've had. My Windows 10 was a permissions mess due to it originally dating back to a Vista install. Needed to fresh install but just never had the time. Till now.
So, trying to cut this all short...about $250 later, it's working. Had to actually buy a copy of 10. The one from the free transition was going to be a pain in trying to get M$ to transfer it. Part due to the fact I reinstalled on another HDD. Then lacking an original 7 key that was lost.
But...a 3TB drive with some files I don't really want to lose, which I reinstalled 10 on to start, is now refusing to be accessed. How this happened was I did the reinstall with my SSD cache drive in. Now I had turned off the caching for the hardware update, but on the reinstall, Windows decided to install part of itself onto the cache drive and part onto the 3TB. So the SSD didn't want to be wiped, nothing would work other than putting it into an external and wiping it from another computer.
Unfortunately I didn't realize at the time that the SSD was necessary for the 3TB to boot. So it effectively put me back to square one, only this time, the 3TB couldn't be accessed. Now my original boot drive still can be accessed, just refuses to boot with that error.
So I popped in a new drive to try and sort this all out. The original pops up fine, I transferred stuff over no problem. The 3TB however, doesn't want to do anything. Admin tools sees it, sees there is an OS on it and all the works, but it won't mount it.
At this point I'm thinking, buy an external for a 3.5 drive and see if I can pull the same trick like I did with the SSD. Maybe starting from a USB will resolve it/etc. But if it doesn't work, I don't even know where to go next. Never seen Windows fight me so hard.
I'd like to tell it's Windows installation to switch off and I came across this during the last two days trying out stuff in the command prompt. Surprised I could actually re-enable an old Win 7 installation. But I forgot the commands it took to get there.
So yeah, file scans don't work, rebuilding mbr doesn't work. Just about every prompt trick or check disk doesn't work. The drive is otherwise fine and healthy. Just Windows is preventing it from being accessed. Ideas? I've messed a little with Aomei's disk partition thing but everything that might work, requires the paid version. Hate to spend money on something that will likely be one time use. Although I might because it has something that can turn a GPT drive to MBR without data loss. I'd get my SSD Cache drive back if it works.
So, trying to cut this all short...about $250 later, it's working. Had to actually buy a copy of 10. The one from the free transition was going to be a pain in trying to get M$ to transfer it. Part due to the fact I reinstalled on another HDD. Then lacking an original 7 key that was lost.
But...a 3TB drive with some files I don't really want to lose, which I reinstalled 10 on to start, is now refusing to be accessed. How this happened was I did the reinstall with my SSD cache drive in. Now I had turned off the caching for the hardware update, but on the reinstall, Windows decided to install part of itself onto the cache drive and part onto the 3TB. So the SSD didn't want to be wiped, nothing would work other than putting it into an external and wiping it from another computer.
Unfortunately I didn't realize at the time that the SSD was necessary for the 3TB to boot. So it effectively put me back to square one, only this time, the 3TB couldn't be accessed. Now my original boot drive still can be accessed, just refuses to boot with that error.
So I popped in a new drive to try and sort this all out. The original pops up fine, I transferred stuff over no problem. The 3TB however, doesn't want to do anything. Admin tools sees it, sees there is an OS on it and all the works, but it won't mount it.
At this point I'm thinking, buy an external for a 3.5 drive and see if I can pull the same trick like I did with the SSD. Maybe starting from a USB will resolve it/etc. But if it doesn't work, I don't even know where to go next. Never seen Windows fight me so hard.
I'd like to tell it's Windows installation to switch off and I came across this during the last two days trying out stuff in the command prompt. Surprised I could actually re-enable an old Win 7 installation. But I forgot the commands it took to get there.
So yeah, file scans don't work, rebuilding mbr doesn't work. Just about every prompt trick or check disk doesn't work. The drive is otherwise fine and healthy. Just Windows is preventing it from being accessed. Ideas? I've messed a little with Aomei's disk partition thing but everything that might work, requires the paid version. Hate to spend money on something that will likely be one time use. Although I might because it has something that can turn a GPT drive to MBR without data loss. I'd get my SSD Cache drive back if it works.