cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
glundby
Ctrl-Alt-Del
Posts: 16
Registered: ‎12-16-2016
Location: NO
Views: 501
Message 11 of 17

Re: Yoga 3 pro blue screen

Hi again! Definitely Disk failure! 

  • MT 80HE
  • SN PF0ERF4X

Attached is SysLog from Ubuntu even when not using or mounting the builtin SSD:

 

Apr 28 15:48:53 gustav-YOGA kernel: [ 2063.090030] ata1: COMRESET failed (errno=-32)
Apr 28 15:48:53 gustav-YOGA kernel: [ 2063.090043] ata1: reset failed, giving up
Apr 28 15:48:53 gustav-YOGA kernel: [ 2063.090070] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen t2
Apr 28 15:48:53 gustav-YOGA kernel: [ 2063.090074] ata1: irq_stat 0x00000040, connection status changed
Apr 28 15:48:53 gustav-YOGA kernel: [ 2063.090079] ata1: SError: { DevExch }
Apr 28 15:48:53 gustav-YOGA kernel: [ 2063.090088] ata1: hard resetting link
Apr 28 15:48:55 gustav-YOGA kernel: [ 2065.318092] ata1: COMRESET failed (errno=-32)
Apr 28 15:48:55 gustav-YOGA kernel: [ 2065.318105] ata1: reset failed (errno=-32), retrying in 8 secs
Apr 28 15:49:03 gustav-YOGA kernel: [ 2073.154432] ata1: limiting SATA link speed to 1.5 Gbps
Apr 28 15:49:03 gustav-YOGA kernel: [ 2073.154437] ata1: hard resetting link
Apr 28 15:49:05 gustav-YOGA kernel: [ 2075.382376] ata1: COMRESET failed (errno=-32)
Apr 28 15:49:05 gustav-YOGA kernel: [ 2075.382391] ata1: reset failed (errno=-32), retrying in 8 secs
Apr 28 15:49:13 gustav-YOGA kernel: [ 2083.394707] ata1: hard resetting link
Apr 28 15:49:15 gustav-YOGA kernel: [ 2085.618735] ata1: COMRESET failed (errno=-32)
Apr 28 15:49:15 gustav-YOGA kernel: [ 2085.618744] ata1: reset failed (errno=-32), retrying in 33 secs
Apr 28 15:49:50 gustav-YOGA kernel: [ 2120.259653] ata1: hard resetting link
Apr 28 15:49:52 gustav-YOGA kernel: [ 2122.519673] ata1: COMRESET failed (errno=-32)
Apr 28 15:49:52 gustav-YOGA kernel: [ 2122.519686] ata1: reset failed, giving up
Apr 28 15:49:52 gustav-YOGA kernel: [ 2122.519713] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen t1
Apr 28 15:49:52 gustav-YOGA kernel: [ 2122.519717] ata1: irq_stat 0x00000040, connection status changed
Apr 28 15:49:52 gustav-YOGA kernel: [ 2122.519721] ata1: SError: { DevExch }
Apr 28 15:49:52 gustav-YOGA kernel: [ 2122.519729] ata1: hard resetting link
Apr 28 15:49:55 gustav-YOGA kernel: [ 2124.743650] ata1: COMRESET failed (errno=-32)
Apr 28 15:49:55 gustav-YOGA kernel: [ 2124.743662] ata1: reset failed (errno=-32), retrying in 8 secs
Apr 28 15:50:02 gustav-YOGA kernel: [ 2132.547881] ata1: limiting SATA link speed to 1.5 Gbps
Apr 28 15:50:02 gustav-YOGA kernel: [ 2132.547891] ata1: hard resetting link
Apr 28 15:50:05 gustav-YOGA kernel: [ 2134.771983] ata1: COMRESET failed (errno=-32)
Apr 28 15:50:05 gustav-YOGA kernel: [ 2134.771995] ata1: reset failed (errno=-32), retrying in 8 secs
Apr 28 15:50:13 gustav-YOGA kernel: [ 2142.788021] ata1: hard resetting link
Apr 28 15:50:15 gustav-YOGA kernel: [ 2145.048055] ata1: COMRESET failed (errno=-32)
Apr 28 15:50:15 gustav-YOGA kernel: [ 2145.048063] ata1: reset failed (errno=-32), retrying in 33 secs

 

This happens again and again and the disk disapear from Ubuntu and even from BIOS! Sometimes I'm able to use the Disk for a short time, but the SysLog is full of errors like above.

payso87
Punch Card
Posts: 8
Registered: ‎02-09-2016
Location: Pittsburgh PA
Views: 498
Message 12 of 17

Re: Yoga 3 pro blue screen

Quick question.

Can you tell me the bios settings needed in order to install Ubuntu 17.04 to do some testing.

Also was the hard drive eventually crashing while running Ubuntu like it was with Windows minus the blue screen?
glundby
Ctrl-Alt-Del
Posts: 16
Registered: ‎12-16-2016
Location: NO
Views: 489
Message 13 of 17

Re: Yoga 3 pro blue screen

There is two routes to installing Ubuntu 17.04, either alongside Windows 10, it makes its own partition. When I did this, it gradually deterioated, even when I did not ever started in Windows. This proved to me that the Win10 creators update where not to blame. This method inserts GRUB2 in the EFI partition, so you can select which OS to boot. Easy just follow default suggestions all the way.

 

The other method I selected to be able to run without the defective SSD, is to install on a bootable USB(3) stick. This is not that strighet forward. I did a lot of failed attempts. The important is to select advanced and force Boot to the efi partition on sdb1 and / on the sdb2 formated to ext4.

 

In Bios, disable fast boot, enable USB boot ,disable secure OS. and then set the USB Ubuntu as first boot and internal win 10 as second boot. ( uefi boot must be the method. )

glundby
Ctrl-Alt-Del
Posts: 16
Registered: ‎12-16-2016
Location: NO
Views: 486
Message 14 of 17

Re: Yoga 3 pro blue screen

I forgot to mention that you of cource first has to create a bootable live image, either on CD or on USB stick as described in the Ubuntu pages...
payso87
Punch Card
Posts: 8
Registered: ‎02-09-2016
Location: Pittsburgh PA
Views: 469
Message 15 of 17

Re: Yoga 3 pro blue screen

Just a quick update. 

 

I replaced the SSD reinstalled windows 10 and windows 8.1 and got the blue screen errors again. I`m not sure what else the problem may be unless its possibly the RAM thats going bad?

glundby
Ctrl-Alt-Del
Posts: 16
Registered: ‎12-16-2016
Location: NO
Views: 459
Message 16 of 17

Re: Yoga 3 pro blue screen

Did you run the Lenovo HW test suite? There is extensive tests for memory... and SSD. In my case the tests all came through.

 

From Ubuntu, in my case, looking at the SysLog, I can see lots of errors regarding HW ATA1. It does however not look like read/write errors, but is regarding connect - disconnet of the SSD. It tries first 6.0Mbit theen 3.0 Mbit then 1.5 Mbit then gives up on the SSD. May it be the SATA HW on the motherboard???? 

 

The error also reflects in the Bios. Sometimes you does not see any SSD to boot.

 

Apr 30 21:38:09 Gustav-YOGA kernel: [16146.713832] ata1: SATA link down 
(SStatus 0 SControl 300)
Apr 30 21:38:14 Gustav-YOGA kernel: [16151.798275] ata1: hard resetting link
Apr 30 21:38:15 Gustav-YOGA kernel: [16152.113604] ata1: SATA link up 
6.0 Gbps (SStatus 133 SControl 300)
Apr 30 21:38:15 Gustav-YOGA kernel: [16152.116774] ata1.00: ACPI cmd 
ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Apr 30 21:38:15 Gustav-YOGA kernel: [16152.117722] ata1.00: ACPI cmd 
ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Apr 30 21:38:15 Gustav-YOGA kernel: [16152.118027] ata1.00: configured 
for UDMA/133
Apr 30 21:38:15 Gustav-YOGA kernel: [16152.118031] ata1: EH complete
Apr 30 21:38:19 Gustav-YOGA kernel: [16156.424496] ata1: limiting SATA 
link speed to 3.0 Gbps
Apr 30 21:38:19 Gustav-YOGA kernel: [16156.424503] ata1: exception Emask 
0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
Apr 30 21:38:19 Gustav-YOGA kernel: [16156.424513] ata1: irq_stat 
0x00400040, connection status changed
Apr 30 21:38:19 Gustav-YOGA kernel: [16156.424520] ata1: SError: { 
PHYRdyChg 10B8B DevExch }
Apr 30 21:38:19 Gustav-YOGA kernel: [16156.424528] ata1: hard resetting link
Apr 30 21:38:20 Gustav-YOGA kernel: [16157.134574] ata1: SATA link down 
(SStatus 0 SControl 320)
Apr 30 21:38:25 Gustav-YOGA kernel: [16162.295027] ata1: hard resetting link
Apr 30 21:38:25 Gustav-YOGA kernel: [16162.610517] ata1: SATA link down 
(SStatus 0 SControl 320)
Apr 30 21:38:25 Gustav-YOGA kernel: [16162.610529] ata1: limiting SATA 
link speed to 1.5 Gbps
Apr 30 21:38:30 Gustav-YOGA kernel: [16167.671441] ata1: hard resetting link
Apr 30 21:38:30 Gustav-YOGA kernel: [16167.987086] ata1: SATA link down 
(SStatus 0 SControl 310)
Apr 30 21:38:30 Gustav-YOGA kernel: [16167.987095] ata1.00: disabled
Apr 30 21:38:30 Gustav-YOGA kernel: [16167.987115] ata1: EH complete
Apr 30 21:38:30 Gustav-YOGA kernel: [16167.987130] ata1.00: detaching 
(SCSI 0:0:0:0)

glundby
Ctrl-Alt-Del
Posts: 16
Registered: ‎12-16-2016
Location: NO
Views: 326
Message 17 of 17

Re: Yoga 3 pro blue screen

Finally got my Yoga 3 Pro back from warranty repear. Disk changed, restored with last backup image. Looks good, but allways looks good after restore. Time will show if the SSD really was the sinner. I think yes because in the end it got worse and worse and at last stopped working.

Check out current deals!


Shop current deals

Top Kudoed Authors