clone no boot although edited fstab and menu.lst

English Install/Boot/Login
#1

I cloned a disk with Clonezilla. As Suse now use /dev/disk/by-id/ annoyance, I edit fstab and menu.lst to use /dev/sda instead.
I searched a few forums, and this is supposed to fix the booting problem.
The PC has only one disk so sda is it.
BTW I notice the partitions have no LABEL. Some other distros use this system for fstab, and cloning disks is so breezy, and
handles multiple disks.
The disk has structure: sda1=swap, sda2=/ and sda3=/home
So I edit fstab and menu.lst to agree with this.
Still no bootee. GRUB will lauch Suse - I get the splash screen, but progress bar remains a small dot until some messages spew forth.
One is “resume device /sda1 not found (ignoring)”
Later it collapses thus:
Could not find /dev/root
want me to fall back to /dev/disk/by-id/model-serial-number-huge-string
So what else needs changing?
There are 3 other files which contain the /dev/disk/by-id/ gibberish
/boot/grub/device.map
/etc/sysconfig/bootloader
/etc/init.d/boot.multipath

Or else can I change the by-id to the “edd-int13_dev80” format instead?
Points to same disk, but avoids the model and serial number disease.
Does Suse cope with that?

#2

Have you taken the backup and restored to the disk or done a disk-disk cloning?

#3

On 2014-01-19 09:56, retspeej wrote:
> I cloned a disk with Clonezilla. As Suse now use /dev/disk/by-id/
> annoyance, I edit fstab and menu.lst to use /dev/sda instead.
> I searched a few forums, and this is supposed to fix the booting
> problem.

You also need to recreate initrd.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

#4

You can use labels you just have to define them yourself. And tell the installer to use them.

Also you did not say what openSUSE version 13.1 uses grub 2 and no longer uses a menu.lst file