Hellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 3 days agodd: disk destroyerlemmy.caimagemessage-square37fedilinkarrow-up1330arrow-down14
arrow-up1326arrow-down1imagedd: disk destroyerlemmy.caHellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 3 days agomessage-square37fedilink
minus-squaremuhyb@programming.devlinkfedilinkarrow-up33·3 days agoAlways lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.
minus-squareReginaPhalange@lemmy.worldlinkfedilinkarrow-up1·9 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-squaremuhyb@programming.devlinkfedilinkarrow-up9·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.