Brand new SATA3 disk gives errors on install

[colin-adams]

I have a 4-yearold SATA2 motherboard and disk. The disk failed, so yesterday I ordered a new (SATA 3) disk. Today it arrived, and I tried installing to it from a live USB (64-bit) boot. I have tried both without and with jumpering to limit the transfer rate to 3 gbps. No difference (so I guess the jumper isn't needed).

The install goes fine until the compulsory reboot. The post-install graphical procedures seem to hang. Ctrl-alt-F2 gets me to a console, where I see lots of errors like:

(I'm copying the messages I see on the console, so I may not get it 100% accurate):

ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: BMDMA stat 0x25
ata3.00: failed command: READ DMA EXT
ata3.00 cmd 25/00:08:f8:95:c7/00:00:e2:00:00/e0 tag 0 dma 4096 in
res 51/40:08:f8:95:c7/40:00:e2:00:00/e0 Emask 0x9 (media error) (some lines have Emaek 0x1 (device error))
ata3.00: status: {DRDY ERR }
ata3.00: error: { UNC }
end_request: I/O error, dev sda, sector 3804730872


Is there anything I can do (like mapping out bad sectors somehow??? - I'm not sure I know what I'm talking about), or do I have to try and get a replacement?

Thank you.

---------- Post added at 05:28 AM ---------- Previous post was at 05:26 AM ----------

P.S. After a while, the errors stop coming out, and I can login on a tty console. And I can do telinit 3 and work OK (as far as I've tried), but if I go telinit 5, then the errors appear again (for a few minutes). Which makes me think it's just one or two bad sectors that need mapping out.

[Seve]

First, check and see if thetr is a BIOS upgrade for your MB, if so, consider flashing it to the latest release.

If not, check your BIOS settings to see if they make sense?

At the very least, reset your BIOS and boot fresh, then make any BIOS adjustments that you do, and see how that works.

[george_toolan]

Please try a different sata cable.

What kind of motherboard or sata host adapter is this?

Can you try a different sata host adapter or computer to rule out any incompatibilities?

What kind of drive is this? On a 2 TB drive this sector would be near the end of the capacity.

Try to read the smart values from the drive

smartctl -a /dev/sda

Then try to run a long self test on the drive which will try to read all sectors and could take several hours to complete.

smartctl -t long /dev/sda