Hard Drive replacement |
![]() |
| log in |
Message boards : Number crunching : Hard Drive replacement
| Author | Message |
|---|---|
|
Hello: | |
| ID: 1173579 · | |
|
Just change the name, merge, then change it back to the new name. Should only take a few reboots, plus you might get some of the work resent that you lost. | |
| ID: 1173581 · | |
Just change the name, merge, then change it back to the new name. Should only take a few reboots, plus you might get some of the work resent that you lost. Thanks, I'll give it a shot. Didn't realize that I could change the name back after merging. Again, Thanks! ____________ | |
| ID: 1173586 · | |
|
Yep, I had to do the same thing after reformatting a computer. The creation date on the new machine ID is after the last contact from the old one (obviously), so you shouldn't have any snags. | |
| ID: 1173589 · | |
Just change the name, merge, then change it back to the new name. Should only take a few reboots, plus you might get some of the work resent that you lost. I just edit that section within BOINC to make it say what I want. I got tired of my Pentium III & II systems not being displayed correctly & I also like my video cards being displayed correctly. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1173655 · | |
|
As far as I know, the only way to merge two computer IDs if they have the same name is the older one has to have all of its tasks gone. That means waiting for wingmates to report, then for your "lost" tasks to time out and be re-sent out to another wingmate, validate, and finally DB purge. After all of the tasks are cleared and gone, the old computer ID can be merged with the new one. | |
| ID: 1173680 · | |
As far as I know, the only way to merge two computer IDs if they have the same name is the older one has to have all of its tasks gone. AFAIK, that only applies to deleting hosts. However, there are two places where you can merge hosts: "Merge computers by name" on the "Your computers" page and "Merge duplicate records of this computer" on each host's "Details" page. There may be a client_state.xml hack that you can do where you just go in and edit the computer ID in there, but I don't know if it will reset itself or not. There is a hack, but you'll have to watch out for <rpc_seqno>; it must be greater than that of the last server contact. Gruß, Gundolf | |
| ID: 1173686 · | |
Just change the name, merge, then change it back to the new name. Should only take a few reboots, plus you might get some of the work resent that you lost. Since the edit was to boinc.exe, it does exactly as it is told. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1173720 · | |
|
Just wondering, can we install Boinc seti@home (command line version) into a USB thumbdrive. | |
| ID: 1173795 · | |
|
That wouldn't be recommended, as it would create new HostID's every time you change computers. Plus, if the hardware changed, some application incompatibility could cause a ton of errors. | |
| ID: 1173797 · | |
Just wondering, can we install Boinc seti@home (command line version) into a USB thumbdrive. I do a similar thing on a stack of machines that I run PE on. It works well for me & I don't have to mess around with installing BOINC. Also I use the SSE2 opt app so I don't have any issues as some of the machines are older. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1173850 · | |
That wouldn't be recommended, as it would create new HostID's every time you change computers. Plus, if the hardware changed, some application incompatibility could cause a ton of errors. The HostID is held in client_state.xml. The machine name and hardware info will be updated the next time BOINC connects to the servers. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1173851 · | |
Message boards : Number crunching : Hard Drive replacement
| Copyright © 2013 University of California |