My biggest cruncher 8646786 is on a 128gb drive and it's only got 6gb free. Seti is complaining about not having enough space. I have another 120gb drive available. Can I format the new drive and move my /home and the all in one boinc to the new drive? Any pitfalls to watch for? I'm on lubuntu at the moment.

---

You can probably free up some space by finding and deleting the large numbers of "update" files that can be delivered and never removed.
It is theoretically possible under most Linux distros to join a second HDD to an existing one to create a single "virtual" drive from the two, it might be worth having a quick google to find the how (and pitfalls)

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

You likely have large and increasing log files taking up all your space. Not normal. Check to see which directory and files is large. Likely /var/log and the kern.log or the syslog files. Some error is constantly being written to the files. You need to look at the files and determine what the error is. You need to add some commands to the grub kernel command line to ignore the errors.

Somebody, I can't remember who, wrote about their disk filling up because of TLP errors on the PCI bus and fixed it by using a kernel command line argument. Mr. Kevvy . . . Ian, I can't remember.

I have many 128GB SSD's that have been running for over a year and only 25% filled.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

You likely have large and increasing log files taking up all your space. Not normal. Check to see which directory and files is large. Likely /var/log and the kern.log or the syslog files. Some error is constantly being written to the files. You need to look at the files and determine what the error is. You need to add some commands to the grub kernel command line to ignore the errors.

Somebody, I can't remember who, wrote about their disk filling up because of TLP errors on the PCI bus and fixed it by using a kernel command line argument. Mr. Kevvy . . . Ian, I can't remember.

I have many 128GB SSD's that have been running for over a year and only 25% filled.

I will have to check it out. I know every few days I have to restart boinc. I get errors like ..has restarted 3 times.... I'm not sure why.

---

Open up the Logs application in your Applications list and see what is showing for Important. You will need to remedy what is causing errors.

Or write a script to truncate the logs constantly, to keep from filling up your drive.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I will when I get home from work.

Edit: Come to think of it , I had the same problem in Windows. I might have a hardware problem.
Had a pair of GTX 750ti's before the current GTX 960's

---

If you haven't installed it already, go to your Software library and search for and install Disk Usage Analyzer. That would confirm which directory and file(s) are the culprits of eating your disk space. Then investigate the logged errors and correct them.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

You likely have large and increasing log files taking up all your space. Not normal. Check to see which directory and files is large. Likely /var/log and the kern.log or the syslog files. Some error is constantly being written to the files. You need to look at the files and determine what the error is. You need to add some commands to the grub kernel command line to ignore the errors.

Somebody, I can't remember who, wrote about their disk filling up because of TLP errors on the PCI bus and fixed it by using a kernel command line argument. Mr. Kevvy . . . Ian, I can't remember.

I have many 128GB SSD's that have been running for over a year and only 25% filled.

That was me. I wrote up a fix for it. I’ll find it when I get back from lunch if someone else doesn’t find my post and link it before I get back lol.

ASUS motherboards seem to be the worst offenders. Especially the X99 ones.

Edit. Here is my post.

https://setiathome.berkeley.edu/forum_thread.php?id=83613&postid=1967880#1967880

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

You likely have large and increasing log files taking up all your space. Not normal. Check to see which directory and files is large. Likely /var/log and the kern.log or the syslog files. Some error is constantly being written to the files. You need to look at the files and determine what the error is. You need to add some commands to the grub kernel command line to ignore the errors.

Somebody, I can't remember who, wrote about their disk filling up because of TLP errors on the PCI bus and fixed it by using a kernel command line argument. Mr. Kevvy . . . Ian, I can't remember.

I have many 128GB SSD's that have been running for over a year and only 25% filled.

That was me. I wrote up a fix for it. I’ll find it when I get back from lunch if someone else doesn’t find my post and link it before I get back lol.

ASUS motherboards seem to be the worst offenders. Especially the X99 ones.

Edit. Here is my post.

https://setiathome.berkeley.edu/forum_thread.php?id=83613&postid=1967880#1967880

It's a Z10PE-D8 WS Asus motherboard C 612 chipset. I'll have to look to see if both cards are on the same cpu. I might try moving a card depending on pcie slots are mapped.

---

I personally had this issue on an ASUS z270 board. I’ve helped several others with the same problem on ASUS X79 and X99 boards. And most of the people having similar issues I found online seem to have ASUS x99 boards.

It’s pretty easy to just change the behavior causing the issue by editing the grub file with the specified kernel command lines.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Edit: Come to think of it , I had the same problem in Windows. I might have a hardware problem.

Windows can tie itself up in knots with a failed update.

Basically the machine goes and downloads a ~100mb update file, tries to install it, and fails. Next day it tries again, same result. A few months later you run out of disk space and if you dig around it's in the software downloads and/or temp folders.

Usually no hardware fault, and deleting the crud and running through the diagnostics for Windows Update usually fixes the problem.

I've had machines running Seti for years, sometime with only an 80gb drive. Looking at my 2 desktop machines they have 7 and 8 projects active, and both around 2gb used by BOINC,

So yeah, start with a disk analyser and see where the space is being wasted. Could be some massive and meaningless log file?