Hellfire103 to [email protected]English • 3 days agodd: disk destroyerlemmy.camessage-square75fedilinkarrow-up1499
arrow-up1499imagedd: disk destroyerlemmy.caHellfire103 to [email protected]English • 3 days agomessage-square75fedilink
minus-square@[email protected]linkfedilink54•3 days agoAlways lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.
minus-square@[email protected]linkfedilink1•3 hours agoFirst thing I do after loading the liveusb is write the “mylsblk” which does the much more sane thing of: lsblk -o NAME,LABEL,PARTLABEL,UUID,SIZE,MOUNTPOINTS
minus-square@[email protected]linkfedilink14•2 days agoIt’s a design thing. BIOS can know NVMe disks’ location because they’re directly mounted to PCIe. SATA isn’t like this. Similar logic with the RAM slots.
Always
lsblkbeforedd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.First thing I do after loading the liveusb is write the “mylsblk” which does the much more sane thing of:
Why is this?
It’s a design thing. BIOS can know NVMe disks’ location because they’re directly mounted to PCIe. SATA isn’t like this. Similar logic with the RAM slots.
deleted by creator