Thread: [Clonezilla-live] Restoring a CentOS disk to VmWare : help needed
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
clonezilla-live
|
From: Matthieu G. <mat...@ga...> - 2009-06-17 16:56:54
|
Hi,
I'm trying to restore a physical installation of Centos to a VMWare
virtual machine.
I received the dreaded "Running: grub-install-no-floppy-root-
directory=/tmp/hd_img.QiFQFv /dev/sda
grub-probe: error: Cannot open '/boot/grub/devise_map'
/usr/sbin/grub-install: line 374: [: =: unary operator expected" error
message.
Anyhow, when I try to boot the machine, I received a Kernel Panic :
Volume group "VolGroup00" not found
Trying to resume form /dev/VolGroup/LogVol01
Unable to access resume device
(...)
Mount : Could not find filesystem '/dev/root'
(...)
Kernel Panic - not syncing : Attempted to kill init!
here is a screen capture of the console :
The disk is formatted with a boot Linux partition, followed by a big
LVM partition :
fdisk-l output on the restored machine :
Disk /dev/sda: 134.2 GB, 134217728000 bytes
255 heads, 63 sectors/track, 16317 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000baed3
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 14593 117113850 8e Linux LVM
The LVM volume itself is composed of the following logical volumes :
pvdisplay output :
--- Physical volume ---
PV Name /dev/sda2
VG Name VolGroup00
PV Size 111.69 GB / not usable 1018.00 KB
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 3574
Free PE 0
Allocated PE 3574
PV UUID HsETnF-XSTU-V5A4-Zkux-oBJm-JRAl-8mHoLd
vgdisplay output :
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 111.69 GB
PE Size 32.00 MB
Total PE 3574
Alloc PE / Size 3574 / 111.69 GB
Free PE / Size 0 / 0
VG UUID pwaNUO-hXTM-LAdC-TUds-yyAq-ylm4-mM0jOP
lvdisplay output :
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID RpV3Ix-rLod-Idnm-mOdf-31kV-spSr-2Tdf03
LV Write Access read/write
LV Status available
# open 1
LV Size 111.19 GB
Current LE 3558
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID td59rA-cLl0-H2Ie-jOp0-A0Z2-4doJ-3PQ9ry
LV Write Access read/write
LV Status available
# open 0
LV Size 512.00 MB
Current LE 16
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
Following the advices related to an analog problem (Giorgos) , I
mounted the LVM partition in order to edit the fstab file.
The contents of this file are the following :
/dev/VolGroup00/LogVol00 / ext3
defaults 1 1
LABEL=/boot /boot ext3
defaults 1 2
tmpfs /dev/shm tmpfs
defaults 0 0
devpts /dev/pts devpts
gid=5,mode=620 0 0
sysfs /sys sysfs
defaults 0 0
proc /proc proc
defaults 0 0
/dev/VolGroup00/LogVol01 swap swap
defaults 0 0
I'm quite new to Linux, but cannot see anything wrong here...
For your info, I'm also posting the files grub.conf and menu.lst
GRUB.CONF
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
boot=/dev/hdc
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-128.1.10.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.18-128.1.10.el5.img
title CentOS (2.6.18-128.1.6.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.18-128.1.6.el5.img
title CentOS (2.6.18-128.1.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.1.el5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.18-128.1.1.el5.img
MENU.LST
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
boot=/dev/hdc
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-128.1.10.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.18-128.1.10.el5.img
title CentOS (2.6.18-128.1.6.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.18-128.1.6.el5.img
title CentOS (2.6.18-128.1.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.1.el5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.18-128.1.1.el5.img
Can anyone help me to make my restored CentOS boot on vmware ?
Thanks
Matthieu
|
|
From: Matthieu G. <mgw...@fa...> - 2009-07-03 16:35:01
|
For the record : the problem was that the default disk emulation of vmware (at least Fusion, mac) is SCSI, while the originating machine was an IDE one. Looks like centos wasn't equipped with the necessary drivers to handle the SCSI interface. Solution 1 : change the interface type to IDE and restore again Solution 2 : add the drivers needed (not tried) Thanks for the help Steven ! Matthieu Début du message réexpédié : De : Steven Shiau <[1]st...@nc...> Date : 1 juillet 2009 10:01:12 GMT+02:00 À : Matthieu Gaillet <[2]mat...@ga...> Objet : Rép : [Clonezilla-live] Restoring a CentOS disk to VmWare : help needed Yes, vmlinuz will be loaded, then when initrd.img is loaded, and when it tries to find the root partition, it can not find, since SCSI driver is not found in initrd.img, so it won't be able to mount the root partition on SCSI disk. Therefore it shows you kernel panic. Steven. Matthieu Gaillet wrote: Would it boot anyway until the Kernel panic ? Even without those drivers ? I'll try to check if they are presents and to install them if needed. Le 01-juil.-09 à 08:46, Steven Shiau a écrit : Hi Matthieu, Matthieu Gaillet wrote: Nope, the contrary : * disk image taken on Physical IDE --> restored on vmware SCSI emulation (default setting) =>* doesn't work (panic)* * disk image taken on Physical IDE --> restored on vmware IDE emulation --> *works !* That makes sense... Since maybe your initrd of OS taken from IDE disk does not include the driver for SCSI device. Steven. Matthieu Le 01-juil.-09 à 04:39, Steven Shiau a écrit : Hi Matthieu, Did you mean you installed CentOS on your IDE in the VMware machine, and it works ? But if CentOS is installed on SCSI disk, Clonezilla failed to restore ? Steven. Matthieu Gaillet wrote: Steven, I tried using an IDE drive emulation on the VMware machine : IT WORKS ! Any idea ? Should it work ? How could I make it work in SCSI anyway ? Thanks Matthieu Début du message réexpédié : *De : *Matthieu Gaillet <mat...@ga... <[3]mailto:mat...@ga...>> *Date : *30 juin 2009 09:22:46 GMT+02:00 *À : *Steven Shiau <st...@nc... <[4]mailto:st...@nc...>> *Objet : **Rép : [Clonezilla-live] Restoring a CentOS disk to VmWare : help needed* Hi Steven, Thanks for your answer. I didn't saw any other error messages, but it is possible that I missed one of them... Is there a log of the activities written somewhere on the ramdisk ? Regarding the image dir : it is stored on an external hardrive that I access through Samba at restore time. Here is the result of the find command : Thanks Maybe a lead : the original physical machine is equipped with IDE / ATA drives. Vmware presents a SCSI interface... Could it be the origin of the problem ? Matthieu Le 29-juin-09 à 17:03, Steven Shiau a écrit : Matthieu, Matthieu Gaillet wrote: Hi, I'm trying to restore a physical installation of Centos to a VMWare virtual machine. I received the dreaded "Running: grub-install-no-floppy-root-directory=/tmp/hd_img.QiFQFv /dev/sda grub-probe: error: Cannot open '/boot/grub/devise_map' /usr/sbin/grub-install: line 374: [: =: unary operator expected" error message. This is a harmless error. Check this: [5]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513216 BTW, when you saved or restored the image, did you see any error messages other than the above one ? How about the image dir ? Could you please run: find /home/partimag/$YOUR_IMAGE -print (Replace $YOUR_IMAGE with your image name) then post the results ? Steven. Anyhow, when I try to boot the machine, I received a Kernel Panic : References 1. mailto:st...@nc... 2. mailto:mat...@ga... 3. mailto:mat...@ga... 4. mailto:st...@nc... 5. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513216 |
|
From: Les M. <les...@gm...> - 2009-07-03 17:01:59
|
Matthieu Gaillet wrote:
>
>
> For the record : the problem was that the default disk emulation of
> vmware (at least Fusion, mac) is SCSI, while the originating machine was
> an IDE one. Looks like centos wasn't equipped with the necessary drivers
> to handle the SCSI interface.
>
> Solution 1 : change the interface type to IDE and restore again
> Solution 2 : add the drivers needed (not tried)
You have the same issue if you move to a physical host with a different scsi
controller. Basically the disk driver for the root filesystem has to be
included in either the kernel or the initrd. You can usually boot the install
disk (even in vmware), add the driver you need to /etc/modprobe.conf and rebuild
the initrd. Or a simple-minded approach is to do an install on the same or
similar hardware, save the contents of /boot, then copy that back over the
clonezilla load. That should give you the drivers the installer picks without
having to know the modules you need yourself.
--
Les Mikesell
les...@gm...
|
|
From: Steven S. <st...@nc...> - 2009-07-04 07:22:41
|
Matthieu, Thanks for sharing this conclusion. Steven. Matthieu Gaillet wrote: > > > For the record : the problem was that the default disk emulation of > vmware (at least Fusion, mac) is SCSI, while the originating machine > was an IDE one. Looks like centos wasn't equipped with the necessary > drivers to handle the SCSI interface. > > Solution 1 : change the interface type to IDE and restore again > Solution 2 : add the drivers needed (not tried) > > Thanks for the help Steven ! > > Matthieu > > > > Début du message réexpédié : > >> *De : *Steven Shiau <st...@nc... <mailto:st...@nc...>> >> *Date : *1 juillet 2009 10:01:12 GMT+02:00 >> *À : *Matthieu Gaillet <mat...@ga... <mailto:mat...@ga...>> >> *Objet : **Rép : [Clonezilla-live] Restoring a CentOS disk to VmWare >> : help needed* >> >> Yes, vmlinuz will be loaded, then when initrd.img is loaded, and when >> it tries to find the root partition, it can not find, since SCSI >> driver is not found in initrd.img, so it won't be able to mount the >> root partition on SCSI disk. Therefore it shows you kernel panic. >> >> Steven. >> >> Matthieu Gaillet wrote: >>> Would it boot anyway until the Kernel panic ? Even without those >>> drivers ? I'll try to check if they are presents and to install them >>> if needed. >>> >>> Le 01-juil.-09 à 08:46, Steven Shiau a écrit : >>> >>>> Hi Matthieu, >>>> >>>> Matthieu Gaillet wrote: >>>>> >>>>> Nope, the contrary : >>>>> >>>>> * disk image taken on Physical IDE --> restored on vmware SCSI >>>>> emulation (default setting) =>* doesn't work (panic)* >>>>> * disk image taken on Physical IDE --> restored on vmware IDE >>>>> emulation --> *works !* >>>> That makes sense... Since maybe your initrd of OS taken from IDE >>>> disk does not include the driver for SCSI device. >>>> >>>> Steven. >>>>> >>>>> Matthieu >>>>> >>>>> >>>>> Le 01-juil.-09 à 04:39, Steven Shiau a écrit : >>>>> >>>>>> Hi Matthieu, >>>>>> Did you mean you installed CentOS on your IDE in the VMware >>>>>> machine, and it works ? >>>>>> But if CentOS is installed on SCSI disk, Clonezilla failed to >>>>>> restore ? >>>>>> >>>>>> Steven. >>>>>> >>>>>> Matthieu Gaillet wrote: >>>>>>> >>>>>>> Steven, >>>>>>> >>>>>>> I tried using an IDE drive emulation on the VMware machine : IT >>>>>>> WORKS ! >>>>>>> >>>>>>> Any idea ? Should it work ? How could I make it work in SCSI >>>>>>> anyway ? >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Matthieu >>>>>>> >>>>>>> >>>>>>> >>>>>>> Début du message réexpédié : >>>>>>> >>>>>>>> *De : *Matthieu Gaillet <mat...@ga... >>>>>>>> <mailto:mat...@ga...>> >>>>>>>> *Date : *30 juin 2009 09:22:46 GMT+02:00 >>>>>>>> *À : *Steven Shiau <st...@nc... <mailto:st...@nc...>> >>>>>>>> *Objet : **Rép : [Clonezilla-live] Restoring a CentOS disk to >>>>>>>> VmWare : help needed* >>>>>>>> >>>>>>>> >>>>>>>> Hi Steven, >>>>>>>> >>>>>>>> Thanks for your answer. I didn't saw any other error messages, >>>>>>>> but it is possible that I missed one of them... Is there a log >>>>>>>> of the activities written somewhere on the ramdisk ? >>>>>>>> >>>>>>>> Regarding the image dir : it is stored on an external hardrive >>>>>>>> that I access through Samba at restore time. >>>>>>>> >>>>>>>> Here is the result of the find command : >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> Maybe a lead : the original physical machine is equipped with >>>>>>>> IDE / ATA drives. Vmware presents a SCSI interface... Could it >>>>>>>> be the origin of the problem ? >>>>>>>> >>>>>>>> Matthieu >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le 29-juin-09 à 17:03, Steven Shiau a écrit : >>>>>>>> >>>>>>>>> Matthieu, >>>>>>>>> >>>>>>>>> >>>>>>>>> Matthieu Gaillet wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I'm trying to restore a physical installation of Centos to a >>>>>>>>>> VMWare >>>>>>>>>> virtual machine. >>>>>>>>>> >>>>>>>>>> I received the dreaded "Running: >>>>>>>>>> grub-install-no-floppy-root-directory=/tmp/hd_img.QiFQFv /dev/sda >>>>>>>>>> grub-probe: error: Cannot open '/boot/grub/devise_map' >>>>>>>>>> /usr/sbin/grub-install: line 374: [: =: unary operator >>>>>>>>>> expected" error >>>>>>>>>> message. >>>>>>>>> This is a harmless error. Check this: >>>>>>>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513216 >>>>>>>>> >>>>>>>>> BTW, when you saved or restored the image, did you see any error >>>>>>>>> messages other than the above one ? >>>>>>>>> How about the image dir ? Could you please run: >>>>>>>>> find /home/partimag/$YOUR_IMAGE -print >>>>>>>>> (Replace $YOUR_IMAGE with your image name) >>>>>>>>> then post the results ? >>>>>>>>> >>>>>>>>> Steven. >>>>>>>>>> >>>>>>>>>> Anyhow, when I try to boot the machine, I received a Kernel >>>>>>>>>> Panic : >>>>>>>>>> > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Steven S. <st...@nc...> - 2009-06-29 15:03:20
|
Matthieu, Matthieu Gaillet wrote: > > Hi, > > I'm trying to restore a physical installation of Centos to a VMWare > virtual machine. > > I received the dreaded "Running: > grub-install-no-floppy-root-directory=/tmp/hd_img.QiFQFv /dev/sda > grub-probe: error: Cannot open '/boot/grub/devise_map' > /usr/sbin/grub-install: line 374: [: =: unary operator expected" error > message. This is a harmless error. Check this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513216 BTW, when you saved or restored the image, did you see any error messages other than the above one ? How about the image dir ? Could you please run: find /home/partimag/$YOUR_IMAGE -print (Replace $YOUR_IMAGE with your image name) then post the results ? Steven. > > Anyhow, when I try to boot the machine, I received a Kernel Panic : > > Volume group "VolGroup00" not found > Trying to resume form /dev/VolGroup/LogVol01 > Unable to access resume device > > (...) > > Mount : Could not find filesystem '/dev/root' > > (...) > > Kernel Panic - not syncing : Attempted to kill init! > > here is a screen capture of the console : > > > > The disk is formatted with a boot Linux partition, followed by a big > LVM partition : > > fdisk-l output on the *restored* machine : > > Disk /dev/sda: 134.2 GB, 134217728000 bytes > 255 heads, 63 sectors/track, 16317 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x000baed3 > > Device Boot Start End Blocks Id System > /dev/sda1 * 1 13 104391 83 Linux > /dev/sda2 14 14593 117113850 8e Linux LVM > > The LVM volume itself is composed of the following logical volumes : > > pvdisplay output : > > --- Physical volume --- > PV Name /dev/sda2 > VG Name VolGroup00 > PV Size 111.69 GB / not usable 1018.00 KB > Allocatable yes (but full) > PE Size (KByte) 32768 > Total PE 3574 > Free PE 0 > Allocated PE 3574 > PV UUID HsETnF-XSTU-V5A4-Zkux-oBJm-JRAl-8mHoLd > > vgdisplay output : > > --- Volume group --- > VG Name VolGroup00 > System ID > Format lvm2 > Metadata Areas 1 > Metadata Sequence No 4 > VG Access read/write > VG Status resizable > MAX LV 0 > Cur LV 2 > Open LV 1 > Max PV 0 > Cur PV 1 > Act PV 1 > VG Size 111.69 GB > PE Size 32.00 MB > Total PE 3574 > Alloc PE / Size 3574 / 111.69 GB > Free PE / Size 0 / 0 > VG UUID pwaNUO-hXTM-LAdC-TUds-yyAq-ylm4-mM0jOP > > > lvdisplay output : > > --- Logical volume --- > LV Name /dev/VolGroup00/LogVol00 > VG Name VolGroup00 > LV UUID RpV3Ix-rLod-Idnm-mOdf-31kV-spSr-2Tdf03 > LV Write Access read/write > LV Status available > # open 1 > LV Size 111.19 GB > Current LE 3558 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:0 > --- Logical volume --- > LV Name /dev/VolGroup00/LogVol01 > VG Name VolGroup00 > LV UUID td59rA-cLl0-H2Ie-jOp0-A0Z2-4doJ-3PQ9ry > LV Write Access read/write > LV Status available > # open 0 > LV Size 512.00 MB > Current LE 16 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:1 > > > > Following the advices related to an analog problem (Giorgos) , I > mounted the LVM partition in order to edit the fstab file. > The contents of this file are the following : > > > /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 > LABEL=/boot /boot ext3 defaults 1 2 > tmpfs /dev/shm tmpfs defaults 0 0 > devpts /dev/pts devpts gid=5,mode=620 0 0 > sysfs /sys sysfs defaults 0 0 > proc /proc proc defaults 0 0 > /dev/VolGroup00/LogVol01 swap swap defaults 0 0 > > > I'm quite new to Linux, but cannot see anything wrong here... > > > For your info, I'm also posting the files grub.conf and menu.lst > > GRUB.CONF > > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this > file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 > # initrd /initrd-version.img > boot=/dev/hdc > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (2.6.18-128.1.10.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol00 > initrd /initrd-2.6.18-128.1.10.el5.img > title CentOS (2.6.18-128.1.6.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=/dev/VolGroup00/LogVol00 > initrd /initrd-2.6.18-128.1.6.el5.img > title CentOS (2.6.18-128.1.1.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-128.1.1.el5 ro root=/dev/VolGroup00/LogVol00 > initrd /initrd-2.6.18-128.1.1.el5.img > > MENU.LST > > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this > file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 > # initrd /initrd-version.img > boot=/dev/hdc > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (2.6.18-128.1.10.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol00 > initrd /initrd-2.6.18-128.1.10.el5.img > title CentOS (2.6.18-128.1.6.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=/dev/VolGroup00/LogVol00 > initrd /initrd-2.6.18-128.1.6.el5.img > title CentOS (2.6.18-128.1.1.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-128.1.1.el5 ro root=/dev/VolGroup00/LogVol00 > initrd /initrd-2.6.18-128.1.1.el5.img > > > > * > * > *Can anyone help me to make my restored CentOS boot on vmware ? * > > Thanks > > Matthieu > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X