I couldn't find this exact issue anywhere so far and I've asked all of my colleagues and everyone is at a loss. I'm not used to older machines, so maybe I'm missing something obvious.
A good customer (otherwise I would've gave up on this long ago) brought in 3 Panasonic ToughBooks that work but there's no storage left on the HDD. Two are on Win7 Ultimate 32-bit and the other is Win8 I think but not as important. Whenever I remove the HDD from the CF-30 and CF-18 my rigs' Disk Managers say it's unallocated. Health is 100% and they run just fine in their native machines. UFS Recovery and all the Medicat software don't see the drives as well. Whenever I put in a brand new good HDD/SSD into these machines, this same situation occurs with them as well and I have to format them to use them. Same thing occurs when I clone the HDD's and attempt to boot from them.
I had a colleague test it out on his rig and he managed to get a HDD show up but it had a question mark on it and was inaccessible. Unplugged it, plugged back in and then it became unallocated like it always did for me. I hope this made sense. First time I've come across such a mess and I feel crazy now. TIA for reading through it at least if you did.
A good customer (otherwise I would've gave up on this long ago) brought in 3 Panasonic ToughBooks that work but there's no storage left on the HDD. Two are on Win7 Ultimate 32-bit and the other is Win8 I think but not as important. Whenever I remove the HDD from the CF-30 and CF-18 my rigs' Disk Managers say it's unallocated. Health is 100% and they run just fine in their native machines. UFS Recovery and all the Medicat software don't see the drives as well. Whenever I put in a brand new good HDD/SSD into these machines, this same situation occurs with them as well and I have to format them to use them. Same thing occurs when I clone the HDD's and attempt to boot from them.
I had a colleague test it out on his rig and he managed to get a HDD show up but it had a question mark on it and was inaccessible. Unplugged it, plugged back in and then it became unallocated like it always did for me. I hope this made sense. First time I've come across such a mess and I feel crazy now. TIA for reading through it at least if you did.