Page 1 of 2

[SOLVED] How to check hardware

PostPosted: Apr 1st, '16, 11:01
by evaldas
Sometimes my pc screen goes back with the note that ¨no input system¨. Then I need to power off using power button and then it work normally for week or so and then problem occur again.
May I ask if there is an error logs somewhere so that I would be able to know what was the cause of the problem?

Re: How to check hardware

PostPosted: Apr 1st, '16, 20:40
by jiml8
That error means that your BIOS is failing to find the boot drive, and the result is that it thinks there is no OS to boot. There won't be any logs telling you this; the logs always come only after the OS loads.

Your problem is a BIOS setting, specifying where to boot from. Why it would occur intermittently is not at all obvious to me; possibly you have some problem with your hard drive or with its connections. But that is where your problem is.

Re: How to check hardware

PostPosted: Apr 2nd, '16, 01:25
by benmc
Im not sure from your request.

Does the system not boot up from cold, or after a while of use the
evaldas wrote:¨no input system¨.
is displayed?

Re: How to check hardware

PostPosted: Apr 3rd, '16, 19:57
by evaldas
the message appears after a while of use and this seems strange for me.

Re: How to check hardware

PostPosted: Apr 3rd, '16, 20:56
by filip
Is it possible that overheating is a problem?

Re: How to check hardware

PostPosted: Apr 4th, '16, 21:35
by evaldas
It is unlikely overheating.
Please see screen picture below. It looks like HDD error. Although after reload it works normally

Re: How to check hardware

PostPosted: Apr 5th, '16, 02:58
by benmc
are you able to run a bad blocks scan on the drive, or,
if s.m.a.r.t. is set-up in your bios, you can check the viability or otherwise of the drive.

Download the smartmontools package, and run (as root) the command "smartctl -a /dev/sdN" where sdN is the specific drive you are testing . Copy/paste the results here.
... thank you to jiml8

Re: How to check hardware

PostPosted: Apr 5th, '16, 10:17
by filip

Re: How to check hardware

PostPosted: Apr 7th, '16, 06:06
by evaldas
thank you, it is really nice tool. However no errors found.
What means dev/sda4 file system with errors?

Re: How to check hardware

PostPosted: Apr 7th, '16, 11:51
by filip
evaldas wrote:What means dev/sda4 file system with errors?

It means they should be fixed. Automatic attempt failed so you have to do that manually. File system must not be mounted for fsck so a safe option is to boot from a Live media.

Re: How to check hardware

PostPosted: Apr 8th, '16, 19:35
by evaldas
some more info using journalctl -xb:
Code: Select all
ACPI: Executed 1 blocks of module-level executable AML code
Bal 08 00:24:45 localhost kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Bal 08 00:24:45 localhost kernel: ACPI: Dynamic OEM Table Load:
Bal 08 00:24:45 localhost kernel: ACPI: SSDT 0xFFFF88011A62E000 0003D3 (v01 PmRef  Cpu0Cst  00003001 INTL 20120711)
Bal 08 00:24:45 localhost kernel: ACPI: Dynamic OEM Table Load:
Bal 08 00:24:45 localhost kernel: ACPI: SSDT 0xFFFF88011A5AA800 0005AA (v01 PmRef  ApIst    00003000 INTL 20120711)
Bal 08 00:24:45 localhost kernel: ACPI: Dynamic OEM Table Load:
Bal 08 00:24:45 localhost kernel: ACPI: SSDT 0xFFFF88011A60F800 000119 (v01 PmRef  ApCst    00003000 INTL 20120711)
Bal 08 00:24:45 localhost kernel: ACPI: Interpreter enabled
Bal 08 00:24:45 localhost kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150410/hwxface-580)
Bal 08 00:24:45 localhost kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Bal 08 00:24:45 localhost kernel: ACPI: (supports S0 S3 S4 S5)
Bal 08 00:24:45 localhost kernel: ACPI: Using IOAPIC for interrupt routing
Bal 08 00:24:45 localhost kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Bal 08 00:24:45 localhost kernel: ACPI: Power Resource [FN00] (off)
Bal 08 00:24:45 localhost kernel: ACPI: Power Resource [FN01] (off)
Bal 08 00:24:45 localhost kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Bal 08 00:24:45 localhost kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Bal 08 00:24:45 localhost kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
Bal 08 00:24:45 localhost kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
Bal 08 00:24:45 localhost kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
Bal 08 00:24:45 localhost kernel: PCI host



System wakeup disabled by ACPI
Bal 08 00:24:45 localhost kernel: pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400
Bal 08 00:24:45 localhost kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Bal 08 00:24:45 localhost kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Bal 08 00:24:45 localhost kernel: pci 0000:00:1c.2: [8086:8c14] type 01 class 0x060400
Bal 08 00:24:45 localhost kernel: pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Bal 08 00:24:45 localhost kernel: pci 0000:00:1c.2: System wakeup disabled by ACPI


Non-volatile memory driver v1.3
Bal 08 00:24:49 localhost kernel: ACPI: Invalid active2 threshold
Bal 08 00:24:49 localhost kernel: thermal LNXTHERM:00: registered as thermal_zone0
Bal 08 00:24:49 localhost kernel: ACPI: Thermal Zone [TZ00] (28 C)
Bal 08 00:24:49 localhost kernel: thermal LNXTHERM:01: registered as thermal_zone1
Bal 08 00:24:49 localhost kernel: ACPI: Thermal Zone [TZ01] (30 C)
Bal 08 00:24:47 localhost systemd-udevd[496]: starting version 217
Bal 08 00:24:49 localhost fedora-loadmodules[442]: Loading modules: nvram evdev acpi-cpufreq cpufreq_powersave cpufreq_conservative cpufreq_ondemand
Bal 08 00:24:49 localhost udevadm[491]: settle: invalid option -- '/'
Bal 08 00:24:49 localhost kernel: ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20150
Bal 08 00:24:49 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Bal 08 00:24:49 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Bal 08 00:24:49 localhost kernel: s

r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Bal 08 00:24:50 localhost kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control

usbhid: USB HID core driver
Bal 08 00:24:50 localhost kernel: WARNING! power/level is deprecated; use power/control instead

 kvm: disabled by bios
Bal 08 00:24:51 localhost kernel: kvm: disabled by bios
Bal 08 00:24:51 localhost kernel: kvm: disabled by bios

 FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Bal 08 00:24:51 localhost kernel: Adding 4193276k swap on /dev/sda3.  Priority:-1 extents:1 across:4193276k FS
Bal 08 00:24:51 localhost swapon[633]: swapon: /dev/sda3: swapon failed: Įrenginys ar resursas užimtas
Bal 08 00:24:51 localhost systemd[1]: dev-sda3.swap swap process exited, code=exited status=255
Bal 08 00:24:51 localhost systemd[1]: Unit dev-sda3.swap entered failed state.
Bal 08 00:24:52 localhost kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Bal 08 00:24:52 localhost systemd-fsck[647

Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4: File ... (inode #6292343, mod time Sun Apr  3 21:19:22 2016)
Bal 08 00:24:54 localhost systemd-fsck[647]: has 1 multiply-claimed block(s), shared with 1 file(s):
Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4:         ... (inode #6293211, mod time Mon Apr  4 22:17:39 2016)
Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4:
Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Bal 08 00:24:54 localhost systemd-fsck[647]: (i.e., without -a or -p options)
Bal 08 00:24:54 localhost systemd-fsck[647]: fsck failed with error code 4.
Bal 08 00:24:54 localhost systemd-fsck[647]: Running request emergency.target/start/replace
Bal 08 00:24:54 localhost alsactl[669]: alsactl 1.0.28 daemon started
Bal 08 00:24:54 localhost kernel: EXT4-fs (sda4): warning: mounting fs with errors, running e2fsck is recommended
Bal 08 00:24:54 localhost kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: acl
Bal 08 00:24:55 localhost systemd-timesyncd[681]: System clock time unset or jumped backwards, restoring from recorded timestamp: Fri 2016-04-08 08:00:28 EEST
Bal 08 08:00:28 localhost systemd-timesyncd[681]: The system is configured to read the RTC time in the local time zone. This mode can not be fully supported. All system time to RTC updates are
Bal 08 08:00:30 localhost service_harddrake[1116]: ### Program is starting ###
Bal 08 08:00:30 localhost service_harddrake[1116]: running: dmidecode
Bal 08 08:00:30 localhost service_harddrake[1116]: modified file /etc/sysconfig/harddrake2/kernel
Bal 08 08:00:30 localhost service_harddrake[1116]: modified file /etc/sysconfig/harddrake2/xorg
Bal 08 08:00:32 localhost service_harddrake[1116]: created file /etc/sysconfig/harddrake2/previous_hw
Bal 08 08:00:32 localhost service_harddrake[1116]: launched command: display_driver_helper --check-loaded
Bal 08 08:01:22 localhost swapon[1193]: swapon: /dev/sda3: swapon failed: Įrenginys ar resursas užimtas
Bal 08 08:01:22 localhost systemd[1]: dev-sda3.swap swap process exited, code=exited status=255
Bal 08 08:01:22 localhost systemd[1]: Failed to activate swap Swap Partition.
-- Subject: Unit dev-sda3.swap has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-sda3.swap has failed.
--
-- The result is failed.
Bal 08 08:01:22 localhost systemd[1]: Unit dev-sda3.swa

 WARNING: CPU: 0 PID: 2820 at net/wireless/sme.c:979 cfg80211_connect+0x3f1/0x6a0 [cfg80211]()
Bal 08 08:01:29 localhost kernel: Modules linked in: xt_multiport nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_conntrack_ipv6 nf_nat_sip nf_defrag_ipv6 n
Bal 08 08:01:29 localhost kernel:  uvcvideo aes_x86_64 videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev wl(PO) btusb media usblp btbcm btintel bluetooth hid_generic usbhi



Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 178345 microseconds.
Bal 08 11:30:25 localhost lightdm[4204]: pam_tcb(lightdm:session): Session opened for namai by (uid=0)
Bal 08 11:30:25 localhost kernel: EXT4-fs error (device sda4): ext4_mb_generate_buddy:757: group 769, block bitmap and bg descriptor inconsistent: 1703 vs 1704 free clusters
Bal 08 11:30:26 localhost kernel: EXT4-fs error (device sda4): ext4_mb_generate_buddy:757: group 771, block bitmap and bg descriptor inconsistent: 11499 vs 11368 free clusters
Bal 08 11:30:26 localhost systemd[4208]: Starting Sound Service...
-- Subject: Unit UNIT has begun with start-up
-- Def


dbus[1223]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Bal 08 11:30:29 localhost mgaapplet[4396]: ### Program is starting ###
Bal 08 11:30:29 localhost udisksd[4403]: udisks daemon version 2.1.4 starting
Bal 08 11:30:30 localhost dbus[1223]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Bal 08 11:30:30 localhost udisksd[4403]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Bal 08 11:30:31 localhost dbus[1223]: [system] Activating service name='org.mate.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Bal 08 11:30:31 localhost dbus[1223]: [system] Successfully activated service 'org.mate.SettingsDaemon.DateTimeMechanism'
Bal 08 11:30:31 localhost org.a11y.Bus[4295]: Activating service name='org.a11y.atspi.Registry'
Bal 08 11:30:32 localhost org.a11y.Bus[4295]: Successfully activated service 'org.a11y.atspi.Registry'
Bal 08 11:30:32 localhost org.a11y.atspi.Registry[4439]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Bal 08 11:30:32 localhost org.a11y.atspi.Registry[4439]: Xlib:  extension "XEVIE" missing on display ":0".
Bal 08 11:30:35 localhost kernel: ERROR @wl_dev_intvar_get : error (-1)
Bal 08 11:30:35 localhost kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)
Bal 08 11:30:35 localhost kernel: ERROR @wl_dev_intvar_get : error (-1)
Bal 08 11:30:35 localhost kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)
Bal 08 11:30:35 localhost mgaapplet[4396]: running: ionice -p 4396 -n7
Bal 08 11:30:38 localhost kernel: ERROR @wl_dev_intvar_get : error (-1)
Bal 08 11:30:38 localhost kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)


EXT4-fs (sda4): error count since last fsck: 49
Bal 08 11:31:17 localhost kernel: EXT4-fs (sda4): initial error at time 1459797492: ext4_mb_generate_buddy:757
Bal 08 11:31:17 localhost kernel: EXT4-fs (sda4): last error at time 1460104225: ext4_mb_generate_buddy:757
Bal 08 11:31:38 localhost kernel: ERROR @wl_dev_intvar_get : error (-1)
Bal 08 11:31:38 localhost kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)
Bal 08 11:32:38 localhost kernel: ERROR @wl_dev_intvar_get : error (-1)
Bal 08 11:32:38 localhost kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)
Bal 08 11:32:40 localhost systemd-timesyncd[681]: Timed out waiting for reply from 216.239.36.15:123 (time3.google.com).
Bal 08 11:32:40 localhost systemd-timesyncd[681]: Using NTP server [2001:4860:4802:36::f]:123 (time3.google.com).
Bal 08 11:33:32 localhost kernel: EXT4-fs error (device sda4): ext4_lookup:1588: inode #6291687: comm DOM Worker: deleted inode referenced: 6308129
Bal 08 11:33:38 localhost kernel: ERROR @wl_dev_intvar_get : error (-1)
Bal 08 11:33:38 localhost kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)
Bal 08 11:34:38 localhost kernel: ERROR @wl_dev_intvar_get : error (-1)
Bal 08 11:34:38 localhost kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)



just wander is it RAM problem or power management?

Re: How to check hardware

PostPosted: Apr 8th, '16, 19:54
by evaldas
do you mean to download, write to dvd and run as recue?
I don´t use kde or gnome - I use mate desktop. What should I do?

Re: How to check hardware

PostPosted: Apr 8th, '16, 22:53
by doktor5000
evaldas wrote:some more info using journalctl -xb:
Code: Select all
Bal 08 00:24:51 localhost kernel: Adding 4193276k swap on /dev/sda3.  Priority:-1 extents:1 across:4193276k FS
Bal 08 00:24:51 localhost swapon[633]: swapon: /dev/sda3: swapon failed: Įrenginys ar resursas užimtas
Bal 08 00:24:51 localhost systemd[1]: dev-sda3.swap swap process exited, code=exited status=255
Bal 08 00:24:51 localhost systemd[1]: Unit dev-sda3.swap entered failed state.
Bal 08 00:24:52 localhost kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Bal 08 00:24:52 localhost systemd-fsck[647

Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4: File ... (inode #6292343, mod time Sun Apr  3 21:19:22 2016)
Bal 08 00:24:54 localhost systemd-fsck[647]: has 1 multiply-claimed block(s), shared with 1 file(s):
Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4:         ... (inode #6293211, mod time Mon Apr  4 22:17:39 2016)
Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4:
Bal 08 00:24:54 localhost systemd-fsck[647]: /dev/sda4: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Bal 08 00:24:54 localhost systemd-fsck[647]: (i.e., without -a or -p options)
Bal 08 00:24:54 localhost systemd-fsck[647]: fsck failed with error code 4.

Bal 08 00:24:54 localhost kernel: EXT4-fs (sda4): warning: mounting fs with errors, running e2fsck is recommended
Bal 08 00:24:54 localhost kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: acl

Bal 08 08:01:22 localhost swapon[1193]: swapon: /dev/sda3: swapon failed: Įrenginys ar resursas užimtas
Bal 08 08:01:22 localhost systemd[1]: dev-sda3.swap swap process exited, code=exited status=255
Bal 08 08:01:22 localhost systemd[1]: Failed to activate swap Swap Partition.
-- Subject: Unit dev-sda3.swap has failed

-- Unit dev-sda3.swap has failed.
--
-- The result is failed.
Bal 08 08:01:22 localhost systemd[1]: Unit dev-sda3.swa

Bal 08 11:30:25 localhost kernel: EXT4-fs error (device sda4): ext4_mb_generate_buddy:757: group 769, block bitmap and bg descriptor inconsistent: 1703 vs 1704 free clusters
Bal 08 11:30:26 localhost kernel: EXT4-fs error (device sda4): ext4_mb_generate_buddy:757: group 771, block bitmap and bg descriptor inconsistent: 11499 vs 11368 free clusters
Bal 08 11:30:26 localhost systemd[4208]: Starting Sound Service...

EXT4-fs (sda4): error count since last fsck: 49
Bal 08 11:31:17 localhost kernel: EXT4-fs (sda4): initial error at time 1459797492: ext4_mb_generate_buddy:757
Bal 08 11:31:17 localhost kernel: EXT4-fs (sda4): last error at time 1460104225: ext4_mb_generate_buddy:757

Bal 08 11:33:32 localhost kernel: EXT4-fs error (device sda4): ext4_lookup:1588: inode #6291687: comm DOM Worker: deleted inode referenced: 6308129




just wander is it RAM problem or power management?


If two of your filesystems are broken, it's not a RAM problem or power management in the first place.

First you need to fix those filesystem errors, in failsafe mode as root run
Code: Select all
fsck -y /dev/sda3
fsck -y /dev/sda4

Can't check currently but I think for your swap partition that won't be possible, you would need to recreate that with
Code: Select all
mkswap /dev/sda3


Then I suggest to check the harddisk with the harddisk vendor's diagnosis toolset.
What harddisk model do you use?

Re: How to check hardware

PostPosted: Apr 10th, '16, 20:10
by evaldas
I don know how to go into safe mode, bur when I do it in regular user the output is;
Code: Select all
[root@localhost namai]# fsck -y /dev/sda3
fsck from util-linux 2.25.2
[root@localhost namai]# fsck -y /dev/sda4
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/sda4 is mounted.
e2fsck: Cannot continue, aborting.

Re: How to check hardware

PostPosted: Apr 10th, '16, 21:40
by doktor5000
In the bootmenu there's an entry for safe mode, you can use that one.

Re: How to check hardware

PostPosted: Apr 11th, '16, 19:18
by evaldas
something is wrong. The output is the same - aborting
HDD name is Seagate Barracuda 7200.14 (AF)

Re: How to check hardware

PostPosted: Apr 11th, '16, 19:49
by jiml8
you need to have a space after the -y. The command is fsck -y /dev/... not fsck -y/dev/...

Re: How to check hardware

PostPosted: Apr 22nd, '16, 20:21
by evaldas
unfortunately the output is the same - dev/sda4 is mounted
What means "fsck failed with error code 4"?

Re: How to check hardware

PostPosted: Apr 23rd, '16, 11:23
by doktor5000
You can look up the exit codes in the man page of fsck or e2fsck. It tells you that it's mounted and hence will not continue.
filip already told you that it shouldn't be mounted: viewtopic.php?p=63508#p63508

Re: How to check hardware

PostPosted: Apr 24th, '16, 20:40
by evaldas
I deciced to reinstall Mageia. There were some problems during instalation:
Code: Select all
failed to delete partition #1 om /dev/sda

but after several attempts I succeded

Re: How to check hardware

PostPosted: Apr 24th, '16, 20:44
by doktor5000
Please mark the thread accordingly by editing the topic of the first post and prefix it by [DONE], thanks

Re: How to check hardware

PostPosted: Apr 24th, '16, 20:47
by evaldas
maybe someone could remind me how to change root password?

Re: How to check hardware

PostPosted: Apr 24th, '16, 21:22
by doktor5000
You may open a new thread for that.

Re: How to check hardware

PostPosted: May 15th, '16, 12:32
by evaldas
so, I didn't understand what was the problem - software or hardware. And why after reintalling I left with only 45 Gb of HDD...
Also I suspicious about how Mageia recognizes all-in-one pc - it looks like it thinks it is a laptop with batteries...
Also - that strange "click" sound in both speakers immediately after login appeared again only after I installed first pack of updates after reinstalation

Re: How to check hardware

PostPosted: May 15th, '16, 14:30
by doktor5000
And what shall we do about that?