Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle eMMC and NVMe naming schemes (also for migrations) #1301

Closed
ProBackup-nl opened this issue Apr 14, 2017 · 1 comment
Closed

Handle eMMC and NVMe naming schemes (also for migrations) #1301

ProBackup-nl opened this issue Apr 14, 2017 · 1 comment
Assignees
@gdha
Labels
enhancement Adaptions and new features fixed / solved / done
Milestone
ReaR v2.1

Comments

@ProBackup-nl
Copy link
Contributor

ProBackup-nl commented Apr 14, 2017 •
edited

  • rear version: 2.00 git
  • OS version: Arch
  • rear configuration files: USB NETFS
  • Are you using legacy BIOS or UEFI boot? UEFI
  • Brief description of the issue: Migration from /dev/sda to /dev/nvme0n1 fails, due to device translation /dev/sda1 becomes /dev/nvme0n11 in the new disklayout.conf, which in the generated script becomes partition 11 (instead of 1).

Note:
/dev/nvme0n1 = first NVMe drive
/dev/nvme9n1 = 10th NVMe drive
/dev/nvme10n1 = 11th NVMe drive

I suspect similar failures for eMMC storage, using naming scheme /dev/mmcblk*

And Clonezilla lists that there are also nvme naming schemes like nvme*n2, nvme*n3:

  • Expand NVME support to disk device name like /dev/nvme0n2, and /dev/nvme0n3 instead of /dev/nvme0n1 only.
@ProBackup-nl ProBackup-nl mentioned this issue Apr 14, 2017
Merged
ProBackup-nl pushed a commit to ProBackup-nl/rear that referenced this issue Apr 15, 2017
Include mmcblk as bootable device type in guess_bootloader
f91c9b7 
Related to issue rear#1301
@ProBackup-nl ProBackup-nl mentioned this issue Apr 15, 2017
Merged
@gdha gdha self-assigned this Apr 18, 2017
@gdha gdha added this to the ReaR v2.1 milestone Apr 18, 2017
@gdha gdha added the enhancement Adaptions and new features label Apr 18, 2017
@jsmeix
Copy link
Member

jsmeix commented Apr 19, 2017

@ProBackup-nl
I assume this issue is "fixed/solved/done"
with #1302
and #1305
merged. If not, reopen it.

@jsmeix jsmeix closed this as completed Apr 19, 2017
@jsmeix jsmeix mentioned this issue Mar 18, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gdha gdha

Labels
enhancement Adaptions and new features fixed / solved / done
Projects
None yet
Milestone
ReaR v2.1
Development

No branches or pull requests
3 participants
@ProBackup-nl @gdha @jsmeix