Hellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 2 days agodd: disk destroyerlemmy.caimagemessage-square68fedilinkarrow-up1476arrow-down15cross-posted to: linuxhumor@lemmy.ml
arrow-up1471arrow-down1imagedd: disk destroyerlemmy.caHellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 2 days agomessage-square68fedilinkcross-posted to: linuxhumor@lemmy.ml
minus-squaremuhyb@programming.devlinkfedilinkarrow-up53·2 days agoAlways lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.
minus-squaremuhyb@programming.devlinkfedilinkarrow-up13·1 day 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.
deleted by creator