o1bigtenor | 3 Nov 18:51 2015
Picon

Question

Greetings

I would like to use mondo to back up (at least periodically) a raid array.

Want to use 25 GB Bluray discs to do that but such are not an option
under mondo - - - is this capability being worked on at this time?

TIA

Dee

------------------------------------------------------------------------------
Peter | 29 Oct 00:03 2015
Picon

mondorescue.pubkey issue with perl-Module-ScanDeps


When trying to install from the mondo repo
(ftp://ftp.mondorescue.org/rhel/7/x86_64/) vi yum on Scientific Linux 7
I am seeing the following error.

Downloading packages:
warning:
/var/cache/yum/x86_64/7/mondorescue/packages/perl-Module-ScanDeps-1.10-3.el7.noarch.rpm:
Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
Retrieving key from
ftp://ftp.mondorescue.org//rhel/7/x86_64/mondorescue.pubkey

The GPG keys listed for the "rhel 7 x86_64 - mondorescue Vanilla
Packages" repository are already installed but they are not correct for
this package.
Check that the correct key URLs are configured for this repository.

 Failing package is: perl-Module-ScanDeps-1.10-3.el7.noarch
 GPG Keys are configured as:
ftp://ftp.mondorescue.org//rhel/7/x86_64/mondorescue.pubkey

It looks like package perl-Module-ScanDeps-1.10-3.el7.noarch is signed
with the wrong key.  I couldn't find this issue listed in the mail
archives, nor the wiki nor the bugs.

Thanks,
Peter

------------------------------------------------------------------------------
(Continue reading)

JB | 2 Nov 18:33 2015
Picon

Re: afio: Ready for volume

Any word on a fix for this issue?

Many Thanks to Peter Clark for the workaround, had to run mine as a separate script but it did the trick none the less.

Best Regards,
Jeff Brunner
------------------------------------------------------------------------------
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
o1bigtenor | 30 Oct 17:53 2015
Picon

Problems on install

Greetings

Needing (desperately) to use a program to find files from a failed raid array.

mondorescue seems like to should be able to find the files but it doesn't want to function.

/var/log/mindi.log


mindi v3.0.1-r3456
x86_64 architecture detected
mindi called with the following arguments:

Start date : Fri Oct 30 11:30:53 CDT 2015
-----------------------------
MONDO_SHARE =  
MINDI_LIB = /usr/lib/mindi
MINDI_SBIN = /usr/sbin
MINDI_CONF = /etc/mindi
MINDI_CACHE = /var/cache/mindi
-----------------------------
Mindi configuration file    
-----------------------------
-----------------------------
In Mindi
--------
EXTRA_SPACE = 120000
BOOT_SIZE = 86000
--------
FATAL ERROR. Please install isolinux first. If your syslinux RPM doesn't include isolinux, you may download an isolinux RPM from Mondo's website - go to http://www.mondorescue.org/downloads.shtml



/var/log/mondoarchive.log

INFO: Time started: Fri Oct 30 11:09:41 2015

DBG2: [TH=8738] libmondo-tools.c->setup_tmpdir#715: bkpinfo->tmpdir is being set to /tmp/mondo.tmp.jNcf3Z
DBG2: [TH=8738] libmondo-tools.c->setup_scratchdir#736: Purging old scratchdir /mondo.scratch.*
DBG2: [TH=8738] libmondo-tools.c->setup_scratchdir#757: bkpinfo->scratchdir is being set to /tmp/mondo.scratch.fyghV2
INFO: root is mounted at /dev/sda
INFO: That doesn't mean /dev/sda is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode().
DBG1: [TH=8738] libmondo-devices.c->am_I_in_disaster_recovery_mode#167: Is this a ramdisk? result = FALSE
INFO: running: dmesg -n1 > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: Mondo Archive v3.2.1-r3456 --- http://www.mondorescue.org
INFO: running x86_64 binaries
INFO: running on x86_64 architecture
INFO: -----------------------------------------------------------
INFO: NB: Mondo logs almost everything, so don't panic if you see
INFO: some error messages.  Please read them carefully before you
INFO: decide to break out in a cold sweat.    Despite (or perhaps
INFO: because of) the wealth of messages. some users are inclined
INFO: to stop reading this log. If Mondo stopped for some reason,
INFO: chances are it's detailed here.  More than likely there's a
INFO: message at the very end of this log that will tell you what
INFO: is wrong. Please read it!                          -Devteam
INFO: -----------------------------------------------------------
INFO: Zero...
DBG1: [Main] mondoarchive.c->welcome_to_mondoarchive#96: One...
DBG2: [Main] mondoarchive.c->welcome_to_mondoarchive#97: Two...
DBG3: [Main] mondoarchive.c->welcome_to_mondoarchive#98: Three...
DBG4: [Main] mondoarchive.c->welcome_to_mondoarchive#99: Four...
DBG2: [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#114: Unmounting old ramdisks if necessary
INFO: running: mount | grep cdrom | grep super > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=256
INFO: running: mount | grep floppy | grep super > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=256
DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1160: Started sub
DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1161: About to set g_boot_mountpt[0] to '\0'
DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1163: Done. Great. Seeting command to something
DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1165: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[    ]/boot[         ]" | tr -s ' ' '        ' | cut -f1 | head -n1'
DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1169: tmp = 'UUID=325c280b-4a4b-420e-8ac4-82aec9db48ec'
DBG2: [Main] libmondo-tools.c->mount_boot_if_necessary#1170: /boot is at UUID=325c280b-4a4b-420e-8ac4-82aec9db48ec according to /etc/fstab
DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1210: Ended sub
DBG1: [Main] libmondo-tools.c->get_kernel_version#245: g_kernel_version = 4.100000
INFO: running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: Checking sanity of your Linux distribution
INFO: running: grep ramdisk /proc/devices > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: 1 ramdisk
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: /dev/sda1 on /windows type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
INFO: /dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -Ew efi > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: /dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro)
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: I think you have a EFI/UEFI partition.
DBG4: [Main] libmondo-files.c->find_home_of_exe#360: find_home_of_exe --- Found cmp at /usr/bin/cmp
------------- mindi logfile included -------------------------
mindi v3.0.1-r3456
x86_64 architecture detected
mindi called with the following arguments:
-V
Start date : Fri Oct 30 11:09:41 CDT 2015
-----------------------------
MONDO_SHARE = /usr/share/mondo
MINDI_LIB = /usr/lib/mindi
MINDI_SBIN = /usr/sbin
MINDI_CONF = /etc/mindi
MINDI_CACHE = /var/cache/mindi
-----------------------------
Mindi configuration file    
-----------------------------
-----------------------------
In Mindi
--------
EXTRA_SPACE = 120000
BOOT_SIZE = 86000
--------
FATAL ERROR. Please install isolinux first. If your syslinux RPM doesn't include isolinux, you may download an isolinux RPM from Mondo's website - go to http://www.mondorescue.org/downloads.shtml
Please e-mail a copy of /var/log/mindi.log to the mailing list.
See http://www.mondorescue.org for more information.
WE CANNOT HELP unless you enclose that file.

Mindi 3.0.1-r3456 is exiting
End date : Fri Oct 30 11:09:42 CDT 2015
--------------------------------------------------------------
INFO: running: mindi -V > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: FATAL ERROR. Please install isolinux first. If your syslinux RPM doesn't include isolinux, you may download an isolinux RPM from Mondo's website - go to http://www.mondorescue.org/downloads.shtml
INFO: Please e-mail a copy of /var/log/mindi.log to the mailing list.
INFO: See http://www.mondorescue.org for more information.
INFO: WE CANNOT HELP unless you enclose that file.
INFO:  
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=65280
INFO: Could not ascertain mindi's version number.
INFO: You have not installed Mondo and/or Mindi properly.
INFO: Please uninstall and reinstall them both.
DBG1: [Main] ../common/newt-specific.c->fatal_error#304: Fatal error received - 'Please reinstall Mondo and Mindi.'
DBG3: [Main] ../common/newt-specific.c->fatal_error#320: OK, I think I'm the main PID.
DBG2: [Main] ../common/newt-specific.c->fatal_error#327: I'm going to do some cleaning up now.
DBG4: [Main] ../common/newt-specific.c->fatal_error#328: killall mindi 2> /dev/null
INFO: running: ps auxww | grep " /mondo/do-not " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: running: kill `ps auxww | grep " /mondo/do-not " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
INFO: kill -l [exitstatus]
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=512
INFO: running: ps auxww | grep " mondo.tmp " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: running: kill `ps auxww | grep " mondo.tmp " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
INFO: kill -l [exitstatus]
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=512
INFO: running: ps auxww | grep " ntfsclone " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
-----------------------------
Mindi configuration file    
-----------------------------
-----------------------------
In Mindi
--------
EXTRA_SPACE = 120000
BOOT_SIZE = 86000
--------
FATAL ERROR. Please install isolinux first. If your syslinux RPM doesn't include isolinux, you may download an isolinux RPM from Mondo's website - go to http://www.mondorescue.org/downloads.shtml
Please e-mail a copy of /var/log/mindi.log to the mailing list.
See http://www.mondorescue.org for more information.
WE CANNOT HELP unless you enclose that file.

Mindi 3.0.1-r3456 is exiting
End date : Fri Oct 30 11:09:42 CDT 2015
--------------------------------------------------------------
INFO: running: mindi -V > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: FATAL ERROR. Please install isolinux first. If your syslinux RPM doesn't include isolinux, you may download an isolinux RPM from Mondo's website - go to http://www.mondorescue.org/downloads.shtml
INFO: Please e-mail a copy of /var/log/mindi.log to the mailing list.
INFO: See http://www.mondorescue.org for more information.
INFO: WE CANNOT HELP unless you enclose that file.
INFO:  
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=65280
INFO: Could not ascertain mindi's version number.
INFO: You have not installed Mondo and/or Mindi properly.
INFO: Please uninstall and reinstall them both.
DBG1: [Main] ../common/newt-specific.c->fatal_error#304: Fatal error received - 'Please reinstall Mondo and Mindi.'
DBG3: [Main] ../common/newt-specific.c->fatal_error#320: OK, I think I'm the main PID.
DBG2: [Main] ../common/newt-specific.c->fatal_error#327: I'm going to do some cleaning up now.
DBG4: [Main] ../common/newt-specific.c->fatal_error#328: killall mindi 2> /dev/null
INFO: running: ps auxww | grep " /mondo/do-not " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: running: kill `ps auxww | grep " /mondo/do-not " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
INFO: kill -l [exitstatus]
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=512
INFO: running: ps auxww | grep " mondo.tmp " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: running: kill `ps auxww | grep " mondo.tmp " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
INFO: kill -l [exitstatus]
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=512
INFO: running: ps auxww | grep " ntfsclone " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: --------------------------------end of output------------------------------
INFO: ...ran just fine. :-)
INFO: running: kill `ps auxww | grep " ntfsclone " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
INFO: kill -l [exitstatus]
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=512
INFO: running: umount -d /mnt/cdrom > /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.jNcf3Z/mondo-run-prog-thing.err
INFO: --------------------------------start of output-----------------------------
INFO: umount: /mnt/cdrom: not mounted
INFO: --------------------------------end of output------------------------------
INFO: ...ran with res=8192


am running on a Debian stretch (testing) system.

Mindi is asking for a syslinux RPM but Debian doesn't use rpms so I'm more than somewhat confused.

What should I be doing to get things working?

Dee
------------------------------------------------------------------------------
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Lauris Idema | 21 Oct 13:51 2015
Picon

Unable to restore from NFS

Hi,

I feel silly asking this, but I am unable to restore my backups from NFS
using the mondorestore Net mount option.
I have created a backup to a NFS share using the backup script from the link
below:
http://trac.mondorescue.org/wiki/Documentation#Backup

The backup was made with the following settings in the script:

NFS_HOST=10.0.2.15
NFS_MOUNT=/var/nfs
MOUNT_PATH=/mnt/backupmondo
BCKUP_PATH=images

So the NFS share 10.0.2.15:/var/nfs is mounted as /mnt/backupmondo on the
backup client server and the backup iso has been created in the directory
images.
The backup itself is ok since I can successfully restore files when I choose
"read from Hard disk" and enter the path /mnt/backupmondo/images.

When I try to do a restore from NFS using the Net mount option I keep
getting the alert "Please mount that partition before you try to backup to
or restore from it".

I think I have tried all possible options for the mondorestore input, but
just to be sure this is what I think it should be.

1. Enter path and directory where archives are stored remotely:

images

2. Which protocol:

nfs

3. Which remote share should I mount:

10.0.2.15:/var/nfs

4. Which user

{blank}	

This is then followed by the alert "Please mount that partition before you
try to backup to or restore from it".
The mondorestore.log is not really helpful.

I am using Mondo 3.2.1-1 and have tried this on both Ubuntu and RHEL, but
get the same results.
Am I doing something wrong here?

Thanks!
Lauris

--
View this message in context: http://mondorescue-mailing-list.679749.n3.nabble.com/Unable-to-restore-from-NFS-tp4026906.html
Sent from the MondoRescue Mailing List mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Joel Girot | 8 Oct 11:30 2015
Picon

mondorescue lvm lvcreate failed

Hi all,

I am trying to test Mondorescue reinstall from mondorescue iso in expert
mode.

I tried to rebuild the lvm structure but lvcreate failed :

system :
debian version 8.2
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19) x86_64
GNU/Linux

mondo version :
Paquet libmondorescue-perl : 3.2.220150910110122-0
Paquet mindi : 3.0.220150910110122-0
Paquet mindi-busybox : 1.21.1-1
Paquet mondo : 3.2.220150910110122-0

Problem :

# fdisk -l

Disk /dev/sda: 465.3 GiB, 499558383616 bytes, 975699968 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa7e58e88

Device     Boot  Start       End   Sectors  Size Id Type
/dev/sda1  *      2048    526335    524288  256M 83 Linux
/dev/sda2       526336 975699967 975173632  465G 8e Linux LVM

# pvcreate /dev/sda2
  Physical volume "/dev/sda2" successfully created

# vgcreate vg00 /dev/sda2
  Volume group "vg00" successfully created

# vgchange -a y vg00
  0 logical volume(s) in volume group "vg00" now active

]# lvcreate -n gv0 -L 40G vg00
  /dev/vg00/gv0: not found: device not cleared
  Aborting. Failed to wipe start of new LV.

]# pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda2
  VG Name               vg00
  PV Size               465.00 GiB / not usable 3.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              119039
  Free PE               119039
  Allocated PE          0
  PV UUID               pSaR3w-hVNH-F0w2-Ep4I-uJV5-5joM-j8Z0ft

# vgdisplay
  --- Volume group ---
  VG Name               vg00
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                0
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               465.00 GiB
  PE Size               4.00 MiB
  Total PE              119039
  Alloc PE / Size       0 / 0
  Free  PE / Size       119039 / 465.00 GiB
  VG UUID               9dR497-qZcx-SMWO-oe2B-stVr-g0iN-TPx074

# lvdisplay

nothing ...

/var/log/mondorestore.log attached.

How to troubleshooting, please suggest

Regards

Joel

mondorestore.log
<http://mondorescue-mailing-list.679749.n3.nabble.com/file/n4026893/mondorestore.log>  

--
View this message in context: http://mondorescue-mailing-list.679749.n3.nabble.com/mondorescue-lvm-lvcreate-failed-tp4026893.html
Sent from the MondoRescue Mailing List mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Thiep Duong | 6 Oct 19:16 2015

Call to mkisofs to make ISO (ISO #2) ...failed

Hi I'm trying to make system backup to external mounted disk on /mnt
using command: 
 #mondoarchive -Oi -d /mnt/OS-Backup -N -s 4g -p eda-desktop-3 \
  -T /var/crash/tmp -S /var/crash/tmp -E "/tmp|/var/crash/tmp|/mnt/OS-Backup"

Thing went fine until it try to make iso 
---progress-form---4--- TASK:  [*..................]   3% done; 88:05 to go
Warning! CD is too big. It occupies 4926736 KB, which is more than the 4096 KB a
Please be patient. Do not be alarmed by on-screen inactivity.
Call to mkisofs to make ISO (ISO #2) ...failed
---promptdialogYN---1--- Failed to create ISO #2. Retry?

Looking at the output, look like first iso only 1.5GB made
[root <at> eda-desktop-3 etc]# ls -l /mnt/OS-Backup/
total 1554228
-rw-r--r--. 1 root root 1591523328 Oct  6 10:06 eda-desktop-3-1.iso

I tried to changed -s to smaller number, make no different, and I do have plenty of space
on system (5TB on /mnt   80GB on /var/tmp) 

OS: Red Hat Enterprise Linux Workstation release 6.5 (Santiago)
mindi-busybox-1.21.1-1.rhel6.x86_64
mindi-3.0.1-1.rhel6.x86_64
mondo-3.2.1-1.rhel6.x86_64

Any idea how to proceed?  Very large log file, and nothing there can tell me
DBG4: [Main] libmondo-fork.c->run_prog_in_bkgd_then_exit#609: sz_command = 'genisoimage -r -p MondoRescue -publisher www.mondorescue.org -A Mondo_Rescue_GPL_Version -J -boot-info-table -no-emul-boot -b isolinux.bin -c boot.cat -boot-load-size 4  -eltorito-alt-boot -e images/mindi-bootroot.img -no-emul-boot -o '/mnt/OS-Backup/eda-desktop-3-2.iso' -V 2 . >> /var/log/mondoarchive.log 2>> /var/log/mondoarchive.log'
I: -input-charset not specified, using iso-8859-1 (detected in locale settings)
File ./archives/198.afio.bz2 is larger than 4GiB-1.
-allow-limited-size was not specified. There is no way do represent this file size. Aborting.

Thanks in advance 
Anthony



------------------------------------------------------------------------------
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Saravanan S | 6 Oct 15:30 2015
Picon

Paritioning failed in Red hat 6.6

Hi

We have installed the Mondo Rescue in the Redhat environment with selinux enbabled and enforcing, The backup and restoration was successful. But the partition was not created correctly and the files are not copied properly.

During restore there was error saying partition failed. Attached are the archive and restore logs. Please help in troubleshoot.

DBG1: [Main] mondo-prep.c->partition_device#1649: last line = +512000K
DBG1: [Main] mondo-prep.c->partition_device#1650: Failed to create partition 1 on /dev/sda; sending 'Enter'...
DBG1: [Main] mondo-prep.c->p
artition_device#1655: Trying to set partition 1 type now on /dev/sda
DBG1: [Main] mondo-prep.c->set_partition_type#1872: Setting /dev/sda1's type to ext4 (83)
DBG2: [Main] mondo-prep.c->partition_device#1715: partition_device() --- leaving
DBG2: [Main] mondo-prep.c->partition_drive#1430: Found partition /dev/sda2 in mountlist
DBG2: [Main] mondo-prep.c->partition_device#1564: partition_device('/dev/sda', 2, 1, 'lvm', 292423680) --- starting
DBG2: [Main] mondo-prep.c->partition_device#1579: Partitioning device /dev/sda2 (285570 MB)
DBG1: [Main] libmondo-devices.c->is_this_device_mounted#1098: Is /dev/sda2 mounted?
DBG4: [Main] libmondo-devices.c->is_this_device_mounted#1127: tmp (command) = 'cat /proc/swaps | grep -E "^/dev/sda2 " > /dev/null 2> /dev/null'
INFO: Found MBR partition table format type on /dev/sda
DBG1: [Main] mondo-prep.c->partition_device#1641: Doing the new all-in-one fdisk thing
DBG1: [Main] mondo-prep.c->partition_device#1642: output = 'n
p
2

+292423680K
'
DBG1: [Main] mondo-prep.c->partition_device#1649: last line = +512000K
DBG1: [Main] mondo-prep.c->partition_device#1650: Failed to create partition 2 on /dev/sda; sending 'Enter'...
DBG1: [Main] mondo-prep.c->partition_device#1655: Trying to set partition 2 type now on /dev/sda

DBG1: [Main] mondo-prep.c->set_partition_type#1872: Setting /dev/sda2's type to lvm (8e)
DBG1: [Main] mondo-prep.c->set_partition_type#1899: last line = '+512000K'; part type set failed
DBG1: [Main] mondo-prep.c->partition_device#1658: Failed. Trying again...
DBG1: [Main] mondo-prep.c->set_partition_type#1872: Setting /dev/sda2's type to lvm (8e)
DBG1: [Main] mondo-prep.c->set_partition_type#1899: last line = '+512000K'; part type set failed
DBG1: [Main] mondo-prep.c->partition_device#1663: ...but failed to set type
DBG2: [Main] mondo-prep.c->partition_device#1715: partition_device() --- leaving
INFO: ------------------- fdisk.log looks like this ------------------
Can't locate Exporter/Heavy.pm in <at> INC ( <at> INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/share/perl5/Exporter.pm line 19.
BEGIN failed--compilation aborted at /usr/sbin/mr-parted2fdisk line 16.



OS installed
Red Hat Enterprise Linux Server release 6.6 (Santiago)

Mondo Rescue version
mondo-3.2.120150513102616-0.rhel6.x86_64
mindi-busybox-1.21.1-1.rhel6.x86_64
mindi-3.0.120150513102616-0.rhel6.x86_64

Attachment (log.rar): application/rar, 97 KiB
------------------------------------------------------------------------------
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Robert Grasso | 20 Sep 11:29 2015
Picon

Mondoarchive 3.2.1-1 and Ubuntu 14.04.3 : ok (sort of) (continued)

To be fair, Mondo is not meant for cloning in the first place : a nuke 
restore on the original computer is more likely to happen (I guess ?)

So I just tested that, hoping that the previous issues would not happen 
: well, it has not been so :

- the partitions UUID obviously changed at some point during the restore 
(knowing that I asked to reformat the partitions) so I had to regenerate 
grub.cfg by hand

- file system labels : here, I did not dig very deep : however, it seems 
that the first time, when I did not regenerate grub.cfg, the labels were 
kept; but as soon as I regenerated grub.cfg (hijacking the shell for 
initrd regeneration) the labels were blanked (I noticed that in the 
shell for relabeling the disks); which is an issue if you use the labels 
to identify the partitions in fstab (which I do)

I am attaching mondorestore.log.

BTW, I do not know how much this is related to those issues : a 
subcomponent keeps complaining that it does not find strict.pm; for 
instance in mondorestore.log :

Can't locate strict.pm in  <at> INC (you may need to install the strict 
module) ( <at> INC contains: /etc/perl /usr/local/lib/perl/5.18.2 
/usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 
/usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at 
/usr/sbin/mr-parted2fdisk line 14.

Well, in my OS, I find strict.pm here :
/usr/share/perl/5.18.2/strict.pm

actually :

root <at> tharv:~# ll /usr/share/perl/
total 20
drwxr-xr-x   3 root root  4096 sept. 20 10:17 ./
drwxr-xr-x 300 root root 12288 sept. 20 10:18 ../
lrwxrwxrwx   1 root root     6 sept. 20 10:17 5.18 -> 5.18.2/
drwxr-xr-x  58 root root  4096 sept. 20 10:17 5.18.2/

I guess the symbolic link must be missing ...

--

-- 
Robert Grasso
 <at> home
---
UNIX was not designed to stop you from doing stupid things, because
   that would also stop you from doing clever things. -- Doug Gwyn

Attachment (mondorestore.log): text/x-log, 351 KiB
------------------------------------------------------------------------------
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Robert Grasso | 19 Sep 22:00 2015
Picon

Mondoarchive 3.2.1-1 and Ubuntu 14.04.3 : ok (sort of)

Hello Bruno and list,

I just tested this latest Mondo version on my test vms : so, in short : it is kind of ok.

Before going into the details and underlining some issues, I want to thank you again for this huge and so useful piece of code, which you alone have to maintain on this overwhelming number of distributions and versions ! it is too bad that my company runs mostly Windows, we won't be a paid customer :-(

So now some details :

- the installation went well, and a backup through NFS on my host desktop went well too;
- restoring a small file and a big one (>100 MB) went well;
- booting in compare mode went well;

- now, I wanted to test a nuke restore : here, the road has been a bit more bumpy :
* first, I followed the suggested steps : I regenerated initrd, then as I restored into a new machine, I entered the "clone" section; and afterwards, the boot failed to find my root partition; so, the solution was to regenerate /boot/grub/grub.cfg with

grub-mkconfig -o /boot/grub/grub.cfg

I did this in the same shell  in which I regenerated initrd. Obviously, the suggested steps where one can change fstab, mtab, and grub.cfg prior to tuning grub did not do it : the grub.cfg generated here contained a wrong root partition UUID (probably the original one, I did not verify). BTW, on Ubuntu, it is not recommended to edit boot.cfg : here is the comment at the beginning of the file :

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub

Another thought : what is the point of suggesting to EDIT /etc/mtab ? I always believed one never had to change this one ?

* second : once I found the fix with grub-mkconfig, I first went nevertheless into the "clone" section : well, after that, fstab was completely messed up; I am attaching a snapshot; I first believed it was that weird text editor (oh, it is: nano ? well, I learned vi 25 years ago and I will stick to it - this one is kind of a seasoned IT sysadmin ;-); eventually, fstab was fixed NOT entering the "clone" section AT ALL !

* eventually, I had to relabel my partitions - maybe you could detect if labels exist at backup time, then restore them by default in case of a nuke restore ?

So, once I got all this right, the restored vm booted successfully ! I verified the OS with debsums, and all seems to be well
-- Robert Grasso <at> home --- UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
------------------------------------------------------------------------------
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Simon Magrin | 19 Sep 01:15 2015

Re: Mondo-devel Digest, Vol 112, Issue 17

Hi Bruno, thanks for your reply.

Even if I specify the device/partitions individually, ie;

mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1

mdadm still fails to create the MD arrays, prompting the error message 
below;

mdadm: RUN_ARRAY failed: Invalid argument

Any reason why this occurs?

I had the same problem with the previous mondo build (v3.2.0)

---

Regards

SIMON MAGRIN

On 2015-09-19 08:17, mondo-devel-request <at> lists.sourceforge.net wrote:

> Send Mondo-devel mailing list submissions to
> mondo-devel <at> lists.sourceforge.net
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/mondo-devel [1]
> or, via email, send a message with subject or body 'help' to
> mondo-devel-request <at> lists.sourceforge.net
> 
> You can reach the person managing the list at
> mondo-devel-owner <at> lists.sourceforge.net
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mondo-devel digest..."
> 
> Today's Topics:
> 
> 1. Re: Unable to restore to mdadm (mirror) arrays (Bruno CAPELETO)
> 2. mondonarchive fails on nfs with mkisofs error (Michael Lager)
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 18 Sep 2015 17:00:09 +0200
> From: Bruno CAPELETO <bruno.capeleto <at> abcreseau.com>
> Subject: Re: [Mondo-devel] Unable to restore to mdadm (mirror) arrays
> To: mondo-devel <mondo-devel <at> lists.sourceforge.net>
> Message-ID:
> <CABa3fk5-d0k1kuo4Y=BiSa7Jj6gsHpXGYiarRavm8MiV48kE9g <at> mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> very strange : the command is indeed invalid as it should be 
> ".../dev/sda1
> /dev/sdb1", not sd[ab]1
> Le 18 sept. 2015 14:59, "Simon Magrin" <simon <at> magrin.com> a ?crit :
> 
>> Hi there, I'm experiencing a problem with mondo v3.2.1 that'll like to 
>> report and
> 
> resolved.
> 
>> I'm try to restore a CentOS 7 build that consists of two MD mirror 
>> arrays. The archived host has a / (root) and swap array (/dev/md0 and 
>> /dev/md1
> 
> respectively).
> 
>> The destined host has the same hardware configuration and using the
> 
> 'nuke' option to auto restore.
> 
>> It progresses past the disk partitioning, but fails to create the two 
>> MD
> 
> arrays, prompting to use 'Interactive Mode' instead.
> 
>> Changing the partition tables and restoring to a single drive (not an 
>> MD
> 
> array), the mondo progresses to restore the data.
> 
>> Trying to create the arrays at a spare TTY prompt yields the error 
>> below; mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[ab]1 
>> mdadm: RUN_ARRAY failed: Invalid argument If I understand correctly, 
>> this means the kernel doesn't have the
> 
> CONFIG_MD_RAID1 parameter needed to create MD mirrors.
> 
>> Attached (logs.7z) for the archive, rescue tasks and fdisk logs. 
>> Please let me know if you need further information or require 
>> additional
> 
> testing from my end.
> 
>> -- Regards SIMON MAGRIN
> 
> ------------------------------------------------------------------------------
> 
>> _______________________________________________ Mondo-devel mailing 
>> list Mondo-devel <at> lists.sourceforge.net 
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel [1]
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 24 Aug 2015 16:52:29 +0100
> From: Michael Lager <outbound <at> lager.freeserve.co.uk>
> Subject: [Mondo-devel] mondonarchive fails on nfs with mkisofs error
> To: mondo-devel <at> lists.sourceforge.net
> Message-ID: <55DB3DBD.30203 <at> lager.freeserve.co.uk>
> Content-Type: text/plain; charset="us-ascii"
> 
> An HTML attachment was scrubbed...
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: mondoarchive.log
> Type: text/x-log
> Size: 392526 bytes
> Desc: not available
> 
> ------------------------------
> 
> ------------------------------------------------------------------------------
> 
> ------------------------------
> 
> _______________________________________________
> Mondo-devel mailing list
> Mondo-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mondo-devel [1]
> 
> End of Mondo-devel Digest, Vol 112, Issue 17
> ********************************************


Links:
------
[1] https://lists.sourceforge.net/lists/listinfo/mondo-devel

------------------------------------------------------------------------------

Gmane