On 2025-08-27 18:01:58 [+0900], Damien Le Moal wrote: > Yep, looks like it. > What is the driver used for that "PowerEdge R6525 which exposes a "DELLBOSS VD" > device with firmware MV.R00-0" ? Is it the regular ahci driver ? > If yes, we can quirk it to limit the max command size, but we would need to > know what the limit is. That means repeating that test with varying max command > sise (max_sectors_kb) to try to figure out the threshold. issued 'dd if=/dev/sda of=/dev/null bs=4M count=1 iflag=direct' | echo 3584 > /sys/block/sda/queue/max_sectors_kb survives | echo 4096 > /sys/block/sda/queue/max_sectors_kb dies after a few attempts. | lrwxrwxrwx 1 root root 0 Aug 27 11:01 0:0:0:0 -> ../../../devices/pci0000:a0/0000:a0:03.1/0000:a1:00.0/ata1/host0/target0:0:0/0:0:0:0 | a1:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11) | Subsystem: Dell BOSS-S1 Adapter | Kernel driver in use: ahci | Kernel modules: ahci so a Marvell one. Interesting. > And maybe contact Dell support too if this is still a supported device. > (I have zero experience with this, no idea what that DELLBOSS VD is...) There are two physical disks which are behind this controller and exposed as one virtual device after applying some raid magic. I have no idea if this limitation is due to the physical device or the controller. Now, how do I put this. The disk behind it is an INTEL SSDSCKKB240G8R. The firmware XC31DL6P exposed this problem. After an update to XC31DL6R the problem is gone. Sebastian
