Arch Linux

Gruntz

Member

From: Haskovo, Bulgaria

Registered: 2007-08-31

Posts: 291

Disk problem, unable to boot, ata2: COMRESET failed (errno=-16)

Hello.

From some time now, I am having disk problems. When I try to boot my system in the morning, my bios splash screen froze for a while and my disk scratches (I don`t know which one). Then the grub boot menu pops up. When I try to boot my archlinux, I got several "ata2: COMRESET failed (errno=-16)" messages and the system does not boot. When I reboot the system by pressing the power button, the system usually boots normally. Some times i got the COMRESET error for two or three reboots, but eventually, my system boots. I tried to find the problem via smartctl, but everything is OK. During the day, when I reboot my system, to windows, and then back to linux, or when I am shutting down the machine in order to move, i don`t get these errors. I am getting the error when my box is cold (stayed off during the night, or I halt it for several hours and boot again.) As my root file system is on the SSD, and only the /var is on the HDD, i suppose that the problem is with the SSD.

I tested to boot directly windows in the morning, but I got disk error. Since the Windows does have nothing to do with the SSD, the HDD may be the problem.

Bottom line, I can`t pinpoint the problem :S

I tried to remove and install the disks again, but the problem does not seems to be a loose cable connection.

I read in the forum about that error, and that maybe the firmware re-install can fix it, but I can`t find any linux related samsung firmware re-install handbooks.

My machine is Lenovo y850 laptop, with SSD and HDD disks.

I have two disks:
SSD:

=== START OF INFORMATION SECTION ===
Device Model:     SAMSUNG MZMPC032HBCD-000L1
Serial Number:    S0Y2NEAC623408
Firmware Version: CXM12L1Q
User Capacity:    32,017,047,552 bytes [32.0 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Sep 25 13:21:31 2013 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

HDD:

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus SpinPoint M8 (AF)
Device Model:     ST1000LM024 HN-M101MBB
Serial Number:    S2U5J9AC742697
LU WWN Device Id: 5 0004cf 208117e25
Firmware Version: 2AR10001
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Sep 25 13:22:19 2013 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

The disks have GPT partition layout and uefi boot. My partitions are as follows:
SSD:
    p1 - fat, efi system partition
    p2 - ext4, /
HDD:
    p1 - /home
    p2 - Windows 8 partition
    p3 - /var

I will post any needed information, just ask.

Thank you for the help.

Last edited by Gruntz (2013-09-25 10:49:28)

Spider.007

Member

Registered: 2004-06-20

Posts: 1,176

Re: Disk problem, unable to boot, ata2: COMRESET failed (errno=-16)

Doesn't

dmesg |grep ata2

tell you the device that is connected the to ata2 bus? If it is the ssd; try a firmware-upgrade. If that doesn't help; post the lspci -v output for your sata controller here

Jezza

Member

Registered: 2015-03-25

Posts: 2

Re: Disk problem, unable to boot, ata2: COMRESET failed (errno=-16)

Hi all,

I realise this topic is sort of old, but it hasn't been solved and I am having the same issue (with both sda (currently not in use, as it wouldn't even show up any more... I am surprised that it showed up again after all, see below) and sdb (on which I installed Arch) - both are Samsung SSD's; sdc and sdd are HDD's). My lsblk output is

[jezza@jq-archhost ~]$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 238.5G  0 disk 
sdb      8:16   0 238.5G  0 disk 
├─sdb1   8:17   0    84K  0 part 
├─sdb2   8:18   0   250M  0 part /boot
├─sdb3   8:19   0    40G  0 part /
├─sdb4   8:20   0     8G  0 part [SWAP]
└─sdb5   8:21   0 190.2G  0 part /home
sdc      8:32   0   2.7T  0 disk 
└─sdc1   8:33   0   2.7T  0 part /home/media
sdd      8:48   0   2.7T  0 disk 
└─sdd1   8:49   0   2.7T  0 part 
sr0     11:0    1  1024M  0 rom 

and my output for dmesg | grep ata2 is

[jezza@jq-archhost ~]$ dmesg | grep ata2
[    0.527061] ata2: SATA max UDMA/133 abar m2048@0xdc136000 port 0xdc136180 irq 34
[    0.846421] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.848307] ata2.00: supports DRM functions and may not be fully accessible
[    0.848339] ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
[    0.848340] ata2.00: ATA-9: Samsung SSD 850 PRO 256GB, EXM01B6Q, max UDMA/133
[    0.848341] ata2.00: 500118192 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[    0.848542] ata2.00: supports DRM functions and may not be fully accessible
[    0.848568] ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
[    0.848612] ata2.00: configured for UDMA/133

Anyone who can help, please? Thanks very much in advance!

firekage

Member

From: Eastern Europe, Poland

Registered: 2013-06-30

Posts: 624

Re: Disk problem, unable to boot, ata2: COMRESET failed (errno=-16)

Can you post smart of HDD disk?

Jezza

Member

Registered: 2015-03-25

Posts: 2

Re: Disk problem, unable to boot, ata2: COMRESET failed (errno=-16)

Thanks for trying to help! /dev/sdb, /dev/sdc and /dev/sdd are fine. But /dev/sda gives this result:

[jezza@jq-archhost ~]$ sudo smartctl -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.2-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               /0:0:0:0
Product:              
Compliance:           SPC-5
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

I am not knowledgeable enough to properly judge this, but it certainly looks different from the other three tests I did...