Незнам длаи сакам линукс :S немам некое добро искуство
Не мислам само да видиш дали проблемот е хардверски или софтверски. Ако линуксот не го дава овој проблем тогаш не е хард дискот. Можеш да пробаш со Убунту life cd
http://www.ubuntu.com/download немора да го инсталираш.
Или...
This is one of the most frustrating error messages you can ever deal with. Sometimes the fix is simple, sometimes it's a complete pain. Having recently dealt with this again, I thought I'd post my thoughts in the hopes that it helps someone else out there.
So you receive the dreaded "a disk read error occurred. Press Ctrl+Alt+Del to restart". Multiple restarts result in the same error message.
If you put your drive into another computer, or connecting it as a slave on your own computer, it will typically work fine, and no data is missing.
Because this error is not usually associated with data loss, DO NOT RE-PARTITION THE DRIVE. Your data is likely safe and sound.
Here's how we'll recover your data. Try each step below, in order, and see if your drive becomes accessible after each step. In my experience, you won't start seeing results until step 5 or so.
1. Run CHKDSK /R /P from the recovery console (it will typically find no error)
2. run FIXBOOT from recovery console (typically has no result)
3. run FIXMBR from recovery console (typically has no result)
4. Run the manufacturer's diagnostic utility, downloaded from their website (it will typically find no error)
5. Changing the drives from cable select to Master/Slave may fix it.
6. Replacing the data cable may fix it, but usually not.
7. Setting the BIOS to use defaults may fix it, but usually not.
8. Changing the BIOS drive settings from auto to user-specified, ensuring that LBA is selected may fix it.
9. Pulling the CMOS battery to let the BIOS lose it settings may work.
At this point, you may be feeling some frustration.
If all that fails, here's what will usually work:
Ghost your data to a new drive, and use the original one as a slave. It will work.
And all of your data will still be accessible. Your computer should boot normally. If it doesn't, or it there are errors, run the Repair Installation option from your Windows boot CD.
But why does this happen? Nobody seems to know why. The problem typically evades all forms of detection.
Here's what I've learned: this error message likely has more to do with a hardware interaction between the drive and your system than any actual issues with the drive. To put it one way, your motherboard and drive are no longer on speaking terms.
I don't know why the original disk has no problems being a slave. Perhaps it got tired of running the show. Perhaps it's preparing for retirement.
in my experience "A disk read error occurred" has nothing to do with the health of HD or damaged file system, but is a comunication error between MOBO - BIOS - PROCESSOR - HD's mbr.
most of the times it's due to a HIGH TEMPERATURE of the CPU, even if transient.
i.e.: during XP (or other O.S.) 1st phase setup a new mbr is written on the hd and. if the mentioned communication error is present, a bad mbr ad a bad partition table will be written, so that after reboot one will receive the mentioned error.
in most cases the high temp is due to a old Thermal paste or a a wrong position of the heatsink
My fix was uber easy.
I opened the back of my PC, I checked the cable going in to my HDD and it felt very firm, didn't feel loose at all. There was lots of dust inside so i cleared that all out. Choaking myself in the process! Then i reattached the cover and rebooted my PC.
It was fixed! That was it, so simple. I believe that there was too much dust clogging up the wrong area of the inside of my PC. So, for anyone with this error, I recommend trying this, check your cables and clean any dust inside before trying more drastic measures such as reformatting or getting new drives etc.
Allright. My computer is working fine now. The only difference between this and my first time installing Win7 (see above) is that I didn't install Comodo Time Machine. And it works. Could be a coincidence, but I, like, got a feeling that it's not. So. A subtle word of warning to those who are going to install CTM.
Please do not immediately resort to hard disk formatting and the like as some of the forum posts that I found through google! In my case I solved the problem by simply changing the SATA cable! Do yourself a favor and go through the less drastic test procedures that some have posted in this thread.
I knew my harddisk should be fine when I saw it listed on the bios post screen so that should be another indicator to watch!
I fixed mine by going to the BIOS, BOOT settings, HARD DISK DRIVES, and switching the order of the drives around - ie. I have a Raid-0 (which was the first in the list) and a Seagate 1TB (which was the second), so I pressed the '+' key which changed their order in the list (Seagate is now first, Raid-0 is now second).
While I was getting the Disk Read Error I could boot from the Vista setup DVD, run Repair, and it would boot,... until I turned the computer off or changed the Boot Disk priority in the BIOS (ie. from Boot first: CD/DVD, Boot second: HDD; to Boot first: HDD, Boot second: none).
But yeah, really odd...