El día 9 de julio de 2013 16:47, C. L. Martinez <[email protected]> escribió: > 2013/7/9 Maykel Franco <[email protected]>: >> El día 9 de julio de 2013 16:42, Maykel Franco >> <[email protected]> escribió: >>> 2013/7/9 C. L. Martinez <[email protected]>: >>>> On Tue, Jul 9, 2013 at 2:33 PM, Maykel Franco <[email protected]> >>>> wrote: >>>>> El día 9 de julio de 2013 16:18, Maykel Franco >>>>> <[email protected]> escribió: >>>>>> El día 9 de julio de 2013 16:13, Maykel Franco >>>>>> <[email protected]> escribió: >>>>>>> El día 9 de julio de 2013 16:00, Camaleón <[email protected]> escribió: >>>>>>>> El Tue, 09 Jul 2013 13:49:30 +0200, Maykel Franco escribió: >>>>>>>> >>>>>>>>> Hola muy buenas, aun siendo una lista de debian(por eso pongo >>>>>>>>> off-topic), he realizado una instalación de un mandrake 2005 porque >>>>>>>>> quería realizar unas pruebas en una VM y luego aplicarselas a un >>>>>>>>> servidor en producción que lleva activo desde el 2005. >>>>>>>>> >>>>>>>>> El problema que tengo, es que al bootear y arrancar me reporta el >>>>>>>>> siguiente error: >>>>>>>>> >>>>>>>>> pivot_root(/sysroot,/sysroot/initrd) failed: 2 >>>>>>>> >>>>>>>> (...) >>>>>>>> >>>>>>>> Bueno, el error creo que es anterior y lo que dice es que no puede >>>>>>>> montar >>>>>>>> la partición raíz ("/"). La pregunta es por qué. >>>>>>>> >>>>>>>> ¿Has instalado desde cero ese sistema? ¿Has probado a iniciar el >>>>>>>> sistema >>>>>>>> manualmente desde el cargador de arranque? >>>>>>>> >>>>>>>> Saludos, >>>>>>>> >>>>>>>> -- >>>>>>>> Camaleón >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> To UNSUBSCRIBE, email to [email protected] >>>>>>>> with a subject of "unsubscribe". Trouble? Contact >>>>>>>> [email protected] >>>>>>>> Archive: http://lists.debian.org/[email protected] >>>>>>>> >>>>>>> >>>>>>> Gracias por contestar chicos. >>>>>>> >>>>>>> Sí he intentado arrancarlo desde grub rescue, siguiendo estos pasos: >>>>>>> >>>>>>> http://forum.mandriva.com/en/viewtopic.php?p=791873 >>>>>>> >>>>>>> Y el resultado es el mismo. Le generado con mkinitrd -f .... y me >>>>>>> genera el nuevo initrd pero aún así no arranca... >>>>>> >>>>>> >>>>>> Perdonar, no es una instalación nueva, es que tengo 2 máquinas sorry... >>>>>> >>>>>> Es una imagen de una máquina física restaurada en una VM KVM...Con lo >>>>>> cual eso me dice que puede ser que le falte algún módulo... >>>>>> >>>>>> Pero la verdad es que no sé por dónde tirar... >>>>>> >>>>>> Saludos y perdona por la equivocación es que estoy liado con 2 >>>>>> máquinas a la vez. >>>>> >>>>> Dejo una parte del log dmesg haber si ayuda algo... >>>>> >>>>> BIOS EDD facility v0.16 2004-Jun-25, 1 devices found >>>>> devfs_mk_dev: could not append to parent for md/0 >>>>> md: Autodetecting RAID arrays. >>>>> md: autorun ... >>>>> md: ... autorun DONE. >>>>> RAMDISK: Compressed image found at block 0 >>>>> EXT2-fs warning: checktime reached, running e2fsck is recommended >>>>> VFS: Mounted root (ext2 filesystem). >>>>> SCSI subsystem initialized >>>>> HP CISS Driver (v 2.6.4) >>>>> cciss: Device 0x46 has been found at bus 4 dev 3 func 0 >>>>> cciss: using DAC cycles >>>>> blocks= 286734240 block_size= 512 >>>>> heads= 255, sectors= 32, cylinders= 35139 >>>>> >>>>> blocks= 286734240 block_size= 512 >>>>> heads= 255, sectors= 32, cylinders= 35139 >>>>> >>>>> /dev/cciss/host0/target0: p1 p2 < p5 p6 p7 > >>>>> libata version 1.10 loaded. >>>>> ReiserFS: cciss/c0d0p6: found reiserfs format "3.6" with standard journal >>>>> ReiserFS: cciss/c0d0p6: using ordered data mode >>>>> ReiserFS: cciss/c0d0p6: journal params: device cciss/c0d0p6, size >>>>> 8192, journal first block 18, max trans len 1024, max batch 900, max >>>>> commit age 30, max trans age 30 >>>>> ReiserFS: cciss/c0d0p6: checking transaction log (cciss/c0d0p6) >>>>> ReiserFS: cciss/c0d0p6: Using r5 hash to sort names >>>>> ReiserFS: cciss/c0d0p6: warning: reiserfs: cannot create >>>>> /proc/fs/reiserfs/cciss/c0d0p6 >>>>> Freeing unused kernel memory: 296k freed >>>>> usbcore: registered new driver usbfs >>>>> usbcore: registered new driver hub >>>>> USB Universal Host Controller Interface driver v2.2 >>>>> uhci_hcd 0000:00:1d.0: UHCI Host Controller >>>>> PCI: Setting latency timer of device 0000:00:1d.0 to 64 >>>>> uhci_hcd 0000:00:1d.0: irq 16, io base 0x2000 >>>>> uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 >>>>> hub 1-0:1.0: USB hub found >>>>> hub 1-0:1.0: 2 ports detected >>>>> uhci_hcd 0000:00:1d.1: UHCI Host Controller >>>>> PCI: Setting latency timer of device 0000:00:1d.1 to 64 >>>>> uhci_hcd 0000:00:1d.1: irq 19, io base 0x2020 >>>>> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 >>>>> hub 2-0:1.0: USB hub found >>>>> hub 2-0:1.0: 2 ports detected >>>>> uhci_hcd 0000:00:1d.2: UHCI Host Controller >>>>> PCI: Setting latency timer of device 0000:00:1d.2 to 64 >>>>> uhci_hcd 0000:00:1d.2: irq 18, io base 0x2040 >>>>> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 >>>>> hub 3-0:1.0: USB hub found >>>>> hub 3-0:1.0: 2 ports detected >>>>> uhci_hcd 0000:00:1d.3: UHCI Host Controller >>>>> PCI: Setting latency timer of device 0000:00:1d.3 to 64 >>>>> uhci_hcd 0000:00:1d.3: irq 16, io base 0x2060 >>>>> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4 >>>>> hub 4-0:1.0: USB hub found >>>>> hub 4-0:1.0: 2 ports detected >>>>> ehci_hcd 0000:00:1d.7: EHCI Host Controller >>>>> PCI: Setting latency timer of device 0000:00:1d.7 to 64 >>>>> ehci_hcd 0000:00:1d.7: irq 23, pci mem 0xfbef0000 >>>>> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5 >>>>> PCI: cache line size of 128 is not supported by device 0000:00:1d.7 >>>>> ehci_hcd 0000:00:1d.7: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 >>>>> hub 5-0:1.0: USB hub found >>>>> hub 5-0:1.0: 8 ports detected >>>>> Adding 1019976k swap on /dev/cciss/c0d0p5. Priority:-1 extents:1 >>>>> hw_random hardware driver 1.0.0 loaded >>>>> ReiserFS: cciss/c0d0p7: found reiserfs format "3.6" with standard journal >>>>> ReiserFS: cciss/c0d0p7: using ordered data mode >>>>> ReiserFS: cciss/c0d0p7: journal params: device cciss/c0d0p7, size >>>>> 8192, journal first block 18, max trans len 1024, max batch 900, max >>>>> commit age 30, max trans age 30 >>>>> ReiserFS: cciss/c0d0p7: checking transaction log (cciss/c0d0p7) >>>>> ReiserFS: cciss/c0d0p7: Using r5 hash to sort names >>>>> ReiserFS: cciss/c0d0p7: warning: reiserfs: cannot create >>>>> /proc/fs/reiserfs/cciss/c0d0p7 >>>>> ReiserFS: cciss/c0d0p1: found reiserfs format "3.6" with standard journal >>>>> ReiserFS: cciss/c0d0p1: using ordered data mode >>>>> ReiserFS: cciss/c0d0p1: journal params: device cciss/c0d0p1, size >>>>> 8192, journal first block 18, max trans len 1024, max batch 900, max >>>>> commit age 30, max trans age 30 >>>>> ReiserFS: cciss/c0d0p1: checking transaction log (cciss/c0d0p1) >>>>> ReiserFS: cciss/c0d0p1: Using r5 hash to sort names >>>>> ReiserFS: cciss/c0d0p1: warning: reiserfs: cannot create >>>>> /proc/fs/reiserfs/cciss/c0d0p1 >>>>> loop: loaded (max 8 devices) >>>>> hda: ATAPI 24X CD-ROM drive, 128kB Cache >>>>> Uniform CD-ROM driver Revision: 3.20 >>>>> tg3.c:v3.23 (February 15, 2005) >>>>> eth0: Tigon3 [partno(N/A) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) >>>>> 10/100/1000BaseT Ethernet 00:12:79:d1:f4:4f >>>>> eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] >>>>> TSOcap[0] >>>>> eth1: Tigon3 [partno(N/A) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) >>>>> 10/100/1000BaseT Ethernet 00:12:79:d1:f4:4e >>>>> eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] >>>>> TSOcap[1] >>>>> >>>>> >>>>> Nuevamente, gracias. >>>>> >>>> >>>> Este log corresponde a una máquina física, no a una VM. ¿Qué metodo >>>> P2V has utilizado? >>> >>> El método que he utilizado el fsarchiver -A -a, restaurar grub y >>> generar nueva imagen de arranque /boot/*. >>> >>> Así he pasado siempre las máquinas que estaban en prod, a VM, pero >>> este mandrake del 2005 se me está resistiendo...Lo mismo es porque usa >>> el controlador de HP para raid y tengo que generar nuevos módulos... >>> no sé estoy un poco perdido con este error la verdad... >> > > Bueno lo que está claro es que el método que has utilizado no es > confiable para ciertas distros. No he hecho muchas P2V en debien (de > hecho ninguna) pero creo que el método que explican para RedHat te > puede servir: > > http://libguestfs.org/virt-v2v/ > https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/V2V_Guide/chap-V2V_Guide-P2V_Migration_Converting_Physical_Machines_to_Virtual_Machines.html > > Úsalo como referencia. Yo lo he utilizado en sistemas de producción y > VM's "gordotas" y no he tenido problemas ...
Muchas gracias, voy a probarlo. Saludos y gracias a todos. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAJ2aOA_MJnzrPLtaG0fHjEZ0GOJo7K3gVw+A+E2S=7pw-xy...@mail.gmail.com
