- Jun 30, 2004
- 15,669
- 1,422
- 126
At this point, my main concern is to restore the Stablebit drivepool that has all my important document archives, spreadsheets and other items. If I had a TB of DVR movie/TV captures on the server, I may be able to get those back.
But I'm inclined to decommission my server now. I had been planning to do it since three household users gave way to only one -- ME. I have become very used to having a file server in the mix. I need a new strategy without the server.
Something happened the other day to cause the server to restart or reboot. It was unable to read the boot drive. I don't have the means to restore that boot drive. The Drive Pool should be "intact". I should be able to install Stablebit on any Win 10 system that I have, then move the controller card and the drives for the drive pool to that system, and stablebit should recognize the drive pool and configure it to the system. Once done, I can pull all of my important (and up-to-date) files -- document archives etc -- and store it all locally on a workstatiion with good backup until I can decide whether to replace the server with a NAS device, or simply implement file-sharing between my workstations.
I was really a bit stupid about this all along. I should've cloned the server boot disk, or otherwise made some backup arrangement for it. SYNCBACK SE was used to back up important folders on the drive pool -- so -- there's "that". But I need to install Syncback on one of my systems and follow the program's instructions to restore the files.
It would just seem the easiest and most direct way to restore the drive pool on the spare Win 10 system. Once I get all my files back, I will decide whether to have a NAS or a new server. But I don't think I need (or want) to do this -- with the server -- anymore.
For all I know, this might just be some problem with a CMOS battery. It all might come back if I just reset the BIOS. I frankly don't understand how a Crucial SSD 250GB boot-system disk could go south by itself. With the Win 2012 OS on that disk, it mostly would just read system files. It would never have had any major "workout" that would cause the disk to fail. There were no "temperature" or other issues in the server box. I don't have the time to do this hobbyist troubleshooting as I once did.
What a pain.
But I'm inclined to decommission my server now. I had been planning to do it since three household users gave way to only one -- ME. I have become very used to having a file server in the mix. I need a new strategy without the server.
Something happened the other day to cause the server to restart or reboot. It was unable to read the boot drive. I don't have the means to restore that boot drive. The Drive Pool should be "intact". I should be able to install Stablebit on any Win 10 system that I have, then move the controller card and the drives for the drive pool to that system, and stablebit should recognize the drive pool and configure it to the system. Once done, I can pull all of my important (and up-to-date) files -- document archives etc -- and store it all locally on a workstatiion with good backup until I can decide whether to replace the server with a NAS device, or simply implement file-sharing between my workstations.
I was really a bit stupid about this all along. I should've cloned the server boot disk, or otherwise made some backup arrangement for it. SYNCBACK SE was used to back up important folders on the drive pool -- so -- there's "that". But I need to install Syncback on one of my systems and follow the program's instructions to restore the files.
It would just seem the easiest and most direct way to restore the drive pool on the spare Win 10 system. Once I get all my files back, I will decide whether to have a NAS or a new server. But I don't think I need (or want) to do this -- with the server -- anymore.
For all I know, this might just be some problem with a CMOS battery. It all might come back if I just reset the BIOS. I frankly don't understand how a Crucial SSD 250GB boot-system disk could go south by itself. With the Win 2012 OS on that disk, it mostly would just read system files. It would never have had any major "workout" that would cause the disk to fail. There were no "temperature" or other issues in the server box. I don't have the time to do this hobbyist troubleshooting as I once did.
What a pain.