Cloning - 12.3 Hanging on boot - started show plymouth boot screen

Hey - your input would be greatly appreciated.

I installed and updated opensuse 12.3 on a system that is running AMD FM2 with a Samsung Pro SSD drive.

I build this with the idea of being able to clone this off to a different drive.

It didn’t seem to matter if I used the small efi partition with a swap and ext4 file system or if I kept it just like the system that it is replacing with just a swap and ext4.

When cloning I am using Clonezilla, it looks like it clones properly but when it boots it gets stuck at ‘Started Show Plymouth Boot Screen’ for a minute or so then it finally gets to a login screen.

If I put the hard drive that I originally installed it on boots very quick and does have this issue.

Thanks Jeff

On 2014-10-15 00:06, jedaon12 wrote:

> When cloning I am using Clonezilla, it looks like it clones properly but
> when it boots it gets stuck at ‘Started Show Plymouth Boot Screen’ for
> a minute or so then it finally gets to a login screen.

Perhaps “systemd-analyze critical-chain” or systemd-analyze blame"" show
something.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

I just did the systemd-analyze blame and the one the boots the fastest is about 1000ms slower than the one that takes longer to boot.

This is the same brand / size of SSD in the same machine that was cloned by going to an image then back to the other drive.

Any suggestions?

Thanks Jeff

On 2014-10-15 15:56, jedaon12 wrote:
>
> I just did the systemd-analyze blame and the one the boots the fastest
> is about 1000ms slower than the one that takes longer to boot.
>
> This is the same brand / size of SSD in the same machine that was cloned
> by going to an image then back to the other drive.
>
> Any suggestions?

Disable plymouth and boot in verbose mode, and watch the messages…


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

I did that and is seems to be getting stuck on the hard drive.

The hard drive that I am cloning it to is the same brand and model.

I did notice that it has the serial number after Samsung_SSD_840_PRO_Series_SERIALNUMBER-part1

Where do I go to change that? Also is there a way to generalize it to just Samsung_SSD_840_PRO_Series

Appreciate the response

Jeff

On 2014-10-15 18:36, jedaon12 wrote:
>
> I did that and is seems to be getting stuck on the hard drive.
>
> The hard drive that I am cloning it to is the same brand and model.
>
> I did notice that it has the serial number after
> Samsung_SSD_840_PRO_Series_SERIALNUMBER-part1
>
> Where do I go to change that? Also is there a way to generalize it to
> just Samsung_SSD_840_PRO_Series

No, the serial number is what it is, you can not change it. What you should check is if you have something that is still referring the old serial number and edit it. Obvious candidates are fstab and grub. And then you have to run mkinitrd.

This may cause a boot delay: the system tries to open a partition, fails, then tries to locate it somewhere else, and this takes time.

Another possibility is that the new drive uses a different kernel driver. mkinitrd should adjust this. I think.

These are the available partition identifiers:


Telcontar:/etc # l /dev/disk/
total 0
drwxr-xr-x  7 root root  140 Oct  1 22:21 ./
drwxr-xr-x 19 root root 6620 Oct 15 05:04 ../
drwxr-xr-x  2 root root 4160 Oct 15 03:58 by-id/
drwxr-xr-x  2 root root  800 Oct 15 03:58 by-label/
drwxr-xr-x  2 root root   80 Oct  1 22:21 by-partuuid/
drwxr-xr-x  2 root root 1060 Oct 15 03:58 by-path/
drwxr-xr-x  2 root root  860 Oct 15 03:58 by-uuid/
Telcontar:/etc #

Any type will work. Some are cloned, and some are not. Also, notice that a device may have several ‘id’ names:


Telcontar:/etc # l /dev/disk/by-id/ | grep sdb6
lrwxrwxrwx 1 root root   10 Oct  1 22:21 ata-ST3500418AS_SERIAL-part6 -> ../../sdb6
lrwxrwxrwx 1 root root   10 Oct  1 22:21 scsi-1ATA_ST3500418AS_SERIAL-part6 -> ../../sdb6
lrwxrwxrwx 1 root root   10 Oct  1 22:21 scsi-SATA_ST3500418AS_SERIAL-part6 -> ../../sdb6
lrwxrwxrwx 1 root root   10 Oct  1 22:21 wwn-0x5000.....-part6 -> ../../sdb6
Telcontar:/etc #

I’m not familiar with “wwn…”, but it appears not to have the serial number.

Me, I use LABEL.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Thanks I was able to get everything going by editing the serial number of the hard drive.

I appreciate all the help…thanks for the quick responses.

Jeff

PS - I know this is not the section, I posted this is network / internet but I haven’t received any response.

Not sure how much you know about VNC, but with this same installation opensuse 12.3 KDE I am trying to VNC into the box and it only works if a user is logged in. This is an issue since I plan on using this for a database server that wont have a keyboard / mouse/ or monitor.

Any suggestions?

On 2014-10-19 00:16, jedaon12 wrote:
>
> Thanks I was able to get everything going by editing the serial number
> of the hard drive.
>
> I appreciate all the help…thanks for the quick responses.

Welcome :slight_smile:

> PS - I know this is not the section, I posted this is network / internet
> but I haven’t received any response.

You will have to be patient.

> Not sure how much you know about VNC, but with this same installation
> opensuse 12.3 KDE I am trying to VNC into the box and it only works if a
> user is logged in. This is an issue since I plan on using this for a
> database server that wont have a keyboard / mouse/ or monitor.
>
> Any suggestions?

Sorry, I don’t use VNC myself. I use plain ssh instead. I did try vnc or
similar, but I didn’t like the idea.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)