mondo-devel Mailing List for Mondo Rescue

On 7/21/2014 12:28 PM, Bruno Cornec wrote:
> Hello Steve,
>
> Steve Campbell said on Mon, Jul 21, 2014 at 12:00:34PM -0400:
>> The last time I attempted restoring a Mondo backup on a Centos 6.5
>> server, I had problems. The list sort of gave me the idea that it was
>> due to the systemd stuff.
> Humm no. RHEL 6.5 doesn't use systemd. RHEL 7 is.
> So your problems are unrelated to that issue, that in between has been
> solved. But for that you need version 3.2.0 of MondoRescue (only in beta
> for now).
>
> If you had issues with restoring, please provide your logs as per
> http://mondorescue.org/support.shtml
>
> Best regards,
> Bruno.
Sorry Bruno,

I was thinking of another problem we were having (glusterfs related).

Any way, we are having a problem restoring.

I have a pair of Centos 6.5 servers. I've built one and was going to use 
Mondo to create the second one using "Nuke". These machines have two 
SATA drives in them and were set up using software RAID during the 
initial installation and partitioning of the Centos install. I guess you 
could say the RAID had 3 containers, one for /boot, one for swap and one 
for "/".

I start the "nuke" and get the following messages:

No filesystem could mount root, tried: ISO9660
Kernel panic - not syncing : VFS: unable to mount root fs on 
unknown-block(1,0)
Pid: 1, comm: swapper Not tainted 2.6.32-431.el6.x86_64 #1
Call Trace:

And then there are a bunch of lines of the form
[<ffffffff815271fa>] ? panic+0xa7/0x16f


I'm wondering if the reference to ISO9660 is a problem with the DVD or 
do you need the other trace lines?

Thanks for the help

steve campbell

Back from my trip, and running some tests. I installed a new vm Ubuntu 
v14.04 x86_64 in Virtualbox v4.3.12, for tests purposes. It is hosted on 
my main x86_64 Ubuntu 12.10 home computer - I will upgrade my OS when I 
have a stable Mondorescue ;-) .

So, here is the command I am using on my test vm, almost identical to my 
standard one :

mondoarchive -On  nfs://power4:/backup_rubedo -N -d tharv/`date +'%Y%U'` 
-p "tharv-full-`date +'%Y%m%d'`" -s 20g -L -g -S /var/tmp -T /var/tmp -V

power4 is my host.

and some issues :

- the directory with the current week as the name was not created 
automatically, mondo reported an error : but I am running the same mondo 
test version on my firewall running Ubuntu 13.10, and there these 
directories are created automatically ? I am a bit puzzled ...

- I had this error message :
INFO: Incorporating Network-related settings
Can't locate IO/Interface/Simple.pm in @INC (you may need to install the 
IO::Interface::Simple module) (@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/bin/mr-net-get-config line 13.
BEGIN failed--compilation aborted at /usr/bin/mr-net-get-config line 13.

and another one complaining about the lack of Net/IPv4Addr.pm, so I 
installed the packages libio-interface-perl and 
libnetwork-ipv4addr-perl; then the errors were gone.

Then I wanted to boot from the iso in Compare mode : the iso booted 
correctly, I started the "compare" mode, and quickly I had a wonderful 
(=ugly) System panic. Same with mondorescue.iso. You can watch the boot 
video recorded with Virtualbox's video capture here :

https://drive.google.com/file/d/0B4xZuHiNqi6mWHlOOF9oclpZdUk/edit?usp=sharing

Now, I wanted to try to restore something interactively (remote nfs 
directory mounted) => Segmentation fault : strace log attached ...

What next, boss ;-) ?

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

On 06/30/2014 11:52 AM, Bruno Cornec wrote:
> Robert Grasso said on Mon, Jun 30, 2014 at 09:32:40AM +0200:
>> I am leaving for two weeks so I won't be able to run many more tests.
>> But one full backup of a small Ubuntu 13.10 machine across NFS ran just
>> fine (and just in time ;-) )
> Thanks for your feedback !
>
> Bruno.

Hello Steve,

Steve Campbell said on Mon, Jul 21, 2014 at 12:00:34PM -0400:
> The last time I attempted restoring a Mondo backup on a Centos 6.5 
> server, I had problems. The list sort of gave me the idea that it was 
> due to the systemd stuff.

Humm no. RHEL 6.5 doesn't use systemd. RHEL 7 is.
So your problems are unrelated to that issue, that in between has been
solved. But for that you need version 3.2.0 of MondoRescue (only in beta
for now).

If you had issues with restoring, please provide your logs as per
http://mondorescue.org/support.shtml

Best regards,
Bruno.
-- 
Open Source Profession, Linux Community Lead WW http://opensource.hp.com
EMEA EG Open Source Technology Strategist       http://hpintelco.net
FLOSS projects:     http://mondorescue.org     http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

Just wondering...
The last time I attempted restoring a Mondo backup on a Centos 6.5 
server, I had problems. The list sort of gave me the idea that it was 
due to the systemd stuff.

Has this been resolved? The last I saw was that Bruno had been in touch 
with some folk that might have helped him resolve the systemd problems.

Thanks all for a great utility.

steve campbell

After a bit more testing, I discovered that Mondo no longer likes the -I
option and segfaults whenever it is present.

--
Jon
352-572-5637


On Fri, Jul 18, 2014 at 2:16 PM, Jon Tyler <tek...@gm...> wrote:

> Mondo backs-up fine in interactive mode, buts segfaults at from the
> command line. I don't see anything in the logs to indicate the problem.
>
> command executed: mondoarchive -Oi -s 4000m -d
> /backup/media-20140718-132336 -I / -E
> "/data/video|/data/admin/websites|/local/video/tv|/local/video/tmp|/local/video/movies|/tftpboot/images|/var/cache/mindi|/backup"
> -3 -N -p media
>
> Log attached. Please advise,
>
>  --
> Jon
>
>

Segmentation fault caused by missing LZOP package
Workaround: install LZOP package

Hamish McIntyre-Bhatty said on Wed, Jul 02, 2014 at 09:13:36PM +0100:
> I'm not sure I understand, the non-test repository only contains older
> version of the software in the test repo, thus it will be ignored, plus

True, this is a feature.

> it doesn't include package for newer distributions anyway. What's

MOre or less true. I try to publish what is missing, but I may forgot
some distro tuples.

> benefited by adding the older one too? Is there another package I'm
> supposed to install besides mondo, mindi and mindi-busybox? Thanks, Hamish

afio, buffer and now perl-ProjectBuilder are required packages in 3.2.0.
This depends whether the distro already provides them or not.

Bruno.
-- 
Open Source Profession, Linux Community Lead WW http://opensource.hp.com
EMEA EG Open Source Technology Strategist       http://hpintelco.net
FLOSS projects:     http://mondorescue.org     http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

I'm not sure I understand, the non-test repository only contains older
version of the software in the test repo, thus it will be ignored, plus
it doesn't include package for newer distributions anyway. What's
benefited by adding the older one too? Is there another package I'm
supposed to install besides mondo, mindi and mindi-busybox? Thanks, Hamish

On 29/06/14 22:56, Bruno Cornec wrote:
> You need to use both the test *and* non test repo as now mondo will use
> more perl modules.
>
> Bruno.
>
> Hamish McIntyre-Bhatty said on Mon, Jun 23, 2014 at 08:27:37AM +0100:
>> Same problem as below on Ubuntu 12.04-14.04, although I haven't checked
>> anything older.
>>> Trying 'apt-get install mindi' on Debian Sid with the sources.list that 
>>> you provide, I get:
>>>
>>> The following packages have unmet dependencies:
>>>   mindi : Depends: libmondorescue-perl but it is not going to be installed
>>>           Depends: mindi-busybox (>= 1.21.1-1) but 1.18.5-3 is to be 
>>> installed
> mindi-busybox has also been updated.
>
> Bruno.

Hello,

Due to a large electricity maintenance activity in the Solution Center
that is histing the MondoRescue main server (thanks again to HP for
providing this hosting !), the web server, ftp server and trac instance
will be down starting tomorrow Thursday 3rd of July till late Saturday
5th or Sunday 6th of July.

In the mean time, you can use our mirrors available at
http://mondo.quadrata.it/
http://mondo.mirror.pclark.com/
for the Web site

and
http://mondo.quadrata.it/ftp
ftp://mondo.mirror.pclark.com/pub/mondorescue/
for the ftp site.

Time also to thank them for dedicating a bit of their bandwidth,
resources and time to give freely that service to our community.

So don't hesitate to download the 3.2.0 test version and report !
Bruno.
-- 
Open Source Profession, Linux Community Lead WW http://opensource.hp.com
EMEA EG Open Source Technology Strategist       http://hpintelco.net
FLOSS projects:     http://mondorescue.org     http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

Jep It solved my problem. Had to put -N to network shares on fstab. 

thank you Will! :)



--
View this message in context: http://mondorescue-mailing-list.679749.n3.nabble.com/unable-to-run-mondoarchive-Ubuntu-10-04-amd-tp4026278p4026280.html
Sent from the MondoRescue Mailing List mailing list archive at Nabble.com.

I see 'FATAL ERROR. Please use -k <path> to specify kernel.' Sometimes
mondo has trouble finding the correct path to newer kernels, try adding the
-k option an specifying the path to the kernel in your call to mondo, e.g.
/boot/vmlinuz-3.XX-X or whatever you're using. I've never used mondo with
RAID (and know next to nothing about it), so maybe the reason it can't find
the kernel is because of RAID related issues. But -k would be the simplest
thing to try.

You might also want to try the -N option to exclude networked mounted file
systems (unless thats what you want it to do!) , but I think that's would
stop the errors like 'Unable to open //192.168.3.232/StockMasterPrint'
<http://192.168.3.232/StockMasterPrint>



On Tue, Jul 1, 2014 at 7:40 AM, tonisl <to...@va...> wrote:

> I'm unable to run start Mondo something with fstab thanks to RAID
> controller or something. here's mondorestore log file
>
> Time started: Tue Jul  1 14:21:10 2014
>
> running: dmesg -n1 > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> Mondo Archive v3.0.4-r3177 --- http://www.mondorescue.org
> running x86_64 binaries
> running on x86_64 architecture
> -----------------------------------------------------------
> NB: Mondo logs almost everything, so don't panic if you see
> some error messages.  Please read them carefully before you
> decide to break out in a cold sweat.    Despite (or perhaps
> because of) the wealth of messages. some users are inclined
> to stop reading this log. If Mondo stopped for some reason,
> chances are it's detailed here.  More than likely there's a
> message at the very end of this log that will tell you what
> is wrong. Please read it!                          -Devteam
> -----------------------------------------------------------
> Zero...
> [Main] mondoarchive.c->welcome_to_mondoarchive#104: One...
>         [Main] mondoarchive.c->welcome_to_mondoarchive#105: Two...
>                 [Main] mondoarchive.c->welcome_to_mondoarchive#106: Three...
>                         [Main] mondoarchive.c->welcome_to_mondoarchive#107: Four...
>         [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#124: Unmounting old ramdisks if necessary
> running: mount | grep cdrom | grep super > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran with res=256
> running: mount | grep floppy | grep super > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran with res=256
> [Main] libmondo-tools.c->mount_boot_if_necessary#1249: Started sub
>                         [Main] libmondo-tools.c->mount_boot_if_necessary#1250: About to set g_boot_mountpt[0] to '\0'
>                         [Main] libmondo-tools.c->mount_boot_if_necessary#1252: Done. Great. Seeting command to something
>                         [Main] libmondo-tools.c->mount_boot_if_necessary#1255: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[  ]/boot[         ]" | tr -s ' ' '        ' | cut -f1 | head -n1'
>                         [Main] libmondo-tools.c->mount_boot_if_necessary#1259: tmp = 'UUID=a17bd9b1-e615-40ef-908a-d3c032b1eb27'
>         [Main] libmondo-tools.c->mount_boot_if_necessary#1261: /boot is at UUID=a17bd9b1-e615-40ef-908a-d3c032b1eb27 according to /etc/fstab
> [Main] libmondo-tools.c->mount_boot_if_necessary#1305: Ended sub
> [Main] libmondo-tools.c->get_kernel_version#254: g_kernel_version = 2.632000
> running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> Checking sanity of your Linux distribution
> running: grep ramdisk /proc/devices > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> 1 ramdisk
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mond
> o.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran with res=256
>                         [Main] libmondo-files.c->find_home_of_exe#369: find_home_of_exe () --- Found cmp at /usr/bin/cmp
> running: mindi -V > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> Mindi v2.0.4-r2045
> ERROR: modinfo: could not find module libata
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> ------------- mindi logfile included -------------------------
> mindi v2.0.4-r2045
> x86_64 architecture detected
> mindi called with the following arguments:
> --makemountlist /tmp/mondo.tmp.IAnuaa/mountlist.txt.test
> Start date : Tue Jul  1 14:21:10 EEST 2014
> -----------------------------
> MONDO_SHARE = /usr/share/mondo
> MINDI_LIB = /usr/lib/mindi
> MINDI_SBIN = /usr/sbin
> MINDI_CONF = /etc/mindi
> Found isolinux.bin at /usr/lib/syslinux/isolinux.bin
> LVM set to v2
> ----------
> mount result:
> -------------
> /dev/md0p1 on / type ext4 (rw,errors=remount-ro)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> none on /sys type sysfs (rw,noexec,nosuid,nodev)
> none on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> none on /dev type devtmpfs (rw,mode=0755)
> none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> none on /dev/shm type tmpfs (rw,nosuid,nodev)
> none on /var/run type tmpfs (rw,nosuid,mode=0755)
> none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
> none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
> none on /var/lib/ureadahead/debugfs type debugfs (rw,relatime)
> /dev/md0p6 on /boot type ext2 (rw)
> //192.168.3.232/StockMasterPrint on /samba type cifs (rw,mand)
> //192.168.3.250/NetBackup/StockMaster on /backup type cifs (rw,mand)
> //192.168.3.250/NetBackup/StockMaster on /backup type cifs (rw,mand)
> /dev/loop0 on /tmp/mindi.UBlWdbpQI8/mnt1 type ext2 (rw)
> -------------
> -------------
> /etc/raidtab content:
> -------------
> # Generated by Mondo Rescue
> raiddev /dev/md0
>     raid-level            1
>     nr-raid-disks         2
>     persistent-superblock 1
>
>     device                /dev/sdb1
>     raid-disk             1
>     device                /dev/sda1
>     raid-disk             0
>
> -------------
> cat /proc/cmdline:
> -------------
> BOOT_IMAGE=/vmlinuz-2.6.32-25-server root=UUID=bd871fdd-16a1-4e06-a5df-329ba4f47829 ro quiet
> -------------
> cat /proc/swaps:
> -------------
> Filename                                Type            Size    Used    Priority
> /dev/md0p5                              partition       8388600 16164   -1
> -------------
> cat /proc/partitions:
> -------------
> major minor  #blocks  name
>
>    7        0      49152 loop0
>    8        0  312571224 sda
>    8        1  312568641 sda1
>    8       16  312571224 sdb
>    8       17  312568641 sdb1
>    9        0  312568576 md0
>  259        0  293601280 md0p1
>  259        1          1 md0p2
>  259        2    8388608 md0p5
>  259        3      96256 md0p6
> -------------
> cat /proc/filesystems:
> -------------
> nodev   sysfs
> nodev   rootfs
> nodev   bdev
> nodev   proc
> nodev   cgroup
> nodev   cpuset
> nodev   tmpfs
> nodev   devtmpfs
> nodev   debugfs
> nodev   securityfs
> nodev   sockfs
> nodev   pipefs
> nodev   anon_inodefs
> nodev   inotifyfs
> nodev   devpts
>         ext3
>         ext2
>         ext4
> nodev   ramfs
> nodev   hugetlbfs
> nodev   ecryptfs
> nodev   fuse
>         fuseblk
> nodev   fusectl
> nodev   mqueue
> nodev   cifs
>         msdos
>         vfat
> -------------
> lsmod result:
> -------------
> Module                  Size  Used by
> nls_iso8859_1           4633  0
> vfat                   10866  0
> msdos                   7936  0
> fat                    55062  2 vfat,msdos
> nls_cp437               6351  3
> cifs                  279110  5
> fbcon                  39270  71
> tileblit                2487  1 fbcon
> font                    8053  1 fbcon
> bitblit                 5811  1 fbcon
> softcursor              1565  1 bitblit
> snd_hda_codec_atihdmi     3023  1
> vga16fb                12757  1
> vgastate                9857  1 vga16fb
> snd_hda_codec_realtek   279040  0
> snd_hda_intel          25773  0
> snd_hda_codec          85663  3 snd_hda_codec_atihdmi,snd_hda_codec_realtek,snd_hda_intel
> radeon                740922  0
> ppdev                   6375  0
> ttm                    60815  1 radeon
> snd_hwdep               6778  1 snd_hda_codec
> parport_pc             29958  1
> lp                      9336  0
> snd_pcm                87312  2 snd_hda_intel,snd_hda_codec
> parport                37160  3 ppdev,parport_pc,lp
> drm_kms_helper         30742  1 radeon
> snd_timer              23617  1 snd_pcm
> snd                    70978  6 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
> drm                   198532  3 radeon,ttm,drm_kms_helper
> soundcore               8052  1 snd
> i2c_algo_bit            6024  1 radeon
> intel_agp              29063  0
> serio_raw               4950  0
> xhci                   41830  0
> snd_page_alloc          8500  2 snd_hda_intel,snd_pcm
> raid10                 21450  0
> raid456                54784  0
> async_pq                3891  1 raid456
> async_xor               3111  2 raid456,async_pq
> xor                     4685  1 async_xor
> async_memcpy            1537  1 raid456
> async_raid6_recov       1816  1 raid456
> usbhid                 41084  0
> raid6_pq               80147  2 async_pq,async_raid6_recov
> async_tx                2545  5 raid456,async_pq,async_xor,async_memcpy,async_raid6_recov
> hid                    83440  1 usbhid
> r8169                  39650  0
> mii                     5237  1 r8169
> pata_jmicron            2747  0
> ahci                   37870  0
> raid1                  22514  1
> raid0                   6778  0
> multipath               7181  0
> linear                  4158  0
> FORCE_MODS:
> -------------
>
> -------------
> DENY_MODS:
> -------------
> kqemu
> -------------
> df result:
> ----------
> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> /dev/md0p1    ext4   288994624  57206560 217108000  21% /
> none      devtmpfs     2019960       264   2019696   1% /dev
> none         tmpfs     2024512         0   2024512   0% /dev/shm
> none         tmpfs     2024512      3076   2021436   1% /var/run
> none         tmpfs     2024512         0   2024512   0% /var/lock
> none         tmpfs     2024512         0   2024512   0% /lib/init/rw
> none       debugfs   288994624  57206560 217108000  21% /var/lib/ureadahead/debugfs
> /dev/md0p6    ext2       90195     31827     53556  38% /boot
> //192.168.3.232/StockMasterPrint
>               cifs    61440560  10647300  50793260  18% /samba
> //192.168.3.250/NetBackup/StockMaster
>               cifs   2870346112 1757785276 1112458436  62% /backup
> //192.168.3.250/NetBackup/StockMaster
>               cifs   2870346112 1757785276 1112458436  62% /backup
> /dev/loop0    ext2       46059       766     44802   2% /tmp/mindi.UBlWdbpQI8/mnt1
> -------------
> Liste of extra modules is:
> ht st osst ide-tape ide_tape ide ide-floppy floppy ide-generic ide-detect ide-mod ide-disk ide_disk ide-cd ide_cd ide_cd_mod ide-cd
> _mod ide-cs ide-core ide_core edd paride ata_generic ata_piix libata dock via82cxxx generic nvidia ahci sata_nv cmd64x pata_amd pat
> a_marvell pata_serverworks pata_sis amd74xx sis5513 usb-storage usb-ohci usb-uhci usbcore usb_storage input hid uhci_hcd ehci_hcd u
> hci-hcd ehci-hcd ohci-hcd ohci_hcd usbkbd usbhid keybdev mousedev libusual scsi_mod pcmcia_core ds yenta_socket 3w-xxxx 3w_xxxx 3w_
> 9xxx 3w-9xxx 53c7,8xx a100u2w a320raid aacraid adpahci advansys aha152x aha1542 aha1740 aic79xx aic79xx_mod aic7xxx aic7xxx_mod aic
> 7xxx_old AM53C974 atp870u BusLogic cciss cpqfc dmx3191d dpt_i2o dtc eata eata_dma eata_pio fdomain gdth g_NCR5380 i2o_block i2o_cor
> e ide-scsi ieee1394 imm in2000 initio ips iscsi isp megaraid megaraid_mm megaraid_mbox megaraid_sas mptbase mptscsih mptsas mptspi
> mptfc mptscsi mptctl NCR53c406a ncr53c8xx nsp32 pas16 pci2000 pci2220i pcmcia ppa psi240i qla1280 qla2200 qla2300 qla2400 qla2xxx q
> la2xxx_conf qlogicfas qlogicfc qlogicisp raw1394 scsi_debug scsi_mod scsi_transport_sas scsi_transport_spi sd_mod seagate sg sim710
>  sr_mod sym53c416 sym53c8xx sym53c8xx_2 t128 tmscsim u14-34f ultrastor wd7000 vmhgfs intermodule sunrpc nfs nfs_acl lockd fscache l
> oop mii 3c59x e100 bcm5700 bnx2 e1000 eepro100 ne2k-pci tg3 pcnet32 8139cp 8139too 8390 forcedeth vmxnet vmnet exportfs af_packet c
> drom isocd isofs inflate_fs nls_iso8859-1 nls_base nls_cp437 nls_utf8 sg sr_mod zlib_inflate iso9660 vfat fat loop md-mod linear ra
> id0 raid1 xor raid5 raid456 lvm-mod dm-mod dm-snapshot dm-zero dm-mirror jfs xfs xfs_support pagebuf reiserfs ext2 ext3 minix nfs n
> fs_acl nfsd lockd sunrpc jbd mbcache
> -------------
> Your raw fstab file looks like this:
> ------------------------------------
> # /etc/fstab: static file system information.
> #
> # Use 'blkid -o value -s UUID' to print the universally unique identifier
> # for a device; this may be used with UUID= as a more robust way to name
> # devices that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point>   <type>  <options>       <dump>  <pass>
> proc            /proc           proc    nodev,noexec,nosuid 0       0
> # / was on /dev/md0p1 during installation
> UUID=bd871fdd-16a1-4e06-a5df-329ba4f47829 /               ext4    errors=remount-ro 0       1
> # /boot was on /dev/md0p6 during installation
> UUID=a17bd9b1-e615-40ef-908a-d3c032b1eb27 /boot           ext2    defaults        0       2
> /dev/md0p5      none            swap    sw              0       0
> /dev/scd0       /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
>
> //192.168.3.232/StockMasterPrint        /samba      cifs    rw,username=Operaator1,password=Operaator.1,uid=1002,gid=1002     0
>    0
> #//192.168.3.30/StockMaster              /backup     cifs    rw,domain=SAAR,username=varukopi,password=123456,uid=1000,gid=1000
>     0          0
> //192.168.3.250/NetBackup/StockMaster   /backup     cifs    rw,username=varukopi,password=123456,uid=1000,gid=1000      0       0
> Your mountlist will look like this:
> -----------------------------------
>         DEVICE          MOUNTPOINT      FORMAT          SIZE (MB)       LABEL/UUID
>
> Unable to open proc
> Examining /dev/md0p6 (mount=/boot fmt=ext2 psz=-1)
>         /dev/md0p6      /boot           ext2                  0 a17bd9b1-e615-40ef-908a-d3c032b1eb27
> Examining /dev/md0p5 (mount=swap fmt=swap psz=8388600)
>         /dev/md0p5      swap            swap               8191
>
> Unable to open //192.168.3.232/StockMasterPrint
> Examining //192.168.3.232/StockMasterPrint (mount=/samba fmt=cifs psz=61440560)
>         //192.168.3.232/StockMasterPrint /samba          cifs              60000
>
> Unable to open //192.168.3.250/NetBackup/StockMaster
> Examining //192.168.3.250/NetBackup/StockMaster (mount=/backup fmt=cifs psz=2870346112 2870346112)
> You are using Mindi-Linux v2.0.4-r2045 to make boot+data disks
> Mindi-BusyBox v1.7.3-r2622 (2010-06-09 10:07:28 CEST) multi-call binary
> insmod: can't read '/lib/modules/2.6.32-25-server/*/*/misc/aes.*o.gz': No such file or directory
> insmod: can't read 'loop': No such file or directory
> insmod: can't read 'cdrom': No such file or directory
> insmod: can't read 'ide-cd': No such file or directory
> insmod: can't read 'isofs': No such file or directory
> insmod: can't read 'linear': No such file or directory
> insmod: can't read 'raid0': No such file or directory
> insmod: can't read 'raid1': No such file or directory
> insmod: can't read 'raid5': No such file or directory
> DIFFERENTIAL =
> INTERNAL TAPE BLOCK SIZE =
> NOT_BOOT = ''
> FATAL ERROR. Please use -k <path> to specify kernel.
> 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 2.0.4-r2045 is exiting
> End date : Tue Jul  1 14:21:15 EEST 2014
> --------------------------------------------------------------
> mindi --makemountlist /tmp/mondo.tmp.IAnuaa/mountlist.txt.test failed for some reason.
> Please run that command by hand and examine /var/log/mindi.log
> for more information. Perhaps your /etc/fstab file is insane.
> Perhaps Mindi's MakeMountlist() subroutine has a bug. We'll see.
> running: parted2fdisk -l 2>/dev/null | grep -i raid > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo
> -run-prog-thing.err
> --------------------------------start of output-----------------------------
> /dev/sda1               1       38913   312568641   fd  Linux raid autodetect
> /dev/sdb1   *           1       38913   312568641   fd  Linux raid autodetect
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> Failed.
>         [Main] libmondo-tools.c->pre_param_configuration#722: Your distribution did not pass Mondo's sanity test.
> [Main] newt-specific.c->fatal_error#329: Fatal error received - 'Pre-param initialization phase failed. Please review the error mes
> sages above, make the specified changes, then try again. Exiting...'
>                 [Main] newt-specific.c->fatal_error#347: OK, I think I'm the main PID.
>         [Main] newt-specific.c->fatal_error#355: I'm going to do some cleaning up now.
>                         [Main] newt-specific.c->fatal_error#356: killall mindi 2> /dev/null
> running: ps auxww | grep " /mondo/do-not " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2>
>  /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> running: kill `ps auxww | grep " /mondo/do-not " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing
> .tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> kill: 1: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
> kill -l [exitstatus]
> --------------------------------end of output------------------------------
> ...ran with res=512
> running: ps auxww | grep " mondo.tmp " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tm
> p/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> running: kill `ps auxww | grep " mondo.tmp " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp
>  2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> kill: 1: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
> kill -l [exitstatus]
> --------------------------------end of output------------------------------
> ...ran with res=512
> running: ps auxww | grep " ntfsclone " | grep -v "grep" | awk '{print $2;}' > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tm
> p/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> --------------------------------end of output------------------------------
> ...ran just fine. :-)
> running: kill `ps auxww | grep " ntfsclone " | grep -v "grep" | awk '{print $2;}'` > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp
>  2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> kill: 1: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
> kill -l [exitstatus]
> --------------------------------end of output------------------------------
> ...ran with res=512
> running: umount -d /mnt/cdrom > /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.IAnuaa/mondo-run-prog-thing.err
> --------------------------------start of output-----------------------------
> umount: /mnt/cdrom: not mounted
> --------------------------------end of output------------------------------
> ...ran with res=256
>
>
> ------------------------------
> View this message in context: unable to run mondoarchive Ubuntu 10.04. amd
> <http://mondorescue-mailing-list.679749.n3.nabble.com/unable-to-run-mondoarchive-Ubuntu-10-04-amd-tp4026278.html>
> Sent from the MondoRescue Mailing List mailing list archive
> <http://mondorescue-mailing-list.679749.n3.nabble.com/> at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Mondo-devel mailing list
> Mon...@li...
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>
>

I'm unable to run start Mondo something with fstab thanks to RAID controller
or something. here's mondorestore log file



--
View this message in context: http://mondorescue-mailing-list.679749.n3.nabble.com/unable-to-run-mondoarchive-Ubuntu-10-04-amd-tp4026278.html
Sent from the MondoRescue Mailing List mailing list archive at Nabble.com.