Tutorial [Script Collection][2025-08-29] IPSet-based Firewall & Tunnel Director, WireGuard Port Forwarder, SSD Trimming, and more

[XIII]

I have other values:

➜ cat /sys/block/sda/queue/discard_max_bytes

4294966784

➜ cat /sys/block/sda/queue/discard_granularity

4096

 

[kuchkovsky]

File systemp is ext4:
/dev/sda1 ext4 57431276 2203612 52280544 4% /tmp/mnt/SSD

cat /sys/block/sda/queue/discard_max_bytes
0
cat /sys/block/sda/queue/discard_granularity
0

The empty values for the queue mean that UNMAP was not properly applied to the device, even though the mode is set by the unmap script. I think it's either the enclosure or the SSD that isn't supported. I'll probably add an explicit error message for such cases to the script by checking these values.

What's odd is that it shows up as "VLI Manufacturer String" - it's just a generic name from the controller. The vendor should have given a specific name to the device to make it recognizable. What brand is your enclosure/SSD?

I have other values:

➜ cat /sys/block/sda/queue/discard_max_bytes

4294966784

➜ cat /sys/block/sda/queue/discard_granularity

4096

Your drive reports proper values. What file system are you using? ext4?

I tested TRIM on my second drive formatted as NTFS, and it didn't work (which was expected), but the error message was different:

ssd_trim: ERROR: fstrim: FITRIM: Inappropriate ioctl for device

 

[XIII]

What file system are you using? ext4?

Yes:

➜ mount | grep ssd
/dev/sda1 on /tmp/mnt/ssd type ext4 (rw,nodev,relatime)

 

[XIII]

Does this help determining whether TRIM is supported?

➜ lsblk -D /dev/sda1
NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
sda1        0        4K       4G         0

According to the link below a value greater than zero for DISC-MAX would mean that TRIM might be enabled?

Enabling TRIM on an external SSD on a Raspberry Pi | Jeff Geerling

www.jeffgeerling.com