[SOLVED] HDD Spindown, spinup after startup

[KammutierSpule]

Hi all,

After the Linux Mint desktop starts, after login, the HDD spins down/up several times.. until it gets stable.

I already played with some configurations on Disks / Driver Settings but it didn't change.

I dont mind the disk spins down/up to save power, but I dont understand why it is doing it several times after start.

I'm using latest Linux Mint version with current updates.

Any suggestions?

[SMG]

I'm using latest Linux Mint version with current updates.

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

[ricardogroetaers]

I dont mind the disk spins down/up to save power, but I dont understand why it is doing it several times after start.

If I understand your text correctly, I don't see anything unusual.
Something is being read or written on the disc.
It can even be just the Update Manager, fsck checking a file system (if defined in fstab) or some program working.

[KammutierSpule]

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz

Here it go:

Code: Select all

System:
  Kernel: 5.4.0-73-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: Gigabyte model: GA-78LMT-USB3 6.0 v: SEx 
  serial: <filter> BIOS: Award v: F2 date: 11/25/2014 
CPU:
  Topology: 8-Core model: AMD FX-8320E bits: 64 type: MCP arch: Bulldozer 
  L2 cache: 2048 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 51425 
  Speed: 1410 MHz min/max: 1400/3200 MHz boost: enabled Core speeds (MHz): 
  1: 1454 2: 1653 3: 1577 4: 3013 5: 1437 6: 1437 7: 3442 8: 1499 
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI 
  driver: nvidia v: 460.73.01 bus ID: 01:00.0 chip ID: 10de:128b 
  Display: x11 server: X.Org 1.20.9 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa 
  resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 460.73.01 
  direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0e0f 
  Sound Server: ALSA v: k5.4.0-73-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: ce00 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IF-ID-1: docker0 state: down mac: <filter> 
Drives:
  Local Storage: total: 1.13 TiB used: 50.75 GiB (4.4%) 
  ID-1: /dev/sda vendor: Emtec model: X150 240GB size: 223.57 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: E1.2 scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
  speed: 1.5 Gb/s rotation: 7200 rpm serial: <filter> rev: CC43 scheme: MBR 
Partition:
  ID-1: / size: 92.68 GiB used: 22.52 GiB (24.3%) fs: ext4 dev: /dev/sda5 
  ID-2: /home size: 233.68 GiB used: 25.21 GiB (10.8%) fs: ext4 
  dev: /dev/sdb5 
  ID-3: swap-1 size: 14.90 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb7 
Sensors:
  System Temperatures: cpu: 32.5 C mobo: N/A gpu: nvidia temp: 40 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 50% 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/home:Alexx2000.list 
  1: deb http://download.opensuse.org/repositories/home:/Alexx2000/xUbuntu_20.04/ /
  Active apt repos in: /etc/apt/sources.list.d/lazygit-team-release-focal.list 
  1: deb http://ppa.launchpad.net/lazygit-team/release/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb https://ftp.rnl.tecnico.ulisboa.pt/pub/linuxmint-packages ulyssa main upstream import backport
  2: deb http://ftp.rnl.tecnico.ulisboa.pt/pub/ubuntu/archive focal main restricted universe multiverse
  3: deb http://ftp.rnl.tecnico.ulisboa.pt/pub/ubuntu/archive focal-updates main restricted universe multiverse
  4: deb http://ftp.rnl.tecnico.ulisboa.pt/pub/ubuntu/archive focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/packagecloud-shiftky-desktop.list 
  1: deb [arch=amd64] https://packagecloud.io/shiftkey/desktop/any/ any main
Info:
  Processes: 335 Uptime: 5m Memory: 11.68 GiB used: 2.86 GiB (24.5%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 8/9 
  Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[KammutierSpule]

If I understand your text correctly, I don't see anything unusual.
Something is being read or written on the disc.

I have an SSD for / and this HDD is for /home/ and other software/data I manually install.

The things is that this spindown/spinup thing (on disk diagnostic is shows as Start/Stop count) happens mostly at system startup during some minutes ... every about 5 seconds the disk goes down.. a clack sound is heard and spinup/searching again.
Then after that it gets stable and only oasionaly happens after this initial start.

This is a new HDD I bought some months ago.

The previous one that was installed has also with this problem but it only started recently. So I'm wondering if it was after some Mint update.
After I got this new HDD I installed a new system.

I have a good power supply

Is there any logs I can check to see some activity or why the HDD starts/stop ?

[SMG]

I have an SSD for / and this HDD is for /home/ and other software/data I manually install.

Your data indicates you have / on the SSD and /home and /swap on the HDD. At start-up, swap must be initialized even if it is not being used at that time.

Code: Select all

Drives:
  Local Storage: total: 1.13 TiB used: 50.75 GiB (4.4%) 
  ID-1: /dev/sda vendor: Emtec model: X150 240GB size: 223.57 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: E1.2 scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
  speed: 1.5 Gb/s rotation: 7200 rpm serial: <filter> rev: CC43 scheme: MBR 
Partition:
  ID-1: / size: 92.68 GiB used: 22.52 GiB (24.3%) fs: ext4 dev: /dev/sda5 
  ID-2: /home size: 233.68 GiB used: 25.21 GiB (10.8%) fs: ext4 
  dev: /dev/sdb5 
  ID-3: swap-1 size: 14.90 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb7 

The things is that this spindown/spinup thing (on disk diagnostic is shows as Start/Stop count) happens mostly at system startup during some minutes ... every about 5 seconds the disk goes down.. a clack sound is heard and spinup/searching again.
Then after that it gets stable and only oasionaly happens after this initial start.

I do not understand what you think is wrong about what is happening. Do you not think that the disk should be used at all? You have two different partitions on it. Both need to be initialized and then both will be used during the course of a session.

Is there any logs I can check to see some activity or why the HDD starts/stop ?

You want to know if there is a log for every read-write being done? Someone else will have to help with that as I do not understand the end goal of your question and thus am not able to help.

[KammutierSpule]

I will try to better clarify.
There is a sound/noise that all HDD do when they are power up.
This sound/noise happens when, for instance, put the PC in standby (HDD spin down/turn off) and after back from standby ( HDD turns On, spinup)
I suppose we all recognise this sound ?

Do you not think that the disk should be used at all? You have two different partitions on it. Both need to be initialized and then both will be used during the course of a session.

I was expecting that the HDD is used all the time, so it should be all time on and spinning and never turns off.
but that is not happening, I can hear it go off .. then on .. off ...on ..off

[SMG]

I was expecting that the HDD is used all the time, so it should be all time on and spinning and never turns off.
but that is not happening, I can hear it go off .. then on .. off ...on ..off

I would not expect /home or /swap to be in use all the time, but that is just a guess on my part. I would defer to others with more knowledge on the topic.

[KammutierSpule]

I found something, when I experience the problem I can see the following kind of (lots of) messages start appearing at $ cat /var/log/syslog
then after some minutes it gets less frequent until it eventually stop

Code: Select all

May 18 07:00:31 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  386.461919] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 18 07:00:31 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  386.471256] ata5.00: configured for UDMA/33
May 18 07:00:31 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  386.471282] ata5: EH complete
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162182] ata5.00: exception Emask 0x50 SAct 0x19000000 SErr 0x90a00 action 0xe frozen
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162191] ata5.00: irq_stat 0x00400000, PHY RDY changed
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162196] ata5: SError: { Persist HostInt PHYRdyChg 10B8B }
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162202] ata5.00: failed command: READ FPDMA QUEUED
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162212] ata5.00: cmd 60/08:c0:c0:11:01/00:00:1d:00:00/40 tag 24 ncq dma 4096 in
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162212]          res 40/00:e0:b0:bc:17/00:00:1c:00:00/40 Emask 0x50 (ATA bus error)
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162217] ata5.00: status: { DRDY }
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162221] ata5.00: failed command: READ FPDMA QUEUED
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162230] ata5.00: cmd 60/08:d8:58:b4:3c/00:00:15:00:00/40 tag 27 ncq dma 4096 in
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162230]          res 40/00:e0:b0:bc:17/00:00:1c:00:00/40 Emask 0x50 (ATA bus error)
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162234] ata5.00: status: { DRDY }
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162237] ata5.00: failed command: READ FPDMA QUEUED
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162246] ata5.00: cmd 60/08:e0:b0:bc:17/00:00:1c:00:00/40 tag 28 ncq dma 4096 in
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162246]          res 40/00:e0:b0:bc:17/00:00:1c:00:00/40 Emask 0x50 (ATA bus error)
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162249] ata5.00: status: { DRDY }
May 18 07:00:50 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  405.162256] ata5: hard resetting link
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.114320] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126288] ata5.00: configured for UDMA/33
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126316] sd 4:0:0:0: [sdb] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126322] sd 4:0:0:0: [sdb] tag#27 Sense Key : Illegal Request [current] 
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126327] sd 4:0:0:0: [sdb] tag#27 Add. Sense: Unaligned write command
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126332] sd 4:0:0:0: [sdb] tag#27 CDB: Read(10) 28 00 15 3c b4 58 00 00 08 00
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126337] blk_update_request: I/O error, dev sdb, sector 356299864 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126366] sd 4:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126370] sd 4:0:0:0: [sdb] tag#28 Sense Key : Illegal Request [current] 
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126374] sd 4:0:0:0: [sdb] tag#28 Add. Sense: Unaligned write command
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126378] sd 4:0:0:0: [sdb] tag#28 CDB: Read(10) 28 00 1c 17 bc b0 00 00 08 00
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126382] blk_update_request: I/O error, dev sdb, sector 471317680 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
May 18 07:00:55 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  410.126404] ata5: EH complete
May 18 07:01:00 kammutierspule-GA-78LMT-USB3-6-0 systemd[1]: Starting Ubuntu Advantage APT and MOTD Messages...
May 18 07:01:00 kammutierspule-GA-78LMT-USB3-6-0 systemd[1]: ua-messaging.service: Succeeded.
May 18 07:01:00 kammutierspule-GA-78LMT-USB3-6-0 systemd[1]: Finished Ubuntu Advantage APT and MOTD Messages.
May 18 07:01:01 kammutierspule-GA-78LMT-USB3-6-0 rtkit-daemon[1743]: Supervising 4 threads of 2 processes of 1 users.
May 18 07:01:01 kammutierspule-GA-78LMT-USB3-6-0 rtkit-daemon[1743]: message repeated 3 times: [ Supervising 4 threads of 2 processes of 1 users.]
May 18 07:01:01 kammutierspule-GA-78LMT-USB3-6-0 rtkit-daemon[1743]: Successfully made thread 5280 of process 4577 owned by '1000' RT at priority 10.
May 18 07:01:01 kammutierspule-GA-78LMT-USB3-6-0 rtkit-daemon[1743]: Supervising 5 threads of 3 processes of 1 users.
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510429] ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510434] ata5.00: irq_stat 0x00400000, PHY RDY changed
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510437] ata5: SError: { Persist HostInt PHYRdyChg 10B8B }
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510439] ata5.00: failed command: FLUSH CACHE EXT
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510445] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 27
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510445]          res 40/00:b8:d0:16:01/00:00:1d:00:00/40 Emask 0x50 (ATA bus error)
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510448] ata5.00: status: { DRDY }
May 18 07:01:05 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  420.510452] ata5: hard resetting link
May 18 07:01:10 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  425.462574] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 18 07:01:10 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  425.464800] ata5.00: configured for UDMA/33
May 18 07:01:10 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  425.464803] ata5.00: retrying FLUSH 0xea Emask 0x50
May 18 07:01:10 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  425.464983] ata5: EH complete
May 18 07:01:33 kammutierspule-GA-78LMT-USB3-6-0 anacron[975]: Job `cron.daily' terminated
May 18 07:01:33 kammutierspule-GA-78LMT-USB3-6-0 anacron[975]: Normal exit (1 job run)
May 18 07:01:33 kammutierspule-GA-78LMT-USB3-6-0 systemd[1]: anacron.service: Succeeded.
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367337] ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367345] ata5.00: irq_stat 0x00400000, PHY RDY changed
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367350] ata5: SError: { Persist HostInt PHYRdyChg 10B8B }
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367354] ata5.00: failed command: FLUSH CACHE EXT
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367364] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 17
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367364]          res 40/00:00:68:20:81/00:00:16:00:00/40 Emask 0x50 (ATA bus error)
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367369] ata5.00: status: { DRDY }
May 18 07:01:56 kammutierspule-GA-78LMT-USB3-6-0 kernel: [  471.367375] ata5: hard resetting link

[KammutierSpule]

I believe I fixed the issue:

I changed grub to

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=noncq"

and then run the following commands:

Code: Select all

sudo touch /forcefsck
sudo reboot
fsck /dev/sdaX
e2fsck -y /dev/sdaX

[Pjotr]

I'm not sure about the desirability of that NCQ disabling.... This is how I used to deal with that problem, namely by tweaking hdparm:
https://easylinuxtipsproject.blogspot.c ... .html#ID13
(item 13)

As I have no spinning hard disks any more, only SSDs, I haven't used this tweak for quite some time. But at the time it worked well.

[KammutierSpule]

Actually, I didn't solved the completely problem yet, now I got a different messages:

Code: Select all

[21969.909584] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[21969.911288] ata3.00: configured for UDMA/133
[22038.256043] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[22038.264256] ata3.00: configured for UDMA/133
[22099.662264] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[22099.676932] ata3.00: configured for UDMA/133
[22114.666510] ata3: limiting SATA link speed to 1.5 Gbps
[22119.646925] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[22119.658670] ata3.00: configured for UDMA/133
[22243.119357] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[22243.121055] ata3.00: configured for UDMA/133

[KammutierSpule]

Now it shows different message errors:

Code: Select all

May 20 09:32:59  kernel: [  344.977058] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 20 09:32:59  kernel: [  344.979271] ata3.00: configured for UDMA/33
May 20 09:32:59  kernel: [  344.979287] ata3: EH complete
May 20 09:33:01  kernel: [  346.697041] ata3.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen
May 20 09:33:01  kernel: [  346.697050] ata3.00: irq_stat 0x00400000, PHY RDY changed
May 20 09:33:01  kernel: [  346.697058] ata3: SError: { Persist HostInt PHYRdyChg 10B8B }
May 20 09:33:01  kernel: [  346.697063] ata3.00: failed command: READ DMA EXT
May 20 09:33:01  kernel: [  346.697073] ata3.00: cmd 25/00:10:08:bc:17/00:00:1c:00:00/e0 tag 2 dma 8192 in
May 20 09:33:01  kernel: [  346.697073]          res 50/00:00:87:1c:c1/00:00:01:00:00/e1 Emask 0x50 (ATA bus error)
May 20 09:33:01  kernel: [  346.697078] ata3.00: status: { DRDY }
May 20 09:33:01  kernel: [  346.697085] ata3: hard resetting link
May 20 09:33:06  kernel: [  351.701074] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 20 09:33:06  kernel: [  351.716260] ata3.00: configured for UDMA/33
May 20 09:33:06  kernel: [  351.716291] sd 3:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 20 09:33:06  kernel: [  351.716297] sd 3:0:0:0: [sdb] tag#2 Sense Key : Illegal Request [current] 
May 20 09:33:06  kernel: [  351.716301] sd 3:0:0:0: [sdb] tag#2 Add. Sense: Unaligned write command
May 20 09:33:06  kernel: [  351.716306] sd 3:0:0:0: [sdb] tag#2 CDB: Read(10) 28 00 1c 17 bc 08 00 00 10 00
May 20 09:33:06  kernel: [  351.716311] blk_update_request: I/O error, dev sdb, sector 471317512 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
May 20 09:33:06  kernel: [  351.716347] ata3: EH complete
May 20 09:33:16  kernel: [  362.197121] ata3.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen
May 20 09:33:16  kernel: [  362.197129] ata3.00: irq_stat 0x00400000, PHY RDY changed
May 20 09:33:16  kernel: [  362.197135] ata3: SError: { Persist HostInt PHYRdyChg 10B8B }
May 20 09:33:16  kernel: [  362.197140] ata3.00: failed command: READ DMA EXT
May 20 09:33:16  kernel: [  362.197150] ata3.00: cmd 25/00:08:80:1a:81/00:00:1b:00:00/e0 tag 5 dma 4096 in
May 20 09:33:16  kernel: [  362.197150]          res 50/00:00:2f:15:81/00:00:1b:00:00/e0 Emask 0x50 (ATA bus error)
May 20 09:33:16  kernel: [  362.197154] ata3.00: status: { DRDY }
May 20 09:33:16  kernel: [  362.197161] ata3: hard resetting link
May 20 09:33:21  kernel: [  367.137075] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 20 09:33:21  kernel: [  367.138809] ata3.00: configured for UDMA/33
May 20 09:33:21  kernel: [  367.138825] ata3: EH complete
May 20 09:33:21  kernel: [  367.361077] ata3.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen
May 20 09:33:21  kernel: [  367.361084] ata3.00: irq_stat 0x00400000, PHY RDY changed
May 20 09:33:21  kernel: [  367.361089] ata3: SError: { Persist HostInt PHYRdyChg 10B8B }
May 20 09:33:21  kernel: [  367.361093] ata3.00: failed command: READ DMA
May 20 09:33:21  kernel: [  367.361101] ata3.00: cmd c8/00:40:40:31:08/00:00:00:00:00/e0 tag 13 dma 32768 in
May 20 09:33:21  kernel: [  367.361101]          res 50/00:00:0f:21:81/00:00:1a:00:00/e0 Emask 0x50 (ATA bus error)
May 20 09:33:21  kernel: [  367.361104] ata3.00: status: { DRDY }
May 20 09:33:21  kernel: [  367.361110] ata3: hard resetting link
May 20 09:33:26  kernel: [  372.317092] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 20 09:33:26  kernel: [  372.322346] ata3.00: configured for UDMA/33
May 20 09:33:26  kernel: [  372.322367] sd 3:0:0:0: [sdb] tag#13 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 20 09:33:26  kernel: [  372.322372] sd 3:0:0:0: [sdb] tag#13 Sense Key : Illegal Request [current] 
May 20 09:33:26  kernel: [  372.322377] sd 3:0:0:0: [sdb] tag#13 Add. Sense: Unaligned write command
May 20 09:33:26  kernel: [  372.322382] sd 3:0:0:0: [sdb] tag#13 CDB: Read(10) 28 00 00 08 31 40 00 00 40 00
May 20 09:33:26  kernel: [  372.322387] blk_update_request: I/O error, dev sdb, sector 536896 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 0
May 20 09:33:26  kernel: [  372.322421] ata3: EH complete
May 20 09:33:40  kernel: [  385.701132] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 20 09:33:40  kernel: [  385.702841] ata3.00: configured for UDMA/33

[SMG]

Now it shows different message errors:

Are you still using that kernel parameter or have you removed it? I would suggest removing it to make sure what errors you are seeing are because of your hardware and not because of the kernel parameter.

The errors you have listed seem to indicate there is either an issue with the drive or with the cable connecting it. However, it is hard to know what errors may be showing because of the kernel parameter.

[KammutierSpule]

Are you still using that kernel parameter or have you removed it? I would suggest removing it to make sure what errors you are seeing are because of your hardware and not because of the kernel parameter.

I removed that flags options in kernel.

I found on another forum someone suggested it was a fault in the cable.

I didn't changed the cable but I changed it to other free connector slot and the problem is gone.

Not sure what it means since it was working for years and only recently this problem started.

[SMG]

I didn't changed the cable but I changed it to other free connector slot and the problem is gone.

Not sure what it means since it was working for years and only recently this problem started.

Glad to hear the issue is resolved. It's possible the connection just became loose over time due to normal vibrations which can happen.