Re: AM4 B350 chipset Sata/IDE problem

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

 



Hello again, I wonder why my previous mail was wrapped like that. Leafpad and me are to blame!


> libata.force=noncq option seems to prevent the messages from occurring. 5 kernel builds (j16) with none.
I knew it, I was sure!

> [    2.314441] ata2.00: ATA-7: ST3160815AS, 4.AAB, max UDMA/133
I suppose that your third ST3160815AS with 4.AAB firmware has no issue, correct?
> [    2.933706] ata5.00: ATA-7: ST3160811AS, 3.AAE, max UDMA/133
I suppose that your second ST3160815AS with 3.AAE firmware has no issue, correct?

They were produced in different years but all of them have no firmware update!
If you see the datecode on its sticker, the 3.AAD datecode must start from 07 or 08 while the 3.AAE datecode must start from 08 or 09 while the 4.AAB must start from 08, 09 or even 10.
You must contact seagate and inform them that the older one is incompatible with B350 when NCQ enabled. I bet they already know it but you can try.

> [    1.721248] ata9.00: ATA-6: ST3500320NS, SN04, max UDMA/133
I assume that your Barracuda ES.2 has caused no trouble, right?

Maybe all 7200.10 with 3.* must have NCQ disabled on AMD SATA controllers. It can be done but that would only do the trick for some affected disks not for all.
OEMs like HP have different firmware with different versions. A blacklist for 3.* would not detect an HP ST3160815AS with HPF0 firmware.
The same applies to DELL disks and so on...


> [    1.680035] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [    2.248065] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [    2.872065] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Clearly you are stuck with SATA I speeds. This can be done using two or three ways. I will not say a thing on that.
My brother read the information you uploaded and reminded me that those disks have a small jumper which can limit the maximum SATA interface speed.
That was needed to make them work on VT8237 series chipsets.
I suppose you have used that jumper configuration on all three disks but forgot it since you must have done it around 8 or more years ago...


>   5 Reallocated_Sector_Ct   PO--CK   100   100   036    -    0
>  10 Spin_Retry_Count        PO--C-   100   100   097    -    0
> 187 Reported_Uncorrect      -O--CK   100   100   000    -    0
> 189 High_Fly_Writes         -O-RCK   100   100   000    -    0
> 198 Offline_Uncorrectable   ----C-   100   100   000    -    0
Your disk is in great condition despite its 75675 hours.
As I said before: "Those disks are very reliable".

I would suggest running all self tests(with NCQ disabled) as the last one occured at 9725 hours. That was 65950 hours ago. It is a very long time.
I have not seen any disk reaching 50000 operating hours!


Can you please measure the speed of all three disks on the Ryzen board with AHCI with queue depth 31, 2 and 1?


> hpet0: 3 comparators, 32-bit...
AMD still uses 32bit for HPET! I wonder why.
��.n��������+%������w��{.n�����{��'^�)��jg��������ݢj����G�������j:+v���w�m������w�������h�����٥




[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