Hellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 8 days agodd: disk destroyerlemmy.caimagemessage-square85fedilinkarrow-up1525arrow-down16
arrow-up1519arrow-down1imagedd: disk destroyerlemmy.caHellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 8 days agomessage-square85fedilink
minus-squaremuhyb@programming.devlinkfedilinkarrow-up56·8 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·6 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
minus-squaremuhyb@programming.devlinkfedilinkarrow-up15·8 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.
deleted by creator