Hard awt problem.

Introduction:
An applet opens a modal java.awt.Dialog. The dialog contains a grid for displaying data. When the dialog is opened a separate thread is fetching data from the server. When the data arrives it is displayed in the grid in the dialog. The grid adds a scrollbar to itself whenever required (if the number of rows to be displayed is greater than the number of rows that fit inside the visible part of the grid).
The code for adding/ removing the scrollbar is in the doLayout() method of the Grid.
Problem:
When I call invalidate() or validate() on the grid in the modal dialog the call hangs until the modal dialog returns from it�s setVisible() method. Why ???! It seems to be impossible to trigger a refresh of the layout of the grid programmatically. If I do not refresh the layout the scrollbar will only get added if I resize the window or in any other way make the system trigger a refresh of the layout. When I use the same Grid in any Container that is not a modal dialog there is no problem at all.
What is the reason for this behavior, and how do I solve the problem?
Ragnvald

Thanks Luke, but that doesn�t work for me.
This is an awt- applet, supposed to run on IE without signing or any additional downloading. That implies java 1.1.8 only. awt and no swing. And all the security restrictions apply as well.
There must be a workaround!!!!
The swing you provided has it�s equivalent in awt://1.1.8:
Toolkit.getDefaultToolkit().getSystemEventQueue().postEvent(event);
//and 1.2:
Toolkit.getEventQueue().postEvent(new InvocationEvent(Toolkit.getDefaultToolkit(), runnable));The problem is the applet restriction. I get an exception:
SecurityException at getSystemEventQueue
There has got to be another solution!
Ragnvald.

Similar Messages

  • 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.

  • Hard drive problem...... Please Help

    Hard drive problems
    I am sure it is due to my error or mistake but I received a new Maxtor III touch as a replacement for my failed drive yesterday after connecting it I went to Maxtor one touch manager software that came with it and the drive did not appear in the window so then I opened disk utilities and copied my notebook hard drive over to the Maxtor ran permissions on each drive and then closed down my system ! today when I opened my Powerbook with the Maxtor on it gave me the grey screen 2x so I disconnected the Maxtor ran permissions again and everything was fine until i power up the Maxtor and Grey screen again! Help How do I fix this?????

    Maxtor one touch III firewire 800 its connected to my Titanium G$ Powerbook I am beginning to think its just another drive failure

  • Computer is balky random freezes across apps. Two hard drive cleans later (their scan reveals no hard drive problems) photo shop won't work at all, magic touch mouse inoperable and their diagnoses is corrupted data? Anybody heard of this?

    Computer is balky random freezes across apps. Two hard drive cleans later (their scan reveals no hard drive problems) photo shop won't work at all, magic touch mouse inoperable and their diagnoses is corrupted data? Anybody heard of this?

    Well, yes, data does get corrupted sometimes.
    The trick is finding what data.
    By 'cleaned' are you therefor meaning that the drive has been erased and the system re-installed?
    Because that's the quickest way to deal with such a situation.
    Back up the system first of course,
    Add back 3rd party apps one at a time in case one of them is causing the problem.

  • I was trying to sync my 120GB iPod Classic earlier and it said it couldn't sync as the iPod disk could not be "read" or "written to". I now can't get anything onto my iPod, and I was wondering if it is a hard drive problem? Any help appreciated. Thanks.

    I was trying to sync my 120GB iPod Classic earlier, and it said it couldn't sync as the iPod disk could not be "read" or "written to." I now can't get anything onto my iPod, and I was wondering if it is a hard drive problem? Any help appreciated. Thanks.

    Did you go into iTunes to change the location of your media files? if not you will need to go into iTunes and click on preference and select the advance tab then click the iTunes Media folder location.  Select the location of your on external hard drive. 

  • Snow Leopard and hard disk problems?

    This may just be a coincidence but I and several colleagues have had problems with Macs over the past week.
    a) My Macbook Pro lost the date/time and wi-fi settings. Next reboot wi-fi was still lost. Now seems OK again.
    b) At times my 24" iMac is running slowly when nothing seems to be hogging resources (eg just copying a 3Gb file to an external hard disk). Time Machine also seems to be taking much longer to backup.
    c) Hard disk failed on a Macbook Pro of a colleague
    d) iMac 27" seems to be having severe hard disk problems for another colleague - Applecare will be visiting after trying numerous fixes over the phone.
    On my machines I have run the Cocktail suite (permissions, scripts and caches) Disk Utility Repair and Techtools Deluxe (no reported problems) but the iMac problems seem to creep back.
    It is like a disk caching process (or Spotlight?) is not cleaning up properly and is clagging up the system. Or maybe a hard disk is close to failure but the problem is not severe enough to show up in diagnostics? In any case I am diligent about backing up at the moment!

    Or maybe a hard disk is close to failure but the problem is not severe enough to show up in diagnostics?
    Common symptoms of a dying hard drive
    Hard drive is making a clicking, whirring, grinding, ping pong ball noise or any other type of unusal noises.
    Hard drive is not spinning.
    Computer is not recognizing the hard drive.
    Sluggish loading of applications.
    System freezes and hangs.
    An interesting site - Hard Drive Sounds by drive manufacturer.
    How much hard drive space do you have left?
    Disk Inventory X
    OmniDiskSweeper
    WhatSize
    SpaceControl
    Disconnect all peripherals from your computer. Boot from your install disc & run _*Repair Disk*_ from the utility menu. To use the Install Mac OS X disc, insert the disc, and restart your computer while holding down the C key as it starts up.
    Select your language.
    Once on the desktop, select Utility in the menu bar.
    Select *Disk Utility.*
    Select the disk or volume in the list of disks and volumes, and then click *First Aid.*
    Click _*Repair Disk.*_
    Restart your computer when done.
    Repair permissions after you reach the desktop-http://docs.info.apple.com/article.html?artnum=25751

  • MBA hard disk problems

    I appear to be having hard disk problems and would appreciate any suggestions as to how to determine what the cause might be.
    It began when the MBA late 2008 with 10.6.6 would not startup, just an endless cog wheel. Using the installation disk I found that the disk repair utility identified that the MBA hard disk was corrupted and the repair utility couldn't repair it.
    I deleted the contents of the MBA disk verified the disk and reinstalled the system software and all my other programmes and files.
    (This took about a day as I did not have a backup of the MBA but I did have the files and programmes on other disks etc. (Never again - I bought an external hard disk so that I could have a copy of the installation disc on it and also a backup of the MBA and all the system software updates.)
    All has been well for a couple of weeks until today when the MBA would not start. For the first time in my life I saw a message covering most of the screen saying "Will not start up - turn the computer off by holding down the power button until it turns off and then restart the computer" or something similar.
    Needless to say the computer refused to restart and again after looking at the MBA disk with the disk utility it required repair and again the repair utility said it could not complete the repair.
    Wiped the MBA disk again and reinstalled and restored the programmes and files. (so much easier with the install image and backup on an external hard disk and Time Machine is tremendous).
    So the MBA appears to be back to normal.
    But will it stop again? It the hard disk flawed or fundamentally corrupted?
    I have verified the hard disk with the apple disk utility and also with onyx. Both say it appears to be ok.
    Any suggestions as to how to work out what if anything is going wrong would be much appreciated.

    When I said verified I meant that I ran the verify and repair command in the apple disk utility and also ran both the smart status in onyx and additionally the verification command in onyx.
    Just to clarify the second occasion that the MBA would not startup falls under the category of “You need to restart your computer” which indicates a indicates a “kernel panic”.

  • Windows has detected a hard disk problem

    I just got a warning from windows that I have a hard disk problem then Toshiba Utility notifies me with the following:
    Disk0
    Your HDD has the SMART Predict Failure function which monitors the HDD operating status. Your HDD is experiencing a problem and SMART monitoring software predicts that the HDD will fail. Toshiba strongly recommends you create a back-up for your HDD data. Then contact an authorized service provider in order to check your drive and purchase a new replacement drive if necessary.
    I have never had problems with a hard disk, all I know is that I should get a backup drive as soon as possible. After I back up my files and everything....what is the next step? Take it to a repair man to fix, get a new harddrive, contact about warranty, what exactly do you do with this kind of situation? Is it fixable?
    System Details:
    Toshiba Satellite L675D-S7052
    Windows 7 Home Premium 64 Bit

    If you're computer is under warranty, you should contact customer support at (800) 457-7777. The hard drive will need to be replaced.
    - Peter

  • Window detected a hard disk Problem on my Satellite L505-S5988

    Hi,
    I have a Toshiba Satellite L505-S5988 with window 7 Home Premium 09 Service pack 1.  It is 2+ years old and my hard drive is Toshiba MK3263GSX 287GB.  Lately, I got a window warning message as “ Windows detected a hard disk Problem.  Back up your files immediately to prevent information loss, and then contact the computer manufacturer to determine if you need to repair or place the disk…..  The following hard disks are reporting failure:  Disk Name: TOSHIBA MK3263GSX Volume: C:\  “. 
    Since then, I have imaged my laptop and run malware/spyware softwares, and it looks like my computer is clean.  The laptop device manager said my hard drive is working properly.  However the warning keeps pops up.  I opened Administrative Event Viewer and found the below warning:
    “Log Name: System,   Source: Disk,    Event ID: 52.
    The driver has detected that device \Device\Harddisk0\DR0 has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent.”
    EventData
    \Device\Harddisk0\DR0
    0E00030001000000000000003400048002000000000000000000000000112
    D000000000000000000000000
    Besides this warning,  there are also other errors and warnings back to years ago, such as AFS failed to load, print service…  Despite all these errors and warnings, my laptop seems to be running OK.  I was not prevented from doing anything that I usually do.
    Questions:
    Is there a tool I can run to verify that my hard drive is truly bad?
    Can any tool further identify where?
    Can it be repaired? Reformat? Or I have to replace with a new one?
    What options I have if I have to replace with a new one?
    What is average cost of it?
    Any help will be highly appreciated.

    Satellite L505-S5988
    Event ID: 52 - Source: Disk
    ..the warning keeps pops up.
    That's good enough for me. I would replace the disk.
    You can verify it with the free trial of HD Tune.
    -Jerry

  • Recurring iMac G5 Hard Disk problem and worthless AppleCare

    Hello all! I have a recurring iMac G5 2Ghz (20-inch) Hard Disk problem.
    I bought my parents, aged 52 and 55, an iMac last summer. Hoping this would be their solution to a hassle free and easy computer environment, since I would leave for China for about 1 year. But last month the hard drisk crashed and could not be fixed.
    At first the start up speed slowed down, then the start up process would continue infinitely, then the computer just booted into a screen with a question mark.
    I have a AppleCare Protection Plan (APP) and so I called the Help Desk and they put me in touch with a Service Center (Sittard, the Netherlands). Now I thought, since I live within the proper range of at least 3 service centers (Heerlen, the Netherlands), I could get on-site support (as stated in APP), unfortunately for unknown reasons, my parents had to drag the 20 inch monster to the service center.
    Normally the repair should take 2 days, but instead it took 10 working days. My dad naturally asked, if they could restore the data on the disk. This was only possible if we paid about 2000 euro. So, no deal!
    After picking the iMac up again, the computer booted into the Mac OS installation. This again surprised me, since according to the APP they should at least put some effort into restoring the applications. Not even iLife was pre-installed, which was of course on the computer when we bought it. Next to that the Service Center's Mac OS installation disc was still in the drive; how careless!
    They were quite sad about the lost data, but accepted it, as we all know that these things can happen to electronics. BUT today, the same problem recurred! First the start up process slowed down and now (again) it tries to start up infinitely.
    The hard disk is brand new (1 month), no strange programs and no abnormal use. According to the diagnostic tools the file structure is damaged, but it seems to keep getting worse. The Apple Help Desk guy was even surprised this happened to a brand new disk and installation. He recommended reinstalling the system.
    But, I'm not happy with this solution! A hard disk breaking down, is one thing. But the same problem recurring 1 month later made a couple of alarm bells go off. I'm hoping Apple will consider replacing this machine from **** with a brand new iMac. Since my parents are scared ********, that whatever document they type today might disappear again tomorrow. This is not a comfortable computing experience.
    By the way: the computer has only basic software: Microsoft Office, Skype and iLife and my parents only use those programs, surf the net and send email.
    Any of you had a similar bad experience with the iMac's hard disk, AppleCare or any of Apple's Service Centers? Or does anyone know how to reach Apple by email?
    iMac 20 G5 2Ghz   Mac OS X (10.4.6)  

    I had a similar problem with my 20" 2Ghz iMac.
    After replacing the HD and the next 'going bad' the tech realized there was a different problem.
    After discussing it, and the distance to an authorized repairer he offered on-site repair.
    After a lengthy parts delay I was offered an upgrade to a iSight iMac.
    The tech narrowed my problem down to a faulty logic board before offering a replacement. He could have been wrong but it seemed logical with all of the same symptoms.
    Press your AppleCare to replace this computer. They are going to try and repair but insist if this fix doesn't work you want a new iMac.
    I hope everything works out for you.
    Edit: There is a great program that Apple techs recommend called DiskWarrior. It did not fix my problem but it allowed me to get my most important info off of the computer before it went to computer heaven. Might not work for all but it works well for me as I still use it today.

  • Hard drive problem with HP Pavillion dv7-4180us

    Hard drive problem with my HP Pavillion dv7-4180us. Using Windows 7.
    Boots up sometimes and very slow.
    Appreciate any help.

    Have you booted into the BIOS or Diagnostics Tool to run the Hard Drive Test?

  • Windows 7 on MacBook Pro Retina late 2013. Showing popup window as "Windows detected a hard disk problem"

    I have installed Windows 7 64 bit version in my MacBook Pro Retina(13") late 2013 model . It was working fine from last 8 months but recently popup window showing as "Windows detected a hard disk problem" once login. Please check the following image.
    I have contacted Apple Support team. They have tested the hard disk while booting from Mac OS and all the reports showing as hard disk is fine. Then I thought might be it was some virus and removed the Bootcamp partition and re-installed Windows 7 Operating System. But once updated Windows 7 with latest updates. This message showing again.
    Would you please help me out to fix this issue. Anybody faced similar issue?

    No I think that all drive are really on failure
    I've boot with an ubuntu livecd and smartmontools see also the failure.
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x001a   200   200   000    Old_age   Always       -       0
      5 Reallocated_Sector_Ct   0x0033   100   100   000    Pre-fail  Always       -       0
      9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1872
    12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       762
    169 Unknown_Attribute       0x0013   253   253   010    Pre-fail  Always       -       4003597393408
    173 Unknown_Attribute       0x0036   100   100   100    Old_age   Always   FAILING_NOW 12124890467160
    174 Unknown_Attribute       0x0022   099   099   000    Old_age   Always       -       7469954
    175 Program_Fail_Count_Chip 0x0022   099   099   000    Old_age   Always       -       4989854
    192 Power-Off_Retract_Count 0x0012   099   099   000    Old_age   Always       -       31
    194 Temperature_Celsius     0x0022   064   064   000    Old_age   Always       -       36 (Min/Max 11/75)
    197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
    199 UDMA_CRC_Error_Count    0x001a   200   199   000    Old_age   Always       -       0
    240 Unknown_SSD_Attribute   0x0022   100   100   000    Old_age   Always       -       0
    When I use the Mac disk tools from the startup menu, it see also the problem.
    Now the big question is : Why I've this type of issue with 2 MBA and 1 Macbook pro 15".
    Their configurations are the same : windows 7 with truecrypt.
    Maybe Windows drastically reduces the lifetime of the Apple SSD drive.
    The 3 Mac are used for less than 6 month !!!!

  • I have lost my info for my ipod due to hard drive problem. Can I upload the info on my ipod to my computer. I don't want to lose what is on my ipod.

    Lost ipod info on computer due to hard drive problem. Can I upload info on ipod back to my computer and how do i do it.

    - Transfer iTunes purchases by:
    iTunes Store: Transferring purchases from your iPhone, iPad, or iPod to a computer
    - Transfer othe music by using a third-party program like one of those discussed here:
    Best iPod to PC
    - Create a backup of the iPod by connecting the iPod to the computer.  Right click on the iPod under Devices in iTunes and select Back Up.
    - Restore the iPod from thzt backup and sync a necessary.

  • Restoring iTunes files after hard drive problems

    HI.
    I recently had hard drive problems and since the recovery of the data I have lost all my files from iTunes. The sogs I have put on to the Mac via CD's are all still there but all the iTunes downloads have disapeared. This is probably because I didn't back up!
    I also have numerous duplications, which I eventually removed from itunes but I know the majority of which will return if I drag my music folder across.
    This will be a hige taks again to remove the duplications.
    I want to use this unfortunate incident to my advantage though and now have a clear out of my unwanted files and keep my iTunes nicely organised.
    I also lost my playlists, which is a major pain.
    By looking at the support threads it seems that I can use my ipod to put my library back as it should be. Will this also replace my downloaded songs? My other issue is that some of my iTunes downloads, downloaded with some problems, which are obviously on my ipod. How do I go about getting the songs repaired?
    Thanks for any help.

    [Zevoneer's detailed instructions on getting music off an iPod|http://discussions.apple.com/message.jspa?messageID=9053179#9053179]
    [Wired's How To: Get Your Music Off of Your iPod|http://howto.wired.com/wiki/GetYour_Music_Off_of_YouriPod]
    [http://www.metaphoriclabs.com/articles/5-ways-to-copy-music-off-your-ipod-windo ws-mac-os-x>
    I imagine if the files exist on the ipod you can get them transferred over. if they don't exist, they are gone.
    As for the corrupt files you would need to provide more information on the issues.

  • MacBook Hard Drive Problems?

    I've used this MacBook for a few years without any issues. It has always had very snappy response and very few problems. Earlier this week, I noticed that it takes about 4 minutes to boot up now as opposed to the 30 seconds it used to take just a week ago. Once running, Safari also tends to be unresponsive at times and slow to load. Upon closer inspection, I noticed that during boot up, I can HEAR the hard drive give off some "clicks" and faint "beeps" (for lack of a more technical description). In my experience with Windows machines, this is often a sign of hard drive problems.
    With Vista, I can run a CHKDSK and fix the drive by taking the bad sectors out of the mix. I am trying to figure out how to best diagnose and repair my drive on this Mac. I tried booting from the Snow Leopard DVD and running Disk Utility/First Aid to find the problem, but this utility reports that everything is fine and dandy. I am not sure I agree.
    Can someone tell me of a more powerful tool for the Mac that will fully diagnose any hardware or software problems on this machine so I can get it back to tip top performance. Is there a diagnostic utility provided by Apple? Other utilities built in to Snow Leopard? Third party applications?
    As I have never had problems with a Mac before, I am in uncharted waters with regard to diagnostics so if anyone can help, I would greatly appreciate it.
    Thanks!

    domtrump wrote:
    In addition to OSX (Leopard) I have two (2) "MacBook Mac OSX Install" discs. Does anyone know which one is bootable and contains the AHT utility?
    You have to determine what version of Leopard shipped with your Mac. It might say on the disk. If not, put in the leopard disk and see which version it is. As stated in the link I gave you.........
    For Intel-based Apple computers shipping with Mac OS X v10.5.4 or earlier, Apple Hardware Test is located on the Mac OS X Install Disc 1 and should be included with your computer.
    For Intel-based Apple computers shipping with Mac OS X v10.5.5 or later, Apple Hardware Test is located on the Applications Install Disc 2 and should be included with your computer.
    Here's another AHT faq.
    DALE

Maybe you are looking for