What is the meaning of these error messages in the system log, when I plug in [a 2.5" spinning-disk SATA drive](https://www.seagate.com/files/staticfiles/support/docs/samsung-ds/100698122c.pdf) that I _know_ works, using a [USB-to-SATA adapter](https://web.archive.org/web/20230401071626/https://sabrent.com/products/ec-ss31) ? Jun 25 16:08:07 hostname kernel: [181603.928983] scsi 6:0:0:0: Direct-Access SABRENT 2210 PQ: 0 ANSI: 6 Jun 25 16:08:07 hostname kernel: [181603.931640] sd 6:0:0:0: Attached scsi generic sg1 type 0 Jun 25 16:08:07 hostname kernel: [181603.938380] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK Jun 25 16:08:07 hostname kernel: [181603.938391] sd 6:0:0:0: [sdb] Sense Key : Illegal Request [current] Jun 25 16:08:07 hostname kernel: [181603.938398] sd 6:0:0:0: [sdb] Add. Sense: Invalid command operation code Jun 25 16:08:07 hostname kernel: [181603.939443] sd 6:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B) Jun 25 16:08:07 hostname kernel: [181603.939449] sd 6:0:0:0: [sdb] 0-byte physical blocks Jun 25 16:08:07 hostname kernel: [181603.942357] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled Jun 25 16:08:07 hostname kernel: [181603.943386] sd 6:0:0:0: [sdb] Asking for cache data failed Jun 25 16:08:07 hostname kernel: [181603.943393] sd 6:0:0:0: [sdb] Assuming drive cache: write through Jun 25 16:08:07 hostname kernel: [181603.944506] sd 6:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes) Jun 25 16:08:07 hostname kernel: [181603.948248] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK Jun 25 16:08:07 hostname kernel: [181603.948255] sd 6:0:0:0: [sdb] Sense Key : Illegal Request [current] Jun 25 16:08:07 hostname kernel: [181603.948257] sd 6:0:0:0: [sdb] Add. Sense: Invalid command operation code Jun 25 16:08:07 hostname kernel: [181603.960998] sd 6:0:0:0: [sdb] Attached SCSI disk Specifically: […] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK […] Sense Key : Illegal Request [current] […] Add. Sense: Invalid command operation code The device spins up fine mechanically with no unusual noises, but none of the partitions are being detected, and as a result, they don't show up in the file manager. I don't think this matters much, but just to provide some context, it's an Ubuntu 20.04-based distribution (elementary OS 6.1 Jólnir) running on a Samsung Series 9.

I have a computer, running Debian 12, that is equipped with 2 RDX (from dead Tandberg / Overland company) cartridge drives. One is an internal SATA, and one is an external USB. They are cartridge drives. That means that they can be without a cartridge inserted. Maybe because of that, the drives are not always assigned to the same device node. For example, if both have a cartridge, the SATA one is on sdb, and the second on sdc. If the SATA is empty and I reboot, the drive will be sdb and the SATA on sdc. The device have been swapped. I want to be sure they will always be at the same device, regardless of the fact they have a drive inserted or not. I guess I need to write a custom udev rule, but I am not sure on how to do so. I already have a udev rule to make it execute some action on drive cartridge insertion: KERNEL=="sd[a-z][0-9]", SUBSYSTEMS=="usb", ATTRS{vendor}=="TANDBERG", ACTION=="add", RUN+="/bin/systemctl start rdx_mount@%k.service" KERNEL=="sd[a-z][0-9]", SUBSYSTEMS=="scsi", ATTRS{vendor}=="TANDBERG", ACTION=="add", RUN+="/bin/systemctl start rdx_mount@%k.service" KERNEL=="sd[a-z][0-9]", SUBSYSTEMS=="usb", ATTRS{vendor}=="TANDBERG", ACTION=="remove", RUN+="/bin/systemctl stop rdx_mount@%k.service" KERNEL=="sd[a-z][0-9]", SUBSYSTEMS=="scsi", ATTRS{vendor}=="TANDBERG", ACTION=="remove", RUN+="/bin/systemctl stop rdx_mount@%k.service" Keeping these rules working, how can I force each drive on a predictable device?

I can't seem to get this PICe card working and I can't find any info/drivers about it on the internet. All the SATA HDDs in my server are connected using this card which came with the system. It works instantly plug-and-play in Windows. But on Linux, nothing. lspci shows the card but no drives or /dev/sdX devices show up, and I don't see any messages/errors regarding it in dmesg, not sure what I should be looking for though. I'm using Ubuntu Desktop 20.04 btw. (And if you're curious why desktop on a server, it's a headless box but I installed the desktop so I can VNC in as well as SSH in) Here is the card. It says "Newer MAXPower RAID mini-SAS 6G PCIe 2.0" EDIT: Here's what lspci -v shows: 06:00.0 RAID bus controller: HighPoint Technologies, Inc. Device 1e10 (rev 03) Subsystem: HighPoint Technologies, Inc. Device 0000 Physical Slot: 3 Flags: fast devsel Memory at 90940000 (64-bit, non-prefetchable) [disabled] [size=128K] Memory at 90900000 (64-bit, non-prefetchable) [disabled] [size=256K] Expansion ROM at 90960000 [disabled] [size=64K] Capabilities: Power Management version 3 Capabilities: MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: Express Endpoint, MSI 00 Capabilities: Advanced Error Reporting Capabilities: Virtual Channel

I am running kernel 6.12.10 and in the depth of my dmesg log, I found those entries:

kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
kernel: ata4.00: Model 'INTEL SSDSCKJF360A5L', rev 'LT2i', applying quirks: zeroaftertrim
kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out
kernel: ata4.00: supports DRM functions and may not be fully accessible
kernel: ata4.00: ATA-10: INTEL SSDSCKJF360A5L, LT2i, max UDMA/133
kernel: ata4.00: 703282608 sectors, multi 0: LBA48 NCQ (depth 32), AA
kernel: ata4.00: Features: Trust Dev-Sleep
kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out
kernel: ata4.00: supports DRM functions and may not be fully accessible
kernel: ata4.00: configured for UDMA/133
kernel: scsi 3:0:0:0: Direct-Access     ATA      INTEL SSDSCKJF36 LT2i PQ: 0 ANSI: 5
kernel: sd 3:0:0:0: Attached scsi generic sg0 type 0
kernel: sd 3:0:0:0: [sda] 703282608 512-byte logical blocks: (360 GB/335 GiB)
kernel: sd 3:0:0:0: [sda] Write Protect is off
kernel: sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kernel: sd 3:0:0:0: [sda] Preferred minimum I/O size 512 bytes
kernel:  sda: sda1 sda2 sda3 sda4 sda5 sda6
kernel: sd 3:0:0:0: [sda] Attached SCSI disk

What do the following messages mean? * supports DRM functions and may not be fully accessible * read cache: enabled, doesn't support DPO or FUA What does DRM stand for in this context? (I doubt it means digital rights management.) Are those messages related? These messages seem to be new. I cannot remember to have seen them previously. But I don't know since which kernel version they have started to appear.

I run Solaris 10 in Qemu vm on Linux host. All works fine (sata, usb, etc..) I ran on IDE because on some old version of libvirt/qemu Solaris 10 gave a lot of error (ioapic timeout and similar) if installed on SATA disk. Now finally those error disappear. To "migrate" Solaris from IDE to SATA I have only updated libvirt configuration (remove ide disk, add sata disk using old ide disk). Works fine but... From where vold take the information? On /etc/ the string c2t0d0s7 is only on file /etc/lvm/md.conf.

Since a couple weeks, I sporadically find in dmesg a bunch of errors similar to the following one:

[174745.892138] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[174745.892149] ata7.00: failed command: FLUSH CACHE EXT
[174745.892152] ata7.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 21
                         res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[174745.892163] ata7.00: status: { DRDY }
[174745.892169] ata7: hard resetting link
[174746.201093] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[174746.218236] ata7.00: configured for UDMA/133
[174746.218245] ata7.00: retrying FLUSH 0xea Emask 0x4
[174746.218356] ata7: EH complete

It is always ata7 and it is always this same exception Emask. I already looked at the SMART data of all my disks, but they seem to be healthy, I cannot see any weird numbers under reallocated sectors count or something like this. I tried this answer here https://superuser.com/a/617193 to find out the actuyl sdX disk name, I get the following:

# grep '[0-9]' /sys/class/scsi_host/host{0..9}/unique_id
/sys/class/scsi_host/host0/unique_id:1
/sys/class/scsi_host/host1/unique_id:2
/sys/class/scsi_host/host2/unique_id:3
/sys/class/scsi_host/host3/unique_id:4
/sys/class/scsi_host/host4/unique_id:5
/sys/class/scsi_host/host5/unique_id:6
/sys/class/scsi_host/host6/unique_id:7
/sys/class/scsi_host/host7/unique_id:8
/sys/class/scsi_host/host8/unique_id:9
/sys/class/scsi_host/host9/unique_id:10

if I interpret this correctly, the disk ata7 belongs to SCSI Host 6? I then tried to find which disk is at host 6:

# ls -l /sys/block/sd*
lrwxrwxrwx 1 root root 0 Nov 24 19:28 /sys/block/sda -> ../devices/pci0000:00/0000:00:11.4/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Nov 24 19:28 /sys/block/sdb -> ../devices/pci0000:00/0000:00:11.4/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Nov 24 19:28 /sys/block/sdc -> ../devices/pci0000:00/0000:00:11.4/ata3/host2/target2:0:0/2:0:0:0/block/sdc
lrwxrwxrwx 1 root root 0 Nov 24 19:28 /sys/block/sdd -> ../devices/pci0000:00/0000:00:11.4/ata4/host3/target3:0:0/3:0:0:0/block/sdd
lrwxrwxrwx 1 root root 0 Nov 24 19:28 /sys/block/sde -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sde
lrwxrwxrwx 1 root root 0 Nov 24 19:28 /sys/block/sdf -> ../devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdf
lrwxrwxrwx 1 root root 0 Nov 24 19:28 /sys/block/sdg -> ../devices/pci0000:00/0000:00:1f.2/ata7/host6/target6:0:0/6:0:0:0/block/sdg

to me, it looks like the host 6 has disk sdg attached. However, when I check the SMART log of disk sdg, I cannot see anything that is dramatically different to all other disks, so I am wondering, are my above assumptions correct at all? and how can I find out what causes this strange errors in my dmesg? they seem to appear randomly, sometimes there are a few per hour, sometimes there is none for days. Is my disk dying and I just need to replace it, or is my hardware the problem? how can I isolate this? This is on a production system, so unfortunately it will not be so simple to randomly pull drives, change hardware or power off the system.

I am working my way backwards through various historical Linux distributions and have come up against a roadblock with disk management. RHEL/CentOS 2.1 ships with Linux kernel 2.4.x, which includes very early support for SATA devices. I have already updated to the final release kernel version 2.4.9-e.74, which includes support for the necessary kernel module sata_sil.o. However, I can't get the attached device to appear when I run fdisk -l, so I cannot mount it. I can see my primary disk on the ATA bus:

# fdisk -l

Disk /dev/hda: 255 heads, 63 sectors, 15566 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1        64    512000   83  Linux
Partition 1 does not end on cylinder boundary:
     phys=(63, 221, 30) should be (63, 254, 63)
/dev/hda2            64       325   2097152   82  Linux swap
Partition 2 does not end on cylinder boundary:
     phys=(324, 242, 46) should be (324, 254, 63)
/dev/hda3           325     15567 122424320   83  Linux

My SATA drive is detected by the adapter itself but is not recognized by the operating system at boot, which I think is the source of the problem. I have to manually load the kernel module every time.

# modprobe -a sata_sil
  Vendor: ATA       Model: CT500MX500SSD1    Rev: M3CR
  Type:   Direct-Access                      ANSI SCSI revision: 05

The device is detected properly, which can be confirmed through dmesg.

# dmesg
...
SCSI subsystem driver Revision: 1.00
libata version 1.02 loaded.
sata_sil version 0.54
PCI: Found IRQ 10 for device 00:09.0
PCI: Sharing IRQ 10 with 00:04.2
ata1: SATA max UDMA/100 cmd 0xE89B3080 ctl 0xE89B308A bmdma 0xE89B3000 irq 10
ata2: SATA max UDMA/100 cmd 0xE89B30C0 ctl 0xE89B30CA bmdma 0xE89B3008 irq 10
ata1: dev 0 cfg 49:2f00 82:706b 83:7409 84:4163 85:7069 86:b409 87:4163 88:407f
ata1: dev 0 ATA, max UDMA/133, 976773168 sectors: lba48
ata1: dev 0 configured for UDMA/100
ata2: no device found (phy stat 00000000)
scsi0 : sata_sil
scsi1 : sata_sil
  Vendor: ATA       Model: CT500MX500SSD1    Rev: M3CR
  Type:   Direct-Access                      ANSI SCSI revision: 05

I can also see the device in /proc/scsi/scsi.

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: CT500MX500SSD1   Rev: M3CR
  Type:   Direct-Access                    ANSI SCSI revision: 05

Red Hat Enterprise Linux 2.1 uses an older kernel (2.4 series), which predates the /sys filesystem introduced in the 2.6 kernel series. Therefore, rescanning for devices in RHEL 2.1 has to be done differently than in later releases. ChatGPT provided the following recommendation. > **Rescan SCSI Bus Manually** > > In older systems, SATA devices were often treated as SCSI devices. You > can try forcing a rescan of the SCSI bus by writing to the > /proc/scsi/scsi interface. This can sometimes help the system > recognize new drives. > > To rescan the SCSI bus, do the following: > > First, identify the SCSI host adapter: >

>     cat /proc/scsi/scsi
>

> Then, trigger a rescan of the SCSI bus: >

>     echo "scsi add-single-device H C I L" > /proc/scsi/scsi
>

> Replace H, C, I, and L with the host, channel, ID, and LUN of > your drive. For example, if your device is on host 0, channel 0, ID 0, > and LUN 0, the command would be: >

>     echo "scsi add-single-device 0 0 0 0" > /proc/scsi/scsi
>

> Check dmesg for any output related to the new device. This did not have any result. I would like to get this working, as I have been able to get CentOS 3.9, 4.9, 5.11, and 6.10 all working with this same SATA adapter. I have other plans for the ATA bus and would prefer to have this system booting off of the SATA adapter, if possible. Although Silicon Image did release official Linux drivers, they only provided precompiled kernel modules, none of which are compatible. My only option is the sata_sil kernel module. From the experience I have gained working backwards through these older releases, I believe that there is nothing wrong with the driver and that this is some kind of user error. The sata_sil kernel module was not included in the original 2.4.9-e.40 kernel release, so I believe the issue is that the kernel module isn't loading before the system scans for attached devices, and I don't know how to get it working. I tried adding the following line to /etc/modules.conf, but it did not cause the kernel module to load during boot.

alias sii3112 sata_sil

I have tried running the kudzu a hardware detection utility.

kudzu --probe

I believe this is run automatically at boot anyways, but I can confirm that the adapter is being detected correctly, as well as the correct kernel module being specified for it by examining /etc/sysconfig/hwconf.

...
class: OTHER
bus: PCI
detached: 0
driver: sata_sil
desc: "CMD Technology Inc|Silicon Image SiI 3112 SATARaid Controller"
vendorId: 1095
deviceId: 3112
subVendorId: 1095
subDeviceId: 3112
pciType: 1
...

I tried adding modprobe sata_sil to /etc/rc.local. Although this does ensure that the kernel module is loaded at boot, this file is executed *after* all other init scripts, which is no different from loading it after logging in, which doesn't allow the device to appear in fdisk -l. I also tried creating a new initrd after loading the sata_sil kernel module. This didn't work either.

# mkinitrd initrd-2.4.9-e.74.img 2.4.9-e.74

What is the correct procedure to configure the system to load the sata_sil kernel module at boot in RHEL/CentOS 2.1 (kernel 2.4.x)? I would also like to know if it's possible to rescan the SCSI/SATA bus at runtime to get the drive working without having to reboot. Additional Information ---------------------- This question includes examples which indicate that I was testing with a Crucial MX500 500GB (CT500MX500SSD1). I don't know if LBA48 support was ever backported to this particular kernel, but this is not the source of the problem. I confirmed this by swapping the drive for a 128GB one and continue to have the same issue. Progress -------- I've managed to find a workaround to get these disks to be detected and mount. The initrd needs to be remade using the options --with=scsi_mod --with=sd_mod --with=sata_sil. Adding these modules to /etc/modules.conf doesn't make a difference.

mkinitrd --with=scsi_mod --with=sd_mod --with=sata_sil /boot/initrd-$(uname -r).img $(uname -r)

There is still one more step though. modprobe sata_sil still needs to be called after the system has booted, either manually or through rc.local. The output is also different from before, with additional output showing that the drive has been attached.

# modprobe sata_sil
  Vendor: ATA       Model: Samsung SSD 850   Rev: EXM0
  Type:   Direct-Access                      ANSI SCSI revision: 05
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 250069680 512-byte hdwr sectors (128036 MB)

Although this does allow me to mount a SATA drive, because the process does not occur automatically during the boot process, I cannot boot from this drive, which is my intention. I can confirm that this isn't an issue with the sata_sil kernel module specifically. I replicated the same problem and workaround with a Promise branded SATA controller. How can I get the system to load this module automatically and early enough so that it can be made bootable?

I am trying to install an auxiliary/slave SATA hard drive on an Ubuntu PC. The new drive is 2 TB. I am able to install 1 TB drives, however when I try the new 2 TB disk, it is not recognized. At first I believed the drive to be at fault and had it replaced. The replacement behaves in the same way, making me think there's a system problem/oversight. In the BIOS, the SATA mode is set to AHCI. The other options are disabled, IDE and RAID mode. The 2tb hdd does not seem to show up in the boot options. Just what I believe is the main drive and the DVD drive. Could it be that the BIOS or Mother board do not accept 2T HDDs? The mother board is an Asus P8Z68-M Pro and the BIOS version is 0402. "sudo fdisk -l" shows only the master drive and not the second disk: Disk /dev/sdb: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xdd82f21f Dispositivo Inicializar Start Fim Setores Size Id Tipo /dev/sdb1 * 2048 1928396799 1928394752 919,5G 83 Linux /dev/sdb2 1928398846 1953523711 25124866 12G 5 Estendida /dev/sdb5 1928398848 1953523711 25124864 12G 82 Linux swap / lspci returns: 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5) 00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01) 05:01.0 Multimedia audio controller: Xilinx Corporation RME Hammerfall DSP (rev 11) 06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 07:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller

I'm trying to install a CSL USB 3.0 express card to my Arch Linux system. However, when I do this, I get the following error message: > xhci_hcd 0000:05:00.0: xHCI host controller not responding, assume dead > xhci_hcd 0000:05:00.0: HC died; cleaning up I googled and tried adding the following kernal parameters intel_iommu=off Some sites also mention iommu I already tried adding kernel parameter intel_iommu=off pciehp.pciehp_force=1. **This unfortunately didn't help me anything.** I also tried to add: pciehp pciehp_force=1 And tried to do sudo modprobe pciehp pciehp_force=1 But Arch Linux complains that it doesn't find the kernel module pciehp. I didn't find any information on how to install pciehp kernel module on Arch Linux. Some say, it is build into the kernel or something. **debug information:** kernel version: 4.16.6-1-ARCH **lspci -nn** 05:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02) **dmesg** - **dmesg** with debugging xhci_hcd enabled and xhci_hcd greped - full **dmesg** **Mailing List Patches** - Patches for "Renesas uPD72020x workaround" don't work **References to places with people working on the problem:** Linux mailing list - Re: kernel does not receive any USB3.0 plug/unplug events from the Renesas upd720202 chipset - Patches for "Renesas uPD72020x workaround" don't work Other platforms - Linux Kernel Bug Tracker - bugzilla.kernel.org - Arch Linux forum discussion - bbs.archlinux.org

When trying to sudo dd if=/dev/sda of=dump.dd conv=noerror,sync on my Kingston SSD (SA400S37/120G, SBFK71E0) the dmesg log shows the following:

usb 4-4: new SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 scsi host0: uas
 scsi 0:0:0:0: Direct-Access     SATAFIRM    S11           0    PQ: 0 ANSI: 6
 sd 0:0:0:0: Attached scsi generic sg0 type 0
 sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
 sd 0:0:0:0: [sda] Write Protect is off
 sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
 sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
 sd 0:0:0:0: [sda] Attached SCSI disk
 
...

 sd 0:0:0:0: [sda] tag#29 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
 sd 0:0:0:0: [sda] tag#29 CDB: Read(10) 28 00 00 00 6e a0 00 04 00 00
 sd 0:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
 sd 0:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 00 00 e2 a0 00 04 00 00
 sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 30 inflight: CMD IN 
 ...
 scsi host0: uas_eh_device_reset_handler start
 usb 4-4: reset SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: device firmware changed
 scsi host0: uas_eh_device_reset_handler FAILED err -19
 sd 0:0:0:0: Device offlined - not ready after error recovery
 sd 0:0:0:0: Device offlined - not ready after error recovery
 ...
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 ce a0 00 04 00 00
 I/O error, dev sda, sector 52896 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 2
 ...
 sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s
 sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 00 7a a0 00 04 00 00
 I/O error, dev sda, sector 31392 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 2
 sd 0:0:0:0: rejecting I/O to offline device
 usb 4-4: USB disconnect, device number 8
 Buffer I/O error on dev sda, logical block 3412, async page read
 Buffer I/O error on dev sda, logical block 3412, async page read
 ...
 sd 0:0:0:0: [sda] Synchronizing SCSI cache
 sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
 usb 4-4: new SuperSpeed USB device number 9 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb-storage 4-4:1.0: USB Mass Storage device detected
 scsi host0: usb-storage 4-4:1.0
 usb 4-4: reset SuperSpeed USB device number 9 using xhci_hcd

I disabled UAS since "uas_eh_abort_handler" implies some issue related to it. After dd again I got the following:

usb 4-4: new SuperSpeed USB device number 11 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb 4-4: UAS is ignored for this device, using usb-storage instead
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 scsi 0:0:0:0: Direct-Access     SATAFIRM    S11           0    PQ: 0 ANSI: 6
 sd 0:0:0:0: Attached scsi generic sg0 type 0
 sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
 sd 0:0:0:0: [sda] Write Protect is off
 sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sd 0:0:0:0: [sda] Attached SCSI disk
 usb 3-1.4.1: reset high-speed USB device number 7 using xhci_hcd
 usb 4-4: reset SuperSpeed USB device number 6 using xhci_hcd
 usb 4-4: device firmware changed
 usb 4-4: USB disconnect, device number 6
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=31s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 4f fb 28 00 01 00 00
 I/O error, dev sda, sector 5241640 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 4f fc 28 00 01 00 00
 I/O error, dev sda, sector 5241896 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
 sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
 sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 4f fb 28 00 00 08 00
 I/O error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 device offline error, dev sda, sector 5241640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
 Buffer I/O error on dev sda, logical block 655205, async page read
 Buffer I/O error on dev sda, logical block 655206, async page read
 Buffer I/O error on dev sda, logical block 655206, async page read
 sd 0:0:0:0: [sda] Synchronizing SCSI cache
 sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
 usb 4-4: new SuperSpeed USB device number 7 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 usb 4-4: reset SuperSpeed USB device number 7 using xhci_hcd
 usb 4-4: USB disconnect, device number 7
 usb 4-4: new SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb 4-4: UAS is ignored for this device, using usb-storage instead
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 scsi 0:0:0:0: Direct-Access     SATAFIRM    S11           0    PQ: 0 ANSI: 6
 sd 0:0:0:0: Attached scsi generic sg0 type 0
 sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
 sd 0:0:0:0: [sda] Write Protect is off
 sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sd 0:0:0:0: [sda] Attached SCSI disk
 usb 4-4: reset SuperSpeed USB device number 8 using xhci_hcd
 usb 4-4: device firmware changed
 usb 4-4: USB disconnect, device number 8
 sd 0:0:0:0: [sda] Synchronizing SCSI cache
 sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
 usb 4-4: new SuperSpeed USB device number 9 using xhci_hcd
 usb 4-4: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00
 usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 usb 4-4: Product: Ugreen Storage Device
 usb 4-4: Manufacturer: Ugreen
 usb 4-4: SerialNumber: 26A1EE832456
 usb-storage 4-4:1.0: USB Mass Storage device detected
 usb-storage 4-4:1.0: Quirks match for vid 174c pid 1153: 800000
 scsi host0: usb-storage 4-4:1.0
 usb 4-4: reset SuperSpeed USB device number 9 using xhci_hcd

So the problem still remains. Someone has an idea what's going on and can help me? Also I'm interested why actually UAS is used and in the log it says about Attached SCSI even though it is a SATA.

Am Interested to know whether FC9 can be installed on internal sata SSD or it supports pata drives only?

I'm having trouble with a hard drive that is (supposed to be) a part of a RAID5. Here's is the smart log:

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-107-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     HUH721212ALE601
Serial Number:    8DHHX2AH
LU WWN Device Id: 5 000cca 253d55276
Firmware Version: LEGL0002
User Capacity:    12,000,138,625,024 bytes [12.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jun  2 09:58:42 2024 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x80) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (   87) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (   1) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   132   132   054    Pre-fail  Offline      -       96
  3 Spin_Up_Time            0x0007   253   253   024    Pre-fail  Always       -       78 (Average 35)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       92
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   140   140   020    Pre-fail  Offline      -       15
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       13784
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       18
 22 Unknown_Attribute       0x0023   100   100   025    Pre-fail  Always       -       100
 45 Unknown_Attribute       0x0023   100   100   001    Pre-fail  Always       -       1095233372415
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       277
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       277
194 Temperature_Celsius     0x0002   162   162   000    Old_age   Always       -       37 (Min/Max 15/57)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   177   177   000    Old_age   Always       -       35
231 Temperature_Celsius     0x0032   100   100   000    Old_age   Always       -       0
241 Total_LBAs_Written      0x0012   100   100   000    Old_age   Always       -       1249778606260
242 Total_LBAs_Read         0x0012   100   100   000    Old_age   Always       -       1530512354490

SMART Error Log Version: 1
ATA Error Count: 35 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 35 occurred at disk power-on lifetime: 13784 hours (574 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 01 68 08 00 00 40 08      00:16:02.030  WRITE FPDMA QUEUED
  2f 00 01 30 06 00 a0 08      00:16:02.028  READ LOG EXT
  2f 00 01 30 00 00 a0 08      00:16:02.027  READ LOG EXT
  2f 00 01 00 00 00 a0 08      00:16:02.027  READ LOG EXT
  2f 00 01 30 08 00 a0 08      00:16:02.026  READ LOG EXT

Error 34 occurred at disk power-on lifetime: 13784 hours (574 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 01 20 08 00 00 40 08      00:16:01.440  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 a0 08      00:16:01.440  FLUSH CACHE EXT
  60 08 00 08 00 00 40 08      00:16:01.427  READ FPDMA QUEUED
  60 01 f8 10 00 00 40 08      00:16:01.427  READ FPDMA QUEUED
  60 08 b8 08 00 00 40 08      00:16:01.427  READ FPDMA QUEUED

[...]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     13784         -
# 2  Short offline       Completed without error       00%     13386         -
# 3  Vendor (0x70)       Completed without error       00%     13326         -
# 4  Vendor (0x71)       Completed without error       00%     13325         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

As you can see several smart tests run througgh fine. However when i try to re-add the drive to my array, the drive keeps changing to a different device letter. From the dmesg output, it looks like there is a communication issue as it seems to dial down the interfact speed (dmesg output below). **Is this a cable issue, is the controller at fault, or is really the drive defective?** I have four of the drives in place, and this is the only one to cause issues - but I don't have a spare SATA port to test the drive at another port. The fill dmesg is available [here](https://pastebin.com/CwpCQuHK)

I bought an AXAGON SDSA-FP3 FASTport3 SATA to USB adapter. I have three HDDs which worked before. Through the adapter sometimes I can write data to them, sometimes they spin up but don't show up in fdisk -l or Double Commander and sometimes they show up but can't be mounted. rsync on one of the drives ended with

rsync: [receiver] write failed on "/file/on/the/connected/disk": Read-only file system (30)
rsync error: error in file IO (code 11) at receiver.c(378) [receiver=3.2.3]
rsync: [sender] write error: Broken pipe (32)

I started it again, it outputs many of this

rsync: [receiver] mkstemp "/file/on/the/connected/disk.[random 6 characters]" failed: Read-only file system (30)

I use debian. Is the adapter faulty? If not, how can I make it work?

I sometimes need to plug a disk into a disk bay. At other times, I have the very weird setup of connecting a SSD using a SATA-eSATA cable on my laptop while pulling power from a desktop. How can I safely remove the SATA disk from the system? This Phoronix forum thread has some suggestions: > justsumdood wrote: >> An(noymous)droid wrote: >> What then do you do on the software side before unplugging? Is it a simple "umount /dev/sd"[drive letter]? > after unmounting the device, to "power off" (or sleep) the unit: > > hdparm -Y /dev/sdX > (where X represents the device you wish to power off. for example: /dev/sdb) > > this will power the drive down allowing for it's removal w/o risk of voltage surge. Does this mean that the disk caches are properly flushed and powered off thereafter? Another suggestion from the same thread: > chithanh wrote: > All SATA and eSATA hardware is physically able to be hotplugged (ie. not damaged if you insert/pull the plug). > > How the chipset and driver handles this is another question. Some driver/chipset combinations do not properly handle hotplugging and need a warmplug command such as the following one: > > echo 0 - 0 > /sys/class/scsi_host/hostX/scan > Replace X with the appropriate number for your SATA/eSATA port. I doubt whether is the correct way to do so, but I cannot find some proof against it either. So, what is the correct way to remove an attached disk from a system? Assume that I have already unmounted every partition on the disk and ran sync. Please point to some official documentation if possible, I could not find anything in the Linux documentation tree, nor the Linux ATA wiki .

I am currently on a laptop running windows 11 and was looking to dual boot into arch preferably. However when I tried installing arch no recognised drives could be found. I then found by searching that this was just to SATA. I had three options in my BIOS for it. Disabled, ACHI, and RAID. The laptop was currently on RAID but if I changed the SATA to either disabled or ACHI windows either doesn’t have a boot option or blue screens when I try to. I have system restore points on windows but I am confused from things online on what the best approach is. Do i set to disabled and fully reinstall windows / (can i use a restore point if i do?) or is there a way to allow windows to boot with SATA disabled. Any help would be greatly appreciated, thanks :)

I have a problem with disks on HPE MicroServer gen10 plus. My server has 4 1TB HDD disks and 1 SSD NVMe on PCIE for OS. OS is Proxmox Virtual Environment 6.2-4. I do not have any problems with this SSD disk, but Debian is reporting problems with all HDDs (randomly). First of all - this is definitely not a problem with physical disk condition. SMART isn't reporting any real problems, I have checked all HDD disks with badblock command on pve. I also have checked this disks with GSmartControl on the same machine using HirensBoot (portable Windows) - long tests on all disks, no problems reported. I was looking for similar problem on Internet and I have found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550559 but none of this helped me. I tried to use this parameters in grub config /etc/default/grub **GRUB_CMDLINE_LINUX_DEFAULT="quiet libata.force=noncq,3.0G idex=noprobe combined_mode=libata"** in many combinations, none of this work, I am only getting different errors. I know that HPE do not support Debian platforms, but I believe this can be fix using special config. Before booting PVE this time, I formatted all HDDs on HirensBoot (diskpart -> clean -> convert gpt), after booting pve, I have created anew ZFS raidz storage so you may notice errors about missing storage.

[ 5738.090686] ata3.00: failed command: WRITE FPDMA QUEUED
[ 5738.090707] ata3.00: cmd 61/60:b8:98:0f:bf/01:00:14:00:00/40 tag 23 ncq dma 180224 out
                        res 50/00:58:00:12:bf/00:00:14:00:00/40 Emask 0x50 (ATA bus error)
[ 5738.090757] ata3.00: status: { DRDY }
[ 5738.090771] ata3.00: failed command: WRITE FPDMA QUEUED
[ 5738.090792] ata3.00: cmd 61/58:f8:a8:11:bf/00:00:14:00:00/40 tag 31 ncq dma 45056 out
                        res 50/00:58:00:12:bf/00:00:14:00:00/40 Emask 0x50 (ATA bus error)
[ 5738.090848] ata3.00: status: { DRDY }
[ 5738.090863] ata3: hard resetting link
[ 5738.364263] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 5738.365429] ata1.00: configured for UDMA/100
[ 5738.404235] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 5738.406149] ata3.00: configured for UDMA/133
[ 5738.406168] sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 5738.406170] sd 3:0:0:0: [sdc] tag#0 Sense Key : Illegal Request [current]
[ 5738.406173] sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unaligned write command
[ 5738.406176] sd 3:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 14 bf 12 00 00 00 58 00
[ 5738.406179] blk_update_request: I/O error, dev sdc, sector 348066304 op 0x1:(WRITE) flags 0x700 phys_seg 11 prio class 0
[ 5738.406238] zio pool=local-storage vdev=/dev/sdc1 error=5 type=2 offset=178208899072 size=45056 flags=180880
[ 5738.406258] sd 3:0:0:0: [sdc] tag#13 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 5738.406260] sd 3:0:0:0: [sdc] tag#13 Sense Key : Illegal Request [current]
[ 5738.406260] sd 3:0:0:0: [sdc] tag#13 Add. Sense: Unaligned write command
[ 5738.406261] sd 3:0:0:0: [sdc] tag#13 CDB: Write(10) 2a 00 14 bf 03 38 00 07 e8 00
[ 5738.406262] blk_update_request: I/O error, dev sdc, sector 348062520 op 0x1:(WRITE) flags 0x700 phys_seg 18 prio class 0
[ 5738.406705] zio pool=local-storage vdev=/dev/sdc1 error=5 type=2 offset=178206961664 size=1036288 flags=40080c80
[ 5738.406711] sd 3:0:0:0: [sdc] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 5738.406712] sd 3:0:0:0: [sdc] tag#18 Sense Key : Illegal Request [current]
[ 5738.406713] sd 3:0:0:0: [sdc] tag#18 Add. Sense: Unaligned write command
[ 5738.406714] sd 3:0:0:0: [sdc] tag#18 CDB: Read(10) 28 00 06 8e bb e0 00 01 00 00
[ 5738.406715] blk_update_request: I/O error, dev sdc, sector 110017504 op 0x0:(READ) flags 0x80700 phys_seg 20 prio class 0

dmesg - full lspci syslog udevadm info sda udevadm info sdb udevadm info sdc udevadm info sdd Do you have any ideas what can I do to fix this problem? Maybe you faced similar problem on HPE MicroServer platform? Thanks in advance.

I've added PCIe ASMedia SATA controller to my PC. It's working fine under win10 but not with ubuntu. lspci returned that: 01:00.0 IDE interface: ASMedia Technology Inc. Device 0624 (rev 01) (prog-if 85 [PCI native mode-only controller, supports bus mastering]) Subsystem: ASMedia Technology Inc. Device 1060 Flags: fast devsel, IRQ 16 I/O ports at e040 [size=8] I/O ports at e030 [size=4] I/O ports at e020 [size=8] I/O ports at e010 [size=4] I/O ports at e000 [size=16] Memory at df180000 (32-bit, non-prefetchable) [size=8K] Expansion ROM at df100000 [disabled] [size=512K] Capabilities: Kernel modules: pata_acpi Motherboard controller works fine under ahci: 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) (prog-if 01 [AHCI 1.0]) Subsystem: Elitegroup Computer Systems Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 124 Memory at df228000 (32-bit, non-prefetchable) [size=8K] Memory at df22d000 (32-bit, non-prefetchable) [size=256] I/O ports at f090 [size=8] I/O ports at f080 [size=4] I/O ports at f060 [size=32] Memory at df22c000 (32-bit, non-prefetchable) [size=2K] Capabilities: Kernel driver in use: ahci Kernel modules: ahci Any ideas what can I do to make it work?

Seagate Pipeline HD hard-drive not found in Asus UEFI bios. Though when the machine is booted into Arch Linux with a live usb on the same machine it shows up. Hard-Drive - Model Name: Pipeline HD - Model: ST3320310CS - Firmware: ES11 - Brand: Seagate - Size: 320GB Mother Board - Model Name: Asus B250 Expert Miner Software - Operating System: Arch Linux

I have an old mSATA SSD (model name: Plextor PX-128M6M), which is installed to an mSATA-to-USB enclosure with ASM1153E controller. I want to *(just logically, at the SSD controller level)* erase all of its data. However, it seemed that: 1. blkdiscard command does not actually erase all requested region of data, just the beginning 2GiB minus 32KiB of data was actually erased. 2. hdparm --trim-sector-ranges-stdin seems to work fine, however, the SSD controller *(of this model of SSD specifically, another model does not seem to behave like this)* seems to be protecting the first 8 sectors (4KiB of data) from being erased by TRIM command. -------- My attempts and experiments are as follows: 1. I was doing this under Ubuntu 23.04. 2. Thanks to the guides from Arch Wiki, I found that I have to set /sys/block/sdX/device/scsi_disk/*/provisioning_mode to unmap first. It was full initially. After that, I thought the system was then able to send SCSI UNMAP command (through UASP, translated into TRIM command by the controller) to the old SSD. 3. I then did this to the whole drive: blkdiscard -f -v /dev/sdX (sdX is the actual device name), it then reported that all bytes (matches with the disk capacity) was discarded (erased), however I found that both the main GPT and the backup GPT at the beginning/end of disk space were still not erased. 4. I created a partition sized 2GiB, and then filled it with random data drained from /dev/urandom. 5. blkdiscard -f -v /dev/sdX was done on the whole drive, hexdump then showed that the last 1MiB + 32KiB of the first partiton was not erased (the partition starts from LBA 2048, with a sector size of 512 Bytes). 6. After re-executing blkdiscard -f -v /dev/sdX1 on the new partition instead of the whole drive, hexdump showed that the last 32KiB of this partition was not erased. 7. I then tried hdparm --trim-sector-ranges-stdin, with a list of all sectors of the whole drive fed from stdin. This time the main GPT still stood, but all remaining data was erased to zero. 8. I filled the first 2048 sectors with /dev/urandom data. Then hdparm --trim-sector-ranges-stdin seemed to erase all data except the first 8 sectors (4KiB of data). -------- To confirm that the behavoir of first 8 sectors not being erased is enforced by the SSD controller instead of mSATA-to-USB chip: 9. I then installed this old Plextor SSD as an internal mSATA drive without USB enclosure. The first 8 sectors still survived after hdparm --trim-sector-ranges-stdin. 10. I have another newer Kingston-branded mSATA SSD. I tested it with hdparm --trim-sector-ranges-stdin, but all sectors went zero without one single exception, no matter it's USB-enclosed or directly installed as an internal drive.

There are [a lot of constants in the Kernel named with HORKAGE](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/ata/libata-core.c#n4029) , * ATA_HORKAGE_ZERO_AFTER_TRIM * ATA_HORKAGE_NODMA * ATA_HORKAGE_ATAPI_MOD16_DMA * ATA_HORKAGE_NO_DMA_LOG * ATA_HORKAGE_NO_ID_DEV_LO * ATA_HORKAGE_NO_LOG_DIR * ATA_HORKAGE_WD_BROKEN_LPM However, these are not really documented > Force horkage according to libata.force and whine about it. For consistency with link selection, device number 15 selects the first device connected to the host link. What does "horkage" mean?