Hi Raphael
Raphaël Walther <raphael.walt...@gmail.com> writes:
> I reproduce the same issue on the same computer with the new
> motherboard. I tried to encrypt a partition and it failed again at the
> same step.
Can you please post the logs of this attempt. Without any logs it's hard
to tell why it failed. The logs you previously posted really look like
it's a hardware issue. Maybe it was not the motherboard which is at
fault after all. If the logs still contain similar kernel errors like:
Feb 27 12:53:59 kernel: [ 839.770044] ata1.00: exception Emask 0x0 SAct 0xfffc
SErr 0x0 action 0x6 frozen
Feb 27 12:53:59 kernel: [ 839.770052] ata1.00: failed command: WRITE FPDMA
QUEUED
Feb 27 12:53:59 kernel: [ 839.770062] ata1.00: cmd
61/08:10:90:8e:2b/00:00:00:00:00/40 tag 2 ncq 4096 out
Feb 27 12:53:59 kernel: [ 839.770076] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 27 12:53:59 kernel: [ 839.770078] ata1.00: status: { DRDY }
or
Feb 27 12:53:59 kernel: [ 839.770169] ata1: hard resetting link
Feb 27 12:54:04 kernel: [ 845.124346] ata1: link is slow to respond, please be
patient (ready=0)
Feb 27 12:54:09 kernel: [ 849.760448] ata1: COMRESET failed (errno=-16)
Feb 27 12:54:09 kernel: [ 849.760458] ata1: hard resetting link
Feb 27 12:54:14 kernel: [ 855.106726] ata1: link is slow to respond, please be
patient (ready=0)
Feb 27 12:54:19 kernel: [ 859.742825] ata1: COMRESET failed (errno=-16)
Feb 27 12:54:19 kernel: [ 859.742832] ata1: hard resetting link
Feb 27 12:54:24 kernel: [ 865.097079] ata1: link is slow to respond, please be
patient (ready=0)
Feb 27 12:54:54 kernel: [ 894.701093] ata1: COMRESET failed (errno=-16)
Feb 27 12:54:54 kernel: [ 894.701105] ata1: limiting SATA link speed to 3.0
Gbps
Feb 27 12:54:54 kernel: [ 894.701109] ata1: hard resetting link
Feb 27 12:54:59 kernel: [ 899.712231] ata1: COMRESET failed (errno=-16)
Feb 27 12:54:59 kernel: [ 899.712243] ata1: reset failed, giving up
Feb 27 12:54:59 kernel: [ 899.712247] ata1.00: disabled
I suggest you also run a comprehensive harddisk test with some testing
tool like badblocks from a Live CD or from a testing CD provided by your
hardware vendor. Just to be sure that the hardware issue is indeed fixed.
Gaudenz
>
> Cheers,
> Raphaël
>
>
> --
> To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20130311125250.ga9...@gmail.com
>
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
