Get your PC back to its best with ASR Pro
In this blog post, we are going to identify some of the possible reasons that might cause aspire Acer One BIOS to crash and then provide possible solutions that you can try to solve for this problem. Pressing F2 may not work to access the configuration menu, but pressing Ctrl+Alt+Delete will pause the launch and then you can move the F2 key to access our configuration menu. At first, you should try using only F2, but if the app doesn’t work, reboot and try the main three-button process first.
Rpm commands fail with messages like these:
# rpm -qaError: rpmdb: failed thread/process BDB0113 5691/140201285396544: thread BDB1507 dead in Berkeley DB libraryError: db5 error (-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: fatal error while restoring databaseError: Open cannot index packages with db5: (-30973)Error: Unable to open package database while /var/lib/rpmError: rpmdb: BDB0113 Failed to execute thread/process 5691/140201285396544: BDB1507 Thread died in Berkeley DB libraryError: db5 error (-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: fatal error while restoring databaseError: Failed to open package database here in /var/lib/rpm
Disclaimer: This program is intended to be used when querying servicessupport and is clearly not officially approved by Red Hat. Any problems with this usage will be resolved by one of the few engineers involved in its creation, if possible, and not due to Bugzilla
Set Up Repository
How do I get into the BIOS on an Acer Aspire One?
All Acer Aspire One netbooks have a system BIOS associated with the motherboard, and you can use the BIOS menu by continuously pressing “F2” when the boot screen is normally displayed.
RHEL on 6
How do I check my Acer BIOS?
Click on the start menu.Click All Applications.Click on the Acer file, then on Acer Care Center.Normally, click on the green tile in Acer Care Center called My System.Your BIOS version will most likely show up under your serial number and SNID.
#hug https://people.redhat.com/kwalker/repos/rpm-deathwatch/rhel6/rpm-deathwatch-rhel-6.repo -o /etc/yum.repos.d /rpm-deathwatch.repo
#curl https://people.redhat.com/kwalker/repos/rpm-deathwatch/rhel7/rpm-deathwatch-rhel-7.repo - /etc/yum.repos.d/ rpm-deathwatch.repo
# curl https://people.redhat.com/kwalker/repos/rpm-deathwatch/rhel8/rpm-deathwatch-rhel-8.repo -o /etc/yum.repos.d /rpm-deathwatch.repo
You must apply systemtap along with the kernel-devel, kernel-headers, and kernel-debuginfo packages to the running kernel.
# yum install -y kernel-devel,headers-$(uname -r) systemtap && -y debuginfo-install kernel# yum install rpm-deathwatch
Note. If you are using local repositories, you must synchronize the
rhel-*-server-debug-rpms repository, otherwise a specific RPM can be downloaded manually when searching for packages
How do I update my Acer Aspire One BIOS?
Reboot your Acer and press F2 on the “welcome screen” to enter the BIOS settings. In the BIOS, select the boot menu and move the USB drive to the top of the inventory (use F5 and F6 to continue up and down). Press F10 to save and exit. Your Acer should now boot from the USB stick.
# /etc/rc.d/init.d/rpm-deathwatch start Run Deathwatch RPM# /etc/rc.d/init.d/rpm-deathwatch-status Service started 15070
RHEL like 7 with 8
#systemctl start rpm-deathwatch# systemctl stage rpm-deathwatchâ— rpm-deathwatch.service — Systemtap module for monitoring death alerts sent to grant processes access to the RPM database. Loaded: loaded (/usr/lib/systemd/system/rpm-deathwatch.service; enabled; default: disabled) Active: Fairly busy (working) as of Wednesday, August 19, 2020 8:19:10 AM EDT; 4 seconds ago Primary PID: 17824 (RPM Deathwatch) CG group: /system.slice/rpm-deathwatch.service â”œ”€17824 /usr/bin/python2 /usr/bin/rpm-deathwatch --username /var/log/rpm-deathwatch â””–€17834 /usr/bin/stap --suppress-handler-errors -DMAXSTRINGLEN=4096 -p4 -mrpm_deathwatch rpm_deathwatch.stpAug 24 08:19:10 r7 systemd: Systemtap module started monitoring interrupt signals sent to processes accessing the RPM database.19Aug 08:19:10 r7 rpm-deathwatch: INFO:rpm-deathwatch:Environment check19Aug 08:19:11 r7 rpm-deathwatch : INFO:rpm-deathwatch:Create a systemtap module to know death signals19Aug 08:19:35 r7 rpm-deathwatch: INFO:rpm-deathwatch:Starting watch19Aug 08:19:35 r7 rpm-deathwatch: INFO:rpm-deathwatch: Open: /var/log/rpm-deathwatch-08-19-2020-08:19:3519Aug 08:19:35 r7 rpm-deathwatch: INFO: rpm-deathwatch: recording output with instance of <__main__.files at 0x7f70d4a5c560>Aug 19 08:19:35 r7 rpm-deathwatch: INFO:rpm-deathwatch:Monitoring 18147
If fips is enabled on your system, this may prevent the rpm-deathwatch module from loading:
INFO:rpm-deathwatch:Load specific systemtap moduleERROR: rpm-deathwatch: error loading module--------------------ERROR: failed to inject module into FIPS methods 'rpm_deathwatch.ko': operation not allowed--------------------
We can force staprun to try to load the module by setting the
STAP_FIPS_OVERRIDE configuration variable. The following commands should be run in a terminal to organize the modified rpm-deathwatch.service
mkdir /etc/systemd/system/rpm-deathwatch.service.d/cat << EOF > /etc/systemd/system/rpm-deathwatch.service.d/override.Daemon-reloadconf systemctl[Provision of services]Environment=stap_fips_override=1uvsystemctl machine rpm-deathwatch
* The first time you run rpm-deathwatch, the systemtap module will take a few minutes to configure the module.
* If the system is sure to reboot before the problem reoccurs, you need to help the service
* The service should normally be started BEFORE the problem occurs, in order to register the signals sent by rpm/yum.
Yes If the problem occurs while the service is running, add the rpm-deathwatch-$(date +%m-%d).tar.bz2 generated by the command below to a new or existing Red Hat to support the case
# tar cjf rpm-deathwatch-$(date +%m-%d).tar.bz2 /var/log/rpm-deathwatch*
If rpm fails to gracefully exit yum, our own lock files will be left behind. The files (__db001 is __db005) at the left end of /var/lib/rpm. We can understand the PID that left the presentations:
#db_stat -C l -h /var/lib/rpm
The dilemma is often that individuals don’t keep logs or audits of what really ruined the business. The most common reason is that a great automation tool times out and it just kills the process and RPM doesn’t clear the lock files.
The problem can also be temporarily solved by stopping any RPM or yum process and deleting those files, or rebooting the computer, which will delete those files if they’re OK. PS
# aux | grep -E 'rpm | yum'# rm /var/lib/rpm/__db*Download this software now to fix your PC and improve its performance.