Re: SATA disks disabled on boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greetings

On Wed, Jan 28, 2015 at 2:05 PM, Phillip Susi <psusi@xxxxxxxxxx> wrote:

>> [   12.824479] ata4.00: failed to IDENTIFY (SPINUP failed,
>> err_mask=0x4)
>>
>> which i took as a good sign since i didn't want it spinning up.
>
> Well, you *do* want it spinning up of course, so you can access it.

Yup, but not right at boot, just a bit later.

> Looking at your dmesg, I noticed this:
>
> [ 1806.776781] ata2.00: ATA-9: WDC WD10EFRX-68PJCN0, 01.01A01, max
> UDMA/133
> [ 1806.776785] ata2.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth
> 31/32)
> [ 1806.784760] ata2.00: n_sectors mismatch 1953525168 != 268435455
> [ 1806.784768] ata2.00: revalidation failed (errno=-19)
> [ 1806.784780] ata2: limiting SATA link speed to 1.5 Gbps
> [ 1806.784787] ata2.00: limiting speed to UDMA/133:PIO3
> [ 1811.768094] ata2: hard resetting link
> [ 1811.768103] ata2: nv: skipping hardreset on occupied port
> [ 1812.236126] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>
>
> THIS appears to be your problem.  It looks like the drive is changing
> its mind on its size, indicating some spectacularly broken firmware.
> I also notice that it fails to reset the link and lower the speed...
> is this controller set to IDE mode in the bios?  If so you might have
> better luck in proper AHCI mode.

The "n_sectors mismatch" thing was the red flag that got me starting
this thread in the first place (that and the fact the disks were
"disappearing").
As far as the BIOS goes, it's consistent on the Toshibas as far as
SATA information goes:
Extended IDE drive: auto, Access mode: auto
Cylinder: 65535, Head: 16, Landing Zone: 65534, Sector 255
for both.

With the WDs, not so much. For WD1:
Extended IDE drive: auto, Access mode: large (this one i changed from
the "auto" default to see if it would change anything)
Cylinder: 4095, Head: 240, Landing Zone: 65534, Sector 255

WD2 has no data, it's all 0 (since this is the drive where i recently
enabled PUIS, is this expected? Anyway i'm going to disable it)

I was expecting all drives to have the same values for these fields.
They all do report 1000GB (except WD2) and i believe they all emulate
512K even though they're 4KB. It's kinda weird the landing zone value
is greater than the cylinder but that's just me guessing. Isn't the
landing zone the MBR?

The general SATA values are:
SATA spread spectrum: enabled (this isn't a factory floor or anything
- but it is connected to a low end UPS)
SATA Controller 1, 2: enabled, SATA DMA Transfer: enabled
SATA Port 3, 4: enabled, SATA2 DMA Transfer: enabled (yes, incoherent wording)
IDE prefetch mode: enabled
HDD down on suspend: disabled (not that it would influence boot)

I saw some "sdd failed" message on boot but i can't find it in any
recent file in /var/log (actually dmesg, kern.log and syslog are
pretty much the same). I attibuted that to the PUIS. Anyway on this
boot (attached) all HDDs were detected the first time.

With this information, do you think AHCI mode could help? How can i enable that?

Thanks,
Nuno

Attachment: 2015-01-29.dmesg
Description: Binary data


[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux