Problems After Cloning VM To Physical HD

Hi

RHEL 6.4 (64 Bit) is running as a Virutal Machine in a VCenter Server 5.5
As per our request, Vmware team added 500GB of disk space to this VM. Disk is not visible in "fdisk -l" after run the following command/script, but the new disk could be seen from the "multipath -l" command.

for i in `ls -ld /sys/class/scsi_host/host* | awk '{print $9}' `
do
echo "- - -" > $i/scan
done

Could someone clarify why it is not visible in "fdisk -l" output?

hiiii all

I had installed Windows 7 on /dev/sda1 and /dev/sda2 and then I installed Centos 7.
Since then I cant find Windows entry in the Grub.
And i had tried to use all kind of solution found on the net I still cant see any entry.
I had edited 40_custom script adding:

cat <<EOF
menuentry "windows 7" {
insmod part_msdos
insmod ntfs
set root='hd0,msdos1'
search --no-floppy --fs-uuid --set=root FCDAE998DAE95006
chainloader +1
}
EOF

then this command grub2-mkconfig -o /boot/grub2/grub2.cfg

[root@localhost]# grub2-mkconfig -o /boot/grub2/grub2.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-123.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-123.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-93890f189dec4b309c004fdce969ca5a
Found initrd image: /boot/initramfs-0-rescue-93890f189dec4b309c004fdce969ca5a.img

then this
[root@localhost]# tail -10 /boot/grub2/grub.cfg
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
[root@localhost]#


Still cant find windows in grub
please help me with this guys
thanks

Hey,

My plan is to run some Linux distro's on an external USB HDD. So far I have been able to instal elementary OS, it thus far boots with the elementary OS logo and hangs for a while when it gives me the following message:


"Gave up waiting for boot device.
- Boot args (cat /proc/cmdline)
- Check root delay (Waiting long enough?)
- Check root (Waiting for the right device?)
- Missing modules (cat /proc/modules; 1s/dev)

ALERT! /dev/disk-uuid/*super long number* does not exist. Dropping to a shell!

BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) build-in shell (ash)

Enter 'help' for a list of build-in commands."


To give you an idea of the external HDD partition:
60 GB: ext4 (elementary OS)
4GB: SWAP
Free Space
80 GB: NTFS (Random files)

The ext4 was given '/' for mounting point to keep it simple for now. The 'boot part' I've set to instal on sdc. Which is the external HDD. (I wasn't sure whether I should have chosen the ext4 partition or not.)

Please let me know if you need any addition information. I hope someone is familiar with the problem or knows a solution.

Thanks in advance.

Hi all! I'm a Linux/Ubuntu noob who has recently bought a brand new HP laptop, nuked the Win 8 OS that it came/w & installed Ubuntu 14.04LTS. After DL/installing apps & setting it up a bit I decided to use gparted & partition my HDD for an additional OS, isolate programs from files, adjust swap, etc. All went well until I was prompted to reboot which I did & now I'm stuck @

" BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) multi-call binary.

usage: chroot NEWROOT [PROG ARGS]

Run PROG with root directory set to NEWROOT "

Which invariably produces: (no matter what command I enter?!?)

" (initramfs) boot from BIOS
/bin/sh: boot: not found "

I'm quite confused @ how to proceed here?

My primary concern is the health of my machine through/after this is worked out.
That said, I'd love to not have to re-install Ubuntu/apps, etc. as I was partitioning the HDD because I had gotten it to a nice back-up place & felt ready to set it up.
Like I said I'm new to Linux/Ubuntu & waayyy behind on my terminal coding, but I could really use some pointers here & I'm not usually hard to teach. lol
Help?! :-[
Thanx!
Embarrassingly yours, WS.

I'm trying to install Debian 7.8 on my eMac G4 (700mhz, 640 Mb RAM). I've tried multiple methods but I keep running into problems one way or another. Since my eMac only has a Sony CD-RW drive and a busted Ethernet port I can't install from a DVD nor a netinstall CD which would be the easiest options unfortunately. First I tried using the multiple CD option, which seemed promising at first; until I had to swap to the next disk during "configure the package manager". it won't eject the CD when I use the eject key on my keyboard (imac g3 pro keyboard so I go back to the main menu and select the "eject a CD from the drive" option at the near bottom then things seem to get clustered. When I tried inserting the next disk, nothing else will install. It keeps telling me I need disk 1 again through every step. Then at the end, it tells me the installation is complete before I even install a desktop environment from the final CD. Then I just end up booting into garbled text and errors.

After all of that nonsense, I tried making a bootable USB from the DVD ISO with the OS X terminal. This method usually works with just about anything I've done before. However for some reason Debian apparently simply refuses to boot. As I tried selecting it on the boot menu on the start up, it gives me a black screen then goes straight back to the boot screen with disordered graphics. When I tried booting it from open firmware, it goes to the first screen, then when I hit enter to actually boot to the installer, nothing but errors. Finally I tried booting it straight from the ISO file on the hard drive, that method didn't even work at all.

Could someone point out what I'm doing wrong if possible or perhaps recommend me a different option?

These instructions originate from https://www.linkedin.com/pulse/20140...nvidia-drivers, but I modified them slightly for my desktop environment (64-bit HP Envy Phoenix 810-135qe w/Intel i7-4770 and HP ZR2440w monitor, nVidia GeForce GTX645, Red Hat Enterprise Linux 7.1 w/Gnome3).

The following procedures replace the nouveau drivers with kmod-nvidia drivers from ElRepo.

Install the repository ElRepo from: http://elrepo.org/tiki/tiki-index.php

Install the package nvidia-detect from within Applications>SystemTools>Software

From within the terminal, enter the command nvidia-detect.
Example:
[anthony@hp810135qe ~]$ nvidia-detect
Output is...
Probing for supported NVIDIA devices...
[10de:11c4] NVIDIA Corporation GK106 [GeForce GTX 645 OEM]
This device requires the current 346.59 NVIDIA driver kmod-nvidia

For my system the following software packages will apply (yours maybe slightly different, the key is to note the ###.## version identified for your system using nvidia-detect as explained above): kmod-nvidia-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-32bit-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-346.59-1.el7.elrepo (64-bit)

Now do the following steps in the sequence indicated:

1. Disable X Windows

a) open a terminal and "su" or "sudo -i"

b) ln -fs /lib/systemd/system/multi-user.target /etc/systemd/system/default.target

Note: Another way to disable X Windows is to do the following from within the Terminal # systemctl set-default multi-user.target

To later change back to booting into graphical mode, substitute 'graphical.target' for 'multi-user.target' in the above commands.

c) reboot

2. Remove Nouveau

a) rpm -e xorg-x11-drivers xorg-x11-drv-nouveau

Note: Another way to remove Nouveau is to do the following from within the Terminal

$ yum remove xorg-x11-drivers xorg-x11-drv-nouveau xorg-x11-glamor

See http://elrepo.org/tiki/kmod-nvidia which discusses that glamor still causes a conflict with nVidia in RHEL 7

3. Blacklist Nouveau

a) edit /etc/modprobe.d/blacklist.conf and add line:

blacklist nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/modprobe.d/blacklist.conf
(use INSERT key to make changes in vi; add the line

blacklist nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

b) edit /etc/default/grub and append to GRUB_CMDLINE_LINUX:

rd.driver.blacklist=nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/default/grub and append to GRUB_CMDLINE_LINUX:
(use INSERT key to make changes in vi; add the line

rd.driver.blacklist=nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

IMPORTANT NOTE IF YOU HAVE AN ENCRYPTED BOOTUP DRIVE -

If you have an encrypted root drive, remove "rhgb" from GRUB_CMDLINE_LINUX. This will allow you to interact with the encryption passphrase prompt, since Plymouth doesn't seem to run without a framebuffer friendly video driver loaded. IF YOU DON'T THIS, WHEN YOU BOOTUP YOU WILL GET STUCK AT A BLINKING CURSOR AND BLACKSCREEN THAT HAS THE FOLLOWING ERROR MESSAGES:


[5.757276] scsi 7:0:0:0: alua: not attached
[5.759625] sd 7:0:0:0: [sdg] no caching made page found
[5.759668] sd 7:0:0:0: [sdg] assuming drive cache: write through

WHEN THIS HAPPENS IT MEANS PLYMOUTH IS NOT ABLE TO SHOW YOU THE PROMPT FOR ENTERING THE PASSPHRASE FOR THE ENCRYPTED DRIVES. WITHOUT THE PROMPT THE SYSTEM CAN'T ACCEPT THE PASSPHRASE AND YOU ARE STUCK. IF THIS HAPPENS TO YOU, YOU CAN DO CTRL-ALT-DELETE TO REBOOT - THIS ALLOWS YOU TO HIT 'e' AT THE KERNEL LINE IN GRUB TERMINAL TO EDIT (MOST LIKELY THE TOP KERNEL) AND THEN REMOVE 'rhgb' (which stands for Red Hat Graphical Bootsplashcreen or something like that). WHEN DONE HIT THE KEYS 'CTRL X' TO REBOOT - YOU'LL THEN SEE TEXT MESSAGES SCROLLING AND GET AN OPPORTUNITY TO ENTER THE PASSPHRASE. ENTER THE PASSPHRASE AND YOU SHOULD BE GOOD TO GO.

4. Reconfigure the grub.cfg files

Two options for booting nowadays are BIOS and EFI

-If you chose BIOS boot run this command:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Note: I also have this one being auto-updated-configured in my system (?why? It's EFI).

-If EFI boot on CentOS:
# grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

-If EFI boot on RHEL:
# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
Note: Mine is an EFI system. But I did both this and the BIOS grub.cfg above since it too is being updated by RHEL updates concurrently with the EFI grub.cfg

5. Reboot and Install NVidia Driver - I use ElRepo's kmod-nvidia for this step.

Steps by me to install ElRepo's kmod-nvidia (You should still be in Text mode at this time):

If in multi-user.target mode (text, runlevel 3), then do the following
$ su -
enter root password
# yum install kmod-nvidia - version from above
# yum install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
# yum install nvidia-x11-drv - version from above (this is for Open GL X11 display driver and to be done if kmod didn't already include doing it with the kmod-nvidia installation above)
# exit
$

If still in graphics.target mode (you shouldn't be but if you are) (GUI, runlevel 5),
Use Applications > Software > kmod-nvidia - version from above
Install kmod-nvidia - version from above
Install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
Install nvidia-x11-drv - version from above (this is for Open GL X11 display driver)

6. At this point rebuild initramfs. This recreates initrd w/o nouveau. The existing initrd still has the embedded nouveau drivers if this step is not performed) :

Back up the current initramfs keeping nouveau
# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
Build the new one without nouveau
# dracut /boot/initramfs-$(uname -r).img $(uname -r)

7. Re-Enable X Windows

# systemctl set-default graphical.target

8. Reboot

If you have an encrypted bootup drive, when you bootup you may notice that Plymouth doesn't look so good with its text in a lower resolution and you'll see lines of text scrolling until you get to a stopped cursor waiting for you to enter the passphrase to unencrypt your drive. Maybe eventually there'll be a solution for this to keep things moving with a graphical bootsplash all throughout. Until then, this is a minor inconvenience for me.

I have a dual boot laptop with debian stable & Windows 7.

The HD partitions a
sda1: NTFS for W7
sda2: FAT32 (currently unused)
sda3: linux /boot
sda4: linux ext4, which is LVM with encryption

I've re-installed W7 and now need to recover the MBR & grub menu.

I've booted with the netinst usb in rescue mode, but it fails to mount the root partition /sda4:
"An error occured while mounting the device you entered for your root file system (/dev/sda4) on /target"

and /var/syslog shows:
Code:

rescue-mode: selected root device '/dev/sda4'
umount: cant umount /target: Invalid argument
isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32
EXT2-fs (sda4): error: unable to readsuperblock
EXT3-fs (sda4): error: unable to readsuperblock
rescue: mount: mounting /dev/sda4 on /target failed: Invalid argument

So it seems like something is wrong with the mount command?

Would appreciate suggestions how to solve this.

Thanks

Have Toshiba Tecra 64-bit 500gb disk 4gb ram running Windows 7 professional it has Intel core i5 processor.
I downloaded iso file of DVD LinuxMint Rebecca Cinnamon to DVD.
When I restart the system with the DVD inserted it immediately opens in Windows 7.
I could not follow the instructions to "disable secure boot and (u)efi".
Have partitioned the disk to allocate 100 gb to Linux in E:
First of all I really would like to run Live DVD and then later on to install it permanently it the E: partition.
Can I just simply copy the iso file into disk E:
Help from anyone is greatly appreciated.
Best regards to all of you.

Friends,

I'm completely a Linux newbie, so explain as much as possible.

I installed Linux Deepin on dual boot(practically, triple-boot).
When I select the Linux Deepin option in bootloader, I mostly get a blank screen for a long time.
After practically 2 mins, it presents with some lines of text which I, being a newbie to Linux can't comprehend and hence, cannot counter the error.
The lines go:
"
udevadm settle - timeout of 30 seconds reached, the event queue contains:
/sys/devices/pci0000:00:1d.7/usb1(1080)
/sys/devices/pci0000:00:1d.7/usb1.1-0:1-0(1081)
up waiting for root device. Common reasons for this problem:
root args(cat /proc/cmdline)
Check rootdelay = ...[There's something here I cannot recollect at the moment]
Missing modules(cat /proc/modules; ls /dev)

ALERT! /dev/disk/by-uuid/b4b672ea-c6e5-47fe-a174-165ffde63c8 doesn't exist!
Dropped to shell!
"

Then it goes to a Ubuntu shell or something of that sort.


Surprisingly, every-time I boot into Windows and then restart my desktop and then boot to Deepin, it successfully boots in.
I have Deepin installed on external hard disk which is not very fast(just mentioned this if it is of any use.) Also, my Windows is extremely slow in booting up, it takes almost 10 mins, which is why I switched to Deepin, which boots up almost in 2 mins if it does.

Any help would be extremely appreciated.

Hi

My machine was a dual boot debain + W7. The debian had LUKS encryption and LVM.

I had to re-install W7 and now there is no access to the grub menu and of course to the debian installation.

I tried "boot repair disk"
http://sourceforge.net/projects/boot-repair-cd/
, but it couldnt access the encrypted volume. It did generate the following output:
paste.ubuntu.com/10591353

Would appreciate help how to get the boot repair disk to access the encrypted partition and recover the grub menu

Thanks