От 8-9 месеца имам едно лаптопче 
Acer Aspire 4810TZ Моят модел дойде с Windows 7 Home edition, 4GB ram и 500GB диск. Естествено веднага след като го взех преоразмерих партишъните качих си Windows 7 Umtimate след което си качих и Kubuntu lucid на който съм работил през 98% от времето. Преди около седмица ми се наложи да си пусна windows-а при което той почна да пищи че диска имал проблеми и трябвало да съм започнел незабавна процедура по backup и перформънса му беше ужасен. Отварянето на браузър ми костваше по 3-4 минути. В същото време Kubuntu-то си ми работи на пушка, затова реших че проблема е в OS-а и го рестартирах. След рестарта windows-а почна да си прави чекове на C-то като откриваше една камара грешки, които уж отстраняваше. След като се рестартира чека почваше наново. Повторих тази процедура 3-4 пъти след което ми писна и му казах на Windows-а да се стартира без да прави проверка. Производителността беше кошмар, като и на всичкото отгоре ми се бяха изтрили половината файлове на firefox и разни други приложения.  Заради всички тези проблеми реших че проблема е в OS-а на Гейтс затова му 
преформатирах партишъните с ext4 и го разкарах (ако някой иска да види как съм го направил може да кликне на линка).
Качих си на Kubuntu-то един Vmware workstation с помощта на който на стария С дял си инсталирах една виртуална машина с Windows 7. Инсталацията мина нормално за около 30-40 минути. Обаче когато почнах да си качвам приложения във виртуалния windows load-а на компютъра ми варираше между 15 и 20, vware-а взе да реве че не може да достъпва някакъв файл и dmesg почна да бълва ето такива съобщения:
[62164.042854] ata2.00: status: { DRDY ERR }
[62164.042857] ata2.00: error: { UNC }
[62164.120184] ata2.00: configured for UDMA/100
[62164.120196] ata2: EH complete
[62167.987578] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[62167.987584] ata2.00: irq_stat 0x40000001
[62167.987589] ata2.00: failed command: READ DMA
[62167.987599] ata2.00: cmd c8/00:08:c0:b0:ac/00:00:00:00:00/e0 tag 0 dma 4096 in
[62167.987600]          res 51/40:04:c4:b0:ac/00:00:00:00:00/e0 Emask 0x9 (media error)
[62167.987605] ata2.00: status: { DRDY ERR }
[62167.987609] ata2.00: error: { UNC }
[62168.064939] ata2.00: configured for UDMA/100
[62168.064951] ata2: EH complete
[62171.932417] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[62171.932424] ata2.00: irq_stat 0x40000001
[62171.932429] ata2.00: failed command: READ DMA
[62171.932438] ata2.00: cmd c8/00:08:c0:b0:ac/00:00:00:00:00/e0 tag 0 dma 4096 in
[62171.932440]          res 51/40:04:c4:b0:ac/00:00:00:00:00/e0 Emask 0x9 (media error)
[62171.932445] ata2.00: status: { DRDY ERR }
[62171.932448] ata2.00: error: { UNC }
[62172.009751] ata2.00: configured for UDMA/100
[62172.009763] ata2: EH complete
[62175.877159] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[62175.877166] ata2.00: irq_stat 0x40000001
[62175.877171] ata2.00: failed command: READ DMA
[62175.877180] ata2.00: cmd c8/00:08:c0:b0:ac/00:00:00:00:00/e0 tag 0 dma 4096 in
[62175.877182]          res 51/40:04:c4:b0:ac/00:00:00:00:00/e0 Emask 0x9 (media error)
[62175.877187] ata2.00: status: { DRDY ERR }
[62175.877190] ata2.00: error: { UNC }
[62175.954670] ata2.00: configured for UDMA/100
[62175.954682] ata2: EH complete
[62179.821917] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[62179.821924] ata2.00: irq_stat 0x40000001
[62179.821930] ata2.00: failed command: READ DMA
[62179.821939] ata2.00: cmd c8/00:08:c0:b0:ac/00:00:00:00:00/e0 tag 0 dma 4096 in
[62179.821941]          res 51/40:04:c4:b0:ac/00:00:00:00:00/e0 Emask 0x9 (media error)
[62179.821945] ata2.00: status: { DRDY ERR }
[62179.821949] ata2.00: error: { UNC }
[62179.899262] ata2.00: configured for UDMA/100
[62179.899278] sd 1:0:0:0: [sda] Unhandled sense code
[62179.899281] sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[62179.899287] sd 1:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
[62179.899294] Descriptor sense data with sense descriptors (in hex):
[62179.899297]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
[62179.899312]         00 ac b0 c4 
[62179.899318] sd 1:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[62179.899325] sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 ac b0 c0 00 00 08 00
[62179.899338] end_request: I/O error, dev sda, sector 11317444
Спрях виртуалната машина load-а падна след което направих и ето тези тестове:
root@abadon:/home/genko# smartctl -d ata -l selftest /dev/sda
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: unknown failure    90%      5122         -
# 2  Extended offline    Completed: unknown failure    90%      5119         -
# 3  Extended offline    Completed: unknown failure    90%      5117         -
# 4  Extended offline    Completed: unknown failure    90%      5117         -
root@abadon:/home/genko#  smartctl -d ata -l error /dev/sda
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 6734 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 6734 occurred at disk power-on lifetime: 5119 hours (213 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 02 c1 08 ad 60
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 c0 08 ad 40 08   1d+15:38:29.147  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00   1d+15:38:29.147  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00   1d+15:38:29.147  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+15:38:29.146  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00   1d+15:38:29.146  SET FEATURES [Set transfer mode]
Error 6733 occurred at disk power-on lifetime: 5119 hours (213 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 02 c1 08 ad 60
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 c0 08 ad 40 08   1d+15:38:25.202  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00   1d+15:38:25.202  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00   1d+15:38:25.202  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+15:38:25.201  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00   1d+15:38:25.201  SET FEATURES [Set transfer mode]
Error 6732 occurred at disk power-on lifetime: 5119 hours (213 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 02 c1 08 ad 60
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 c0 08 ad 40 08   1d+15:38:21.258  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00   1d+15:38:21.258  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00   1d+15:38:21.257  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+15:38:21.257  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00   1d+15:38:21.257  SET FEATURES [Set transfer mode]
Error 6731 occurred at disk power-on lifetime: 5119 hours (213 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 02 c1 08 ad 60
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 c0 08 ad 40 08   1d+15:38:17.313  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00   1d+15:38:17.313  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00   1d+15:38:17.313  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+15:38:17.312  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00   1d+15:38:17.312  SET FEATURES [Set transfer mode]
Error 6730 occurred at disk power-on lifetime: 5119 hours (213 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 02 c1 08 ad 60
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 c0 08 ad 40 08   1d+15:38:13.368  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00   1d+15:38:13.368  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00   1d+15:38:13.368  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+15:38:13.367  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00   1d+15:38:13.367  SET FEATURES [Set transfer mode]
Въпроса ми е това хардуерен проблем ли е или е някаква моя грешна конфигурация? В момента като си работя само на Kubuntu-то нямам никакви други проблеми.
Предварително благодаря!