Forum Discussion

CHONG_WU's avatar
CHONG_WU
Level 5
11 years ago

rhel 6.1 BMR backup with Failed to import Config file. (1)

I run bmr backup the rhel 6.1 x86_64 client with netbackup 7.5.0.5, but failed with the following error. 1/26/2014 10:48:22 AM - Error bpbrm(pid=1860) BMRERR: Received BMR error: Failed to import Config file. (1) 1/26/2014 10:48:22 AM - Error bpbrm(pid=1860) BMRERR: Received BMR error: Failed sending the discovery. (1) 1/26/2014 10:48:22 AM - Error bpbrm(pid=1860) BMRERR: Received BMR error: BMR information discovery failed. (1) I check the bmrsavecfg -infoonly on the linux client, the error is as follows, /dev/sdf: read failed after 0 of 2048 at 0: Input/output error /dev/sdg: read failed after 0 of 2048 at 0: Input/output error /dev/sdh: read failed after 0 of 4096 at 0: Input/output error /dev/sdi: read failed after 0 of 4096 at 0: Input/output error What's the aboved error and the solution? Thanks.

7.5
Backup and Recovery
Linux
NetBackup
  • rishi_raj_gupta's avatar
    rishi_raj_gupta
    11 years ago

    As you have found out, the Fdisk command on your system is failing with return code 123.

    The error message given by Fdisk command, "This doesn't look like a partition table. Probably you selected the wrong device." is likely the cause of concern here. 

    In case your fdisk command exits with 0 return code without Multipath software configured, in that case you may try to blacklist those concerning disks during Multipath configuration. I am not too sure on this.

    However, this FDISK command failure is due to system behavior outside of NetBackup BMR due to which I may not be able to help further debug on this. You may want to determine as per your system requirement, the need for these partitions. 

    Do let us know if after system configuration corrections you face any further issue with BMR.

    Regards,

    Rishi Raj

18 Replies

Sort By
Show More
  • rishi_raj_gupta's avatar
    rishi_raj_gupta
    Level 4
    11 years ago

    As you have found out, the Fdisk command on your system is failing with return code 123.

    The error message given by Fdisk command, "This doesn't look like a partition table. Probably you selected the wrong device." is likely the cause of concern here. 

    In case your fdisk command exits with 0 return code without Multipath software configured, in that case you may try to blacklist those concerning disks during Multipath configuration. I am not too sure on this.

    However, this FDISK command failure is due to system behavior outside of NetBackup BMR due to which I may not be able to help further debug on this. You may want to determine as per your system requirement, the need for these partitions. 

    Do let us know if after system configuration corrections you face any further issue with BMR.

    Regards,

    Rishi Raj

  • CHONG_WU's avatar
    CHONG_WU
    Level 5
    11 years ago

    I found  the two partition is FAT and FAT32 file system,  but they are on uninitialized entities, what's  this? BMR support FAT file system or not?

  • rishi_raj_gupta's avatar
    rishi_raj_gupta
    Level 4
    11 years ago

    I am not too sure what you mean by uninitialized entities. In case you do not really need those two partitions due to which FDISK command is failing, then you may considering formating them fresh using fdisk command and create a valid file system that can also be mounted.

    This way your FDISK command failure could be avoided. Also, BMR doesn't current support FAT file system on LINUX, but this may not come in way of BMR if FDISK command failure is handled as mentioned above (or by any other means).

    - Rishi Raj

  • CHONG_WU's avatar
    CHONG_WU
    Level 5
    11 years ago

    From the disk utility of rhel 6.1, this two partition is on the side  of uninitialized entities. I don't know why redhat doesn't reconize them.

  • rishi_raj_gupta's avatar
    rishi_raj_gupta
    Level 4
    11 years ago

    I don't have any other specific suggestion, other than you try to get rid of those two partitions from your system which are not even recognized correctly by redhat, thereby fdisk command giving error.

    I hope you have tried formatting those two partitions and/or create a redhat recognized filesystem over those.

    - Rishi Raj

  • CHONG_WU's avatar
    CHONG_WU
    Level 5
    11 years ago
    But Dell engineer replied that don't opearate the two partition, maybe system will crash.
  • CHONG_WU's avatar
    CHONG_WU
    Level 5
    11 years ago

    What's the error code '123'? Is it  refered to 'Partition 3 does not end on cylinder boundary' or '

    This doesn't look like a partition table Probably you selected the wrong device' ?