mondo-devel Mailing List for Mondo Rescue

Hello all,
    I'm trying to use post-nuke.  I've placed the below script contents 
into a post-nuke file in the usr/bin subdirectory of the where I'm 
running mondoarchive. 

#!/bin/bash

/bin/chmod u+s /bin/ping
/bin/chmod u+s /bin/ping6


I'm calling mondoarchive using -P post_nuke.tgz and in the script that 
calls mondoarchive I call:
tar -zcf post_nuke.tgz usr

I've read the blog about how to use post-nuke and the ridiculously 
documented blurb on it in the man page.  I'd expect this to work and I 
don't get any errors (at least none that have prevented it from running) 
from mondoarchive nor from mondorescue but when the restore operation is 
complete, /bin/ping and /bin/ping6 do not have set-uid permissions.

Since I got 0 response on the patch I submitted, I'm left to assume that 
it was deemed stupid or unnecessary or simply ignored which likely means 
I'll be left to resorting to post-nuke until such time as I find my self 
using a version of tar that supports the extended filesystem 
attributes.  I was wondering if anyone who has actually gotten it 
working could lend some guidance as to why it doesn't seem to be 
working?  Is the path wrong?  Should it be something different in a 
"post-nuke" environment that gets run during mondorescue?

Thanks in advance.

I have all the options I thought I needed to run mondorestore.  I get an 
error while untar is running that says it ran out of space.  All I need 
to do is regenerate the ISO after booting to the stock kernel and 
everything works fine but creating the image while using my custom 
kernel causes the restore to drop to a command prompt after receiving 
the tar error and detecting RAID devices.  Any ideas on what kernel 
modules or features might be missing to cause this?

Hello all,
    I recently restored a backup using fc15 and version 3.0.2 of 
mondoarchive and 2.1.3 of mindi.  I lost the ability to ping.  It spits 
out "Operation not permitted" and it turns out fc15 is using POSIX file 
capabilities, getcap and setcap, rather than setuid on the ping command 
to let the average user run ping and ping6.  As you might imagine, these 
capabilities were lost on the restore so ping and ping6 broke for 
non-root users.  I don't know if more recent versions of GNU tar support 
archiving extended file attributes or not but apparently bsdtar does.  
I've thrown together a patch based on a quick once over of 
mondorestore.c so forgive me if I've violated some convention or some 
sacred philosophy of the mondo project or taken some unnecesary step(s) 
or misinterpreted a variable I was seeing, etc, etc....  I tested a 
small stand alone binary prog that just does what's in the patch and it 
works just fine ** but I have not actually built mondo and tested it 
with this patch **  It should work fine but right now I'm in crisis and 
cannot afford the time to run through the whole test.  It is a hack and 
I know it's a hack.  To compensate for the inadequacy of tar, it would 
take a file capability check on each and every file to be backed up and 
keeping it in a persistent list of file capability restore operations 
that are then processed using setcap during post-restore.  That is 
something much less trivial than what I've done below but at the moment 
it's all I have time for.  It assume the path to ping and ping6 follow 
fedora convention, another down side.  I don't know if there are any 
other files beyond ping and ping6 that will having this problem.  OK, 
now that you have my disclaimer, here you go:


Index: trunk/mondo/src/mondorestore/mondorestore.c
===================================================================
--- mondo/src/mondorestore/mondorestore.c (revision 3080)
+++ mondo/src/mondorestore/mondorestore.c (working copy)
@@ -2742,6 +2742,7 @@
        struct raidlist_itself *raidlist = NULL;
        struct s_bkpinfo *bkpinfo = NULL;
        struct s_node *filelist = NULL;
+       struct stat filestat;
        char *a = NULL, *b = NULL;
        bool run_postnuke = FALSE;
 
@@ -3095,6 +3096,22 @@
                }
        }
 
+       /* Compensate for distros that run ping and ping6 using posix
+          file capabilities instead of running them set-uid root.  This
+          will not be required when gnu tar behaves like bsd tar and
+          archives extended file attributes as well as perms and bits */
+       memset(&filestat, 0, sizeof(filestat));
+       mr_asprintf(&tmp, "%s/bin/ping", bkpinfo->restore_path);
+       if (!stat(tmp, &filestat)) {
+         chmod(tmp, filestat.st_mode|S_ISUID);
+       }
+       mr_free(tmp);
+       mr_asprintf(&tmp, "%s/bin/ping6", bkpinfo->restore_path);
+       if (!stat(tmp, &filestat)) {
+         chmod(tmp, filestat.st_mode|S_ISUID);
+       }
+       mr_free(tmp);
+
        /* clean up at the end */
        if (retval) {
                if (does_file_exist("/tmp/changed.files")) {

dv...@pi... said on Mon, Jan 07, 2013 at 11:23:07AM +0100:

> From time to time we experience errors while performing
> mondorestore. Error is logged as: "bzip2: Data integrity error when
> decompressing."
> That has been confirmed on various servers that are backed up with
> mondo. Files that were affected with this error were not been
> changed during backup. Log files are attached.
> We use mondo as our scheduled backup procedure. Problem is that
> thare is no errors while performing backup with mondo. Errors are
> logged only while performing restore. So it makes mondo backups that
> we make and count on, questionable and unreliable!
> 
> We opened bug at http://trac.mondorescue.org/ticket/661
> Please can you help us how to solve this problem.

1/ don't use -I in your backup script
2/ Use option -V to verify the backup
3/ do you transfer the ISO berfore restoring ? burn them ? check the
md5sum of each image before doing these operations.
4/ There are some errors in your archive log file:
/home/oracle/app/oracle/agent12g/agent_inst/sysman/emd/upload/pending/D_P4_S0_I586304.xml": No such file or directory 
Any relationship with your issue ?
5/ try reducing the size of your media, in case the end is causing issue
(4400m, or 4300m)
6/ change compression tool (gzip and lzo are also supported)
7/ and check your tarbet HDD to be sure it is sane.
8/ exclude the large files causing issue and backup them separately.

My guess is #3

In the last 10 years I've been dealing with MondoRescue, I've never seen
a previous report linked to an issue with bzip2 per se. 

Bruno.
-- 
Open Source & Linux Profession Lead EMEA         http://opensource.hp.com
EMEA Open Source HPISC Chief Technologist        http://hpintelco.net
FLOSS projects:     http://mondorescue.org     http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

After much consternation, here's what I've determined.  Logs are 
attached.  I did have IA 32-bit binary compat disabled in the kernel so 
when mindi would run /sbin/grub it would display an error indicating it 
couldn't execute it but mindi and mondoarchive were still running 
successfully.  I enabled 32-bit binary compat in the kernel and the 
error went away.  but the problems did not change at all.

Here's what I'm using to execute mondoarchive:
mondoarchive -OHNi0 -s 4483m -d /home/rtuser/images -I "/|/mnt/cdrom" -E 
"/backup|/sys|/root/.ssh/known_hosts|/root/.ssh/known_hosts2|/dev|/selinux|/var/cache/ccache|/var/cache/mindi|/var/cache/mondo|/var/cache/mondo-archive|/var/cache/yum|/var/tmp|/usr/src/kernels|/usr/local/src|/usr/share/doc|/usr/lib/mindi" 
-T /home/rtuser/images/temp -S /home/rtuser/images/scratch -f /dev/sda 
-l GRUB

When I reboot after the install, I get:

Loading GRUB Stage 1.5

Please wait, loading grub...


Then nothing at all.  It just sits there forever.  I used a rescue CD 
and ran grub-install /dev/sda.  After that, it does boot one kernel but 
not the one I need it too.  The kernel I need it to boot kicks out an 
error 19 saying the kernel needs to be loaded before init.

Now any ideas what could be going wrong?  This is *killing me*  I've 
been trying to figure this out for days.  I just need a bootable DVD or 
USB stick it does not matter which.  Nothing works.  Very frustrating.  
Thanks for any thoughts or any response at all.

JB





JB wrote:
> I've posted on some of these issues before.  You might recall.  I'm 
> back to not being able to get a USB stick to boot again.  It is 
> definitely not the USB stick.  Very frustrating.  syslinux is writing 
> its boot code to the stick.  I've had to resort to climbing through a 
> disassembly of the mbr instruction by instruction to try and figure 
> out what's happening.  In the mean time...I've always had the option 
> of wasting disc after disc of DVD-R media so I fell back to that.
>
> However, now that's not working either.  It does the entire 
> installation, then on reboot after removing the media and attempting 
> to boot the restored OS, I get the below messages and then it just 
> sits there forever.  Any ideas?
>
>
> GRUB Loading stage 1.5.
>
>
> GRUB loading, please wait...
>
>
>
>
> Thanks in advance!
>
> JB
>

Hi JB,

I know it concerns another GNU/Linux distribution, but could be a track :
https://www.suse.com/support/kb/doc.php?id=7005004

Otherwise, you could check MBR and grub chain through bootinfoscript:
http://bootinfoscript.sourceforge.net

Rgds,
Victor

-----Original Message-----
From: JB [mailto:ge...@it...] 
Sent: vendredi 18 janvier 2013 12:39
To: Mondo mailing list
Subject: [Mondo-devel] fits with fedora 15

I've posted on some of these issues before.  You might recall.  I'm back 
to not being able to get a USB stick to boot again.  It is definitely 
not the USB stick.  Very frustrating.  syslinux is writing its boot code 
to the stick.  I've had to resort to climbing through a disassembly of 
the mbr instruction by instruction to try and figure out what's 
happening.  In the mean time...I've always had the option of wasting 
disc after disc of DVD-R media so I fell back to that.

However, now that's not working either.  It does the entire 
installation, then on reboot after removing the media and attempting to 
boot the restored OS, I get the below messages and then it just sits 
there forever.  Any ideas?


GRUB Loading stage 1.5.


GRUB loading, please wait...




Thanks in advance!

JB

I've posted on some of these issues before.  You might recall.  I'm back 
to not being able to get a USB stick to boot again.  It is definitely 
not the USB stick.  Very frustrating.  syslinux is writing its boot code 
to the stick.  I've had to resort to climbing through a disassembly of 
the mbr instruction by instruction to try and figure out what's 
happening.  In the mean time...I've always had the option of wasting 
disc after disc of DVD-R media so I fell back to that.

However, now that's not working either.  It does the entire 
installation, then on reboot after removing the media and attempting to 
boot the restored OS, I get the below messages and then it just sits 
there forever.  Any ideas?


GRUB Loading stage 1.5.


GRUB loading, please wait...




Thanks in advance!

JB

Hello,

Ken...@sa... said on Tue, Jan 08, 2013 at 03:42:05PM -0500:

> Mondo Gurus:
> 
> I have a BL465 G6 Server with two internal disks. Since this model doesn’t support more internal disks, our application owners are considering buying 2 X 600GB Drives and replacing it with the existing 2 X 100GB Drives.
> 
> I intend to make use of a mondo image that I am going to take.
> 
> Since these are the root disks, can someone point me how I can restore the server/operating system back with the mondo image I have? The server is running RHEL 5.2 at the moment. If you could point me to some documentation, I'd really appreciate it. 

Hummm not sure I understand what you try to do. If you backup everythng
on your 100 GB disks, then you'll be able at restore time to resize
partitions in order to benefit from the 600 GB and then restore your
system. You "just" need the space to store the Mondorescue images

Bruno.
-- 
Open Source & Linux Profession Lead EMEA         http://opensource.hp.com
EMEA Open Source HPISC Chief Technologist        http://hpintelco.net
FLOSS projects:     http://mondorescue.org     http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

The kernel has too many dang options now!  It's a labyrinth


JB wrote:
> Nevermind.  I'm pulled a stupid...it happens...rarely :)
>
> CONFIG_BLK_DEV_LOOP was originally missing before I wrote the message 
> below.  I added it and tried it again then wrote the message below but 
> when I had added it, I had forgotten that I removed the USB stick so I 
> could reboot on my last kernel build.  Doh!  It's now running to 
> completion.  I'll see if it boots here in a while when it's finished.
>
> JB
>
>
> JB wrote:
>   
>> Gattegno, Victor (GSD CSC / CPR&Q / GCC - ISS/SW Tower) wrote:
>>   
>>     
>>> Hi JB,
>>>   
>>>     
>>>       
>>>> when I run mkdosfs on it everything runs just fine.
>>>> I can find no reason why it would be failing when mindi runs it.  
>>>>     
>>>>       
>>>>         
>>> The problem could be related to kpartx, informations and a workaround have been submitted in ticket 651
>>> http://trac.mondorescue.org/ticket/65
>>>     
>>>       
>> Thanks for the reply.  While searching I did come across that ticket but 
>> on my installation I don't even have kpartx installed.  My mindi log 
>> shows this:
>>
>> /sbin/klogd
>> WARNING: /sbin/klogd does not exist; cannot be LDD'd.
>> /sbin/kmod
>> WARNING: /sbin/kmod does not exist; cannot be LDD'd.
>> /sbin/kpartx
>> WARNING: /sbin/kpartx does not exist; cannot be LDD'd.
>>
>> I'd imagine fedora never put it on there because I'm not using LVM nor 
>> the device mapper features of the kernel for any mounts at all.  I've 
>> tried running it both with and without the DM and MD kernel features and 
>> modules both with the same result.  How important is it that kpartx be 
>> installed?  From what I can tell in that bug report, it does something 
>> nasty to what mkdosfs expects anyway so maybe it's a good thing I don't 
>> have it?  Given that all this works wonderfully on the 2.6.43 kernel 
>> packaged with FC15 even with kpartx missing, I can't imagine that would 
>> be the problem.  I read the page that lists kernel requirements but it 
>> is a bit difficult to interpret.  Here is what it says along with my 
>> comments albeit the kernel versions listed clearly indicate *old* kernel 
>> requirements:
>>
>> - stable loopfs support, which means it really needs to be 2.2.19 or 
>> 2.4.7 (or later)
>>     JB ----> Yikes! 2.4.7?  Way old.  I assume this refers to 
>> CONFIG_BLK_DEV_LOOP?  If so, it's there
>>
>> - CD-ROM device support
>>     JB ----> Check, cdrom and usb can be mounted no problems
>>
>> - IS9660 file system support
>>     JB ----> Check, not sure why this is important for USB but it's 
>> there anyway
>>
>> - initrd ramdisk support (built-in)
>>     JB ----> Check, compiled in and not as a module as would be required 
>> anyway
>>
>> - Virtual memory file system support (built-in)
>>     JB ----> I'm guessing this is swap?  If so, Check and confirmed it's 
>> mounted by UUID and writable
>>
>> - ext2 file system support (built-in)
>>     JB ----> Check, ext2, ext3, and ext4 file systems are all compiled 
>> into the kernel with automounter as module
>>
>> - Support for the backup media (Tape, CD-RW, NFS, Hard disk)
>>     JB ----> Check, USB and CD-RW both have support and function with 
>> normal command line utilities
>>
>> - vfat support in the active kernel - mindi needs this when creating 
>> syslinux boot media
>>     JB ----> Check, can manually use syslinux to create boot media on 
>> USB no problem.
>>  
>>
>> I've made numerous sweeps through the kernel looking for imaginable 
>> missing features only to come up empty handed.  I've included things I 
>> didn't even think were relevant and it still doesn't work.
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
>> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
>> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
>> SALE $99.99 this month only - learn more at:
>> http://p.sf.net/sfu/learnmore_122512
>> _______________________________________________
>> Mondo-devel mailing list
>> Mon...@li...
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>   
>>     
>
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> Mondo-devel mailing list
> Mon...@li...
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>   

Nevermind.  I'm pulled a stupid...it happens...rarely :)

CONFIG_BLK_DEV_LOOP was originally missing before I wrote the message 
below.  I added it and tried it again then wrote the message below but 
when I had added it, I had forgotten that I removed the USB stick so I 
could reboot on my last kernel build.  Doh!  It's now running to 
completion.  I'll see if it boots here in a while when it's finished.

JB


JB wrote:
> Gattegno, Victor (GSD CSC / CPR&Q / GCC - ISS/SW Tower) wrote:
>   
>> Hi JB,
>>   
>>     
>>> when I run mkdosfs on it everything runs just fine.
>>> I can find no reason why it would be failing when mindi runs it.  
>>>     
>>>       
>> The problem could be related to kpartx, informations and a workaround have been submitted in ticket 651
>> http://trac.mondorescue.org/ticket/65
>>     
> Thanks for the reply.  While searching I did come across that ticket but 
> on my installation I don't even have kpartx installed.  My mindi log 
> shows this:
>
> /sbin/klogd
> WARNING: /sbin/klogd does not exist; cannot be LDD'd.
> /sbin/kmod
> WARNING: /sbin/kmod does not exist; cannot be LDD'd.
> /sbin/kpartx
> WARNING: /sbin/kpartx does not exist; cannot be LDD'd.
>
> I'd imagine fedora never put it on there because I'm not using LVM nor 
> the device mapper features of the kernel for any mounts at all.  I've 
> tried running it both with and without the DM and MD kernel features and 
> modules both with the same result.  How important is it that kpartx be 
> installed?  From what I can tell in that bug report, it does something 
> nasty to what mkdosfs expects anyway so maybe it's a good thing I don't 
> have it?  Given that all this works wonderfully on the 2.6.43 kernel 
> packaged with FC15 even with kpartx missing, I can't imagine that would 
> be the problem.  I read the page that lists kernel requirements but it 
> is a bit difficult to interpret.  Here is what it says along with my 
> comments albeit the kernel versions listed clearly indicate *old* kernel 
> requirements:
>
> - stable loopfs support, which means it really needs to be 2.2.19 or 
> 2.4.7 (or later)
>     JB ----> Yikes! 2.4.7?  Way old.  I assume this refers to 
> CONFIG_BLK_DEV_LOOP?  If so, it's there
>
> - CD-ROM device support
>     JB ----> Check, cdrom and usb can be mounted no problems
>
> - IS9660 file system support
>     JB ----> Check, not sure why this is important for USB but it's 
> there anyway
>
> - initrd ramdisk support (built-in)
>     JB ----> Check, compiled in and not as a module as would be required 
> anyway
>
> - Virtual memory file system support (built-in)
>     JB ----> I'm guessing this is swap?  If so, Check and confirmed it's 
> mounted by UUID and writable
>
> - ext2 file system support (built-in)
>     JB ----> Check, ext2, ext3, and ext4 file systems are all compiled 
> into the kernel with automounter as module
>
> - Support for the backup media (Tape, CD-RW, NFS, Hard disk)
>     JB ----> Check, USB and CD-RW both have support and function with 
> normal command line utilities
>
> - vfat support in the active kernel - mindi needs this when creating 
> syslinux boot media
>     JB ----> Check, can manually use syslinux to create boot media on 
> USB no problem.
>  
>
> I've made numerous sweeps through the kernel looking for imaginable 
> missing features only to come up empty handed.  I've included things I 
> didn't even think were relevant and it still doesn't work.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> Mondo-devel mailing list
> Mon...@li...
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>   

Gattegno, Victor (GSD CSC / CPR&Q / GCC - ISS/SW Tower) wrote:
> Hi JB,
>   
>> when I run mkdosfs on it everything runs just fine.
>> I can find no reason why it would be failing when mindi runs it.  
>>     
> The problem could be related to kpartx, informations and a workaround have been submitted in ticket 651
> http://trac.mondorescue.org/ticket/65
Thanks for the reply.  While searching I did come across that ticket but 
on my installation I don't even have kpartx installed.  My mindi log 
shows this:

/sbin/klogd
WARNING: /sbin/klogd does not exist; cannot be LDD'd.
/sbin/kmod
WARNING: /sbin/kmod does not exist; cannot be LDD'd.
/sbin/kpartx
WARNING: /sbin/kpartx does not exist; cannot be LDD'd.

I'd imagine fedora never put it on there because I'm not using LVM nor 
the device mapper features of the kernel for any mounts at all.  I've 
tried running it both with and without the DM and MD kernel features and 
modules both with the same result.  How important is it that kpartx be 
installed?  From what I can tell in that bug report, it does something 
nasty to what mkdosfs expects anyway so maybe it's a good thing I don't 
have it?  Given that all this works wonderfully on the 2.6.43 kernel 
packaged with FC15 even with kpartx missing, I can't imagine that would 
be the problem.  I read the page that lists kernel requirements but it 
is a bit difficult to interpret.  Here is what it says along with my 
comments albeit the kernel versions listed clearly indicate *old* kernel 
requirements:

- stable loopfs support, which means it really needs to be 2.2.19 or 
2.4.7 (or later)
    JB ----> Yikes! 2.4.7?  Way old.  I assume this refers to 
CONFIG_BLK_DEV_LOOP?  If so, it's there

- CD-ROM device support
    JB ----> Check, cdrom and usb can be mounted no problems

- IS9660 file system support
    JB ----> Check, not sure why this is important for USB but it's 
there anyway

- initrd ramdisk support (built-in)
    JB ----> Check, compiled in and not as a module as would be required 
anyway

- Virtual memory file system support (built-in)
    JB ----> I'm guessing this is swap?  If so, Check and confirmed it's 
mounted by UUID and writable

- ext2 file system support (built-in)
    JB ----> Check, ext2, ext3, and ext4 file systems are all compiled 
into the kernel with automounter as module

- Support for the backup media (Tape, CD-RW, NFS, Hard disk)
    JB ----> Check, USB and CD-RW both have support and function with 
normal command line utilities

- vfat support in the active kernel - mindi needs this when creating 
syslinux boot media
    JB ----> Check, can manually use syslinux to create boot media on 
USB no problem.
 

I've made numerous sweeps through the kernel looking for imaginable 
missing features only to come up empty handed.  I've included things I 
didn't even think were relevant and it still doesn't work.

Hi JB,

> when I run mkdosfs on it everything runs just fine.
> I can find no reason why it would be failing when mindi runs it.  

The problem could be related to kpartx, informations and a workaround have been submitted in ticket 651
http://trac.mondorescue.org/ticket/651

Rgds,
Victor

-----Original Message-----
From: JB [mailto:ge...@it...] 
Sent: lundi 14 janvier 2013 08:30
To: Mondo mailing list
Subject: [Mondo-devel] mindi not working...again

I'm having another problem...again.  I really am trying hard to 
understand why I'm getting such inconsistently bad behavior out of my 
runs of mondoarchive and mindi.

System:
Fedora core 15
Mondarchive 3.0.2
mindi 2.1.3

I had this successfully working after that strange problem I posted 
about earlier where none of by successfully created USB sticks would 
actually boot.  I imaged them with some windows utility and then they 
suddenly started working for mondo/mindi runs again.  But now, I'm 
getting this in the mondoarchive.log

ERROR: Unable to create a vfat filesystem on /dev/sdb1

And I'm getting this in mindi.log:

INFO: The USB device /dev/sdb now looks like this:

--------------------------------------------------------------------------------------------------------
Disk /dev/sdb: 8004 MB, 8004304896 bytes
21 heads, 32 sectors/track, 23264 cylinders, total 15633408 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
Disk identifier: 0x82c33ec4

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    15633407     7815680    b  W95 FAT32
INFO: Unmounting /dev/sdb1 just in case again
umount: /dev/sdb1: not found
INFO: Creating a vfat filesystem on /dev/sdb1
mkdosfs 3.0.11 (24 Dec 2010)
ERROR: Unable to create a vfat filesystem on /dev/sdb1
       Make sure your USB device is pluged in and partitioned (/dev/sdb1 
must exist on it)

Disk /dev/sdb: 8004 MB, 8004304896 bytes
21 heads, 32 sectors/track, 23264 cylinders, total 15633408 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
Disk identifier: 0x82c33ec4

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    15633407     7815680    b  W95 FAT32
Mindi 2.1.3-r3026 is exiting
End date : Sun Jan 13 22:04:51 MST 2013
--------------------------------------------------------------------------------------------------------


You can see sdb1 is there and when I run mkdosfs on it everything runs 
just fine.  I can find no reason why it would be failing when mindi runs 
it.  I'm running it as the root user as far as I can tell the node 
exists from the start.  I've done a search and lots of people that have 
this error but none match my case.  It isn't already mounted and none of 
the other solutions to this problem I was able to find solve my 
problem.  I'm at a bit of a loss.  It is a custom compiled kernel I'm 
running 2.6.38.8.  Please don't suggest using a different kernel.  I 
have a real constraint why it *must* be that version.  I'm about to 
reboot and try it again with the stock 2.6.43 kernel that FC 15 has and 
see what that yields but if anyone has any suggestions on this, I'd sure 
love to hear them!

Thanks in advance!

JB




------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
Mondo-devel mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/mondo-devel

More info.  I tried under the stock shipped kernel 2.6.43 with FC15 and 
everything worked fine.  I'm at a total loss here.  Here is the module 
list from the working 2.6.43 kernel.

ext2                   72913  0
vfat                   17411  0
msdos                  17325  0
fat                    60279  2 vfat,msdos
usb_storage            52112  0
nvidia              11746144  0
snd_hda_codec_realtek   145364  1
snd_hda_intel          33276  0
snd_hda_codec         115767  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep              17611  1 snd_hda_codec
snd_seq                64807  0
snd_seq_device         14129  1 snd_seq
i2c_nforce2            13166  0
snd_pcm                97170  2 snd_hda_intel,snd_hda_codec
snd_timer              28815  2 snd_seq,snd_pcm
snd                    78908  8 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore              14484  1 snd
snd_page_alloc         18101  2 snd_hda_intel,snd_pcm
ppdev                  17635  0
parport_pc             28082  0
parport                44515  2 ppdev,parport_pc
r8169                  60789  0
mii                    13527  1 r8169
i2c_core               37991  2 nvidia,i2c_nforce2
joydev                 17412  0
pata_acpi              13027  0
ata_generic            12899  0
wmi                    18697  0
pata_amd               14111  0



Here is the module list for the non-working 2.6.38.8 kernel:
usb_storage            47693  0
ext2                   65683  0
vfat                   10515  0
msdos                   7549  0
fat                    50917  2 vfat,msdos
snd_hda_codec_realtek   341739  1
snd_hda_intel          24950  0
snd_hda_codec          89306  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               6557  1 snd_hda_codec
snd_seq                56901  0
snd_seq_device          6449  1 snd_seq
snd_pcm                84210  2 snd_hda_intel,snd_hda_codec
snd_timer              21224  2 snd_seq,snd_pcm
snd                    66009  8 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
i2c_nforce2             5501  0
soundcore               7540  1 snd
i2c_core               22644  1 i2c_nforce2
joydev                  9932  0
r8169                  41770  0
snd_page_alloc          8117  2 snd_hda_intel,snd_pcm
wmi                     9441  0
pcspkr                  1966  0
mii                     4798  1 r8169
ipv6                  317222  22
autofs4                24482  6
ahci                   21302  3
pata_acpi               3667  0
ata_generic             3931  0
libahci                21579  1 ahci
pata_amd               12026  0


As you can see they are nearly identical.  I'm at a loss to describe 
this behavior.  Everything on this system works as expected *except* 
this.  There has to a feature of a compiled module or something I'm 
missing here I just can't imagine what would cause this.  The mkdosfs 
utility works when run from command line but somehow not when mindi runs it?

JB





JB wrote:
> I'm having another problem...again.  I really am trying hard to 
> understand why I'm getting such inconsistently bad behavior out of my 
> runs of mondoarchive and mindi.
>
> System:
> Fedora core 15
> Mondarchive 3.0.2
> mindi 2.1.3
>
> I had this successfully working after that strange problem I posted 
> about earlier where none of by successfully created USB sticks would 
> actually boot.  I imaged them with some windows utility and then they 
> suddenly started working for mondo/mindi runs again.  But now, I'm 
> getting this in the mondoarchive.log
>
> ERROR: Unable to create a vfat filesystem on /dev/sdb1
>
> And I'm getting this in mindi.log:
>
> INFO: The USB device /dev/sdb now looks like this:
>
> --------------------------------------------------------------------------------------------------------
> Disk /dev/sdb: 8004 MB, 8004304896 bytes
> 21 heads, 32 sectors/track, 23264 cylinders, total 15633408 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
> Disk identifier: 0x82c33ec4
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1   *        2048    15633407     7815680    b  W95 FAT32
> INFO: Unmounting /dev/sdb1 just in case again
> umount: /dev/sdb1: not found
> INFO: Creating a vfat filesystem on /dev/sdb1
> mkdosfs 3.0.11 (24 Dec 2010)
> ERROR: Unable to create a vfat filesystem on /dev/sdb1
>        Make sure your USB device is pluged in and partitioned (/dev/sdb1 
> must exist on it)
>
> Disk /dev/sdb: 8004 MB, 8004304896 bytes
> 21 heads, 32 sectors/track, 23264 cylinders, total 15633408 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
> Disk identifier: 0x82c33ec4
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1   *        2048    15633407     7815680    b  W95 FAT32
> Mindi 2.1.3-r3026 is exiting
> End date : Sun Jan 13 22:04:51 MST 2013
> --------------------------------------------------------------------------------------------------------
>
>
> You can see sdb1 is there and when I run mkdosfs on it everything runs 
> just fine.  I can find no reason why it would be failing when mindi runs 
> it.  I'm running it as the root user as far as I can tell the node 
> exists from the start.  I've done a search and lots of people that have 
> this error but none match my case.  It isn't already mounted and none of 
> the other solutions to this problem I was able to find solve my 
> problem.  I'm at a bit of a loss.  It is a custom compiled kernel I'm 
> running 2.6.38.8.  Please don't suggest using a different kernel.  I 
> have a real constraint why it *must* be that version.  I'm about to 
> reboot and try it again with the stock 2.6.43 kernel that FC 15 has and 
> see what that yields but if anyone has any suggestions on this, I'd sure 
> love to hear them!
>
> Thanks in advance!
>
> JB
>
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> Mondo-devel mailing list
> Mon...@li...
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>   

I'm having another problem...again.  I really am trying hard to 
understand why I'm getting such inconsistently bad behavior out of my 
runs of mondoarchive and mindi.

System:
Fedora core 15
Mondarchive 3.0.2
mindi 2.1.3

I had this successfully working after that strange problem I posted 
about earlier where none of by successfully created USB sticks would 
actually boot.  I imaged them with some windows utility and then they 
suddenly started working for mondo/mindi runs again.  But now, I'm 
getting this in the mondoarchive.log

ERROR: Unable to create a vfat filesystem on /dev/sdb1

And I'm getting this in mindi.log:

INFO: The USB device /dev/sdb now looks like this:

--------------------------------------------------------------------------------------------------------
Disk /dev/sdb: 8004 MB, 8004304896 bytes
21 heads, 32 sectors/track, 23264 cylinders, total 15633408 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
Disk identifier: 0x82c33ec4

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    15633407     7815680    b  W95 FAT32
INFO: Unmounting /dev/sdb1 just in case again
umount: /dev/sdb1: not found
INFO: Creating a vfat filesystem on /dev/sdb1
mkdosfs 3.0.11 (24 Dec 2010)
ERROR: Unable to create a vfat filesystem on /dev/sdb1
       Make sure your USB device is pluged in and partitioned (/dev/sdb1 
must exist on it)

Disk /dev/sdb: 8004 MB, 8004304896 bytes
21 heads, 32 sectors/track, 23264 cylinders, total 15633408 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
Disk identifier: 0x82c33ec4

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    15633407     7815680    b  W95 FAT32
Mindi 2.1.3-r3026 is exiting
End date : Sun Jan 13 22:04:51 MST 2013
--------------------------------------------------------------------------------------------------------


You can see sdb1 is there and when I run mkdosfs on it everything runs 
just fine.  I can find no reason why it would be failing when mindi runs 
it.  I'm running it as the root user as far as I can tell the node 
exists from the start.  I've done a search and lots of people that have 
this error but none match my case.  It isn't already mounted and none of 
the other solutions to this problem I was able to find solve my 
problem.  I'm at a bit of a loss.  It is a custom compiled kernel I'm 
running 2.6.38.8.  Please don't suggest using a different kernel.  I 
have a real constraint why it *must* be that version.  I'm about to 
reboot and try it again with the stock 2.6.43 kernel that FC 15 has and 
see what that yields but if anyone has any suggestions on this, I'd sure 
love to hear them!

Thanks in advance!

JB

Hi, all.

I've just tested Fedora 18 RC3 & the Fedora Go/NoGo meeting has just
announced that it'll be released on Tuesday 15th January.

If it would help, seeing as  I've got it installed on an actual physical
server as opposed to a vm, are there any recent images from this year
that I can test Mondo? I can see stuff in the test repo from 04/01/13.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal

Mondo Gurus:

I have a BL465 G6 Server with two internal disks. Since this model doesn’t support more internal disks, our application owners are considering buying 2 X 600GB Drives and replacing it with the existing 2 X 100GB Drives.

I intend to make use of a mondo image that I am going to take.

Since these are the root disks, can someone point me how I can restore the server/operating system back with the mondo image I have? The server is running RHEL 5.2 at the moment. If you could point me to some documentation, I'd really appreciate it. 

Kennedy G. Doss – K-Force, Consultant for:
Regional Service Delivery Americas│Application Hosting Services
GIS – Global Infrastructure Services
TEL: 908 – 981 – 5295 │CELL: 732 – 371 – 2887
MailStop: 55D-310A
55 Corporate Drive – Bridgewater – New Jersey



Please consider the environment before printing this email



-----Original Message-----
From: Ken Arck [mailto:ah...@ah...] 
Sent: Sunday, December 23, 2012 6:46 PM
To: Mondo mailing list
Subject: Re: [Mondo-devel] error on mondorestore

Which versions of everything do I need for an old CentOS 4.x runnng on x86 NON 32/64 bit hardware (Via EP5000)?

I tried several of the i386 versions for rhel 4 and they all fail because they're looking for /lib64, which obviously doesn't exist on my machine

Ken


------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Mondo-devel mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/mondo-devel

 From time to time we experience errors while performing mondorestore. 
Error is logged as: "bzip2: Data integrity error when decompressing."
That has been confirmed on various servers that are backed up with 
mondo. Files that were affected with this error were not been changed 
during backup. Log files are attached.
We use mondo as our scheduled backup procedure. Problem is that thare is 
no errors while performing backup with mondo. Errors are logged only 
while performing restore. So it makes mondo backups that we make and 
count on, questionable and unreliable!

We opened bug at http://trac.mondorescue.org/ticket/661
Please can you help us how to solve this problem.

Thanks
Vedad