busybox error

[rene]

CMOS-battery powers the real-time clock yes, but more importantly here powers your system's store of BIOS-settings. If said settings would get reset every once in a while then, yes, you'd have that message. Said reset could be a matter of failing CMOS-battery -- but it's not common at all and moreover, would not likely have any bearing on the main issue: default BIOS-settings tend to be only more rather than less conservative. I.e., whatever's up there it's not likely causally related to this thread as such.

The tech will have supposedly also generally blown out the system and.or reseated a couple of connectors. For now just wait to see if it the situation has improved; as Marie also said, you/we can't go jumping from one potential issue to the next without any intervening indication/proof as to such. Running with a single DIMM for a bit is (still...) the most useful diagnosis if it hasn't yet improved.

[Marie SWE]

You mentioned the CMOS battery? Well, periodically get a cmos error upon start up. I figured that all the cmos does is keeps the clock time accurate and ntp is more accurate than the battery could be. So that is the problem?

rene explained it well.
Try to remember what the error message is or write it up/take a photo next time.
To add what rene already has written.. some hardware.. (more an exception of the rule).. but some hardware will not even get to Bios boot screen when the battery is bad.. some can start behave weird when used.. This is most common on some laptops and servers.. most common on this ones is that you only get a black screen when you try to power them on... On servers I think this it is a protection mechanism as they have hardware raid and if the bios get reset it can damage the whole raid array. Perhaps some manufactures as Dell/HP that make servers has implemented the same "protection mechanism" on some laptops and desktops too..

a cmos battery is cheep, so if its bad.. replace it.. If you have a voltmeter you can check it. 3V is when its new and I always replace them if they goes under 2.2.. some system stops working when the battery is lower then 1.9V and Bios starts to forget it's settings (if i remember right) at 1.5V

And to quote rene ""you/we can't go jumping from one potential issue to the next without any intervening indication/proof as to such. Running with a single DIMM for a bit is (still...) the most useful diagnosis if it hasn't yet improved.""

You still need to test one thing at the time, before rushing in to the next potential theory. Just thinking and talking about it will never come to an conclusion of what is the cause..

[bmike1]

okay got my little NUC back:
made sure turned on and ran for (browsed) like 3 minutes then ran....

Code: Select all

michael@desktop1:~$ uptime
 12:35:31 up 15 min,  1 user,  load average: 0.20, 0.37, 0.33
michael@desktop1:~$ sensors
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +101.0°C)
temp2:        +29.8°C  (crit = +101.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +55.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:        +55.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:        +53.0°C  (high = +86.0°C, crit = +100.0°C)

then let it sit and ran:

Code: Select all

michael@desktop1:~$ uptime
 12:45:23 up 25 min,  1 user,  load average: 0.35, 0.37, 0.36
michael@desktop1:~$ sensors
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +101.0°C)
temp2:        +29.8°C  (crit = +101.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +57.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:        +57.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:        +53.0°C  (high = +86.0°C, crit = +100.0°C)

Much better than the 72ish I was getting before!

Code: Select all

michael@desktop1:~$ sudo smartctl -A /dev/sda
[code]smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-43-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 48
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       304174
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       1
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       3214
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2405
100 Unknown_Kingston_Attr   0x0032   100   100   000    Old_age   Always       -       2269664
101 Unknown_Kingston_Attr   0x0032   100   100   000    Old_age   Always       -       474752
170 Reserved_Block_Count    0x0032   100   100   000    Old_age   Always       -       1
171 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
174 Unexpect_Power_Loss_Ct  0x0032   100   100   000    Old_age   Always       -       1223
175 Program_Fail_Count_Chip 0x0032   100   100   000    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   000    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   095   095   000    Old_age   Always       -       1576
178 Used_Rsvd_Blk_Cnt_Chip  0x0002   100   100   000    Old_age   Always       -       1
180 Unused_Rsvd_Blk_Cnt_Tot 0x0002   100   100   000    Old_age   Always       -       681
183 Runtime_Bad_Block       0x0032   095   095   000    Old_age   Always       -       21
187 Reported_Uncorrect      0x0033   100   100   000    Pre-fail  Always       -       1
194 Temperature_Celsius     0x0022   051   100   000    Old_age   Always       -       51 (Min/Max 15/66)
195 Hardware_ECC_Recovered  0x0032   100   100   000    Old_age   Always       -       304174
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0012   100   100   000    Old_age   Always       -       0
201 Unc_Read_Error_Rate     0x0032   100   100   000    Old_age   Always       -       0
204 Soft_ECC_Correction     0x0032   100   100   000    Old_age   Always       -       304173
231 SSD_Life_Left           0x0032   095   095   000    Old_age   Always       -       5
233 Media_Wearout_Indicator 0x0032   100   100   000    Old_age   Always       -       4715
234 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       3643
241 Host_Writes_GiB         0x0032   100   100   000    Old_age   Always       -       3213
242 Host_Reads_GiB          0x0032   100   100   000    Old_age   Always       -       3434
250 Read_Retry_Count        0x0032   100   100   000    Old_age   Always       -       304207

[bmike1]

darn:
<after eating lunch>

Code: Select all

michael@desktop1:~$ uptime
 13:35:51 up  1:15,  1 user,  load average: 2.13, 1.98, 1.87
michael@desktop1:~$ sensors
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +101.0°C)
temp2:        +29.8°C  (crit = +101.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +72.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:        +72.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:        +70.0°C  (high = +86.0°C, crit = +100.0°C)

so I guess it just runs hot.

[rene]

At least the high temperature correlates with high load; your first display is good. We've been trying to get you to run e.g. top or that system monitor stuff to see what's eating your CPU and/or correlate this with open browser and/or specific browser tabs.

[bmike1]

mint@mint:~$ uptime
16:26:52 up 15 min, 1 user, load average: 1.20, 2.08, 1.50
mint@mint:~$

[bmike1]

I'm reinstalling again. It freezes right after I select the OS to load and the screen goes black.I ordered an 8 gig DIMM so I will have the same amount of ram and I will test one chip as has been recommended. After around a week w/o a fault I will add one 4 gig card and see if I get a fault. then repeat with the othe 4 gig card.

[rene]

So as to then answer/expand on a previous question of yours: yes, 8+4 works. It's suboptimal in the sense that your dual-channel capable system would then run in single-channel mode -- but in practice you'd probably not even notice. Just something to keep in mind for when the opportunity arises to get the second 8G DIMM.

[bmike1]

so effectively I ill have 12 gig in the machine or only 8? Or what do you mean by single channel mode?

[rene]

12. And the fact that it's in single-channel mode may in fact even "help" you by being slower -- but the 8G DIMM alone is the by far best test as to whether or not you in fact had a memory issue.

[bmike1]

you know..... I ran it with 4 gig and it complained about having less memory than before.

[bmike1]

and memory problems could be the cause of a kernel panic that just happened? I tried to boot again (x3) but the kernel panicked each time. It is like something happened to the / directory. Would a memory issue cause this?

[bmike1]

HMMMMM.... I suppose a kernel panic doesn't have anything to do with the root directory. Is this correct? What could cause the panic?

[bmike1]

Libreoffice just freaked on me with:

Code: Select all

~$ libreoffice 
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'


Fatal exception: Signal 6
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x41eb3)[0x7f77dba22eb3]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x42074)[0x7f77dba23074]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f77db7ea520]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7f77db83ea7c]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f77db7ea476]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7f77db7d07f3]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa2bfe)[0x7f77d8e3ebfe]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xae28c)[0x7f77d8e4a28c]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xae2f7)[0x7f77d8e4a2f7]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xae558)[0x7f77d8e4a558]
/usr/lib/libreoffice/program/libxmlreaderlo.so(+0x3a4d)[0x7f77d9a8ea4d]
/usr/lib/libreoffice/program/libmergedlo.so(+0x14ff3a8)[0x7f77dcf4b3a8]
/usr/lib/libreoffice/program/libmergedlo.so(+0x14eb2bb)[0x7f77dcf372bb]
/usr/lib/libreoffice/program/libmergedlo.so(+0x14eb9db)[0x7f77dcf379db]
/usr/lib/libreoffice/program/libmergedlo.so(+0x14ec452)[0x7f77dcf38452]
/usr/lib/libreoffice/program/libmergedlo.so(+0x14ec7a0)[0x7f77dcf387a0]
/usr/lib/libreoffice/program/libmergedlo.so(+0x14f202d)[0x7f77dcf3e02d]
/usr/lib/libreoffice/program/libmergedlo.so(+0x302933d)[0x7f77dea7533d]
/usr/lib/libreoffice/program/libmergedlo.so(+0x302992a)[0x7f77dea7592a]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0x82)[0x7f77dea6e5e2]
/usr/lib/libreoffice/program/libmergedlo.so(+0x3063f3e)[0x7f77deaaff3e]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x12d)[0x7f77deab0dcd]
/usr/lib/libreoffice/program/libmergedlo.so(+0x35131f6)[0x7f77def5f1f6]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0xf499b)[0x7f77d51af99b]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0xf5eb5)[0x7f77d51b0eb5]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x10832b)[0x7f77d51c332b]
/usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x502)[0x7f77def6d172]
/usr/lib/libreoffice/program/libmergedlo.so(_Z10ImplSVMainv+0xf5)[0x7f77def6e6a5]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0xa3)[0x7f77dddf3cc3]
/usr/lib/libreoffice/program/soffice.bin(+0x10b0)[0x56057b8210b0]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f77db7d1d90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f77db7d1e40]
/usr/lib/libreoffice/program/soffice.bin(+0x10e5)[0x56057b8210e5]
michael@desktop1:~$ 

just a symptom of the memory problem?

[Marie SWE]

yes the system will complain when you change the memory, but only on first reboot..

Okay, so now you still get problems with only one 4GB ram..
Now switch to the other memory and run that for a while and see if you get the same problems or if the problems disappears.

[bmike1]

libreoffice won't start with either memory chip. I don't know about it crashing. I was waiting for the 8gb chip. I'm only running 4 gig now.

[bmike1]

In the morning I will do another install. See if the ol' microsoft fix fixes it. That reminds me. I installed the root partition as ext2 and home as ext4. What is the benefit of doing it that way?

[bmike1]

okay..... I just reinstalled for the libreoffice problem and everything seems to be fine now. still running on one of the 4 gig chips. If I don't get the busybox error after a week do you want me to switch chips and see if I get it then?

[bmike1]

I think I figured out the problem. I’ve been installing on a usb hub and I think it has a loose wire. I figured this out when Firefox, after the last install, wouldn’t start. And before that libre calc didn’t work properly until I reinstalled. I’m reinstalling again now connected directly to the computer so we will see.

[bmike1]

That wouldn't cause the busybox error; would it?