Re: mondorestore command not found

Hi
I need help..

persistent-data/dm-persistent-data.ko
/lib/modules/3.10.0-514.6.2.el7.x86_64/kernel/drivers/md/dm-bio-prison.ko
/lib/modules/3.10.0-514.6.2.el7.
x86_64/kernel/drivers/md/dm-bufio.ko
/lib/modules/3.10.0-514.6.2.el7.x86_64/kernel/fs/xfs/xfs.ko
/lib/modules/3.10.0-514.6.2.el7.x86_64/kernel/f
s/btrfs/btrfs.ko
/lib/modules/3.10.0-514.6.2.el7.x86_64/kernel/lib/zlib_deflate/zlib_deflate.ko
/lib/modules/3.10.0-514.6.2.el7.x86_64/kernel/fs
/ext4/ext4.ko /lib/modules/3.10.0-514.6.2.el7.x86_64/kernel/fs/mbcache.ko
/lib/modules/3.10.0-514.6.2.el7.x86_64/kernel/fs/jbd2/jbd2.ko /lib/mod
ules/3.10.0-514.6.2.el7.x86_64/kernel/fs/nls/nls_utf8.ko to the rootfs with
-k 3.10.0-514.6.2.el7.x86_64
INFO: Deleting devfsd daemon from ramdisk
      ...because /sbin/devfsd not found
cp: error writing
‘/tmp/mondo.tmp.FRgiOq/mountpoint.31948/tmp/mountlist.txt’: No space left
on device
cp: failed to extend
‘/tmp/mondo.tmp.FRgiOq/mountpoint.31948/tmp/mountlist.txt’: No space left
on device
FATAL ERROR. Cannot copy mountlist to ramdisk
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.

INFO: Mindi 3.0.2-r3578 is exiting
INFO: End date : Wed Aug 16 16:43:38 CDT 2017
--------------------------------------------------------------
DBG4: [Main] libmondo-fork.c->run_prog_in_bkgd_then_exit#619: child res =
255
DBG3: [Main]
libmondo-fork.c->run_external_binary_with_percentage_indicator_NEW#684:
Parent res = 255
DBG1: [Main] libmondo-archive.c->call_mindi_to_supply_boot_disks#846:
-------------
DBG1: [Main] libmondo-archive.c->call_mindi_to_supply_boot_disks#847: End
of call to mindi
INFO: Mindi failed to create your boot+data disks.
DBG1: [Main] ../common/newt-specific.c->fatal_error#304: Fatal error
received - 'Failed to generate boot+data disks'
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

here is my df -h - output


[root@co-ps-ntp-a02 mondo]# df -h
Filesystem                                      Size  Used Avail Use%
Mounted on
/dev/mapper/vg00-lv01                            16G  603M   15G   4% /
devtmpfs                                        7.9G     0  7.9G   0% /dev
tmpfs                                           7.9G     0  7.9G   0%
/dev/shm
tmpfs                                           7.9G  485M  7.4G   7% /run
tmpfs                                           7.9G     0  7.9G   0%
/sys/fs/cgroup
/dev/mapper/vg00-lv04                           7.8G  1.5G  5.9G  20% /usr
/dev/mapper/vg00-lv06                           5.8G  199M  5.3G   4%
/usr/local
/dev/mapper/vg00-lv05                           7.8G  1.2G  6.3G  16% /tmp
/dev/mapper/vg00-lv02                           5.8G  111M  5.4G   2% /home
/dev/mapper/vg00-lv07                           6.8G  1.1G  5.4G  16% /opt
/dev/mapper/vg00-lv03                            12G  2.2G  8.9G  20% /var
/dev/sda1                                       491M  169M  323M  35% /boot
tmpfs                                           1.6G     0  1.6G   0%
/run/user/1008
10.129.192.105:/data/col1/testbackup            120T   91T   30T  76%
/testbackup
/dev/loop0                                      137M  1.6M  134M   2%
/tmp/mondo.tmp.h095xU/mountpoint.23617
/dev/loop1                                      228M  2.1M  224M   1%
/tmp/mondo.tmp.jgGhKf/mountpoint.8462
/dev/loop2                                      228M  2.1M  224M   1%
/tmp/mondo.tmp.MTz9vm/mountpoint.25687
/dev/loop3                                      228M  2.1M  224M   1%
/tmp/mondo.tmp.4baZTY/mountpoint.10775
10.129.192.105:/data/col1/testbackup/.snapshot  120T   91T   30T  76%
/testbackup/.snapshot
/dev/loop4                                      228M  2.1M  224M   1%
/tmp/mondo.tmp.FRgiOq/mountpoint.31948
tmpfs                                           1.6G     0  1.6G   0%
/run/user/996
[root@co-ps-ntp-a02 mondo]#


On Fri, Aug 18, 2017 at 8:15 AM, Stanislav Tokoš <
[email protected]> wrote:

>
>
> On 08/18/2017 01:45 PM, Stanislav Tokoš wrote:
>
>> Hello Bruno,
>>
>>
>> On 08/18/2017 12:26 PM, Bruno Cornec wrote:
>>
>>> Hello again,
>>>
>>> Bruno Cornec said on Fri, Aug 18, 2017 at 12:06:19PM +0200:
>>>
>>>> Stanislav Tokoš said on Thu, Aug 17, 2017 at 03:58:28PM +0200:
>>>>
>>>>> I finally figured them out. I am using mondo and mindi in the version
>>>>> 3.2.2. Patches from the attachments
>>>>>
>>>>
>>> I have applied most of your modifications. Please look at:
>>>>
>>>
>>> Well here:
>>> http://trac.mondorescue.org/changeset?sfp_email=&sfph_mail=&
>>> reponame=&new=3683%40branches&old=3680%40branches&sfp_email=&sfph_mail=
>>>
>>> I'm still looking at your patch on mr-make-me-bootable, which I'm not
>>> sure to understand. Could you explain to me the issue you encountered and
>>> the rationale of the fix please ?
>>>
>>
> I fixed this problem:
>
> 12:22 -------------
> 12:22 fdisk result:
> 12:22 -------------
> Disk /dev/vda: 16 GiB, 17179869184 bytes, 33554432 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: 0x0005211a
>
> Device     Boot   Start      End  Sectors Size Id Type
> /dev/vda1          2048  4192255  4190208   2G 82 Linux swap / Solaris
> /dev/vda2  *    4192256 33554431 29362176  14G 83 Linux
> 12:22 -------------
> 12:22 /tmp/mondorestore.cfg result:
> 12:22 -------------
>
>
> Command (m for help): Disk /dev/vda: 16 GiB, 17179869184 bytes, 33554432
> 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: 0x0005211a
>
> Device     Boot   Start      End  Sectors Size Id Type
> /dev/vda1          2048  4192255  4190208   2G 82 Linux swap / Solaris
> /dev/vda2       4192256 33554431 29362176  14G 83 Linux
>
> Command (m for help): The partition table has been altered.
> Calling ioctl() to re-read partition table.
> Syncing disks.
>
> Use of uninitialized value $min in substitution (s///) at
> /usr/sbin/mr-parted2fdisk line 242.
>
> Welcome to fdisk (util-linux 2.28).
> Changes will remain in memory only, until you decide to write them.
> Be careful before using the write command.
>
>
> Command (m for help): Partition number (1,2, default 2):
> The bootable flag on partition 2 is enabled now.
>
> Command (m for help): Partition number (1,2, default 2):
> The bootable flag on partition 2 is disabled now.
>
> Command (m for help): Disk /dev/vda: 16 GiB, 17179869184 bytes, 33554432
> 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: 0x0005211a
>
> Device     Boot   Start      End  Sectors Size Id Type
> /dev/vda1          2048  4192255  4190208   2G 82 Linux swap / Solaris
> /dev/vda2       4192256 33554431 29362176  14G 83 Linux
>
> Command (m for help): The partition table has been altered.
> Calling ioctl() to re-read partition table.
> Syncing disks.
>
> It means that the boot flag was removed by mr-make-me-bootable but the
> script didn't set up again back.
>
> Regards
>
> Stanislav
>
>
>>> Sure.
>>
>> 1. We don't need for cycling. Boot partition for each machine is only
>> one.
>> -       for p in "$activepart"; do
>> -               # First desactivate active partitions (coming from
>> previous usage)
>>
>>
>> 2. echo -en "${cmd}a\n$partno\np\nw\n" is replaced by echo -en
>> "a\n$partno\nw\n"
>> This command is same for mark or unmark boot partition. For that reason I
>> removed
>> cmd variable and piping to mr-parted2fdisk two times. It is the easiest
>> for debugging and
>> working for the each test case scenario without problem. I have already
>> test it.
>>
>> 3. added condition for missing $dummy variable
>>
>> +    elif [ ! "$dummy" ] ; then
>> +       echo -en "a\n$partno\nw\n" | mr-parted2fdisk $drive >> $LOGFILE
>> 2>> $LOGFILE
>>
>> Am I cleared? Is it make sense for you?
>>
>> PS: What about svn access? Is it possible access it? I am not able
>> checkout it. Thanks for your
>> advice.
>>
>> Regards
>>
>> Stanislav
>>
>>
>>>
>>> TIA,
>>> Bruno.
>>>
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mondo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>



-- 
With Regards
Satheesh

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Mondo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mondo-devel