Hellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 10 days agodd: disk destroyerlemmy.caimagemessage-square83fedilinkarrow-up1448arrow-down15
arrow-up1443arrow-down1imagedd: disk destroyerlemmy.caHellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 10 days agomessage-square83fedilink
minus-squaremuhyb@programming.devlinkfedilinkarrow-up51·10 days agoAlways lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.
minus-squaremuhyb@programming.devlinkfedilinkarrow-up12·9 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.
minus-squareReginaPhalange@lemmy.worldlinkfedilinkarrow-up1·7 days 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
lsblk
beforedd
. 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.
First thing I do after loading the liveusb is write the “mylsblk” which does the much more sane thing of: