Computer Woes
Posted: Tue 01 Jul 2014, 10:32
It seemed straightforward at the time. Shortly after I got back from holiday just over three weeks ago, my PC failed. It should have been a simple repair, but it did not turn out like that. Now after three weeks of frustration, a 1.5 TB restore of my data is under way and I am hopeful that normality is about to be restored. With any luck, I can soon stop worrying about my computer and get back to taking photographs.
What I started out with was a PC which loaded its Windows operating system and applications from a 64 GB SSD (Solid State Disk). Data was held on a separate 2 TB RAID 1 disk, RAID 1 being a system whereby data is written simultaneously to two physical disks, but they appear as a single entity to the operating system. Apart from fans, hard drives are the only components in a computer with moving parts which makes them susceptible to failure. Losing a fan is one thing, having all your data disappear is altogether another. RAID 1 has built in redundancy and provides reassurance as one of the disks can fail but a complete copy of the data remains on the survivor. Crucially, I did not have a backup process in place*. I advise other people to do it and although I knew its omission was inadvisable, somehow there always seemed to be better things to do to set than set something up. As I was to find out, I had placed too much reliance on the protection provided by the RAID 1 disk and resolving that has been time consuming. Just one of the difficulties I encountered.
There will be a number of posts in this thread to document what happened. At one level, people might be interested and/or amused to learn about the sequence of events. Perhaps there will also be some learnings for others from this episode. I have already documented the first part of the saga (link below) when I reinstated the SSD and then decided to replace it with a drive of larger capacity. That's when the problems started........
viewtopic.php?f=6&t=1016&p=4756&hilit=computer#p4756 (I have tried to link directly to the post, but you will need to scroll down the page to see it.)
* As it is an important topic, I'll make backups the subject of a separate post.
What I started out with was a PC which loaded its Windows operating system and applications from a 64 GB SSD (Solid State Disk). Data was held on a separate 2 TB RAID 1 disk, RAID 1 being a system whereby data is written simultaneously to two physical disks, but they appear as a single entity to the operating system. Apart from fans, hard drives are the only components in a computer with moving parts which makes them susceptible to failure. Losing a fan is one thing, having all your data disappear is altogether another. RAID 1 has built in redundancy and provides reassurance as one of the disks can fail but a complete copy of the data remains on the survivor. Crucially, I did not have a backup process in place*. I advise other people to do it and although I knew its omission was inadvisable, somehow there always seemed to be better things to do to set than set something up. As I was to find out, I had placed too much reliance on the protection provided by the RAID 1 disk and resolving that has been time consuming. Just one of the difficulties I encountered.
There will be a number of posts in this thread to document what happened. At one level, people might be interested and/or amused to learn about the sequence of events. Perhaps there will also be some learnings for others from this episode. I have already documented the first part of the saga (link below) when I reinstated the SSD and then decided to replace it with a drive of larger capacity. That's when the problems started........
viewtopic.php?f=6&t=1016&p=4756&hilit=computer#p4756 (I have tried to link directly to the post, but you will need to scroll down the page to see it.)
* As it is an important topic, I'll make backups the subject of a separate post.