Forum > Discussion Forum
New cruncher on the way
Mike:
Settings in CCC are similar to power saving settings which only take effect if some cores are idle.
That doesn´t happen while seti is running.
CPU Thermal Throttle and CPU Load Line callibration prevent overheating the CPU by reducing core voltage.
I tested it while overclocking.
4.3 GHZ was just to much for my heatsink, so i ordered a better one.
Mike
Cosmic_Ocean:
So. Since I'm going to be calling in the morning and getting an RMA set up, I was thinking "what am I going to do in the meantime? using the laptop is just weird. OO! I know.. set the laptop up ontop of my case, hook the USB keyboard and mouse up, hook the monitor up, and bam.
Then I got an even better idea. I hadn't nuked my old PATA C drive, and there really wasn't anything stopping me from just putting the old setup back together. Well, except for two bulged caps. Replaced those (again) and well.. here I am, back on the old setup. I can do a lot of stuff, except for write to the array at all, or play games. I can watch TV shows, listen to music, check email and frequent some forums until the replacement board comes back.
Cosmic_Ocean:
Sent the board off today. I'm thinking Tuesday (31st) to have the replacement board. After reading the reviews for it (like I should have done in the first place), it seems it's a real crapshoot as to whether there is going to be a problem with it or not. And the problems range all over the map; there's no one specific common issue. I've heard (from fellow nerds) of ASRock boards being pretty durable and reliable along with being affordable, so I figured I'd give it a shot. We'll see what happens with the replacement.
I do have a question about the opt apps though. If I install BOINC but don't attach to any projects, and then create the project folder in the data directory and put my app_info and EXE in there, THEN attach to the project, will that work right away? My goal is to keep my application details from having any references to stock apps, so I don't want to attach and get assigned work right away after the stock downloads. I want the new machine's app details to look like my single core machine's does. It has been running an app_info since before the app details came along and therefore has no references to stock apps.
[unrelated background information]
In the meantime, I'm doing a lot of data sorting/archiving to clear out enough space on the externals to hold the contents of the array for a few hours. Some time ago (I think it was ~2 years), one drive punted itself from the array randomly. Normally, that's not really that big of a problem (it's a 4x500gb raid-5). I just go in and delete the ghost raidset that thinks three disks are missing, then designate that disk as a hot spare, and the controller pulls it in and auto-rebuilds.
Well that one time two years ago, disk 2 punted itself, and for some stupid reason, I pulled the side panel off and touched one of the cables just right and two more removed themselves from the array as well. So then I had three ghost raidsets and the one correct one. Since each disk reported that it was a member of a raidset and lost contact with all the others, it was technically destroyed and not recoverable. I did a lot of searching around on the Internet and found that in the BIOS setup for the card, there's supposed to be an option for rebuilding where the initialize method is "None (Rescue)." Well mine didn't have that. After some more research, I found that particular option in the BIOS setup didn't come along until the next firmware revision after the original base release that my card has. However, the web interface (localhost:81) has the option in there.
So the fix for this scenario was to delete ALL of the volumesets and raidsets, create a new raidset with exactly the same parameters as before, but make sure initialize was set to Rescue. After an adrenaline explosion and many butterflies in my stomach, I hit the "confirm operation" button. It worked. The controller didn't automatically do it, but I went and told it to do a consistency check just to make sure everything was good. Ended up not having any problems once it was done. Fortunately there wasn't any write operations going on when I had my moment of stupidity.
But in the aftermath of that issue, the name for the raidset that appears is the same as it was before, except instead of #00, it is #R-00, R for "rescued." I had originally set it up for a 16KB stripe size, but I think I can get much better performance if I go to 64KB. I believe this because when I do read benchmarks, or just read large files from it, it tops out at 210MB/sec. Now the first time I had a disk punt itself, I thought for sure it was just a failed disk, so I panicked and ordered a new one from Newegg, and overnight shipping was only $6 more than the regular shipping that was like $2.49 or something like that. While I was waiting for the new disk to arrive, I put the "failed" disk into another machine and ran the WD DLG tools on it, specifically the long test that looks for errors. It found none. Did the short pass of zeroes (first and last million sectors), put it back into the main rig, booted up and told the controller it was a hot spare. Automatic rebuild.
Worked fine for a long time. But now I had a "spare" disk laying around. Of course I turned it into a storage disk that could be used as a raid spare (after swapping the cable from onboard to the card). Same model and everything, and that disk gets 115MB/sec on reads in the first 50GB, and doesn't drop below 100MB/sec until about 125-150GB. Even near the end, it's still pulling 65-70MB/sec. So since raid-5 on reads is basically a raid-0 stripe, I should be getting 300+ at the beginning, and well over 150 at the very end. But since I've only got 16KB for a stripe size, I max out at 210 at the beginning, and it drops down to 105 at the end, with a 175 average. That's still pretty good, but it should easily be twice what I'm getting. Of course I filled the array up too quickly and ran out of storage space elsewhere to rebuild it with a larger stripe size.
It sucks that HDD prices are sky-high right now, too. I was looking forward to picking up a 2TB drive to put in my external enclosure (it's a 5-bay trayless backplane on eSATA), so now my only option to fix my array is to burn stuff onto DVD+R's to clear out enough space to hold the array contents. I think I might just make enough room.. it'll be close. I've also wanted to upgrade the firmware on the raid card, but I'm not totally certain--nor confident--that it won't destroy the array in the process. Safest thing to do is have the data backed-up and then upgrade the firmware. Upgrading the firmware will give me a lot of new options.. such as "no alarm on fan fail." I've gone through five 40mm chipset fans in the 4 years I've had this card. I finally just said "enough!" and put the passive heatsink that came with the card on it, but with no fan, the alarm goes off. Yay old firmware.. ::)
[/unrelated background information]
Okay, so I don't really expect anyone to spend 5-10 whole minutes reading all of that, but I felt like explaining. If you read all of it.. I totally gave you an opt-out at the beginning. :P
arkayn:
I think your best bet would be to copy the old folder over, clean out all the files but leave all the folders in place.
Claggy:
--- Quote from: Cosmic_Ocean on 24 Jan 2012, 03:51:20 am ---I do have a question about the opt apps though. If I install BOINC but don't attach to any projects, and then create the project folder in the data directory and put my app_info and EXE in there, THEN attach to the project, will that work right away? My goal is to keep my application details from having any references to stock apps, so I don't want to attach and get assigned work right away after the stock downloads. I want the new machine's app details to look like my single core machine's does. It has been running an app_info since before the app details came along and therefore has no references to stock apps.
--- End quote ---
You can try attaching with an app_info and apps already popolated in the setiathome directory,
If i don't want to get Stock apps when i attach a host, i Deselect Use CPU & Use Nvidia GPU in my Default Project Preferences,
then when Boinc does the Prroject Initialisation it finds it can't ask for CPU or Nvidia GPU work, so it gets no Stock work, then you can do the app_info and apps,
Claggy
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version