|
Bugzilla – Full Text Bug Listing |
| Summary: | grub config generation uses uuid's and is incompatible with cloning hard drives. Even on identical machines. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Forgotten User TerRWwXMnx <forgotten_TerRWwXMnx> |
| Component: | YaST2 | Assignee: | Michael Chang <mchang> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aschnell, mrmazda, snwint |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 42.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | grub.cfg | ||
|
Description
Forgotten User TerRWwXMnx
2016-08-13 19:47:26 UTC
Yes, cloning is not trivial and has many pitfalls, as a quick glance at clonezilla and ubuntu forums shows. :-) I don't see any other solution than making it the user's responsibility to adjust the config when using a cloned disk. Adding a 'fallback' that basically tries to boot from some random other disk instead of the intended one is imho not a good idea. Anyway, passing on to grub2 maintainer for comment. I don't see anything we can do in yast2 here. It seems to me since Dracut puts the root filesystem UUID into the initrd that a generic fallback menuitem could be provided to use the vmlinuz and initrd symlinks and leave out all the kernel cmdline parameters. I just tried booting TW on multi-multiboot host big41 after stripping everything except noresume and 3 from kernel cmdline and got a perfectly acceptable boot into TW 20170117 on EXT4 on /dev/sda23. This is automated batch bugzilla cleanup. The openSUSE 42.1 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or you can still observe it under openSUSE Leap 15.0, please feel free to reopen this bug against that version (see the "Version" component in the bug fields), or alternatively open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |