Opened 7 years ago

Closed 6 years ago

#664 closed defect (fixed)

Restore from tape OBDR not working

Reported by: teinvf Owned by: bruno
Priority: high Milestone: 3.0.4
Component: mondo Version: 3.0.2
Severity: normal Keywords: obdr, restore

Description (last modified by bruno)

Restore does not work on server HP Proliant Gen8 with an external usb tape DAT 160 using OBDR.

The server has 1 internal disk :   /dev/cciss/c0d0
and looks at several hd of a disk-array (connected via fiber channel):
[2:0:0:0]    storage HP       HSV300           1100  -
[2:0:0:1]    disk    HP       HSV300           1100  /dev/sda
[2:0:0:2]    disk    HP       HSV300           1100  /dev/sdb
[2:0:0:3]    disk    HP       HSV300           1100  /dev/sdc
[2:0:0:4]    disk    HP       HSV300           1100  /dev/sdd
[2:0:1:0]    storage HP       HSV300           1100  -
[2:0:1:1]    disk    HP       HSV300           1100  /dev/sde
[2:0:1:2]    disk    HP       HSV300           1100  /dev/sdf
[2:0:1:3]    disk    HP       HSV300           1100  /dev/sdg
[2:0:1:4]    disk    HP       HSV300           1100  /dev/sdh

When trying to restore I get the error : /dev/nst0 failed to act as extended data disk for booting.

The backup has been done with the following command:

mondoarchive  -N -O -E "/var/lib/ntp/proc|/opt/dbbackup|/opt/mondo|/opt/iso|dev/sd*" -t -o -d /dev/st0 -T /opt/mondo/tmp -S /opt/mondo/scratch

Software installed:


Please help me how to do the restore via tape.


Attachments (1)

mindi.log (258.1 KB) - added by teinvf 7 years ago.

Download all attachments as: .zip

Change History (4)

comment:1 Changed 7 years ago by teinvf

Another info that can help. On the machine there is installed xen, so the kernel is : 3.0.13-0.27-xen

On restore before getting the message: /dev/nst0 failed to act as extended data disk for booting.

I catch the message: mt: can't open /dev/nst0 device or address does not exist

Another update regarding the problem. The problem of restore seems to be how mindi makes the bootable part on the backup device. I have noticed that the bootable parte done from mindi is not well done.

So i have modified some defaults in th efollowing way.

I have modified in /usr/sbin/mindi the following: KERNEL_IS_XEN="yes" I have modfiied in /etc/mindi/mindi.conf : EXTRA_SPACE=580152 BOOT_SIZE=332768

Then I have tried to do a iso cdrom to check if mindi makes a good backup iso file. I executed: mindi and I got the following messages: .ERROR: Sorry, your kernel is too big for your image FATAL ERROR. Try to increase EXTRA_SPACE and BOOT_SIZE in /etc/mindi/mindi.conf Please e-mail a copy of /var/log/mindi.log to the mailing list. See for more information. WE CANNOT HELP unless you enclose that file. Please help me.


Last edited 7 years ago by teinvf (previous) (diff)

Changed 7 years ago by teinvf

comment:2 Changed 6 years ago by bruno

  • Description modified (diff)
  • Status changed from new to assigned

TH last error mentioned should be solved with rev [3115] which will be in mindi 2.1.6.

For the OBDR part, I'd need the mondorestore.log file generated at restore time, as well as the dmesg content in order to understand better why it's not working.

ALso please report what it gives with the latest versions (mondo 3.0.3 and mindi 2.1.5 just announced)

comment:3 Changed 6 years ago by bruno

  • Resolution set to fixed
  • Status changed from assigned to closed

BTW for the OBDR part, you probably need to use the hpsa_obdr_mode program and add it to your installation so it can work as expected. Please Cf: #358

The latest test version of mindi at should solve your problem. Reopen if that doesn't solve your issue.

Note: See TracTickets for help on using tickets.