My main cruncher (i7/950) took a major hit over night and I lost the system (C:) drive. I've tried to restore, chkdsk, and even tried to re-install Windows -- no joy. Placed in the other cruncher and it would not even recognize it. It will be several days/weeks before I can replace it and re-image the system. I hope to replace it with this

http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=5247117&CatId=5298

---

I don't buy computers, I build them!!

Interesting. One of the disk hosting my OSX system is failing. I booted to OSX and received a SMART warning. Didn't know anything about it while running Windows...

I'm about to order one of these to replace it, SAMSUNG 840 Series. I'm going to have to get this sorted before installing Linux on this machine. It might be a few days. My Windows/SETI work is unaffected...for now.

Borrowed a spare drive from one of my neighbors and got the i7/950 back up yesterday. Got a very big surprise this morning when I checked so see if the site was up and noticed it had been up for over 12 hours. Anyway, I had to suspend all of my GPU tasks and reset SETI because for some unknown reason all of my MB GPU tasks were all trying to run at the same time and were ending with errors, over 50+ (sorry about that -- my bad). Back to running only AP tasks on this machine. D/l speed is amazing with speeds going as high as 49k.

---

I don't buy computers, I build them!!

Must be something going around. Got a windows message from one of my older crunchers saying there was a problem with the disk and I should shut down and check/fix. Needless to say, I don't want to shut down or reboot until I've cleared all tasks, as I suspect I will need to replace the drive.

---

Must be something going around. Got a windows message from one of my older crunchers saying there was a problem with the disk and I should shut down and check/fix. Needless to say, I don't want to shut down or reboot until I've cleared all tasks, as I suspect I will need to replace the drive.

My problem was with the system (C:) drive where all of my main programs run. All of my data is on a separate physical drive (D:). So it was no problem in replacing the drive, when I couldn't repair it. I do a daily backup/system image on another drive (E:), so it was just a matter of restoring the sys image onto the borrowed drive. I will have to re-image the system drive (C:) and create new backups to support a SSD image when I put in the SSD in about 2 weeks -- can't wait.

---

I don't buy computers, I build them!!

I don't buy computers, I build them!!

No worries, no piece of hardware will last forever. It happens. Replace and restart! :D

---

The i7/950 machine will be down for several hours, while I install the new SSD, re-image the system and do PM.

---

I don't buy computers, I build them!!

The i7/950 machine will be down for several hours, while I install the new SSD, re-image the system and do PM.

Back up and CRUNCHIN!!

---

I don't buy computers, I build them!!

How is that SSD working out for you?

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

How is that SSD working out for you?

Great!! Machine cycle time is cut by almost 50%, what took 4-5 min on the HDD using an UEFI boot config is now taking up to 2 min to get everything loaded and up and running. The drive is rated at 6Gb, but is only running at a 3Gb rate because of the chipset/board, but I can put up with that. Response time doing anything on the system is remarkable, especially cruising the net. After I save my nickels & dimes for many months I may be able to afford to upgrade the machine to a new version to take advantage of the actual speed of the drive. It would just be my luck the damn thing becomes obsolete by that time. In the mean time I might get one for my other machine after replacing the GPUs in it.

---

I don't buy computers, I build them!!

How is that SSD working out for you?

Great!! Machine cycle time is cut by almost 50%, what took 4-5 min on the HDD using an UEFI boot config is now taking up to 2 min to get everything loaded and up and running. The drive is rated at 6Gb, but is only running at a 3Gb rate because of the chipset/board, but I can put up with that. Response time doing anything on the system is remarkable, especially cruising the net. After I save my nickels & dimes for many months I may be able to afford to upgrade the machine to a new version to take advantage of the actual speed of the drive. It would just be my luck the damn thing becomes obsolete by that time. In the mean time I might get one for my other machine after replacing the GPUs in it.

Gee those times are extremely slow Cliff, my 2500K when it had an SSD in it (before the SSD died) booted inside 20 seconds but even with the WD 1TB Black it boots in just under 1 minute.

BTW both are/were 3GB models.

Cheers.

How is that SSD working out for you?

Great!! Machine cycle time is cut by almost 50%, what took 4-5 min on the HDD using an UEFI boot config is now taking up to 2 min to get everything loaded and up and running. The drive is rated at 6Gb, but is only running at a 3Gb rate because of the chipset/board, but I can put up with that. Response time doing anything on the system is remarkable, especially cruising the net. After I save my nickels & dimes for many months I may be able to afford to upgrade the machine to a new version to take advantage of the actual speed of the drive. It would just be my luck the damn thing becomes obsolete by that time. In the mean time I might get one for my other machine after replacing the GPUs in it.

Gee those times are extremely slow Cliff, my 2500K when it had an SSD in it (before the SSD died) booted inside 20 seconds but even with the WD 1TB Black it boots in just under 1 minute.

BTW both are/were 3GB models.

Cheers.

All well & good for your machine, this is a 1st gen i7/950/DX58SO with a x58 chipset. The machine is in AHCI mode w/o RAID, therefore RST is not installed. Here are some times for you --

From a cold start with 16 items in the start menu - 1.51 min
From a warm start (recycle) with 16 items in the start menu - .39 min
From a warm start (recycle) with 0 items in the start menu - .27 min

---

I don't buy computers, I build them!!

My second computer is running Seti on an AMD 950 4-core with GTX-570 video card. I have BOINC installed solely on my D drive. I have been playing around installing a copy of my Windows 7 drive on a spare drive to be installed in another computer. While allowing the computer to boot from the newly copied drive, BOINC started running and apparently caused 1800+ WU's to be ABANDONED. Why did this affect BOINC when the program and data are on a different drive?

Bob B.

---

My second computer is running Seti on an AMD 950 4-core with GTX-570 video card. I have BOINC installed solely on my D drive. I have been playing around installing a copy of my Windows 7 drive on a spare drive to be installed in another computer. While allowing the computer to boot from the newly copied drive, BOINC started running and apparently caused 1800+ WU's to be ABANDONED. Why did this affect BOINC when the program and data are on a different drive?

Bob B.

Even though your BOINC files are on the "D" drive, there is a file in the "programs and settings" section of your boot drive (usually "C") that tells the computer where to find BOINC, and whether to start it on boot-up. If your "copy" drive is a clone of your boot/"C" drive, that is why it started BOINC.

As to the Abandoned tasks - when a machine contacts the Scheduler, the scheduler request file contains information on, among other things, the number of times that machiine has contacted the scheduler. As I recall previous discussions, if the contact number in the scheduler request is smaller than the number the Scheduler finds in the BOINC database for that machine, is assumes that this is a different machine, assignes it a new CPU ID number, and abandons all current "in progress" tasks for the old CPU ID. So if your machine had contact with the Scheduler after you cloned the "C" drive but before you tried to boot that machine from the clone, that may be what happened.

---

Donald
Infernal Optimist / Submariner, retired

Thanks for the info. Is there any way to prevent this other than not letting BOINC run on the cloned drive? I had to reinstall the cloned drive to correct a MBR problem and BOINC is currently running on it after booting it. It now shows 2800+ abandoned WU's. I don't see any new CPU assignments - it's still showing only my original four.

Bob B.

---

I goofed. The BOINC files on my D drive were not the ones being used. BOINC had actually installed more recently on the C drive so I was switching between 2 different installations. This time I copied the entire BOINC folder from the boot drive to the original C drive before removing it. I then booted the original C and BOINC resumed with no problems. My bad.

Bob B.

---