Scribd
Upload
77 views2 pages

SUSE Linux Target Fails To Boot Properly Waiting For Device To Appear

Uploaded by

ΔΗΜΗΤΡΙΟΣ ΑΛΥΦΑΝΤΗΣ
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
77 views2 pages

SUSE Linux Target Fails To Boot Properly Waiting For Device To Appear

Uploaded by

ΔΗΜΗΤΡΙΟΣ ΑΛΥΦΑΝΤΗΣ
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Support | SUSE Linux target fails to boot properly: waiting for device to appear Page 1 of 2

Knowledgebase FAQ Register Your Product My Favorites

SUSE Linux target fails to boot properly: waiting Document ID:

for device to appear 7009643


Creation Date:
26-OCT-11
This document (7009643) is provided subject to the disclaimer at the end of this document.

Modified Date:
Environment 02-JAN-13
PlateSpin Forge
PlateSpin Migrate NetIQ
PlateSpin Protect
PlateSpin Forge
Source machine is SUSE Linux Enterprise Server 10
PlateSpin Migrate
Situation
PlateSpin Protect
After migrating a SLES 10 source (or during failback) the target machine fails to boot with an error message similar to the
following:

Waiting for device /dev/sda2 to appear: ..................not


-- exiting to /bin/sh

Resolution

1. Boot the target machine into rescue mode, using appropriate boot media
2. Run the following command to determine which devices are /, /boot and swap:

fdisk -l

3. Using that information mount the appropriate devices:

mount /dev/%root device% /mnt


mount /dev/%boot device% /mnt/boot
mount --rbind /proc /mnt/proc
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev

4. Change the system root to the newly selected location:

chroot /mnt

5. Modify the /etc/fstab file to make sure the correct devices are being used. For example the root, boot, and swap
devices might be listed with these device names:

/dev/sda1
/dev/sda2
/dev/sda3

According to the fdisk -l output, however, the devices should be listed as follows:

/dev/cciss/c0d0p1
/dev/cciss/c0d0p2
/dev/cciss/c0d0p3

6. Modify the /boot/grub/menu.lst file and replace the boot partition information with the correct device id. For example,
the boot partition may be listed as this device:

/dev/sda2

Where it should be this device:

/dev/cciss/c0d0p2

7. Make sure that the /var/tmp directory exists and then run the following command (note: the /var/tmp directory may need
to be manually created first):

mkinitrd

8. Reboot the target machine

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our
products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational,
personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY
KIND.

© 2013 Novell Careers Legal

Follow Novell Request a Call +90 212 230 32 17 Print Feedback

http://www.novell.com/support/kb/doc.php?id=7009643 26/9/2013
Support | SUSE Linux target fails to boot properly: waiting for device to appear Page 2 of 2

Follow Novell Request a Call +90 212 230 32 17 Print Feedback

http://www.novell.com/support/kb/doc.php?id=7009643 26/9/2013

You might also like