Click of death hard disk T430 Linux

Hello,
I have a T430 with Fedora 18 and a HITACHI HTS725050A7E630 (firmware version GH2ZB390).
I listened a continuos "click" when i didnt use the hard drive so i use smartctl and i detected that the Load_Cycle_Count grow up after each click. So i use hdparm and disabled the hard drive spindown and the click disappeared. But it's possibile to update harddrive's firmware to support spindown under linux? because the hard drive consume many Watt and the autonomy is very small... (i try to disable the active shock protection under windows but nothing happens..)

UP

Similar Messages

  • Clicking noise from hard disk

    Hello forum,
    one more hard disk noise problem. My new MPB arrived two days ago and I immediately noticed a clicking noise that is presumably emitted by the hard disk. I've got the basic 250GB model, so it's unrelated to the 500GB noise. The sound occurs quite regularly every 20sec or so, but only when the disk is inactive. The system doesn't freeze. The noise appears regardless whether the disk power saving feature is enabled or not. Here is an amplified version of the sound without the normal background noise (fan, hard disk):
    http://www.filefactory.com/file/ah25f1h/n/ClickingNoise_wav
    I've learned that clicking noises are a certain sign of hard disk failure. So should I return it immediately and ask for a replacement?
    Regards

    MKG4 wrote:
    It sounds like you've got two clicking noises happening back to back, correct? I have the new 250GB drive as well (5400 RPM) and I'm hearing a periodic click similar to the second one in your clip.
    I can hear only the second click, too. Only if I mute the background noise and amplify my recording, I hear the first one. Could you perhaps take a record of the sound that your MBP makes so that we can compare the sounds?
    Haven't noticed any other problems with the drive, though. Is yours a Fujitsu? Mine is, and according to their web site, "if the drive is idle it will automatically move the heads periodically to prevent lubricant migration." I'm wondering if that's what the noise is.
    Interesting. Mine is a Fujitsu, too, and perhaps the two noises come from the disk head starting and parking.
    Actually, it sounds a lot like the 500GB noise, except without the beep. I've seen very few, if any, issues with the 250GB drive, but I'm holding out hope that a fix may come along at some point.
    I agree. Currently the sound doesn't seem to be harmful, but one never knows.

  • Need your guidance for format and mount the hard disk in linux

    Hi All,
    I presented 100GB in server (RHEL5.6) through SAN. Now I can able to see the hard disk,
    Disk /dev/sda: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/sda doesn't contain a valid partition table
    Disk /dev/sdb: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/sdb doesn't contain a valid partition table
    Disk /dev/sdc: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/sdc doesn't contain a valid partition table
    Disk /dev/sdd: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/sdd doesn't contain a valid partition table
    Disk /dev/sde: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/sde doesn't contain a valid partition table
    Disk /dev/sdf: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/sdf doesn't contain a valid partition table
    Disk /dev/sdg: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk /dev/sdg doesn't contain a valid partition table
    Now how to configure the multipath and how to use this allocated space.
    Kindly guide me.
    Thanks,
    Muthu

    Linux DM multipath determines whether or not discovered devices are individual devices or whether they are separate paths to one and the same device. This is accomplished by querying the device serial number. To install and configure multipath, please see the DM Multipath Guide available for your OS version installed: https://linux.oracle.com/documentation/.
    If you need more help and examples, check the following thread: multipath -ll command doesn't give any output
    I'm afraid no one can answer your question how to partition and mount your storage space without you giving any information about its purpose.

  • I am deleting files through my trash in my macbook pro (2010) and then emptying the trash can, but my hard disk space is not increasing! i recently upgraded to lion and the problem is new, wasn't the same with snow leopard! HELP!!!!!

    i am deleting files through my trash in my macbook pro (2010) and then emptying the trash can, but my hard disk space is not increasing! i recently upgraded to lion and the problem is new, wasn't the same with snow leopard! HELP!!!!!
    When i press command+I (Get Info) i see that there is 140 GB "Available Space" on my hard disk but when i click on my hard disk icon on the desktop, and then press "space" i only see 102 GB free!! What the f*???
    Please HELP!!!!!! Getting second thoughts on Lion!!!!

    Hi b,
    Have you restarted yet?

  • G570: CD/DVD and Hard Disk drives not recognized

    I have a Lenovo G570 laptop. It used to run fine until it started taking longer and longer boot into windows. Soon the computer would not boot into windows and instead try to repair windows, which would finish but never actually repair the computer. Soon after that the CD/DVD drive dissapeard from the BIOS, and it hasn't been able to do anything with a CD except for twirl it around (but not let it read any of that beautiful data.) Soon after this the hard disk was no longer recognized. I have been able ot get the computer to boot off of a linux live flash drive, but that's only a temporary fix. I wasn't able to reach any hard disks thorugh linux to back up files, and the CD drive wasn't recognized either. How can I fix this? Thank you for reading this.

    hi argiflex,
    Welcome to the Lenovo Forums.
    AFAIK, if the HDD/ODD isn't recognized under BIOS then it's a sign that the device is already failing and needs to be replaced.  You can try using a 2.5" SATA Enclosure to read the drive via the USB port on the G570 or on another PC but if the problem remains then you may need to replace the drive.
    If the data on the HDD is very important, you can opt to send the HDD to a professional data recovery firm (i.e. DriveSavers) to recover the data.
    Regards
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • How to make the hard disk visible in a new admin account?

    I created a new admin account, in order (hopefully) to solve some problems that I've been having with SPSS21 for Mac.  But when I log on as a new admin account, my hard disk no longer appears on the desktop.  It (and all the folders and files in it) are still accessible by clicking on the hard disk in the path bar in a folder, but it's annoying not to have the icon on the hard disk.  I don't know why the icon for the hard disk does not appear on the desktop.  Does anyone know why, and how to make it appear?  Thanks.

    Oh, my god!  I'm so embarrassed that I couldn't figure this out myself, after being a devoted Mac user for three decades!  It's so obvious!  Thank you so much!

  • Lenovo E530c hard disk trouble with Linux

    Hi,
    I've got Lenovo E530c with dual boot Windows7/Ubuntu 14.04 x64 and when i'm working on Linux hard disk becomes noisy and performance is worse 20-30% compared to windows. When i switch to windows everything is back to normal silent mode. Anyone have any idea what is the cause of this behaviour and how can I fix it?

    @ All,
    the official forum language is English. It is understood that for clarity a member may wish to post in another language. In such circumstances it would be appreciated if a translation be included, translate.google.com may be usefull in such circumstances.
    Thanks in advance
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • System freezes due to hard disk problems only on Linux (not windows)

    Intro/context:
    Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
    I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
    tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
    What i've done so far:
    The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
    I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
    Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
    I found no firmware update for this hard drive.
    So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
    Info:
    Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
    Some logs i've recollected all this time:
    journalctl -xfa --system
    abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
    abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
    abr 21 13:51:24 echoes kernel: ata1: hard resetting link
    abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 13:51:24 echoes kernel: ata1: EH complete
    abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
    res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
    abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
    abr 21 14:02:01 echoes kernel: ata1: hard resetting link
    abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
    abr 21 14:02:01 echoes kernel: ata1: EH complete
    abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
    dmesg
    [55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
    [55661.023034] ata1.00: failed command: READ FPDMA QUEUED
    [55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [55661.023042] ata1.00: status: { DRDY }
    [55661.023046] ata1: hard resetting link
    [55666.358537] ata1: link is slow to respond, please be patient (ready=0)
    [55671.053813] ata1: COMRESET failed (errno=-16)
    [55671.053819] ata1: hard resetting link
    [55676.389438] ata1: link is slow to respond, please be patient (ready=0)
    [55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [55681.320305] ata1.00: configured for UDMA/100
    [55681.320319] ata1.00: device reported invalid CHS sector 0
    [55681.320349] ata1: EH complete
    [55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
    [55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
    dmesg
    [102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
    [102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
    [102884.890333] systemd[1]: systemd-journald.service failed.
    [102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
    [102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
    [104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
    [104179.117369] ata1.00: failed command: READ FPDMA QUEUED
    [104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [104179.117377] ata1.00: status: { DRDY }
    [104179.117381] ata1: hard resetting link
    [104184.453382] ata1: link is slow to respond, please be patient (ready=0)
    [104189.149114] ata1: COMRESET failed (errno=-16)
    [104189.149121] ata1: hard resetting link
    [104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [104189.952982] ata1.00: configured for UDMA/100
    [104189.952989] ata1.00: device reported invalid CHS sector 0
    [104189.953004] ata1: EH complete
    [104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    [104508.223798] ata1.00: failed command: SMART
    [104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [104508.223806] ata1.00: status: { DRDY }
    [104508.223810] ata1: hard resetting link
    [104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [104510.698126] ata1.00: configured for UDMA/100
    [104510.698157] ata1: EH complete
    One of the latest and worse
    journalctl -xfa --system
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
    res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
    res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
    abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
    abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
    abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
    abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
    abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
    abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
    abr 22 12:57:11 echoes kernel: ata1: EH complete
    abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
    abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
    abr 22 12:57:11 echoes kernel: ata1: hard resetting link
    abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
    abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
    abr 22 12:57:11 echoes kernel: ata1: EH complete
    Current smart status:
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: Toshiba 2.5" HDD MQ01ABD...
    Device Model: TOSHIBA MQ01ABD100
    Serial Number: Y44MT611T
    LU WWN Device Id: 5 000039 5e1a80e85
    Firmware Version: AX1P5E
    User Capacity: 1,000,204,886,016 bytes [1.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5400 rpm
    Form Factor: 2.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA8-ACS (minor revision not indicated)
    SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Sun May 3 16:42:06 2015 ART
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x82) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection: Enabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 120) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 234) minutes.
    SCT capabilities: (0x003d) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
    5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
    7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
    10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
    193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
    194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
    196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
    197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
    220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
    222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
    223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
    226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
    240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
    SMART Error Log Version: 1
    No Errors Logged
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Vendor (0x50) Completed without error 00% 611 -
    # 2 Short offline Completed without error 00% 611 -
    # 3 Short offline Completed without error 00% 597 -
    # 4 Vendor (0x50) Completed without error 00% 583 -
    # 5 Short offline Completed without error 00% 583 -
    # 6 Vendor (0x50) Completed without error 00% 575 -
    # 7 Short offline Completed without error 00% 575 -
    # 8 Short offline Completed without error 00% 547 -
    # 9 Extended offline Completed without error 00% 529 -
    #10 Short offline Completed without error 00% 355 -
    #11 Short offline Completed without error 00% 355 -
    #12 Extended offline Aborted by host 70% 355 -
    #13 Short offline Completed without error 00% 319 -
    #14 Vendor (0x50) Completed without error 00% 13 -
    #15 Short offline Completed without error 00% 13 -
    #16 Short offline Completed without error 00% 12 -
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
    Last edited by jesu (2015-05-03 19:42:53)

    Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
    Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
    $ lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 931,5G 0 disk
    ├─sda1 8:1 0 1000M 0 part
    ├─sda2 8:2 0 260M 0 part /boot
    ├─sda3 8:3 0 207,7G 0 part
    ├─sda4 8:4 0 25G 0 part
    ├─sda5 8:5 0 14,8G 0 part
    ├─sda6 8:6 0 80,5G 0 part /
    ├─sda8 8:8 0 599G 0 part /home
    └─sda9 8:9 0 2G 0 part [SWAP]
    So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
    Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
    Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
    dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
    [ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
    [ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
    [ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 653.821735] ata1.00: status: { DRDY }
    [ 653.821739] ata1: hard resetting link
    [ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
    [ 663.851604] ata1: COMRESET failed (errno=-16)
    [ 663.851610] ata1: hard resetting link
    [ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
    [ 673.881456] ata1: COMRESET failed (errno=-16)
    [ 673.881462] ata1: hard resetting link
    [ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
    [ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 703.012578] ata1.00: configured for UDMA/100
    [ 703.012584] ata1.00: device reported invalid CHS sector 0
    [ 703.012599] ata1: EH complete
    [ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
    [ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
    [ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
    [ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
    [ 742.443506] Buffer I/O error on device sda8, logical block 9323208
    [ 742.443508] Buffer I/O error on device sda8, logical block 9323209
    [ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
    [ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
    [ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
    [ 742.443524] Buffer I/O error on device sda8, logical block 9323216
    [ 742.443526] Buffer I/O error on device sda8, logical block 9323217
    [ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
    [ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
    [ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
    [ 742.443540] Buffer I/O error on device sda8, logical block 9323226
    [ 742.443542] Buffer I/O error on device sda8, logical block 9323227
    [ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
    [ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
    [ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
    [ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
    [ 742.443555] Buffer I/O error on device sda8, logical block 9323234
    [ 742.443557] Buffer I/O error on device sda8, logical block 9323235
    [ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
    [ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
    [ 756.188116] systemd[1]: systemd-journald.service failed.
    [ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
    [ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
    [ 756.189143] systemd[1]: Listening on Journal Audit Socket.
    [ 756.189801] systemd[1]: Starting Journal Service...
    [ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
    [ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 758.503041] systemd[1]: Started Journal Service.
    [ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
    [ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
    [ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867747] ata1.00: status: { DRDY }
    [ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867763] ata1.00: status: { DRDY }
    [ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867778] ata1.00: status: { DRDY }
    [ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
    res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867793] ata1.00: status: { DRDY }
    [ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
    res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867807] ata1.00: status: { DRDY }
    [ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867821] ata1.00: status: { DRDY }
    [ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
    [ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
    res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [ 974.867835] ata1.00: status: { DRDY }
    [ 974.867841] ata1: hard resetting link
    [ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
    [ 984.900902] ata1: COMRESET failed (errno=-16)
    [ 984.900908] ata1: hard resetting link
    [ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
    [ 994.930829] ata1: COMRESET failed (errno=-16)
    [ 994.930836] ata1: hard resetting link
    [ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 997.014012] ata1.00: configured for UDMA/100
    [ 997.014020] ata1.00: device reported invalid CHS sector 0
    [ 997.014023] ata1.00: device reported invalid CHS sector 0
    [ 997.014025] ata1.00: device reported invalid CHS sector 0
    [ 997.014026] ata1.00: device reported invalid CHS sector 0
    [ 997.014028] ata1.00: device reported invalid CHS sector 0
    [ 997.014030] ata1.00: device reported invalid CHS sector 0
    [ 997.014031] ata1.00: device reported invalid CHS sector 0
    [ 997.014065] ata1: EH complete
    There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
    root and home partitions are both ext4.

  • HP Pavilion g4 2131tx, Hard Disk Error after Blue Screen of Death

    Hello! I do not know what section shoud i post this problem, I apologize for it.
    So my laptop is freezing for a days after BSOD. When I leave my laptop overnight for downloading torrents, I always receive the message "Windows has recovered from unexpected shutdown." when i woke up.
    I already disabled all non-microsoft services, start up items and yet the desktop is still freezing right after the welcome screen but the welcome screen does not load too long.
    The desktop freeze for more than a minute then it will go back to normal again until my laptop went to BSOD
    and received this error from UEFI "Hard Disk Error." after restarting.
    I ran the Hardware Diagnostic Test and I got the result:
    Failure ID: RW042K-6MT6RP-MFPX1F-61BK03
    Product ID: 65H69PA#UUF
    I tried cleaning up registry and defragmenting disk and still no luck.
    * My laptop is HP Pavilion g4 2131tx and still under warranty until June 2014.
    * I am using Windows 7 Ultimate 64bit Service Pack 1
    * My RAM is 4gb with a processor of Intel Core i7
    * My AV is microsoft security essentials
    * I am using Advanced SystemCare for cleaning up registry and defragmenting.
    I was wondering if I could change my hard disk while it's still under warranty.
    Thanks for your help!
    #Edit: bad english >.<
    This question was solved.
    View Solution.

    Here is the Service Manual:
    Manual
    See Page 39. It can take any 2.5 inch wide 9mm thick laptop SATA hard drive. They are industry standard, interchangeable.
    Here is one I would recommend:
    http://www.newegg.com/Product/Product.aspx?Item=9S​IA2W00YW3532
    This is a nice compromise with size, speed and expense. You could install an SSD for maximum speed. Post back if you need help with software or anything else.
    If this is "the Answer" please click "Accept as Solution" to help others find it.

  • Access external USB hard disk drive with REISERFS Linux filesystem.

    I recently bought second-hand an older MBP Pro (2006 model) with Tiger installed, which I use as a desktop system at home and I would like to be able to connect an external IOMEGA 500 GB hard disk drive to it and have read/write access to its contents (mostly video / picture / music files). I spent a while searching on the Internet for solutions - nothing usefule came up. Does anyone in here have any ideas on how to do this? Is it possible at all after all?
    P.S.: Apart from this older MBP Pro, I also have a newer model (bought in early 2008) with Leopard installed - I wouldn't mind finding some solution on my problem on that OS instead...

    Hi,
    The two ways I can see to possibly do it are to network the Linux machine & Drive, then use Samba to access it.
    By using the Mac OS X Virtual File System (VFS) capability and writing kernel extensions, you can add support for other file systems. Examples of file systems that are not currently supported in Mac OS X but that you may wish to add to the system include the Andrew file system (AFS) and the Reiser file system (ReiserFS). If you want to support a new volume format or networking protocol, you’ll need to write a file-system kernel extension.
    http://developer.apple.com/documentation/Darwin/Conceptual/KernelProgramming/Fil esystem/chapter12_section1.html

  • Save the contents into hard disk on click of Save As button in Swing

    Hi,
    I have a JButton "Save As". On clicking the button, the contents in the JTextArea should be saved in the local hard disk by opening a Save As dialog box and allowing the user to save in any location.
    Is it possible to do this? If so, please inform me how it could be done.

    Hi,
    Please find the code below.
    try{
    File f = new File("Out.txt");
    FileInputStream fis = new FileInputStream(f);
    BufferedInputStream bis = new BufferedInputStream(fis); DataInputStream dis = new DataInputStream(bis); String stb = null;
    JDialog w = null;
    stb = new String();
    stb = dis.readLine();
    if(stb != null){
    w = new JDialog();
    final Container c = w.getContentPane();
    c.setLayout(null);
    w.setContentPane(c);
    w.setResizable(true);
    w.setTitle("Log Window");
    w.setSize(330,500);
    final JTextArea jt = new JTextArea();
    JScrollPane jsp = new JScrollPane(jt);
    jt.setLineWrap(true);
    jt.setText("Records not available for the id's"+"\n"+stb);
    jt.setBounds(10,10,285,500);
    final JButton jbSave = new JButton("Save File As");
    JPanel spacer = new JPanel();
    spacer.setMinimumSize(new Dimension(50, 18));
    spacer.setPreferredSize(new Dimension(50, 18));
    JPanel jpButtons = new JPanel();
    jpButtons.add(jbSave);
    jpButtons.add(spacer);
    jpButtons.setBorder(BorderFactory.createEtchedBorder());
    JScrollPane scroll = new JScrollPane();
    c.setLayout(new BorderLayout());
    c.add(jt,BorderLayout.CENTER);
    c.add(jpButtons, BorderLayout.SOUTH);
    jbSave.addActionListener(new ActionListener()
    public void actionPerformed(ActionEvent e)
    JFileChooser fileChooser = new JFileChooser();
    int userOption = fileChooser.showSaveDialog(null);
    if(userOption == JFileChooser.APPROVE_OPTION)
    //*******************STATEMENTS TO BE ADDD****************** }
    jt.getText()-----This is how I can get the contents from JTextArea.
    But how I can save the contents. i.e on click of Save As button, Save dialog box opens, and I can choose the location and give the name. but if I go to the location I don't find the file....
    Please guide me to finish this....
    Thanks in Advance.....

  • Clicking/tickling sound from hard disk

    my macbook pro is making a slight, low tickling sound from right side of trackpad, probably the hard disk. this freaked me out, should I be worried ? I heard it on other laptops, but it's getting really frequent today, is it faulty ?
    Message was edited by: phantom 3444

    I've got a new Macbook Pro 13" for less than 2 weeks. After a few days of the 1st week, i noticed the "click" sound (occurs every 30 second) from the bottom right of the MBP. I thought it's hard disk problem hence i call Apple and sent it to the authorized repair center. They checked and they ordered a hard disk replacement (not sure if they agree if it's a hard disk failure). I've waited for a week but was impatient, so i decided to get a new Western Digital 500gb 5400RPM HDD and the MBP back without the replacement hdd from Apple.
    The result, no sound during installation of Snow Leopard but after using it for one day, the click sound came back. I'm pretty sure it's not a hard disk faulty issue. Can anyone advise on how to solve this ? I've read that it may be due to the hdapm issue, but does anyone notice this problem too ? Thanks.

  • Scary clicks... pending hard disk failure?

    This morning, our iMac would not boot. After turning it on, I heard a series of three clicks (as if it was trying to start spinning something), and then appeared a screen with a blinking lightgrey folder icon.
    I inserted the Install CD and did a hardware test, which did not detect any problem. After this, the computer booted again. While I was logged, I used the Disk Utility to verify the disk, again no problem. I switched the computer off.
    Later, when I turned it on, the same problem happened: a series of three clicks followed by a blinking folder icon. I booted from Install CD and canceled the installation process. After this, the computer booted from the hard drive normally.
    Next, I came back to the computer (I had not shut it down) and logged in. At that point, I heard the now infamous clicks again.
    I am predicting that the hard disk is about to fail. Is this indeed the case? Or would it be some other component? Is there some utility that I could use to detect what is wrong?
    Thanks for your help.
    Best,
    David.
    --

    Well, as other posters here have noted, your internal drive is failing but I can't see why you can't select an external for boot up without the internal trying to mount afterwards. That part sounds like maybe the System software somehow got corrupted while the internal was in the process of failing. If you can't boot up into the external drive cleanly next time, maybe you should consider doing an archive and install of your system software to clean things up. Painful thought, I know but besides chewing up some of your time I don't see how it could hurt and it just may solve the problem. There IS, after all, a long weekend coming up
    Rick

  • Hp dv6 2137-el --a strange click from hard disk

    Hi everybody , sorry for my bad english , i need help.
    March 13 I bought an HP 2137-el DV6 the hard drive makes a sound like a click, usually discontinuous.
    I went by the seller and pointed out the problem give me a new one, now with the new PC I have the same problems.
    I'm wondering if the click is something normal, can anyone answer me?
    my fear is that it is a symptom of a defective hard drive, but it seems strange that both the 2 new pc it occurred the same problem.
    Help!!

    MY HARD DISK IS WD6400BEVT (WD SCORPIO BLUE)

  • Installing Oracle Linux on external hard-disk or DVD

    Hi All,
    Is it possible to install Oracle Enterprise Linux on external hard-disk or DVD?
    I already have Windows 7 and want to install Oracle Enterprise Linux either in dual-boot mode or on external hard-disk/DVD. I want to install Oracle E-Business Suite on Linux.
    Can you also let me know the minimum RAM capacity required for running Oracle E-Business Suite R12 on Oracle Enterprise Linux?
    Pointers and workarounds are highly appreciated.
    Regards,
    Kashif

    It's technically possible, but why bother? Since you are asking this question you will very likely run into more trouble with such a setup. In addition, Oracle Enterprise Linux is designed for server hardware and will give you additional trouble if you install it on a desktop or laptop computer.
    I would recommend to you to install Oracle Virtualbox and install OEL as a guest OS and run Linux side by side with your Windows system. There is plenty of information for this task on the web. For the latest version and info on Virtualbox see http://www.virtualbox.org/
    System and hardware requirements for Oracle e-suite will be a different questions, for which you might find answers here:
    http://download.oracle.com/docs/html/B15721_03/inst_req.htm
    Edited by: Dude on Apr 3, 2011 5:55 AM

Maybe you are looking for