Re: [gentoo-user] the new ssd, is it happy?
On 25.02.2015 17:16, Bob Wya wrote: For my Samsung 830 / 850 Pro SSDs I don't see any similar NCQ queuing error(s) in my boot logs (they are hooked up to the Intel Controller just now - since I can't connect them to my 6Gbit LSI Controller - arrrggg!!) Perhaps this issue is confined to the Samsung EVO lines? It seems like. Maybe I had that with the 840 EVO already, I never looked so close ... but now as I put the 840 into the thinkpad I see that behavior there as well! And the 840 had some firmware updates already while there are no updates yet for the 850.
Re: [gentoo-user] the new ssd, is it happy?
So it probably is Samsung's dodgy firmware not working with the SATA-3.0 extensions (aka SATA 3.1). Like I mentioned I can't even run my Samsung SSD's @6Gbit because none of the models I own support deterministic trim - which is a much bigger problem than yours! I assumed the 850 Pro would support deterministic trim - as the 840 Pro models supported it - but hell no! I wouldn't rely on any firmware updates from Samsung to fix any of this stuff... It has to be really, really bad - like the 840 issues - before they'll pull their finger out. I'll certainly be raising a support issue, over the lack of non-deterministic trim support in the 850 Pro firmware, but I expect that will get as far as my LSI Support issue did... :-( On 26 February 2015 at 10:16, Stefan G. Weichinger li...@xunil.at wrote: On 25.02.2015 17:16, Bob Wya wrote: For my Samsung 830 / 850 Pro SSDs I don't see any similar NCQ queuing error(s) in my boot logs (they are hooked up to the Intel Controller just now - since I can't connect them to my 6Gbit LSI Controller - arrrggg!!) Perhaps this issue is confined to the Samsung EVO lines? It seems like. Maybe I had that with the 840 EVO already, I never looked so close ... but now as I put the 840 into the thinkpad I see that behavior there as well! And the 840 had some firmware updates already while there are no updates yet for the 850. -- All the best, Robert
Re: [gentoo-user] the new ssd, is it happy?
Am 24.02.2015 um 21:49 schrieb Stefan G. Weichinger: ordered myself a new and shiny ssd last week. one thinkpad still had that 60GB OCZ Vertex3 and that was a bit tight now and then. So I ordered a Samsung SSD 850 EVO 500GB for my desktop and planned to move the former 840 EVO 250GB to the thinkpad. have the smaller version - and get the same crap in dmesg. ssd is working fine, changed cables and still get those. But since it has no influence on its operation so far, I decided not to care at all.
Re: [gentoo-user] the new ssd, is it happy?
Am 27.02.2015 um 00:04 schrieb Volker Armin Hemmann:
Am 24.02.2015 um 21:49 schrieb Stefan G. Weichinger:
ordered myself a new and shiny ssd last week.
one thinkpad still had that 60GB OCZ Vertex3 and that was a bit tight
now and then.
So I ordered a Samsung SSD 850 EVO 500GB for my desktop and planned to
move the former 840 EVO 250GB to the thinkpad.
have the smaller version - and get the same crap in dmesg. ssd is
working fine, changed cables and still get those. But since it has no
influence on its operation so far, I decided not to care at all.
nope, is the 840 evo. Still, shits all over dmesg with superscary error
messages every time my box wakes up from S3 or on boot. And then it is ok.
[290276.570699] ata5.00: exception Emask 0x10 SAct 0x7fef SErr
0x40 action 0x6 frozen
[290276.570704] ata5.00: irq_stat 0x0800, interface fatal error
[290276.570707] ata5: SError: { Handshk }
[290276.570710] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570713] ata5.00: cmd 61/00:00:00:a0:60/04:00:03:00:00/40 tag 0
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570715] ata5.00: status: { DRDY }
[290276.570717] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570719] ata5.00: cmd 61/00:08:00:a4:60/04:00:03:00:00/40 tag 1
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570721] ata5.00: status: { DRDY }
[290276.570722] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570725] ata5.00: cmd 61/00:10:00:a8:60/04:00:03:00:00/40 tag 2
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570726] ata5.00: status: { DRDY }
[290276.570727] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570730] ata5.00: cmd 61/00:18:00:ac:60/04:00:03:00:00/40 tag 3
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570731] ata5.00: status: { DRDY }
[290276.570732] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570735] ata5.00: cmd 61/00:28:00:38:60/04:00:03:00:00/40 tag 5
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570736] ata5.00: status: { DRDY }
[290276.570737] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570740] ata5.00: cmd 61/00:30:00:3c:60/04:00:03:00:00/40 tag 6
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570741] ata5.00: status: { DRDY }
[290276.570743] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570745] ata5.00: cmd 61/00:38:00:40:60/04:00:03:00:00/40 tag 7
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570747] ata5.00: status: { DRDY }
[290276.570748] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570750] ata5.00: cmd 61/00:40:00:44:60/04:00:03:00:00/40 tag 8
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570752] ata5.00: status: { DRDY }
[290276.570753] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570756] ata5.00: cmd 61/00:48:00:48:60/04:00:03:00:00/40 tag 9
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570757] ata5.00: status: { DRDY }
[290276.570758] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570761] ata5.00: cmd 61/00:50:00:4c:60/04:00:03:00:00/40 tag 10
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570762] ata5.00: status: { DRDY }
[290276.570763] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570766] ata5.00: cmd 61/00:58:00:50:60/04:00:03:00:00/40 tag 11
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570767] ata5.00: status: { DRDY }
[290276.570769] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570771] ata5.00: cmd 61/00:60:00:54:60/04:00:03:00:00/40 tag 12
ncq 524288 out
res 40/00:30:00:3c:60/00:00:03:00:00/40 Emask 0x10 (ATA bus
error)
[290276.570773] ata5.00: status: { DRDY }
[290276.570774] ata5.00: failed command: WRITE FPDMA QUEUED
[290276.570777] ata5.00: cmd 61/00:68:00:58:60/04:00:03:00:00/40 tag 13
ncq 524288 out
Re: [gentoo-user] the new ssd, is it happy?
On 25.02.2015 10:23, Stefan G. Weichinger wrote: good hint, thanks! I will report back if I find something. Swapped the cable and also the SATA-socket on the board. It always gives the same result ... What is interesting: the HDDs negotiate their NCQ fine: [2.254804] ata2.00: ATA-8: Hitachi HDS721010CLA632, JP4OA41A, max UDMA/133 [2.254809] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [2.254842] ata5.00: ATA-8: ST31000524AS, JC4B, max UDMA/133 [2.254846] ata5.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32) and that with those cheap cables ... I googled that and found https://bugzilla.kernel.org/show_bug.cgi?id=72341 digging through that now :-)
Re: [gentoo-user] the new ssd, is it happy?
This made me recall having to download and alter a Windows SATA Host Controller driver. For some reason I had to get hold of an 6Gbyte development .iso to do this (that's Microsoft for you)... Now that was fun and games!! Basically because the SATA controller driver tried to enable NCQ (I can't remember which now!!) for some old Hitachi IDE drives - I had hooked these up via a SATA-PATA bridge - the bridge said NCQ - YES!! - the drive said NCQ - NO!!. The drives would lock up Windows when I hooked them up to the controller and start twanging constantly as they were reset, over and over again... I read through that bug report - interesting. It shouldn't be too hard for you add a User patch for your Gentoo kernel - to force-ably disable the attempt to negotiate SATA 3.1 and T13 ATA ACS-3 support - for the SATA connection. Since (I guess) you are building the kernel from source anyway! Basically your 850 EVO returns RECEIVE/SEND FPDMA QUEUED supported when initially queried Then when the (Linux) kernel tries to actually queue these commands - the 850 EVO firmware says Uhhhmm, duh - no I don't know how to do that one!! Just out of interest what make is the Host Controller on your motherboard... Is it a Intel one? Or some crappy addon chipset? Perhaps you could post the output of lscpi (with lots of - flags - just the Host Controller bit)? I'm starting get the feeling that Samsung take some very caliver shortcuts with the QC on their SSDs. I've recently bought a Samsung 850 Pro - sucker - as I have already experienced poor after-sales support with some Samsung 830 SSD issues. Now I've found out that the 850 Pro also doesn't support non-deterministic trim - so I can't use it with *any* Host Controllers with LSI-based firmware (or whatever they are called now) - because trim support will be completely disabled!! Sure we all want V-NAND - but perhaps I should have waited a year or two for Intel to catch up... To quote from the bug report (referring to the crappy Samsung 840 EVO firmware): I tried to contact Samsung support, but they answered that for the support of this product, you should contact the reseller. In other words, they don't want to answer. We are dealing with a drive that claims (during identification) to have a capability that it doesn't actually have. :-( On 25 February 2015 at 12:45, Stefan G. Weichinger li...@xunil.at wrote: On 25.02.2015 10:23, Stefan G. Weichinger wrote: good hint, thanks! I will report back if I find something. Swapped the cable and also the SATA-socket on the board. It always gives the same result ... What is interesting: the HDDs negotiate their NCQ fine: [2.254804] ata2.00: ATA-8: Hitachi HDS721010CLA632, JP4OA41A, max UDMA/133 [2.254809] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [2.254842] ata5.00: ATA-8: ST31000524AS, JC4B, max UDMA/133 [2.254846] ata5.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32) and that with those cheap cables ... I googled that and found https://bugzilla.kernel.org/show_bug.cgi?id=72341 digging through that now :-) -- All the best, Robert
Re: [gentoo-user] the new ssd, is it happy?
So this is for my motherboard's (Nehalem - so only one generation before yours) onboard Intel Host Controller... Only a SATA-2 3Gbit capable device. 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. P5Q Deluxe Motherboard Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 27 Region 0: I/O ports at 8c00 [size=8] Region 1: I/O ports at 8880 [size=4] Region 2: I/O ports at 8800 [size=8] Region 3: I/O ports at 8480 [size=4] Region 4: I/O ports at 8400 [size=32] Region 5: Memory at f7efc000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/16 Maskable- 64bit- Address: fee0 Data: 4082 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=0004 Capabilities: [b0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: ahci uname -r 3.19.0-gentoo For my Samsung 830 / 850 Pro SSDs I don't see any similar NCQ queuing error(s) in my boot logs (they are hooked up to the Intel Controller just now - since I can't connect them to my 6Gbit LSI Controller - arrrggg!!) Perhaps this issue is confined to the Samsung EVO lines? On 25 February 2015 at 15:02, Stefan G. Weichinger li...@xunil.at wrote: On 25.02.2015 14:18, Bob Wya wrote: Just out of interest what make is the Host Controller on your motherboard... Is it a Intel one? Or some crappy addon chipset? Perhaps you could post the output of lscpi (with lots of - flags - just the Host Controller bit)? 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0]) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family SATA AHCI Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 26 Region 0: I/O ports at f070 [size=8] Region 1: I/O ports at f060 [size=4] Region 2: I/O ports at f050 [size=8] Region 3: I/O ports at f040 [size=4] Region 4: I/O ports at f020 [size=32] Region 5: Memory at fb205000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: feeff00c Data: 41d1 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=0004 Capabilities: [b0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: ahci -- All the best, Robert
Re: [gentoo-user] the new ssd, is it happy?
On 25.02.2015 14:18, Bob Wya wrote: Just out of interest what make is the Host Controller on your motherboard... Is it a Intel one? Or some crappy addon chipset? Perhaps you could post the output of lscpi (with lots of - flags - just the Host Controller bit)? 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0]) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family SATA AHCI Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 26 Region 0: I/O ports at f070 [size=8] Region 1: I/O ports at f060 [size=4] Region 2: I/O ports at f050 [size=8] Region 3: I/O ports at f040 [size=4] Region 4: I/O ports at f020 [size=32] Region 5: Memory at fb205000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: feeff00c Data: 41d1 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=0004 Capabilities: [b0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: ahci
Re: [gentoo-user] the new ssd, is it happy?
Ahhh, Quoting from the Intel 6 Series Chipset pdf... The PCH supports the Serial ATA Specification, Revision 3.0. The PCH also supports several optional sections of the Serial ATA II: Extensions to Serial ATA 1.0 Specification, Revision 1.0 (AHCI support is required for some elements). Please see Section 1.3 for details on SKU feature availability. So your (newer) Intel Chipset supports the SATA-3 specification. That's probably why you are seeing the issue and I'm not... On 25 February 2015 at 16:16, Bob Wya bob.mt@gmail.com wrote: So this is for my motherboard's (Nehalem - so only one generation before yours) onboard Intel Host Controller... Only a SATA-2 3Gbit capable device. 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. P5Q Deluxe Motherboard Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 27 Region 0: I/O ports at 8c00 [size=8] Region 1: I/O ports at 8880 [size=4] Region 2: I/O ports at 8800 [size=8] Region 3: I/O ports at 8480 [size=4] Region 4: I/O ports at 8400 [size=32] Region 5: Memory at f7efc000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/16 Maskable- 64bit- Address: fee0 Data: 4082 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=0004 Capabilities: [b0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: ahci uname -r 3.19.0-gentoo For my Samsung 830 / 850 Pro SSDs I don't see any similar NCQ queuing error(s) in my boot logs (they are hooked up to the Intel Controller just now - since I can't connect them to my 6Gbit LSI Controller - arrrggg!!) Perhaps this issue is confined to the Samsung EVO lines? On 25 February 2015 at 15:02, Stefan G. Weichinger li...@xunil.at wrote: On 25.02.2015 14:18, Bob Wya wrote: Just out of interest what make is the Host Controller on your motherboard... Is it a Intel one? Or some crappy addon chipset? Perhaps you could post the output of lscpi (with lots of - flags - just the Host Controller bit)? 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0]) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family SATA AHCI Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 26 Region 0: I/O ports at f070 [size=8] Region 1: I/O ports at f060 [size=4] Region 2: I/O ports at f050 [size=8] Region 3: I/O ports at f040 [size=4] Region 4: I/O ports at f020 [size=32] Region 5: Memory at fb205000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: feeff00c Data: 41d1 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=0004 Capabilities: [b0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: ahci -- All the best, Robert -- All the best, Robert
Re: [gentoo-user] the new ssd, is it happy?
On 25.02.2015 00:55, Bob Wya wrote: Super obvious question... but can you enable AHCI mode for your SATA Controller - in the BIOS. AHCI is enabled in the BIOS, I checked right now. Do the messages tell us it isn't? Ah, I see, no NCQ for the SSD ... hmm, right. Are you using HP supplied SATA cables - because these may be sucky crap. If so I would try replacing them - especially if they don't have latches on the plugs. I am not sure, where the cables came from ... the one for the SSD has latches. But I will replace the SATA cable and see if it changes things. I think this is the specification for your motherboard chipset: http://www.intel.com/content/www/us/en/chipsets/mainstream-chipsets/h67-express-chipset.html So you probably need the decent SATA 3G (6Gbit) cables to get the best support for your SSD. I've had some issues with 6Gbit SATA... Basically you are looking at really high switching speeds - where connector quality makes a huge difference. It might even be worth cleaning out your SATA connectors with isopropyl alcohol (99%). good hint, thanks! I will report back if I find something.
[gentoo-user] the new ssd, is it happy?
ordered myself a new and shiny ssd last week. one thinkpad still had that 60GB OCZ Vertex3 and that was a bit tight now and then. So I ordered a Samsung SSD 850 EVO 500GB for my desktop and planned to move the former 840 EVO 250GB to the thinkpad. Done today. Moving was rather *boring* - partition ssd, add new partition to btrfs filesystem, remove old partition from btrfs filesystem, wait ~15 minutes, in the meantime copy over the UEFI ESP to the new disk, install gummiboot there ... it booted up at first time ... oh my, what has happened to good old gentoo? :-P (resized stuff, yes ... but no big blockers anywhere) What I would like to discuss now: # dmesg | grep ata1 [1.930869] ata1: SATA max UDMA/133 abar m2048@0xfb205000 port 0xfb205100 irq 26 [2.235852] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.237378] ata1.00: supports DRM functions and may not be fully accessible [2.237506] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [2.237509] ata1.00: ATA-9: Samsung SSD 850 EVO 500GB, EMT01B6Q, max UDMA/133 [2.237521] ata1.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA [2.237979] ata1.00: supports DRM functions and may not be fully accessible [2.238071] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [2.238166] ata1.00: configured for UDMA/133 [20207.916327] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [20207.916528] ata1.00: supports DRM functions and may not be fully accessible [20207.916598] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [20207.918249] ata1.00: supports DRM functions and may not be fully accessible [20207.918325] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [20207.918419] ata1.00: configured for UDMA/133 Are these failed lines ok? The box itself is a bit older, a Hewlett-Packard HP Elite 7300 Series MT/2AB5, BIOS 7.12 (I never found a BIOS update! btw ...) so maybe the chipset lacks features the SSD might be able to use. Everything works fine so far, I would just like to understand if things are OK with this new piece of hardware. additional: Device Model: Samsung SSD 850 EVO 500GB Firmware Version: EMT01B6Q I did not find any firmware update online, do you agree? Thanks, regards, Stefan
Re: [gentoo-user] the new ssd, is it happy?
Super obvious question... but can you enable AHCI mode for your SATA Controller - in the BIOS. Are you using HP supplied SATA cables - because these may be sucky crap. If so I would try replacing them - especially if they don't have latches on the plugs. I think this is the specification for your motherboard chipset: http://www.intel.com/content/www/us/en/chipsets/mainstream-chipsets/h67-express-chipset.html So you probably need the decent SATA 3G (6Gbit) cables to get the best support for your SSD. I've had some issues with 6Gbit SATA... Basically you are looking at really high switching speeds - where connector quality makes a huge difference. It might even be worth cleaning out your SATA connectors with isopropyl alcohol (99%). On 24 February 2015 at 20:49, Stefan G. Weichinger li...@xunil.at wrote: ordered myself a new and shiny ssd last week. one thinkpad still had that 60GB OCZ Vertex3 and that was a bit tight now and then. So I ordered a Samsung SSD 850 EVO 500GB for my desktop and planned to move the former 840 EVO 250GB to the thinkpad. Done today. Moving was rather *boring* - partition ssd, add new partition to btrfs filesystem, remove old partition from btrfs filesystem, wait ~15 minutes, in the meantime copy over the UEFI ESP to the new disk, install gummiboot there ... it booted up at first time ... oh my, what has happened to good old gentoo? :-P (resized stuff, yes ... but no big blockers anywhere) What I would like to discuss now: # dmesg | grep ata1 [1.930869] ata1: SATA max UDMA/133 abar m2048@0xfb205000 port 0xfb205100 irq 26 [2.235852] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.237378] ata1.00: supports DRM functions and may not be fully accessible [2.237506] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [2.237509] ata1.00: ATA-9: Samsung SSD 850 EVO 500GB, EMT01B6Q, max UDMA/133 [2.237521] ata1.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA [2.237979] ata1.00: supports DRM functions and may not be fully accessible [2.238071] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [2.238166] ata1.00: configured for UDMA/133 [20207.916327] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [20207.916528] ata1.00: supports DRM functions and may not be fully accessible [20207.916598] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [20207.918249] ata1.00: supports DRM functions and may not be fully accessible [20207.918325] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [20207.918419] ata1.00: configured for UDMA/133 Are these failed lines ok? The box itself is a bit older, a Hewlett-Packard HP Elite 7300 Series MT/2AB5, BIOS 7.12 (I never found a BIOS update! btw ...) so maybe the chipset lacks features the SSD might be able to use. Everything works fine so far, I would just like to understand if things are OK with this new piece of hardware. additional: Device Model: Samsung SSD 850 EVO 500GB Firmware Version: EMT01B6Q I did not find any firmware update online, do you agree? Thanks, regards, Stefan -- All the best, Robert
