mondo-devel Mailing List for Mondo Rescue
Brought to you by:
bcornec
Menu
▾
▴
mondo-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(1) |
Feb
(20) |
Mar
(50) |
Apr
(9) |
May
(1) |
Jun
(8) |
Jul
(46) |
Aug
(91) |
Sep
(63) |
Oct
(63) |
Nov
(80) |
Dec
(201) |
| 2002 |
Jan
(248) |
Feb
(390) |
Mar
(328) |
Apr
(278) |
May
(224) |
Jun
(236) |
Jul
(276) |
Aug
(228) |
Sep
(167) |
Oct
(219) |
Nov
(523) |
Dec
(379) |
| 2003 |
Jan
(757) |
Feb
(308) |
Mar
(218) |
Apr
(464) |
May
(692) |
Jun
(585) |
Jul
(417) |
Aug
(197) |
Sep
(531) |
Oct
(595) |
Nov
(303) |
Dec
(139) |
| 2004 |
Jan
(146) |
Feb
(294) |
Mar
(356) |
Apr
(358) |
May
(182) |
Jun
(263) |
Jul
(174) |
Aug
(198) |
Sep
(195) |
Oct
(130) |
Nov
(99) |
Dec
(152) |
| 2005 |
Jan
(243) |
Feb
(108) |
Mar
(150) |
Apr
(104) |
May
(36) |
Jun
(63) |
Jul
(66) |
Aug
(100) |
Sep
(106) |
Oct
(164) |
Nov
(247) |
Dec
(258) |
| 2006 |
Jan
(173) |
Feb
(122) |
Mar
(131) |
Apr
(164) |
May
(270) |
Jun
(178) |
Jul
(128) |
Aug
(112) |
Sep
(153) |
Oct
(157) |
Nov
(311) |
Dec
(277) |
| 2007 |
Jan
(264) |
Feb
(167) |
Mar
(263) |
Apr
(150) |
May
(200) |
Jun
(159) |
Jul
(126) |
Aug
(131) |
Sep
(155) |
Oct
(142) |
Nov
(90) |
Dec
(121) |
| 2008 |
Jan
(161) |
Feb
(70) |
Mar
(78) |
Apr
(94) |
May
(111) |
Jun
(104) |
Jul
(94) |
Aug
(123) |
Sep
(131) |
Oct
(139) |
Nov
(155) |
Dec
(281) |
| 2009 |
Jan
(221) |
Feb
(157) |
Mar
(152) |
Apr
(57) |
May
(93) |
Jun
(58) |
Jul
(83) |
Aug
(58) |
Sep
(60) |
Oct
(125) |
Nov
(153) |
Dec
(94) |
| 2010 |
Jan
(115) |
Feb
(103) |
Mar
(119) |
Apr
(120) |
May
(107) |
Jun
(108) |
Jul
(109) |
Aug
(104) |
Sep
(107) |
Oct
(48) |
Nov
(66) |
Dec
(44) |
| 2011 |
Jan
(111) |
Feb
(107) |
Mar
(170) |
Apr
(160) |
May
(58) |
Jun
(125) |
Jul
(129) |
Aug
(67) |
Sep
(86) |
Oct
(93) |
Nov
(73) |
Dec
(64) |
| 2012 |
Jan
(147) |
Feb
(132) |
Mar
(99) |
Apr
(99) |
May
(101) |
Jun
(132) |
Jul
(43) |
Aug
(35) |
Sep
(45) |
Oct
(29) |
Nov
(111) |
Dec
(65) |
| 2013 |
Jan
(18) |
Feb
(45) |
Mar
(53) |
Apr
(35) |
May
(29) |
Jun
(64) |
Jul
(37) |
Aug
(68) |
Sep
(78) |
Oct
(44) |
Nov
(56) |
Dec
(36) |
| 2014 |
Jan
(38) |
Feb
(35) |
Mar
(36) |
Apr
(41) |
May
(7) |
Jun
(47) |
Jul
(13) |
Aug
(25) |
Sep
(35) |
Oct
(59) |
Nov
(25) |
Dec
(30) |
| 2015 |
Jan
(58) |
Feb
(59) |
Mar
(79) |
Apr
(34) |
May
(36) |
Jun
(9) |
Jul
(30) |
Aug
(34) |
Sep
(82) |
Oct
(30) |
Nov
(52) |
Dec
(43) |
| 2016 |
Jan
(44) |
Feb
(117) |
Mar
(45) |
Apr
(69) |
May
(80) |
Jun
(25) |
Jul
(39) |
Aug
(22) |
Sep
(43) |
Oct
(34) |
Nov
(25) |
Dec
(107) |
| 2017 |
Jan
(58) |
Feb
(11) |
Mar
(38) |
Apr
(15) |
May
(33) |
Jun
(31) |
Jul
(16) |
Aug
(53) |
Sep
(66) |
Oct
(13) |
Nov
(3) |
Dec
(8) |
| 2018 |
Jan
(9) |
Feb
(21) |
Mar
(3) |
Apr
(9) |
May
(16) |
Jun
(13) |
Jul
(22) |
Aug
(20) |
Sep
(3) |
Oct
(6) |
Nov
(5) |
Dec
(13) |
| 2019 |
Jan
(18) |
Feb
(6) |
Mar
(15) |
Apr
(10) |
May
(6) |
Jun
(4) |
Jul
(3) |
Aug
(12) |
Sep
(1) |
Oct
(13) |
Nov
(36) |
Dec
(1) |
| 2020 |
Jan
(3) |
Feb
(7) |
Mar
(6) |
Apr
(13) |
May
|
Jun
|
Jul
(2) |
Aug
(15) |
Sep
|
Oct
(12) |
Nov
(3) |
Dec
(6) |
| 2021 |
Jan
(9) |
Feb
|
Mar
(2) |
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(7) |
Jul
|
Aug
(8) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
(10) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(11) |
Aug
|
Sep
(5) |
Oct
|
Nov
(1) |
Dec
|
| 2024 |
Jan
(2) |
Feb
(12) |
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
(4) |
Oct
(5) |
Nov
(2) |
Dec
(6) |
| 2025 |
Jan
(1) |
Feb
(7) |
Mar
(4) |
Apr
(9) |
May
(12) |
Jun
(5) |
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2026 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
1
|
|
2
|
3
(3) |
4
(2) |
5
|
6
(1) |
7
|
8
|
|
9
|
10
|
11
(1) |
12
|
13
(1) |
14
(3) |
15
|
|
16
|
17
(2) |
18
(2) |
19
|
20
(5) |
21
|
22
|
|
23
|
24
(4) |
25
(1) |
26
|
27
|
28
|
29
|
|
30
|
|
|
|
|
|
|
|
From: <sky...@gm...> - 2014-11-25 12:00:30
|
Just an addendum to my previous post: I found out that by installing the firmware-realtek package from the nonfree repository I could get rid of most of the W: messages, except for these: W: mdadm: no arrays defined in configuration file. W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. Again, I have NO raid arrays, I just did a standard install of Debian to my hard drive. It seems like all the issues in this install not related to the firmware-realtek package have been associated with this single program, mdadm. I'm just wondering, why does Mondo require it as a dependency? Would it break Mondo if I disabled or uninstalled it? If uninstalling mdadm would break Mondo, then I still would like to know if I should have answered "NO" to this question - or would it have made any difference? My main concern is I don't want to get the system into a state where it won't boot! > Configuring mdadm > Once the base system has booted, mdadm can start all MD arrays (RAIDs) specified in /etc/mdadm/mdadm.conf which have not yet been started. This is recommended unless multiple device (MD) support is compiled into the kernel and all partitions are marked as belonging to MD arrays, with type 0xfd (as those and only those will be started automatically by the kernel). > Do you want to start MD arrays automatically? Thanks in advance for any advice on this. |
|
From: <sky...@gm...> - 2014-11-24 20:11:34
|
Will Hopper <wjh...@gm...> wrote: > Try dropping the .1, I have > deb ftp://ftp.mondorescue.org/debian 7 contrib > hope that helps! That did it, thanks! But now I have questions about the install. I should preface this by saying that I am running a straight Debian install, no special partitioning, and only a single hard drive (not even a DVD drive). Definitely no RAID array. During installation, the following question appeared: > Configuring mdadm > If the system's root file system is located on an MD array (RAID), it needs to be started early during the boot sequence. If it is located on a logical volume (LVM), which is on MD, all constituent arrays need to be started. If you know exactly which arrays are needed to bring up the root file system, and you want to postpone starting all other arrays to a later point in the boot sequence, enter the arrays to start here. Alternatively, enter 'all' to simply start all available arrays. If you do not need or want to start any arrays for the root file system, leave the answer blank (or enter 'none'). This may be the case if you are using kernel autostart or do not need any arrays to boot. > Please enter 'all', 'none', or a space-separated list of devices such as 'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted). > MD arrays needed for the root file system: The default was 'all', but I changed it to 'none' - was that the correct thing to do? Then it asked: > Configuring mdadm > Once the base system has booted, mdadm can start all MD arrays (RAIDs) specified in /etc/mdadm/mdadm.conf which have not yet been started. This is recommended unless multiple device (MD) support is compiled into the kernel and all partitions are marked as belonging to MD arrays, with type 0xfd (as those and only those will be started automatically by the kernel). > Do you want to start MD arrays automatically? The default was YES and at this point I was really confused so I just hit OK. Now I'm wondering if I should have done either of those differently, and if so, how do I get back to those screens to change them, since they only appear during the initial install? Then during the install, this was what was displayed: ===== $ sudo apt-get install mondo Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: afio buffer dosfstools dvd+rw-tools fuse gawk genisoimage growisofs libcrypt-passwdmd5-perl liblzo2-2 libparted0debian1 libsigsegv2 lzop mdadm mindi mindi-busybox mtools ntfs-3g ntfsprogs parted syslinux syslinux-common wodim Suggested packages: cdrskin gawk-doc cdrkit-doc libparted0-dev libparted0-i18n mondo-doc floppyd parted-doc The following NEW packages will be installed: afio buffer dosfstools dvd+rw-tools fuse gawk genisoimage growisofs libcrypt-passwdmd5-perl liblzo2-2 libparted0debian1 libsigsegv2 lzop mdadm mindi mindi-busybox mondo mtools ntfs-3g ntfsprogs parted syslinux syslinux-common wodim 0 upgraded, 24 newly installed, 0 to remove and 11 not upgraded. Need to get 6,921 kB of archives. After this operation, 16.6 MB of additional disk space will be used. Do you want to continue [Y/n]? Y WARNING: The following packages cannot be authenticated! afio mindi-busybox mindi mondo Install these packages without verification [y/N]? Y Get:1 http://ftp.us.debian.org/debian/ wheezy/main libsigsegv2 amd64 2.9-4 [28.9 kB] Get:2 http://ftp.us.debian.org/debian/ wheezy/main gawk amd64 1:4.0.1+dfsg-2.1 [972 kB] Get:3 http://ftp.us.debian.org/debian/ wheezy/main liblzo2-2 amd64 2.06-1+deb7u1 [59.0 kB] Get:4 http://ftp.us.debian.org/debian/ wheezy/main libparted0debian1 amd64 2.3-12 [348 kB] Get:5 http://ftp.us.debian.org/debian/ wheezy/main fuse amd64 2.9.0-2+deb7u1 [72.6 kB] Get:6 ftp://ftp.mondorescue.org//debian/ 7/contrib afio amd64 2.5-1 [71.7 kB] Get:7 http://ftp.us.debian.org/debian/ wheezy/main ntfs-3g amd64 1:2012.1.15AR.5-2.1 [620 kB] Get:8 http://ftp.us.debian.org/debian/ wheezy/main buffer amd64 1.19-11 [16.2 kB] Get:9 http://ftp.us.debian.org/debian/ wheezy/main dosfstools amd64 3.0.13-1 [69.4 kB] Get:10 http://ftp.us.debian.org/debian/ wheezy/main genisoimage amd64 9:1.1.11-2 [634 kB] Get:11 http://ftp.us.debian.org/debian/ wheezy/main growisofs amd64 7.1-10 [82.6 kB] Get:12 http://ftp.us.debian.org/debian/ wheezy/main dvd+rw-tools amd64 7.1-10 [102 kB] Get:13 http://ftp.us.debian.org/debian/ wheezy/main libcrypt-passwdmd5-perl all 1.3-10 [10.5 kB] Get:14 http://ftp.us.debian.org/debian/ wheezy/main lzop amd64 1.03-3 [44.8 kB] Get:15 http://ftp.us.debian.org/debian/ wheezy/main mdadm amd64 3.2.5-5 [557 kB] Get:16 http://ftp.us.debian.org/debian/ wheezy/main syslinux-common all 2:4.05+dfsg-6+deb7u1 [934 kB] Get:17 ftp://ftp.mondorescue.org//debian/ 7/contrib mindi-busybox amd64 1.18.5-3 [273 kB] Get:18 http://ftp.us.debian.org/debian/ wheezy/main syslinux amd64 2:4.05+dfsg-6+deb7u1 [94.6 kB] Get:19 http://ftp.us.debian.org/debian/ wheezy/main parted amd64 2.3-12 [158 kB] Get:20 http://ftp.us.debian.org/debian/ wheezy/main mtools amd64 4.0.17-1 [199 kB] Get:21 http://ftp.us.debian.org/debian/ wheezy/main wodim amd64 9:1.1.11-2 [459 kB] Get:22 http://ftp.us.debian.org/debian/ wheezy/main ntfsprogs all 1:2012.1.15AR.5-2.1 [17.5 kB] Get:23 ftp://ftp.mondorescue.org//debian/ 7/contrib mindi amd64 2.1.7-1 [261 kB] Get:24 ftp://ftp.mondorescue.org//debian/ 7/contrib mondo amd64 3.0.4-1 [837 kB] Fetched 6,921 kB in 7s (932 kB/s) Preconfiguring packages ... Selecting previously unselected package libsigsegv2. (Reading database ... 78529 files and directories currently installed.) Unpacking libsigsegv2 (from .../libsigsegv2_2.9-4_amd64.deb) ... Setting up libsigsegv2 (2.9-4) ... Selecting previously unselected package gawk. (Reading database ... 78539 files and directories currently installed.) Unpacking gawk (from .../gawk_1%3a4.0.1+dfsg-2.1_amd64.deb) ... Selecting previously unselected package liblzo2-2:amd64. Unpacking liblzo2-2:amd64 (from .../liblzo2-2_2.06-1+deb7u1_amd64.deb) ... Selecting previously unselected package libparted0debian1:amd64. Unpacking libparted0debian1:amd64 (from .../libparted0debian1_2.3-12_amd64.deb) ... Selecting previously unselected package fuse. Unpacking fuse (from .../fuse_2.9.0-2+deb7u1_amd64.deb) ... Processing triggers for man-db ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 Setting up fuse (2.9.0-2+deb7u1) ... Creating fuse group... Adding group `fuse' (GID 112) ... Done. udev active, skipping device node creation. update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 Selecting previously unselected package ntfs-3g. (Reading database ... 78680 files and directories currently installed.) Unpacking ntfs-3g (from .../ntfs-3g_1%3a2012.1.15AR.5-2.1_amd64.deb) ... Selecting previously unselected package afio. Unpacking afio (from .../archives/afio_2.5-1_amd64.deb) ... Selecting previously unselected package buffer. Unpacking buffer (from .../buffer_1.19-11_amd64.deb) ... Selecting previously unselected package dosfstools. Unpacking dosfstools (from .../dosfstools_3.0.13-1_amd64.deb) ... Selecting previously unselected package genisoimage. Unpacking genisoimage (from .../genisoimage_9%3a1.1.11-2_amd64.deb) ... Selecting previously unselected package growisofs. Unpacking growisofs (from .../growisofs_7.1-10_amd64.deb) ... Selecting previously unselected package dvd+rw-tools. Unpacking dvd+rw-tools (from .../dvd+rw-tools_7.1-10_amd64.deb) ... Selecting previously unselected package libcrypt-passwdmd5-perl. Unpacking libcrypt-passwdmd5-perl (from .../libcrypt-passwdmd5-perl_1.3-10_all.deb) ... Selecting previously unselected package lzop. Unpacking lzop (from .../archives/lzop_1.03-3_amd64.deb) ... Selecting previously unselected package mdadm. Unpacking mdadm (from .../mdadm_3.2.5-5_amd64.deb) ... Selecting previously unselected package syslinux-common. Unpacking syslinux-common (from .../syslinux-common_2%3a4.05+dfsg-6+deb7u1_all.deb) ... Selecting previously unselected package syslinux. Unpacking syslinux (from .../syslinux_2%3a4.05+dfsg-6+deb7u1_amd64.deb) ... Selecting previously unselected package parted. Unpacking parted (from .../parted_2.3-12_amd64.deb) ... Selecting previously unselected package mtools. Unpacking mtools (from .../mtools_4.0.17-1_amd64.deb) ... Selecting previously unselected package mindi-busybox. Unpacking mindi-busybox (from .../mindi-busybox_1.18.5-3_amd64.deb) ... Selecting previously unselected package mindi. Unpacking mindi (from .../mindi_2.1.7-1_amd64.deb) ... Selecting previously unselected package wodim. Unpacking wodim (from .../wodim_9%3a1.1.11-2_amd64.deb) ... Selecting previously unselected package mondo. Unpacking mondo (from .../mondo_3.0.4-1_amd64.deb) ... Selecting previously unselected package ntfsprogs. Unpacking ntfsprogs (from .../ntfsprogs_1%3a2012.1.15AR.5-2.1_all.deb) ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays. W: mdadm: failed to auto-generate the mdadm.conf file. W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no configuration file available. Processing triggers for man-db ... Processing triggers for install-info ... Setting up gawk (1:4.0.1+dfsg-2.1) ... Setting up liblzo2-2:amd64 (2.06-1+deb7u1) ... Setting up libparted0debian1:amd64 (2.3-12) ... Setting up ntfs-3g (1:2012.1.15AR.5-2.1) ... update-initramfs: deferring update (trigger activated) Setting up afio (2.5-1) ... Setting up buffer (1.19-11) ... Setting up dosfstools (3.0.13-1) ... Setting up genisoimage (9:1.1.11-2) ... Setting up growisofs (7.1-10) ... Setting up dvd+rw-tools (7.1-10) ... Setting up libcrypt-passwdmd5-perl (1.3-10) ... Setting up lzop (1.03-3) ... Setting up mdadm (3.2.5-5) ... Generating array device nodes... done. update-initramfs: deferring update (trigger activated) [ ok ] Assembling MD arrays...done (no arrays found in config file or automatically). [ ok ] Starting MD monitoring service: mdadm --monitor. Setting up syslinux-common (2:4.05+dfsg-6+deb7u1) ... Setting up syslinux (2:4.05+dfsg-6+deb7u1) ... Setting up parted (2.3-12) ... Setting up mtools (4.0.17-1) ... Setting up mindi-busybox (1.18.5-3) ... Setting up mindi (2.1.7-1) ... Setting up wodim (9:1.1.11-2) ... Setting up mondo (3.0.4-1) ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. Setting up ntfsprogs (1:2012.1.15AR.5-2.1) ... ===== Note the multiple W: messages, which make no sense to me - do I need to be concerned about these? The other thing that concerns me is where it says "Starting MD monitoring service: mdadm --monitor" - is that something I need to have running on this system? What does it do? I'm really nervous about this right now because the last thing I want to do is mess up this server or have Mondo make backups that can't be restored. So, please tell me if I should have done anything differently! |
|
From: Will H. <wjh...@gm...> - 2014-11-24 15:42:54
|
Try dropping the .1, I have deb ftp://ftp.mondorescue.org/debian 7 contrib hope that helps! On Sun, Nov 23, 2014 at 7:55 PM, <sky...@gm...> wrote: > I attempted to install Mondo Rescue on a Debian 7.7 based system by doing > this (adapted from the page at > http://www.tecmint.com/how-to-clone-linux-systems/): > > wget ftp://ftp.mondorescue.org/debian/7/mondorescue.sources.list > sudo sh -c "cat mondorescue.sources.list >> /etc/apt/sources.list" > sudo apt-get update > sudo apt-get install mondo > > When I ran "sudo apt-get update" I got the following output (stuff about > other packages removed): > > ===== > Get:1 ftp://ftp.mondorescue.org 7.1 Release.gpg > Ign ftp://ftp.mondorescue.org 7.1 Release.gpg > Get:2 ftp://ftp.mondorescue.org 7.1 Release > Ign http://apt.tvheadend.org wheezy/main Translation-en_US > Ign http://apt.tvheadend.org wheezy/main Translation-en > Ign ftp://ftp.mondorescue.org 7.1 Release > Get:3 ftp://ftp.mondorescue.org 7.1/contrib Sources > Get:4 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages > Get:5 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US > Get:6 ftp://ftp.mondorescue.org 7.1/contrib Translation-en > Get:7 ftp://ftp.mondorescue.org 7.1/contrib Sources > Get:8 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages > Get:9 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US > Get:10 ftp://ftp.mondorescue.org 7.1/contrib Translation-en > Get:11 ftp://ftp.mondorescue.org 7.1/contrib Sources > Get:12 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages > Get:13 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US > Get:14 ftp://ftp.mondorescue.org 7.1/contrib Translation-en > Get:15 ftp://ftp.mondorescue.org 7.1/contrib Sources > Get:16 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages > Get:17 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US > Get:18 ftp://ftp.mondorescue.org 7.1/contrib Translation-en > Get:19 ftp://ftp.mondorescue.org 7.1/contrib Sources > Err ftp://ftp.mondorescue.org 7.1/contrib Sources > Unable to fetch file, server said 'Failed to open file. ' > Get:20 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages > Err ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages > Unable to fetch file, server said 'Failed to open file. ' > Get:21 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US > Ign ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US > Get:22 ftp://ftp.mondorescue.org 7.1/contrib Translation-en > Ign ftp://ftp.mondorescue.org 7.1/contrib Translation-en > W: Failed to fetch > ftp://ftp.mondorescue.org//debian/dists/7.1/contrib/source/Sources > Unable to fetch file, server said 'Failed to open file. ' > > W: Failed to fetch > ftp://ftp.mondorescue.org//debian/dists/7.1/contrib/binary-amd64/Packages > Unable to fetch file, server said 'Failed to open file. ' > > E: Some index files failed to download. They have been ignored, or old > ones used instead. > ===== > > I tried installing anyway and it failed: > > $ sudo apt-get install mondo > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package mondo > > I checked the /etc/apt/sources.list file and at the end the following > lines had been added: > > deb ftp://ftp.mondorescue.org//debian 7.1 contrib > deb-src ftp://ftp.mondorescue.org//debian 7.1 contrib > > If I do uname -a I get > Linux server 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2 x86_64 GNU/Linux > And if I do cat /etc/debian_version it shows the version as 7.7 > > Am I doing something wrong, is the repository missing files, is Debian 7.7 > not supported, or what? > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Mondo-devel mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mondo-devel > |
|
From: Vreriks, M. <Vre...@me...> - 2014-11-24 12:13:20
|
Hello, I want to restore a single file from my mondoarchive backup made this weekend. It's failed whit a FATALEERROR. root@odb2011:[]/root# mondorestore ---FATALERROR--- all.tar.gz did not include tmp/biggielist.txt If you require technical support, please contact the mailing list. See http://www.mondorescue.org for details. The list's members can help you, if you attach that file to your e-mail. Log file: /var/log/mondorestore.log Mondo has aborted. Execution run ended; result=254 Type 'less /var/log/mondorestore.log' to see the output log I use mondorestore to attached a net mount volume on which are the iso located! See logging which attached with this mail. mailto:mon...@li... mailto:mondo-devel_at_lists.sourceforge.net Met vriendelijk groet Marcel Vreriks Marcel Vreriks | technisch beheerder ICT | ICT expertdomein OS en Hardware Menzis | De Ruyterlaan 25 | 7511 JH Enschede | Postbus 75000 | 7500 KC Enschede T (053) 485 32 44 | M 06 55 77 77 58 | vre...@me...<mailto:vre...@me...> | www.menzis.nl<http://www.menzis.nl> P Please consider the environment before printing this email -- De inhoud van dit bericht is vertrouwelijk en met de grootst mogelijke zorg verzonden. Ontvangt u dit bericht onterecht? Dan vragen we u ons direct per e-mail te informeren en het bericht te vernietigen. Wij danken u voor uw medewerking. Dit bericht is afkomstig van één van de leden of deelnemingen van de Coöperatie Menzis U.A. (kvk-nr.: 02065142). |
|
From: <sky...@gm...> - 2014-11-24 01:08:39
|
I attempted to install Mondo Rescue on a Debian 7.7 based system by doing this (adapted from the page at http://www.tecmint.com/how-to-clone-linux-systems/): wget ftp://ftp.mondorescue.org/debian/7/mondorescue.sources.list sudo sh -c "cat mondorescue.sources.list >> /etc/apt/sources.list" sudo apt-get update sudo apt-get install mondo When I ran "sudo apt-get update" I got the following output (stuff about other packages removed): ===== Get:1 ftp://ftp.mondorescue.org 7.1 Release.gpg Ign ftp://ftp.mondorescue.org 7.1 Release.gpg Get:2 ftp://ftp.mondorescue.org 7.1 Release Ign http://apt.tvheadend.org wheezy/main Translation-en_US Ign http://apt.tvheadend.org wheezy/main Translation-en Ign ftp://ftp.mondorescue.org 7.1 Release Get:3 ftp://ftp.mondorescue.org 7.1/contrib Sources Get:4 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages Get:5 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US Get:6 ftp://ftp.mondorescue.org 7.1/contrib Translation-en Get:7 ftp://ftp.mondorescue.org 7.1/contrib Sources Get:8 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages Get:9 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US Get:10 ftp://ftp.mondorescue.org 7.1/contrib Translation-en Get:11 ftp://ftp.mondorescue.org 7.1/contrib Sources Get:12 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages Get:13 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US Get:14 ftp://ftp.mondorescue.org 7.1/contrib Translation-en Get:15 ftp://ftp.mondorescue.org 7.1/contrib Sources Get:16 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages Get:17 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US Get:18 ftp://ftp.mondorescue.org 7.1/contrib Translation-en Get:19 ftp://ftp.mondorescue.org 7.1/contrib Sources Err ftp://ftp.mondorescue.org 7.1/contrib Sources Unable to fetch file, server said 'Failed to open file. ' Get:20 ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages Err ftp://ftp.mondorescue.org 7.1/contrib amd64 Packages Unable to fetch file, server said 'Failed to open file. ' Get:21 ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US Ign ftp://ftp.mondorescue.org 7.1/contrib Translation-en_US Get:22 ftp://ftp.mondorescue.org 7.1/contrib Translation-en Ign ftp://ftp.mondorescue.org 7.1/contrib Translation-en W: Failed to fetch ftp://ftp.mondorescue.org//debian/dists/7.1/contrib/source/Sources Unable to fetch file, server said 'Failed to open file. ' W: Failed to fetch ftp://ftp.mondorescue.org//debian/dists/7.1/contrib/binary-amd64/Packages Unable to fetch file, server said 'Failed to open file. ' E: Some index files failed to download. They have been ignored, or old ones used instead. ===== I tried installing anyway and it failed: $ sudo apt-get install mondo Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mondo I checked the /etc/apt/sources.list file and at the end the following lines had been added: deb ftp://ftp.mondorescue.org//debian 7.1 contrib deb-src ftp://ftp.mondorescue.org//debian 7.1 contrib If I do uname -a I get Linux server 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2 x86_64 GNU/Linux And if I do cat /etc/debian_version it shows the version as 7.7 Am I doing something wrong, is the repository missing files, is Debian 7.7 not supported, or what? |
|
From: Gattegno, V. (G. C. / GCC) <vic...@hp...> - 2014-11-20 15:30:47
|
Hi Nick, Mondoarchive option "-I /" is not necessary, use only the -E option. > 28% done; 108:55 to go Hung or not hung? Check /var/log/mondoarchive.log: tail -f /var/log/mondorestore.log Maybe mondoarchive hangs because of a file name containing spaces, because of getfacl used by -z mondoarchive option. I created Mondorescue ticket #760, about a Mondorescue getfacl issue in mondo 3.0.4 (mondo 3.0.3 seems fine with getfacl usage): http://trac.mondorescue.org/ticket/760 Rgds, Victor -----Original Message----- From: Nikolaos Milas [mailto:nm...@no...] Sent: jeudi 20 novembre 2014 12:02 To: Mondo mailing list Subject: Re: [Mondo-devel] Mondoarchive always freezing on a particular host On 20/11/2014 12:43 μμ, Nikolaos Milas wrote: > A new run with the -z option has been initiated. I will let you know > of the results. Unfortunately, this run hung as well. It stalled at: ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- ISO 1: [**************......] 66% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 28% done; 108:55 to go (Note: The successful backup without the -z option produced 4 ISOs.) The process list at this time (when mondoarchive has hung) shows: # ps axjf PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND ---------------------------------------------------------------- ... 2449 4272 4272 4272 ? -1 Ss 0 0:01 \_ sshd: root@pts/0 4272 4274 4274 4274 pts/0 12728 Ss 0 0:00 | \_ -bash 4274 12728 12728 4274 pts/0 12728 S+ 0 0:00 | \_ -bash 12728 12839 12728 4274 pts/0 12728 Sl+ 0 1:20 | \_ /usr/sbin/mondoarchive -O -V -i -z -s 4480m -d /mnt/part1/mondo-vweb.noa.gr-2014-11-20 -I / -E /mnt/part 12839 14469 12728 4274 pts/0 12728 S+ 0 0:00 | \_ sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/acl_list.247.gz 14469 14471 12728 4274 pts/0 12728 S+ 0 0:00 | | \_ gzip -c1 12839 14470 12728 4274 pts/0 12728 S+ 0 0:00 | \_ sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/xattr_list.248.gz 14470 14472 12728 4274 pts/0 12728 S+ 0 0:00 | \_ gzip -c1 ... # ps axuwww USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND ------------------------------------------------------------------------ ... root 12839 1.9 0.0 169880 3284 pts/0 Sl+ 11:50 1:20 /usr/sbin/mondoarchive -O -V -i -z -s 4480m -d /mnt/part1/mondo-vweb.noa.gr-2014-11-20 -I / -E /mnt/part1|/datastore -9 root 14469 0.0 0.0 63844 1060 pts/0 S+ 12:42 0:00 sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/acl_list.247.gz root 14470 0.0 0.0 63844 1064 pts/0 S+ 12:42 0:00 sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/xattr_list.248.gz root 14471 0.0 0.0 4048 460 pts/0 S+ 12:42 0:00 gzip -c1 root 14472 0.0 0.0 4048 412 pts/0 S+ 12:42 0:00 gzip -c1 ... Nick ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Mondo-devel mailing list Mon...@li... https://lists.sourceforge.net/lists/listinfo/mondo-devel |
|
From: Nikolaos M. <nm...@no...> - 2014-11-20 11:02:37
|
On 20/11/2014 12:43 μμ, Nikolaos Milas wrote: > A new run with the -z option has been initiated. I will let you know > of the results. Unfortunately, this run hung as well. It stalled at: ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- ISO 1: [**************......] 66% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 28% done; 108:55 to go (Note: The successful backup without the -z option produced 4 ISOs.) The process list at this time (when mondoarchive has hung) shows: # ps axjf PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND ---------------------------------------------------------------- ... 2449 4272 4272 4272 ? -1 Ss 0 0:01 \_ sshd: root@pts/0 4272 4274 4274 4274 pts/0 12728 Ss 0 0:00 | \_ -bash 4274 12728 12728 4274 pts/0 12728 S+ 0 0:00 | \_ -bash 12728 12839 12728 4274 pts/0 12728 Sl+ 0 1:20 | \_ /usr/sbin/mondoarchive -O -V -i -z -s 4480m -d /mnt/part1/mondo-vweb.noa.gr-2014-11-20 -I / -E /mnt/part 12839 14469 12728 4274 pts/0 12728 S+ 0 0:00 | \_ sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/acl_list.247.gz 14469 14471 12728 4274 pts/0 12728 S+ 0 0:00 | | \_ gzip -c1 12839 14470 12728 4274 pts/0 12728 S+ 0 0:00 | \_ sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/xattr_list.248.gz 14470 14472 12728 4274 pts/0 12728 S+ 0 0:00 | \_ gzip -c1 ... # ps axuwww USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND ------------------------------------------------------------------------ ... root 12839 1.9 0.0 169880 3284 pts/0 Sl+ 11:50 1:20 /usr/sbin/mondoarchive -O -V -i -z -s 4480m -d /mnt/part1/mondo-vweb.noa.gr-2014-11-20 -I / -E /mnt/part1|/datastore -9 root 14469 0.0 0.0 63844 1060 pts/0 S+ 12:42 0:00 sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/acl_list.247.gz root 14470 0.0 0.0 63844 1064 pts/0 S+ 12:42 0:00 sh -c gzip -c1 > /tmp/mondo.tmp.DVfB0a/xattr_list.248.gz root 14471 0.0 0.0 4048 460 pts/0 S+ 12:42 0:00 gzip -c1 root 14472 0.0 0.0 4048 412 pts/0 S+ 12:42 0:00 gzip -c1 ... Nick |
|
From: Nikolaos M. <nm...@no...> - 2014-11-20 10:43:28
|
On 20/11/2014 10:56 πμ, Gattegno, Victor (GSD CSC / GCC) wrote: > Your version of mindi-busybox is not good for Mondorescue. Hi Victor, I was wrong in listing mindi-busybox-1.7.3-1.rhel5.x86_64.rpm. In fact, I had: # rpm -qa | grep mindi-busybox mindi-busybox-1.18.5-1.rhel5 I now upgraded to mindi-busybox-1.18.5-3.rhel5.x86_64. A new run with the -z option has been initiated. I will let you know of the results. Thanks, Nick |
|
From: Gattegno, V. (G. C. / GCC) <vic...@hp...> - 2014-11-20 08:57:46
|
Hello Nick, Your version of mindi-busybox is not good for Mondorescue. I recommend you to uninstall it, and to download and install mindi-busybox 1.18.5-3 from: ftp://ftp.mondorescue.org Check: http://trac.mondorescue.org/wiki/FAQ#Q38Whichversionsofmindiandmondoarecompatible Then you can do a mondoarchive again. Rgds, Victor -----Original Message----- From: Nikolaos Milas [mailto:nm...@no...] Sent: jeudi 20 novembre 2014 06:20 To: Mondo mailing list Subject: Re: [Mondo-devel] Mondoarchive always freezing on a particular host On 18/11/2014 9:13 μμ, Robert Grasso wrote:\ > Hope this helps, until some guru comes to the rescue ... Thank you Robert and Alan for your feedback. I have installed: mindi-2.1.7-1.rhel5.x86_64.rpm mindi-busybox-1.7.3-1.rhel5.x86_64.rpm mindi-debuginfo-2.1.7-1.rhel5.x86_64.rpm mondo-3.0.4-1.rhel5.x86_64.rpm mondo-debuginfo-3.0.4-1.rhel5.x86_64.rpm pbmkbm-0.12.6-1.rhel5.noarch.rpm perl-ProjectBuilder-0.12.6-1.rhel5.noarch.rpm project-builder-0.12.6-1.rhel5.noarch.rpm rpmbootstrap-0.12.6-1.rhel5.noarch.rpm I am running mondoarchive using cron with the following script: Newdir2=/mnt/part1/mondo-`hostname`-`date +%Y-%m-%d` mkdir $Newdir2 /usr/sbin/mondoarchive -O -V -i -z -s 4480m -d $Newdir2 -I / -E "/mnt/part1|/datastore" -9 ... I am using the -z option because on the server we are using Linux ACLs (configured with setfacl) and I want to backup those too. The kill signal was intentionally sent by me (Ctrl-C) after many hours of process hanging. I remember that in the past I used to have problems with -z option as well (I had forgotten), so I tried tonight without the -z option for a start; it worked fine! I am wondering whether the -z option will be fully fixed by the project developers any time soon. Problems with it -as you also mention- exist for long. In any case, if there is something I can do to assist the bug fixing process, I am eager to do it. Thank you for your help. All the best, Nick |
|
From: Nikolaos M. <nm...@no...> - 2014-11-20 05:20:21
|
On 18/11/2014 9:13 μμ, Robert Grasso wrote:\
> Hope this helps, until some guru comes to the rescue ...
Thank you Robert and Alan for your feedback.
I have installed:
mindi-2.1.7-1.rhel5.x86_64.rpm
mindi-busybox-1.7.3-1.rhel5.x86_64.rpm
mindi-debuginfo-2.1.7-1.rhel5.x86_64.rpm
mondo-3.0.4-1.rhel5.x86_64.rpm
mondo-debuginfo-3.0.4-1.rhel5.x86_64.rpm
pbmkbm-0.12.6-1.rhel5.noarch.rpm
perl-ProjectBuilder-0.12.6-1.rhel5.noarch.rpm
project-builder-0.12.6-1.rhel5.noarch.rpm
rpmbootstrap-0.12.6-1.rhel5.noarch.rpm
I am running mondoarchive using cron with the following script:
Newdir2=/mnt/part1/mondo-`hostname`-`date +%Y-%m-%d`
mkdir $Newdir2
/usr/sbin/mondoarchive -O -V -i -z -s 4480m -d $Newdir2 -I / -E
"/mnt/part1|/datastore" -9
...
I am using the -z option because on the server we are using Linux ACLs
(configured with setfacl) and I want to backup those too.
The kill signal was intentionally sent by me (Ctrl-C) after many hours
of process hanging.
I remember that in the past I used to have problems with -z option as
well (I had forgotten), so I tried tonight without the -z option for a
start; it worked fine!
I am wondering whether the -z option will be fully fixed by the project
developers any time soon. Problems with it -as you also mention- exist
for long. In any case, if there is something I can do to assist the bug
fixing process, I am eager to do it.
Thank you for your help.
All the best,
Nick
|
|
From: Alan P. <Ala...@pu...> - 2014-11-18 19:33:18
|
Hi,
Are you (Nick) using the -z option when executing mondoarchive ?
-z Use extended attributes and acl for each file and store
them in the backup media. Use this option if you use
SElinux e.g. but it will slow down backup and restore time
of course.
From my own personal experience, the -z option has caused me many hours of grief. Like you (Nick), the mondoarchive backup process would hang at different times for no apparent reason. Out of desperation, I started adding/removing options until I found the culprit and in my case, it was the -z.
In addition, ever after removing the -z option, mondo would still occasionally hang. To remedy that, I switched to star (replaces afio) by adding the -R option. It has helped a lot with keeping the process running.
Obviously, you'll have to install the star rpm package.
Hope this helps.
Alan
-----Original Message-----
From: Robert Grasso [mailto:rob...@mo...]
Sent: Tuesday, November 18, 2014 2:14 PM
To: Mondo mailing list
Subject: Re: [Mondo-devel] Mondoarchive always freezing on a particular host
Hi,
Well, as today there is nobody else : I am not the most qualified to
deal with your issue, please be warned.
First : can you tell us exactly what rpms you installed ? what is
necessary is : mondo, mindi, and mindi-busybox
Second : in your log, what is interesting is this (close to the end) :
SIGINT signal received from OS
You interrupted me :-)
[Main] newt-specific.c->fatal_error#329: Fatal error received -
'MondoRescue is terminating in response to a signal from the OS'
The signal was sent by the OS : can you monitor your OS logs
(/var/log/messages, etc) at the time of the crash, in order to see if
anything happened ?
Searching the Web for "MondoRescue is terminating in response to a
signal from the OS", I saw twice that a full filesystem can be the cause
of such a crash : can you make sure that you have enough space on your
destination device/directory ? Also, take care : mondo uses temporary
files : try changing the scratch dir (option -S) and the temp dir
(option -T => man mondoarchive) to a partition "large enough".
Hope this helps, until some guru comes to the rescue ...
--
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 11/17/2014 02:25 PM, Nikolaos Milas wrote:
> On 14/11/2014 10:12 μμ, Nikolaos Milas wrote:
>
>> Hi,
>>
>> I am using mondoarchive/mondorestore for years with great success and
>> I thank you for it.
>>
>> I am using it on more than 15 production CentOS 5/6 servers running as
>> VMs under KVM.
>>
>> However, recently the automatic, cron-based mondoarchive procedure on
>> one of these (CentOS 5 x86_64) VMs has stopped working properly; it
>> freezes at some point of the process (which is always different).
>>
>> Today I retried having upgraded to the latest versions of the RPMs
>> published by your project, yet the same problem reoccurred. I am
>> attaching the mondoarchive.log in a zipped file for your reference.
>>
>> Can you please help in determining the cause of the problem and
>> suggest a solution?
>>
>> I am available to provide any additional information you may request
>> to assist you in any way I can.
>>
>> Thank you in advance,
>> Nick
>>
> Anyone??
>
> Nick
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Mondo-devel mailing list
> Mon...@li...
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Mondo-devel mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/mondo-devel
|
|
From: Robert G. <rob...@mo...> - 2014-11-18 19:13:59
|
Hi, Well, as today there is nobody else : I am not the most qualified to deal with your issue, please be warned. First : can you tell us exactly what rpms you installed ? what is necessary is : mondo, mindi, and mindi-busybox Second : in your log, what is interesting is this (close to the end) : SIGINT signal received from OS You interrupted me :-) [Main] newt-specific.c->fatal_error#329: Fatal error received - 'MondoRescue is terminating in response to a signal from the OS' The signal was sent by the OS : can you monitor your OS logs (/var/log/messages, etc) at the time of the crash, in order to see if anything happened ? Searching the Web for "MondoRescue is terminating in response to a signal from the OS", I saw twice that a full filesystem can be the cause of such a crash : can you make sure that you have enough space on your destination device/directory ? Also, take care : mondo uses temporary files : try changing the scratch dir (option -S) and the temp dir (option -T => man mondoarchive) to a partition "large enough". Hope this helps, until some guru comes to the rescue ... -- 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 11/17/2014 02:25 PM, Nikolaos Milas wrote: > On 14/11/2014 10:12 μμ, Nikolaos Milas wrote: > >> Hi, >> >> I am using mondoarchive/mondorestore for years with great success and >> I thank you for it. >> >> I am using it on more than 15 production CentOS 5/6 servers running as >> VMs under KVM. >> >> However, recently the automatic, cron-based mondoarchive procedure on >> one of these (CentOS 5 x86_64) VMs has stopped working properly; it >> freezes at some point of the process (which is always different). >> >> Today I retried having upgraded to the latest versions of the RPMs >> published by your project, yet the same problem reoccurred. I am >> attaching the mondoarchive.log in a zipped file for your reference. >> >> Can you please help in determining the cause of the problem and >> suggest a solution? >> >> I am available to provide any additional information you may request >> to assist you in any way I can. >> >> Thank you in advance, >> Nick >> > Anyone?? > > Nick > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Mondo-devel mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mondo-devel |
|
From: Nikolaos M. <nm...@no...> - 2014-11-17 13:25:40
|
On 14/11/2014 10:12 μμ, Nikolaos Milas wrote: > Hi, > > I am using mondoarchive/mondorestore for years with great success and > I thank you for it. > > I am using it on more than 15 production CentOS 5/6 servers running as > VMs under KVM. > > However, recently the automatic, cron-based mondoarchive procedure on > one of these (CentOS 5 x86_64) VMs has stopped working properly; it > freezes at some point of the process (which is always different). > > Today I retried having upgraded to the latest versions of the RPMs > published by your project, yet the same problem reoccurred. I am > attaching the mondoarchive.log in a zipped file for your reference. > > Can you please help in determining the cause of the problem and > suggest a solution? > > I am available to provide any additional information you may request > to assist you in any way I can. > > Thank you in advance, > Nick > Anyone?? Nick |
|
From: Nikolaos M. <nm...@ad...> - 2014-11-17 13:13:59
|
On 14/11/2014 10:12 μμ, Nikolaos Milas wrote: > Hi, > > I am using mondoarchive/mondorestore for years with great success and > I thank you for it. > > I am using it on more than 15 production CentOS 5/6 servers running as > VMs under KVM. > > However, recently the automatic, cron-based mondoarchive procedure on > one of these (CentOS 5 x86_64) VMs has stopped working properly; it > freezes at some point of the process (which is always different). > > Today I retried having upgraded to the latest versions of the RPMs > published by your project, yet the same problem reoccurred. I am > attaching the mondoarchive.log in a zipped file for your reference. > > Can you please help in determining the cause of the problem and > suggest a solution? > > I am available to provide any additional information you may request > to assist you in any way I can. > > Thank you in advance, > Nick > Anyone?? Nick |
|
From: Nikolaos M. <nm...@no...> - 2014-11-14 20:12:48
|
Hi, I am using mondoarchive/mondorestore for years with great success and I thank you for it. I am using it on more than 15 production CentOS 5/6 servers running as VMs under KVM. However, recently the automatic, cron-based mondoarchive procedure on one of these (CentOS 5 x86_64) VMs has stopped working properly; it freezes at some point of the process (which is always different). Today I retried having upgraded to the latest versions of the RPMs published by your project, yet the same problem reoccurred. I am attaching the mondoarchive.log in a zipped file for your reference. Can you please help in determining the cause of the problem and suggest a solution? I am available to provide any additional information you may request to assist you in any way I can. Thank you in advance, Nick |
|
From: Cicone, A. <ant...@tr...> - 2014-11-14 19:55:15
|
We have new IBM blades that we are installing RHEL 6.X on. They are using the /boot/efi/EFI/redhat/grub.conf instead of the /boot/grub/grub.conf. I can create a monodarchive if I create this link. # ln -s /boot/efi/EFI/redhat/grub.conf /boot/grub/menu.lst Then specify the "-l" and "-f" option in the mondoarchive command. Since RHEL is going in the EFI direction, will this be incorporated into upcoming versions? Thanks. Anthony Cicone Midrange Technical Support T. Rowe Price * Office: (410) 345-3127 * E-mail: ant...@tr...<mailto:ant...@tr...> T. Rowe Price (including T. Rowe Price Group, Inc. and its affiliates) and its associates do not provide legal or tax advice. Any tax-related discussion contained in this e-mail, including any attachments, is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding any tax penalties or (ii) promoting, marketing, or recommending to any other party any transaction or matter addressed herein. Please consult your independent legal counsel and/or professional tax advisor regarding any legal or tax issues raised in this e-mail. The contents of this e-mail and any attachments are intended solely for the use of the named addressee(s) and may contain confidential and/or privileged information. Any unauthorized use, copying, disclosure, or distribution of the contents of this e-mail is strictly prohibited by the sender and may be unlawful. If you are not the intended recipient, please notify the sender immediately and delete this e-mail. |
|
From: Robert G. <rob...@mo...> - 2014-11-14 18:53:48
|
Hi Tom, Various thoughts : Did you make sure that the destination directory is writable ? from a terminal and from the root account, can you run this command : touch /media/"Seagate Backup Plus Drive"/Backup/master/test_file ? Your Mondo version is not brand new : your log states "Mondo Archive v2.2.9.4-r2642", and I just found this old article, mentioning your error, shown for a Mondo version close to yours mkisofs: No such file or directory. Unable to open disc image file http://permalink.gmane.org/gmane.linux.mondo.devel/12966 Would you be able to install the latest stable version for your distribution and try again ? If you got your version from your distribution repository, you should find the latest stable version on the Mondo FTP site : ftp://ftp.mondorescue.org Best regards -- 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 11/13/2014 08:10 AM, Tom Speer wrote: > I'm trying to backup my file system to a 5 Tb Seagate USB drive. > Everything seems to go well until mondorescue tries to write the first > iso. Then I get the error message "genisoimage: No such file or > directory. Unable to open disc image file". The specified path > exists, although the file itself doesn't, of course - that's what > mondorescue is supposed to create. > > I've looked through the log file (attached) and the mailing list > archives, but I am no wiser. Anybody know what's happening here? > > Cheers, > > Tom Speer > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > > _______________________________________________ > Mondo-devel mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mondo-devel |
|
From: Tom S. <ts...@or...> - 2014-11-13 08:02:26
|
I'm trying to backup my file system to a 5 Tb Seagate USB drive. Everything seems to go well until mondorescue tries to write the first iso. Then I get the error message "genisoimage: No such file or directory. Unable to open disc image file". The specified path exists, although the file itself doesn't, of course - that's what mondorescue is supposed to create. I've looked through the log file (attached) and the mailing list archives, but I am no wiser. Anybody know what's happening here? Cheers, Tom Speer |
|
From: Alan P. <Ala...@pu...> - 2014-11-11 17:13:18
|
Hi, After some trial and error, I got the backup to work. What I did was increase the EXTRA_SPACE parameter in the /etc/mindi/mindi.conf file. The value I ended at was 126976. EXTRA_SPACE=126976 # increase if you run out of ramdisk space BOOT_SIZE=262144 # size of the boot disk I don't see where the connection is between this mindi value and where it failed in the mondoarchive process where is was backing up my files, but it does work now. Hopefully this info is helpful to others. Alan -----Original Message----- From: Alan Pittman Sent: Thursday, November 06, 2014 2:29 PM To: Mondo mailing list Subject: Mondoarchive issue with Fedora20 Hi, Having issues with Mondo on Fedora20. This is what is displayed on stdout: gzip: stdout: No space left on device gzip: stdout: No space left on device ./mondo-iso.sh: line 21: 30278 Segmentation fault (core dumped) /usr/sbin/mondoarchive -O -V -i -d /mondo/iso -p $HOST -E "/mondo|/tmp|/share20|/var/log|/Win7|/var/lib/ntp/proc" -R -s 4G -M 128000 -z > /tmp/mondo.out Since I could not find a GA release for Fedora20, I download and installed the following: mondo-3.2.020141027010028-0.fc20.i686 mindi-busybox-1.21.120140703124333-0.fc20.i686 mindi-3.0.020141027010028-0.fc20.i686 perl-ProjectBuilder-0.12.6-1.fc20.noarch The interesting thing is that I'm getting the same stdout message if I use gzip or bzip2. The messages I see on the mondoarchive log are these: DBG1: [Main] newt-specific.c->fatal_error#302: Fatal error received - 'Unable to write tarball to scratchdir' DBG3: [Main] newt-specific.c->fatal_error#318: OK, I think I'm the main PID. DBG2: [Main] newt-specific.c->fatal_error#325: I'm going to do some cleaning up now. DBG4: [Main] newt-specific.c->fatal_error#326: killall mindi 2> /dev/null I am attaching the log for your review. Alan |
|
From: Alan P. <Ala...@pu...> - 2014-11-06 19:41:28
|
Hi, Having issues with Mondo on Fedora20. This is what is displayed on stdout: gzip: stdout: No space left on device gzip: stdout: No space left on device ./mondo-iso.sh: line 21: 30278 Segmentation fault (core dumped) /usr/sbin/mondoarchive -O -V -i -d /mondo/iso -p $HOST -E "/mondo|/tmp|/share20|/var/log|/Win7|/var/lib/ntp/proc" -R -s 4G -M 128000 -z > /tmp/mondo.out Since I could not find a GA release for Fedora20, I download and installed the following: mondo-3.2.020141027010028-0.fc20.i686 mindi-busybox-1.21.120140703124333-0.fc20.i686 mindi-3.0.020141027010028-0.fc20.i686 perl-ProjectBuilder-0.12.6-1.fc20.noarch The interesting thing is that I'm getting the same stdout message if I use gzip or bzip2. The messages I see on the mondoarchive log are these: DBG1: [Main] newt-specific.c->fatal_error#302: Fatal error received - 'Unable to write tarball to scratchdir' DBG3: [Main] newt-specific.c->fatal_error#318: OK, I think I'm the main PID. DBG2: [Main] newt-specific.c->fatal_error#325: I'm going to do some cleaning up now. DBG4: [Main] newt-specific.c->fatal_error#326: killall mindi 2> /dev/null I am attaching the log for your review. Alan |
|
From: John A. (PTC) <Joh...@PA...> - 2014-11-04 23:01:54
|
Bruno, thank you for your help. I edited the file /usr/lib64/mindi/analyze-my-lvm on the server I'm backing up. I made the change detailed in the changeset you pointed to below. I then ran mondoarchive again and created a new iso backup file. Using this new iso backup file I ran mondorestore on the other server. It no longer hangs during logical volume creation. However, there is still a problem with the size of the logical volumes specified in the i-want-my-lvm file. The last lvcreate command failed because there wasn't enough space left in the volume group. Mondorestore did continue and gave me the option to stop or continue when it was unable to mount one of the file systems. I was able to edit the i-want-my-lvm file to reduce the size requested and when I reran mondorestore it completed successfully. Has anything been done about getting the logical volume sizes correct so the last logical volume size requested is not bigger than the available space? John Allan . -----Original Message----- From: Bruno Cornec [mailto:Bru...@hp...] Sent: Monday, November 03, 2014 6:20 PM To: Mondo mailing list Subject: Re: [Mondo-devel] Re : Mondorestore hangs on LVM Commands Look at this changeset: http://trac.mondorescue.org/changeset?reponame=&new=3312%40branches%2F3.2%2Fmindi%2Fanalyze-my-lvm&old=3275%40branches%2F3.2%2Fmindi%2Fanalyze-my-lvm apply it to your version and let me know if that fixes your issue. Best regards, Bruno. Cornec, Bruno (Open Source and Linux Technology Strategist) said on Mon, Nov 03, 2014 at 10:12:46PM +0000: |
|
From: Bruno C. <Bru...@hp...> - 2014-11-04 02:19:47
|
Look at this changeset: http://trac.mondorescue.org/changeset?reponame=&new=3312%40branches%2F3.2%2Fmindi%2Fanalyze-my-lvm&old=3275%40branches%2F3.2%2Fmindi%2Fanalyze-my-lvm apply it to your version and let me know if that fixes your issue. Best regards, Bruno. Cornec, Bruno (Open Source and Linux Technology Strategist) said on Mon, Nov 03, 2014 at 10:12:46PM +0000: > That hang has also been recently reported by one of my hp colleagues and seems linked to a change of behaviour of the lvm commands which now needs a confirmation whereas it wasn't needed previously. I'll give you more pointers when online > > Bruno > Mobile device > > ----- Reply message ----- > De : "John Allan (PTC)" <Joh...@PA...> > Pour : "mon...@li..." <mon...@li...> > Objet : [Mondo-devel] Mondorestore hangs on LVM Commands > Date : lun., nov. 3, 2014 21:36 > > I'm looking at using mondoarchve/mondorestore to do disaster recovery for our Linux servers. They are currently running RHEL 6.6. I used yum to install mondo-3.0.4-1.rhel6.x86_64 from the mondorescue repo. As a test I ran mondoarchive on one of my test servers and created an iso file. I am now trying to restore this backup to a second, physically identical test server and have run into a problem I would like help with. > > This restore hangs when it's creating the logical volumes. This happens whether it's running automatic or interactive. When mondorestore hangs my only option is an Alt-F2 to get a command prompt. When I look at the mondorestore log file the last 2 lines in the file are: > > lvm vgchange -a y vg_ptcp002lx --> 0 > lvm lvcreate -L 51200m -r auto -n lv_root vg_ptcp002lx --> 0 > > If I run the ps command I can see these lvm process listed: > > 10301 root 9236 S sh -c lvm lvcreate -L 24186m -r auto -n lv_swap vg_p > 10302 root 25544 S lvm lvcreate -L 24186m -r auto -n lv_swap vg_ptcp002 > > When I try running the lvm commands in the i-want-my-lvm file from the command line by hand they run with no problem. I have tried changing the order and number of the lvm commands in the i-want-my-lvm file but it always hangs on the second lvm command. > > When looking for a solution for this problem I found where rounding errors for logical volume sizes have caused mondorestore to stop with errors in the past but not hang mondorestore. As a test, I doubled the size of the disk on the sever I'm trying to restore to (changed the servers OS disk array from RAID 1 to RAID 0). With the larger disk, this restore ran with no problems so this does appear to be related to disk size. However, when trying to restore to the smaller disk size I have tried reducing the size of the lvm partitions in the i-want-my-lvm file to half their original size and the restore will still hang on the second lvm command it tries to run. > > Attached are the mondorestore.log file, i-want-my-lvm file and a file with the output from the ps command. Any help you can provide will be greatly appreciated > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Mondo-devel mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mondo-devel -- 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 |
|
From: Cornec, B. (O. S. a. L. T. Strategist)
<bru...@hp...> - 2014-11-03 22:14:31
|
That hang has also been recently reported by one of my hp colleagues and seems linked to a change of behaviour of the lvm commands which now needs a confirmation whereas it wasn't needed previously. I'll give you more pointers when online Bruno Mobile device ----- Reply message ----- De : "John Allan (PTC)" <Joh...@PA...> Pour : "mon...@li..." <mon...@li...> Objet : [Mondo-devel] Mondorestore hangs on LVM Commands Date : lun., nov. 3, 2014 21:36 I'm looking at using mondoarchve/mondorestore to do disaster recovery for our Linux servers. They are currently running RHEL 6.6. I used yum to install mondo-3.0.4-1.rhel6.x86_64 from the mondorescue repo. As a test I ran mondoarchive on one of my test servers and created an iso file. I am now trying to restore this backup to a second, physically identical test server and have run into a problem I would like help with. This restore hangs when it's creating the logical volumes. This happens whether it's running automatic or interactive. When mondorestore hangs my only option is an Alt-F2 to get a command prompt. When I look at the mondorestore log file the last 2 lines in the file are: lvm vgchange -a y vg_ptcp002lx --> 0 lvm lvcreate -L 51200m -r auto -n lv_root vg_ptcp002lx --> 0 If I run the ps command I can see these lvm process listed: 10301 root 9236 S sh -c lvm lvcreate -L 24186m -r auto -n lv_swap vg_p 10302 root 25544 S lvm lvcreate -L 24186m -r auto -n lv_swap vg_ptcp002 When I try running the lvm commands in the i-want-my-lvm file from the command line by hand they run with no problem. I have tried changing the order and number of the lvm commands in the i-want-my-lvm file but it always hangs on the second lvm command. When looking for a solution for this problem I found where rounding errors for logical volume sizes have caused mondorestore to stop with errors in the past but not hang mondorestore. As a test, I doubled the size of the disk on the sever I'm trying to restore to (changed the servers OS disk array from RAID 1 to RAID 0). With the larger disk, this restore ran with no problems so this does appear to be related to disk size. However, when trying to restore to the smaller disk size I have tried reducing the size of the lvm partitions in the i-want-my-lvm file to half their original size and the restore will still hang on the second lvm command it tries to run. Attached are the mondorestore.log file, i-want-my-lvm file and a file with the output from the ps command. Any help you can provide will be greatly appreciated |
|
From: John A. (PTC) <Joh...@PA...> - 2014-11-03 20:33:58
|
I'm looking at using mondoarchve/mondorestore to do disaster recovery for our Linux servers. They are currently running RHEL 6.6. I used yum to install mondo-3.0.4-1.rhel6.x86_64 from the mondorescue repo. As a test I ran mondoarchive on one of my test servers and created an iso file. I am now trying to restore this backup to a second, physically identical test server and have run into a problem I would like help with. This restore hangs when it's creating the logical volumes. This happens whether it's running automatic or interactive. When mondorestore hangs my only option is an Alt-F2 to get a command prompt. When I look at the mondorestore log file the last 2 lines in the file are: lvm vgchange -a y vg_ptcp002lx --> 0 lvm lvcreate -L 51200m -r auto -n lv_root vg_ptcp002lx --> 0 If I run the ps command I can see these lvm process listed: 10301 root 9236 S sh -c lvm lvcreate -L 24186m -r auto -n lv_swap vg_p 10302 root 25544 S lvm lvcreate -L 24186m -r auto -n lv_swap vg_ptcp002 When I try running the lvm commands in the i-want-my-lvm file from the command line by hand they run with no problem. I have tried changing the order and number of the lvm commands in the i-want-my-lvm file but it always hangs on the second lvm command. When looking for a solution for this problem I found where rounding errors for logical volume sizes have caused mondorestore to stop with errors in the past but not hang mondorestore. As a test, I doubled the size of the disk on the sever I'm trying to restore to (changed the servers OS disk array from RAID 1 to RAID 0). With the larger disk, this restore ran with no problems so this does appear to be related to disk size. However, when trying to restore to the smaller disk size I have tried reducing the size of the lvm partitions in the i-want-my-lvm file to half their original size and the restore will still hang on the second lvm command it tries to run. Attached are the mondorestore.log file, i-want-my-lvm file and a file with the output from the ps command. Any help you can provide will be greatly appreciated |
1 message has been excluded from this view by a project administrator.