Hellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 16 hours agodd: disk destroyerlemmy.caimagemessage-square43fedilinkarrow-up1339arrow-down11cross-posted to: [email protected]
arrow-up1338arrow-down1imagedd: disk destroyerlemmy.caHellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 16 hours agomessage-square43fedilinkcross-posted to: [email protected]
minus-squaremuhyb@programming.devlinkfedilinkarrow-up35·13 hours agoAlways lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.
minus-squaremuhyb@programming.devlinkfedilinkarrow-up5·2 hours 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.