https://linux.meerstory.com/categories/storage/Recent content in Storage on MeerStoryHugoen-usWed, 14 Oct 2026 01:20:16 +0900https://linux.meerstory.com/ubuntu/20261014_011947_62/Wed, 14 Oct 2026 01:20:16 +0900https://linux.meerstory.com/ubuntu/20261014_011947_62/<h2 id="overview">Overview</h2> <p>Reliable storage mounting across Linux environments hinges on stable volume identifiers. Because legacy device names like <code>/dev/sda</code> can unpredictably shift between hardware reboots, systems engineers rely on Universally Unique Identifiers (UUIDs) to pin down targets. This tutorial breaks down the standard utility for the job—<code>blkid</code>—explaining how to extract partition identifiers, inspect filesystem signatures, filter block attributes, and safely feed those identifiers into your persistent <code>/etc/fstab</code> configuration.</p> <h2 id="exploring-block-device-layouts-and-global-attributes-with-blkid">Exploring Block Device Layouts and Global Attributes with blkid</h2> <p>Before querying underlying metadata, you can inspect the operational drive hierarchy using <code>lsblk</code>. This offers a bird&rsquo;s-eye view of active partition boundaries, block capacities, and attached mount points across internal NVMe or SATA media.</p>https://linux.meerstory.com/ubuntu/20261014_011001_61/Wed, 14 Oct 2026 01:10:31 +0900https://linux.meerstory.com/ubuntu/20261014_011001_61/<h2 id="overview">Overview</h2> <p>Modern Linux administration relies heavily on <code>blkdiscard</code> to quickly refresh solid-state drives (SSDs) and NVMe media by issuing low-level TRIM directives across block ranges. In this walkthrough, we bypass the dangers of running wipe routines directly on physical hardware by constructing an isolated loopback block device. Following along gives you hands-on experience experimenting with <code>blkdiscard</code> syntax, parameters, and wiping mechanics—essential skills for sanitizing disks and restoring drive throughput before redeployment.</p>