Message boards :
Number crunching :
Setting up Linux to crunch CUDA90 and above for Windows users
Message board moderation
Previous · 1 . . . 81 · 82 · 83 · 84 · 85 · 86 · 87 . . . 162 · Next
Author | Message |
---|---|
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
which version of the app are you running? the standard zi3v? or one of the newer variants? . . Both Linux boxes are running 0.97 from before the "Bananas in Pyjamas" versions (read B1 and B2 :) ), I think it has been called the multiverse release. I have stayed with this because the 'B' releases do not support the -pfl or -pfe parameters. And if Zi3v ever did support them I was unaware of it. With Zi3v the rates were lower but I wasn't crunching the current batches of units with that (at least not that I have recorded). I am curious that the GBT tasks we are getting now seem to have reverted (based on run times) to the original format, before they did whatever they did that got them to run much quicker. But even with these slower versions it seems to not be all of them having the rise in inconclusives, it seems to be different 'batches' or tapes maybe where they go up. . . Computers will often confound you. It amuses me that the overclocked rigs show better results ... :) . . While 5% has been proposed as the 'acceptable' limit for inconclusives I like to keep it below 2% if possible. And that is about where mine are ... most of the time. The main thing, and this tends to support the wingman effect, is that I have Zero (0) invalids. The only thing that bothers me is that the rig with the 970s tends to hit the 4% plus level most often so I am wondering if I should drop it back to -pfl 256 as well, though even with that setting it still had the occasional 4% peak just as the box with the 1050ti still does. . . Oh, and another factor that points the finger at the WU batches is the way in which inconclusives are often higher with CPU crunched tasks than with the Cuda90 results. Stephen . . |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
I'd have to agree with your assessment of the zi3v app versus any flavor of the 0.97 apps including the "b" versions with pfb defaults and loss of pfe parameter. The "b" versions seem to have stabilized at about 4.6% Inconclusive rate on my hosts. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
JohnDK Send message Joined: 28 May 00 Posts: 1222 Credit: 451,243,443 RAC: 1,127 |
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. I first read your post now, so I didn't delete anything... But so far it's working by copying all the BOINC config files to the BOINC home folder. Strange though stating boincmgr from home folder startede the repo BOINC but starting it from the krusader program it worked. All backup projects runs now, hope we will get new seti work soon... Wonder what happens if I uninstall repo BOINC now. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
If you don't Completely Remove All BOINC Repository files from the System folder, then Very Strange things will happen when trying to run the Berkeley BOINC from your Home folder....Guaranteed. <nods head> |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
. . 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 ? ? |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
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. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
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. . . 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 ? ? :( |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
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 Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
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 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. |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
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. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
I avoided issues with grub when I had Linux and Windows on separate drives like you do by not using grub to select the target boot OS. I used, and still do, just use the BIOS to select the drive I want to boot from. Takes grub out of the equation in that respect. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
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. . . First, yes dual drive system 250GB SSD for Windows and 120GB SSD for Linux. I had it configured for boot from the 120GB and I would select Windows from the Linux boot menu. This is why when I was getting a Grub error I disconnected the Linux drive and set the BIOS boot priority to the Windows drive. This should have gone straight into the windows bootloader but nope. I didn't install any Linux components on the Windows drive, the whole point was to keep them totally segregated. But clearly something has at some stage done just that. I have not created any Linux partition/s on the Windows drive either. My first instinct was to boot from the windows 10 CD and do a repair of the windows drive. But in my usual well ordered fashion I have misplaced the Windows 10 CD :( . . I had a look at that link and read through it to try and find the most appropriate method, but too many options only confused me :( . . The only recent changes were when Microsoft launched one of their 'Windows updates you can't refuse" and as usual trashed my video drivers which I re-installed from the downloaded Nvidia drivers file. It booted successfully when that was complete and I am not aware of any changes since then. I have tried a few Linux OS installs but all that was pointed at the now disconnected drive. . . I will try the 'Live' disk again and see if I can find out more with gparted. I considered that before but wasn't sure if it was safe in the 'Live' mode. Stephen <scratching head> |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
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. . . Yep that sounded pretty right to me too, until I couldn't find my Windows 10 install disk :( I think I need a secretary. . . I am going to try Keith's suggestion and run gparted from the Lubuntu 'live' disk, crossing fingers. Stephen <wishing I wasn't bald so I could at least have the satisfaction of pulling my hair out> |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
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. . . Yep, but on that machine only the Windows install has been in regular productive use. I expect to re-install the Linux OS anyway so it seemed the best option, if I could only remember where I put that damned disk. Stephen :( |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
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. The better method in my opinion is to install the bootloader in an EFI FAT32 partition all on its own keeping the Windows completely untouched by grub and Linux completely untouched by grub. So the grub bootloader simply has the UUID pointers for each disk and lets each individual OS bootstrap itself into running. 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. [Edit] Thought maybe a picture worth a thousand words. Here is my system. The grub bootloader is the highlighted FAT32 538MB partition between my two operating system partitions. Notice it is mounted at /boot/efi. This is the partition that the BIOS points to first for loading. Then the grub menu is presented to me to choose either the default partition at the beginning of the disk or to boot the OS occupying the partition at the end of the disk EFI FAT32 Grub bootloader partition Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Tom M Send message Joined: 28 Nov 02 Posts: 5124 Credit: 276,046,078 RAC: 462 |
. . 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? 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 A proud member of the OFA (Old Farts Association). |
Tom M Send message Joined: 28 Nov 02 Posts: 5124 Credit: 276,046,078 RAC: 462 |
I know we don't use command line parameters (mostly) on the CUDA90/91 app.
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?
A proud member of the OFA (Old Farts Association). |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
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. . . That's the thing that bothers me, I never accept the defaults, I always use a custom install and point everything to the 2nd SSD for Linux. And it was working even after the M$ "update you can't refuse" screwed the video drivers again and I had to re-install the Nvidia download. It booted just fine at the end of all that. But after I shut it down manually to avoid lightning damage it refuses to boot and gives a grub error with just the Windows SSD connected. So something, at some time after that, has written some grub component to that drive. 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. . . Not being able to find my Windows 10 install CD I finally borrowed one from a friend and booted it up to run the boot repair option which failed and declared it could not fix the drive. :( . . It is very frustrating :( Stephen :( |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
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. . . Thanks Tom, I gave that a try but it failed saying it could not fix the drive. Stephen :( |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
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.
|
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.