If you try running DISM commands, error code 87. If you try running sfc /scannow, it says Windows Resource Protection could not start the repair service. If you try to open some files, it says File System Error. If you go to network adapters, it shows nothing. Network Sharing Center shows no no active networks and says class unknown. If you click the Start Menu/Search Bar, it does nothing. So good sign after 48 hours of not being able to get into Windows, but now we have a whole plethora of issues. All of our files/apps are there which is good. SSD is in the computer and we got it to boot into Windows (which it didn't do off the bat - had to use Macrium Reflect Rescue Media to resolve boot issue with BCD). We cloned the drive that was still "good" to an SSD. Regardless, that's neither here nor there because we've made some changes and this is where we're at: I don't know if that's true or not - seems like it defeats the purpose. Apparently, from what we've understood (and maybe this is wrong) it seems like there is only one bootable drive in a raid array and if that drive goes, you're beat. Not an expert when it comes to RAID by any means. Intel Rapid Storage or something like that. It does not have a hardware RAID controller it's software that seems to be handled through BIOS. Vendor gave us a computer to run a laboratory instrument a few years ago. This could be a long story but I'm shortening it for your sake and mine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |