hard disks

To diagnose what's wrong with a hard disk setup you can use smartctl. The last time i needed this was when i experienced hiccups/freezes in the os and these messages in syslog :

syslog

Jan 24 00:01:28 hoek kernel: [ 3161.235608] ata6.00: status: { DRDY }
Jan 24 00:01:28 hoek kernel: [ 3161.235611] ata6.00: failed command: WRITE FPDMA QUEUED
Jan 24 00:01:28 hoek kernel: [ 3161.235619] ata6.00: cmd 61/08:38:d0:8c:95/00:00:02:00:00/40 tag 7 ncq dma 4096 out
Jan 24 00:01:28 hoek kernel: [ 3161.235619]          res 40/00:30:10:89:95/00:00:02:00:00/40 Emask 0x50 (ATA bus error)
Jan 24 00:01:28 hoek kernel: [ 3161.235623] ata6.00: status: { DRDY }
Jan 24 00:01:28 hoek kernel: [ 3161.235626] ata6.00: failed command: WRITE FPDMA QUEUED
Jan 24 00:01:28 hoek kernel: [ 3161.235633] ata6.00: cmd 61/08:40:48:97:95/00:00:02:00:00/40 tag 8 ncq dma 4096 out
Jan 24 00:01:28 hoek kernel: [ 3161.235633]          res 40/00:30:10:89:95/00:00:02:00:00/40 Emask 0x50 (ATA bus error)

To diagnose this you can do smartctl first, but to find out which disk it is, here is a script ~/bin/ata.sh that finds them for you :

ata.sh

#!/bin/bash
OLDIFS="$IFS"

for i in /sys/block/sd*; do 
 readlink $i |
 sed 's^\.\./devices^/sys/devices^ ;
      s^/host[0-9]\{1,2\}/target^ ^ ;
      s^/[0-9]\{1,2\}\(:[0-9]\)\{3\}/block/^ ^' \
 \
  |
  while IFS=' ' read Path HostFull ID
  do
     # NEW lines: will now also work without a hitch on r/o environments
     IFS=: h=($HostFull)
     HostMain=${h[0]}; HostMid=${h[1]}; HostSub=${h[2]}

     if echo $Path | grep -q '/usb[0-9]*/'; then
       echo "(Device $ID is not an ATA device, but a USB device [e. g. a pen drive])"
     else
       echo $ID: ata$(< "$Path/host$HostMain/scsi_host/host$HostMain/unique_id").$HostMid$HostSub
     fi
  done
done

# restore original IFS
IFS="$OLDIFS"

ata.sh output

ata.sh
sda: ata2.00
sdb: ata2.01
sdc: ata6.00
(Device sdd is not an ATA device, but a USB device [e. g. a pen drive])
(Device sde is not an ATA device, but a USB device [e. g. a pen drive])

So ata6 is /dev/sdc which was the system disk in this case.

smartctl

smartctl -a /dev/sdc
smartctl -x /dev/sdc
smartctl -h /dev/sdc

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

So the hard disk does not seem to be damaged. What you can do now is :

• try another sata cable
• switch disks on sata ports

The last one actually helped, which also means :

I put a knotted sata cable in that slot in the hope i will understand later on ;)

servert ACPI error

This solution works :

In short :

commands

modprobe -r acpi_power_meter
echo "blacklist acpi_power_meter" >> /etc/modprobe.d/hwmon.conf
echo "install acpi_power_meter /bin/false" >> /etc/modprobe.d/hwmon.conf

vi /etc/sensors3.conf
Go to the bottom of the file and add:

chip “power_meter-acpi-0”
ignore power1

Now reboot