CT Droid
CT Bot
Ok, I've come up with a gameplan.
I'll move the CQC install to the kitchen PC, as it appears to be plenty stable, and is on all the time anyway. It's trivial to move it there, and then I don't have to worry about losing CQC when the WHS machine freezes.
I'll remove the syba serial port card from the WHS machine. I don't absolutely need it, and it will put some extra incentive behind me getting my drivers to work with the quatech box.
I'll remove all but the system disk from the WHS machine.
I'll let that run for a day or so (3 days seems to be definitive) and see how it does. If it's stable, I'll add in a disk at a time and see how it goes.
The idea for this came from this thread that describes almost perfectly the trouble I'm having. They note that it seems to almost always be related to the chkdsk function in the logs, but doing chkdsk manually themselves on each disk reveals nothing. So I'm going to have to remove the disks completely to see if I can narrow down which one is bad.
I'll be losing my WHS backup capability, but the shared directories I've backed up onto an external 500 mb disk, and I'll plug those into the kitchen PC also so they're still available. So really, only the backups and capability will be lost...which so long as I don't need the backup for the next few weeks, I should be able to finish my testing by then and hopefully finally determine the cause of the problems.
This thread is not open. If you wish to respond, please respond using the original blog entry link. View the original blog entry
I'll move the CQC install to the kitchen PC, as it appears to be plenty stable, and is on all the time anyway. It's trivial to move it there, and then I don't have to worry about losing CQC when the WHS machine freezes.
I'll remove the syba serial port card from the WHS machine. I don't absolutely need it, and it will put some extra incentive behind me getting my drivers to work with the quatech box.
I'll remove all but the system disk from the WHS machine.
I'll let that run for a day or so (3 days seems to be definitive) and see how it does. If it's stable, I'll add in a disk at a time and see how it goes.
The idea for this came from this thread that describes almost perfectly the trouble I'm having. They note that it seems to almost always be related to the chkdsk function in the logs, but doing chkdsk manually themselves on each disk reveals nothing. So I'm going to have to remove the disks completely to see if I can narrow down which one is bad.
I'll be losing my WHS backup capability, but the shared directories I've backed up onto an external 500 mb disk, and I'll plug those into the kitchen PC also so they're still available. So really, only the backups and capability will be lost...which so long as I don't need the backup for the next few weeks, I should be able to finish my testing by then and hopefully finally determine the cause of the problems.
This thread is not open. If you wish to respond, please respond using the original blog entry link. View the original blog entry
