On 2014-10-16 15:36, rady wrote:
> Hello robin_listas, thanks for the reply, with a little deeper research
> i found this post
>
> http://tinyurl.com/kq7pvcy
>
> gogalthorp reply helped me in finding what i need. for anybody that is
> curious how to resolve this on the image side and not the cloned side.
>
> simply edit /etc/fstab before you make a clone of the machine.
You also need to look at grub configuration, do not forget it.
> change it to
> Code:
> --------------------
>
> /dev/sda1 swap swap defaults 0 0
> /dev/sda2 / ext4 acl,user_xattr 1 1
> /dev/sda3 /home ext4 acl,user_xattr 1 2
> --------------------
Careful: the developers and the openSUSE documentation recommendation is
not to use such names, because they are not guaranteed to remain the
same. They can change from boot to boot, even on the same session after
hibernation. Some people do not experience this, so they think that it
is OK to use them. Others, like me, experience those changes every day.
Normally, sda is my boot disk. Today it is sdb, and sda is today the
disk caddy used for backups.
> this may not work if you have something different such as raid or dual
> boot or items of that nature im not 100% sure.
>
> what the old code says is: look for device /dev/disk/by-id/ata-LONG
> SERIAL NUMBER JUNK-part1 and mount as swap . BUT if the disk has changed
> (it will if you have platted a cloned image onto another HD)
> then it no longer can find this long serial number disk identifier junk.
The ‘id’ changes, the ‘uuid’ does not. There is a difference in the
name: “uuid≠id”.
> changing it to sda# , it no longer looks for this disk by its long
> string of junk instead it looks for disk 1 partition 1 so on so forth.
> hopes this helps others.
Careful. The official recommendation is NOT to use names such as sda,
sdb, etc. On upgrades, YaST sometimes sees these names and aborts,
telling you to change the names before trying again.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)