Jacques Montier wrote: > / > / > > > Le mar. 28 déc. 2021 à 14:03, Jacques Montier <jmont...@gmail.com > <mailto:jmont...@gmail.com>> a écrit : > > / > / > > > Le mar. 28 déc. 2021 à 13:32, Dale <rdalek1...@gmail.com > <mailto:rdalek1...@gmail.com>> a écrit : > > William Kenworthy wrote: > > A point to keep in mind - if you can feel the drive moving > it may be > > generating errors! Depending on the drive, the errors may > just be > > handled internally and I can see it slowing things down though > > probably would be barely noticeable. I have seen it myself with > > random errors from a WD green drive disappearing when properly > > immobilised. When investigating I ran across articles > discussing the > > problem, one of which fastened the drives to a granite slab for > > tests! Also see discussions on NAS seups and vibrations > affecting co > > located drives. > > > > BillK > > > > ** Interesting read > > > https://www.ept.ca/features/everything-need-know-hard-drive-vibration/ > > > > This is just because it is a SMR drive. It's done this ever > since I > bought the drive and it has passed all tests. There's a whole > thread on > this dating back several years. I managed to buy a SMR drive > before I > even knew they existed. Once it fills up that PMR section, it > gets > really slow. > > Dale > > :-) :-) > > > Hello all, > > Thanks a lot for all your responses ! > I think this issue is kernel related. > No problem with 5.10.76-gentoo-r1, but the issue appears > with 5.15.11-gentoo. > > I read on the net that it could be possible to desactivate the > sata protocol NCQ (Native Command Queuing) > So, in the grub file, i added the > ligne GRUB_CMDLINE_LINUX=libata.force=noncq > Now, all the errors messages are gone and the booting time gets > down to 24s with the two kernel versions. > BUT : do you think it could damage or slow down my SSD and HDD disks ? > > Thanks again, > > Regards, > > -- > Jacques > > > > Me again ! > > Well, il cleaned my dusty mobo, unplugged and plugged again the sata > cables. > Now, with or without NCQ, boot time is rather short (~28s). > So it seems it was a connection problem. > > I still have some errors as : > > ............................................ > [ 24.708377] ata6.00: exception Emask 0x10 SAct 0x50400001 SErr > 0x4010000 action 0xe frozen > [ 24.708385] ata6.00: irq_stat 0x00400040, connection status changed > [ 24.708387] ata6: SError: { PHYRdyChg DevExch } > [ 24.708390] ata6.00: failed command: READ FPDMA QUEUED > [ 24.708391] ata6.00: cmd 60/08:00:78:08:c0/00:00:31:00:00/40 tag 0 > ncq dma 4096 in > res 40/00:00:78:08:c0/00:00:31:00:00/40 Emask > 0x10 (ATA bus error) > [ 24.708397] ata6.00: status: { DRDY } > .......................................... > > To be sure, i'll buy some news sata cables. > > Sorry for the noise and thanks again for having helped me. > > Regards, > > -- > Jacques
It could be that the cable itself is good but just had a dust bunny or something in the connection. Once you reseated the cable, it moved the dust bunny out of the way. I've done this sort of thing with lots of connections and not had any trouble afterwards. I'd suggest unplugging things, blowing them out with compressed air to remove all the dust and such and then reconnecting everything and seeing how that works. No need throwing out what could very well be perfectly good cables. Just a thought. ;-) Dale :-) :-)
