Hellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 11 days agodd: disk destroyerlemmy.caimagemessage-square74fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imagedd: disk destroyerlemmy.caHellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 11 days agomessage-square74fedilink
minus-squaremuhyb@programming.devlinkfedilinkarrow-up0·11 days agoAlways lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.
minus-squaremuhyb@programming.devlinkfedilinkarrow-up0·11 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
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.