which version of the app are you running? the standard zi3v? or one of the newer variants?

for now, i am looking only at the inconclusives on my 2 older linux hosts (im not including the newest one since i just brought it online last night and it has not reached "steady state" with regard to stats.

of these 2 hosts, one of them is running 2x 1050tis and is NOT overclocked, but does exibit a current inconclusive rate of about 4.68%. i could be mistaken, but i thought it was lower in the past. i have not made any changes to this system for several months, so that's why i thought the increase in inconclusives was because of newer WUs.

the other system has 2x 1060s and is overclocked a bit (but i dont remember how much, it's nothing crazy). it's seeing a current inconclusive rate of about 3.9%, and has actually dropped since i looked last night where it was closer to 5%.

both of these hosts are more or less identical from a software standpoint.

maybe it's just crappy wingmen.

EDIT
even my windows machines on SoG seem to be seeing higher than normal inconclives. the best one is sitting at 2.8% and the worst one at 3.9% (but its a low producer). something else is going on here. ironically, among my systems, the more heavily overclocked ones are showing better inconclusive rates xD. probably just coincidence, but still interesting.

Fine with me. But, don't be surprised after the next system update to find a repository version of boinc back in var/lib with a new system ID and loads of tasks.

For the rest of you, the first thing to do would be to backup the boinc-client folder. Then open Synaptic Package Manager and Remove, Including Configuration Files, anything installed pertaining to boinc or seti. Then search the system folder for anything leftover. After that, copy the Boinc All-In-One to Home and populate it with the boinc files from your backed-up boinc-client folder. If you're lucky, all the repository files were removed correctly and the Berkeley BOINC will work fine in your Home folder.

If you are already running the Berkeley version of BOINC from your Home folder, then there isn't any trouble updating, or downgrading, the installed version of BOINC. It's a simple matter of replacing the 5 boinc files in your BOINC folder as mentioned earlier.

I would say no it did not put anything on the Windows drive. The grub entries for the Windows drive changed is all. Likely the UUID number for the drive changed.
Run blkid from Terminal and note what the UUID for the Windows drive is. Then examine the grub.cfg file in /boot/grub for the entry identifying the Windows installation and compare the UUID numbers from what blkid showed. Correct the Windows entry if necessary.

I would say no it did not put anything on the Windows drive. The grub entries for the Windows drive changed is all. Likely the UUID number for the drive changed.
Run blkid from Terminal and note what the UUID for the Windows drive is. Then examine the grub.cfg file in /boot/grub for the entry identifying the Windows installation and compare the UUID numbers from what blkid showed. Correct the Windows entry if necessary.

. . OK, I just had a feeling of empathy for Penny on the Big Bang Theory. Firstly, I have disconnected the Linux drive so there is only the Windows SSD connected (and a USB drive with the SETI data on it). There must be something from Linux on the Windows drive for it to give a grub error ... ?? Secondly, since I cannot boot into an OS I can't do much, I have booted up from the Lubuntu 'Live' USB disk which boots OK and it can see the Windows drive but can I do what is needed from such a state? I guess I'll suck it and see ...

<edit>
. . OK, I ran the blkid and got a UUID for each of the partitions on the Windows drive (system, main and recovery) but it indicates that I am in the Windows drive, main partition, in folder /media/lubuntu but File manager does not see such a folder even when 'display hidden' is on. Not even a /media folder. I am guessing that the grub.cfg file is secreted somewhere in this partition.

. . On booting the errors are -
no such device <8>-<4>-<4>-<4>-<12> {number of digits}
unknown file system
<Grub rescue> prompt

. . Since I was having trouble with the Lubuntu install I doubt if reconnecting the Linux drive would help ... but who knows ...

Stephen ? ?

:(

I think the way I remember Windows boot problems it went something like, Boot to Windows Install media, Go to Repair section, Tell it to FIX MBR & FIX BOOT. I vaguely remember that from somewhere...I could be wrong.

You need to learn about grub I guess. Maybe read up on it or watch some of the many YT tutorials. I assume you are running a dual-disk system with each OS on its own disk? So either you installed grub into the MBR of the Windows disk or possibly into an EFI partition on either of the disks if UEFI based. You should be able to see either disk if booting off the Live USB stick. The /boot/grub directory is in the main Linux partition. You can see all your partitions on all your disks if you launch the gparted or Disks applications from the Live USB stick. You should be able to maneuver to any disk you can see in those applications if you mount them with Nautilus or the File Manager. Use the Disks application to mount the drives. You need to be root to edit the grub.cfg file.

Grub is the bootloader to allow you to select either the Windows or Linux installation to boot from. The pointer that identified the Windows boot installation got changed somehow. Did you update your BIOS by chance? That will usually reenumerate the USB and drive resources. Or did you install a new drive or plug in another USB drive?

Maybe start with this page Ways To Rescue Or Recover Grub

I think the way I remember Windows boot problems it went something like, Boot to Windows Install media, Go to Repair section, Tell it to FIX MBR & FIX BOOT. I vaguely remember that from somewhere...I could be wrong.

I think the way I remember Windows boot problems it went something like, Boot to Windows Install media, Go to Repair section, Tell it to FIX MBR & FIX BOOT. I vaguely remember that from somewhere...I could be wrong.

That would be the brute force way of getting back into Windows. But you won't be able to get back into Linux that way without re-installing grub2 again.

. . OK the problem with the new rig is that Lubuntu seems to have done something to the Windows drive even though it was not active when I shut it down. The machine had been crunching happily under Windows for several weeks, but when I try to restart it I get a grub error. I have disconnected the Linux SSD completely but I still get the same grub error, so it must have put something on the Windows drive. Does anyone know how to remove all trace of Linux from an NTFS windows drive?

Stephen

? ?

Are we using command line parameters on any of the cpu apps?

What does your "app_config.xml" file look like?

Are you doing any "tuning" to your motherboard?

Are you doing any "tuning" to your gpu/cpu?

Thank you.

Question is where is the bootloader? The Linux system may be installed on its separate drive but when you installed it and accepted defaults, when the installer saw the other Windows drive it probably installed the grub bootloader in the MBR of the Windows system. So as long as the Windows system is attached to the computer, the grub bootloader is going to be active.

If you don't know what is going on and don't want to learn how grub works and just want to get running again, I would just run the standard Windows FIX_MBR and FIX_Boot utilities to enable the Windows MBR to boot the Windows drive normally again. Then I would resize and repartition the Linux or Windows drive and make a small EFI FAT32 partition which is usually just a couple hundred megabytes just to hold the grub bootloader.

I think the "windows repair" function will in Win10. If you are running Win7 I have used the command line tool that talks about "fix boot"(track) to get rid of the grub startup.
You can access either by booting from a Windows setup disk and looking for the "repair os" url on I think the 2nd screen right after the first screen.
Tom

Are we using command line parameters on any of the cpu apps? NO

What does your "app_config.xml" file look like? See above

Are you doing any "tuning" to your motherboard? NO

Are you doing any "tuning" to your gpu/cpu? Just the ones amply covered by Petri and TBar before the B1/B2 releases; -pfl 256 and -pfe which are now discarded in the aforementioned releases and -nobs.

Stephen

. .