Arch Linux

ArchLinux20020

Member

Registered: 2014-09-10

Posts: 21

[SOLVED] Triggering uevents...

Running archlinux-2014.09.03-dual.iso from CD
After selecting 86_64, terminal runs and displays the following.

:: running hook [udev]
:: Triggering uevents...
[  34.514137] ata2.00: exception Emask 0x52 SAct 0x0 SErr oxffffffff action 0xe frozen
[  34.514163] ata2L SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[  34.514183] ata2.00: failed command: IDENTIFY PACKET DEVICE
[  34.514199] ata2.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 3 pio 512 in
[  34.514199] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x56 (ATA bus error)
[  34.514218] ata2.00: status: { DRDY }

What do I do from here? Seems I cannot type anything.
Also for future reference, is there a way I can save the text on the terminal screen to a USB? I manually had to type all of this verbiage - this will soon become a headache with the amount of problems I anticipate are likely to occur during installation.

PC Specs

CPU : 4770k
RAM : Corsair 32GB Ram
MOBO : Asus Maximus Extreme IV
HD : WD 2TB

Regards

Last edited by ArchLinux20020 (2014-09-10 19:00:22)

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: [SOLVED] Triggering uevents...

this will soon become a headache with the amount of problems I anticipate are likely to occur during installation.

Curious why you're installing Arch if you're going into it with such a negative attitude?

The error you posted usually indicates a hardware fault -- but often this is triggered by a loose signal cable connecting the disk to the motherboard.

---

blog | ±github

ArchLinux20020

Member

Registered: 2014-09-10

Posts: 21

Re: [SOLVED] Triggering uevents...

this will soon become a headache with the amount of problems I anticipate are likely to occur during installation.

Curious why you're installing Arch if you're going into it with such a negative attitude?

The error you posted usually indicates a hardware fault -- but often this is triggered by a loose signal cable connecting the disk to the motherboard.

Because I just wasted 3.5 weeks trying to install another Distro.

As for this issue, I managed to fix it by randomly moving the Sata Cables around.
Unplugging all other SATA cables apart from the DVD Drive until the error went away, then plugging back in the others and testing.

Last edited by ArchLinux20020 (2014-09-10 19:21:35)