Cloned hard drive to a larger drive, system only boots in emergency mode

English Install/Boot/Login
1

Hi all,

I cloned my 80GB hard drive to a 1TB hard drive using clonezilla.
Cloning was successful, error checks didn’t report anything.

Now, every time I boot up the system, it goes into emergency mode without asking and without any error message. It just says “Welcome to emergency mode. Use “systemctl default” or ^D to enter default mode.” and asks for root login.

I tried “systemctl default” and Ctrl-D to no avail, it goes back to emergency mode.

I then rebooted on gparted live to expand the 50GB original partition to a 900GB partition thinking the unallocated space could be confusing the system somehow.

After resizing, I still have the exact same pattern.

Previous config was 80GB hdd with openSUSE12.2 and one extra 3com ethernet controller
New config is a clone of the 80GB to the 1000GB drive and I removed the 3com ethernet controller. I removed it because it was not being used, everything was being done with the built in gigabit ethernet.

Could someone please advise? Thanks

2

The references to the hard drive are now different. In essence the system no longer knows the right names for the disk/partitions and can’t mount them. You will need to edit the references in Grub and /etc/fstab. to reference the new drive. Under legacy grub it was easy you just needed to edit /boot/grub/menu.lst with grub2 I’m not sure how you would do it.

3

I tried editing the boot options in YaST by changing the device id as per /dev/disk/by-id and also edit /etc/fstab to change the disk id but it doesn’t fix the problem

4

On 2012-09-28 23:46, ShaolinSatellite wrote:

> Now, every time I boot up the system, it goes into emergency mode
> without asking and without any error message. It just says “Welcome to
> emergency mode. Use “systemctl default” or ^D to enter default mode.”
> and asks for root login.

Boot in system V mode to see the error message.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

5

Sure, how do I do that please?

6

On 2012-09-29 01:56, ShaolinSatellite wrote:
>
> robin_listas;2491577 Wrote:

>> Boot in system V mode to see the error message.

> Sure, how do I do that please?

Boot screen, read the bottom line, press the appropriate key. If you are using grub2, asok
somebody else, I have not seen that screen.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

7

There are also some grub parameters (for booting) that need to be changed. If you use encryption, the “/etc/crypttab” would also need changing. Perhaps the “device.map” file under “/boot/grub” or “/boot/grub2” also needs changing.

8

I have a screen called GNU GRUB showing up and there is nothing about verbose mode. I’m confused

9

I think I entered the verbose mode.

It starts up, then stays on

Started Show Plymouth Boot Screen  OK ]

After a few minutes, it says

Dependency failed. Aborted start of /home  ABORT ]
Dependency failed. Aborted start of Login Service  ABORT ]
Dependency failed. aborted start of D-Bus System Message Bus  ABORT ]
Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode. 
Give root password for login:
10

Isn’t there also a reference in initrd? (I just vaguely remember).

11

On 2012-09-29 04:46, ShaolinSatellite wrote:

> I have a screen called GNU GRUB showing up and there is nothing about
> verbose mode. I’m confused

I did not say verbose mode, I said system D mode. Verbose mode is unknown to me. You have to
look at the bottom bar, F1, F2… F5 is the init program. That one.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

12

Yes, it is written systemd, not system D or System D, or even SystemD. And it isn’t system d either.
freedesktop.org - Software/systemd

13

On 2012-09-29 15:03, Carlos E. R. wrote:
> On 2012-09-29 04:46, ShaolinSatellite wrote:
>
>> I have a screen called GNU GRUB showing up and there is nothing about
>> verbose mode. I’m confused
>
> I did not say verbose mode, I said system D mode. Verbose mode is unknown to me. You have to
> look at the bottom bar, F1, F2… F5 is the init program. That one.

Sorry, not system D, but system V - D is what you are using now. Yes, I know how it is written,
I intentionally stress the V or D.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

14

I don’t have any of the options mentioned. This is what the boot screen looks like
http://i.imgur.com/PRiF7.jpg](http://imgur.com/PRiF7)

15

Hmmm it seems I figured it out. I edited the commands in GRUB using the “e” key and replaced the reference to the old drive by a reference to the new one.
This worked, so I edited the GRUB2 start up options using YaST2 to permanently change the reference and it seems to work now.

Still curious as to why I have a boot screen that seems to differ from what others get though.

16

Well, the bootscreen you get is the one for a text only system. When that is not what you have, it is indeed unusual.

17

On 2012-09-29 17:26, ShaolinSatellite wrote:
>
> Hmmm it seems I figured it out. I edited the commands in GRUB using the
> “e” key and replaced the reference to the old drive by a reference to
> the new one.

Aha.

> This worked, so I edited the GRUB2 start up options using YaST2 to
> permanently change the reference and it seems to work now.
>
> Still curious as to why I have a boot screen that seems to differ from
> what others get though.

That’s grub2 in text mode. Somebody else will have to comment on where to find the options.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

18

I do have a text only system so all is normal I suppose