Hellfire103 to linuxmemesEnglish • 3 months agodd: disk destroyerlemmy.caimagemessage-square85fedilinkarrow-up1537arrow-down16cross-posted to: linuxhumor@lemmy.ml
arrow-up1531arrow-down1imagedd: disk destroyerlemmy.caHellfire103 to linuxmemesEnglish • 3 months agomessage-square85fedilinkcross-posted to: linuxhumor@lemmy.ml
minus-square@muhyb@programming.devlinkfedilink58•3 months agoAlways lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.
minus-square@muhyb@programming.devlinkfedilink17•3 months 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.
minus-square@ReginaPhalangelink1•3 months 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
Always
lsblkbeforedd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.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
First thing I do after loading the liveusb is write the “mylsblk” which does the much more sane thing of: