Opened 12 years ago

Closed 12 years ago

#587 closed defect (fixed)

Mondo 3.0 issues

Reported by: bgunda Owned by: Bruno Cornec
Priority: highest Milestone: 3.0.3
Component: mondo Version: 3.0.0
Severity: normal Keywords: Kernel Panic


Very many thanks for create Mondorescue. It is truly a rescuer for me all these years.

But recently, I started facing some issues-

  1. I have upgraded our servers from RHEL 5.6 to 5.7.
  2. I have also upgraded Mondo from 2.2.x to 3.x & Mindi along with it.
  3. I used Mondo 3.0 to take a RHEL 5.7 image and trying to restore on a brand new server.
  4. I get the error while partitioning using LVM. It is a local disk and it looks ‘mondo’ is not calculating the sizes properly.
  5. I checked up the mailing lists and found the problem reported as Defect #577 and saw the solution also.
  6. I downloaded mondo-3.0.1-0.20120203024439.rhel5.x86_64.rpm & mindi-2.1.1-0.20120203024439.rhel5.x86_64.rpm

As per your fix in #577.

  1. But now I have another problem. It does not go further while restoring. It says "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)" and stops

  1. I did the following combinations –
  2. RHEL 5.6 & Older version of Mondo (prior to 3.0) – Works great
  3. RHEL 5.7 & Mondo 3.0 – Gives Partition issues (# 577)
  4. RHEL 5.6 or 5.7 & Mondo – 3.0.1 (test download) – Crashes with Kernel issues (as described in # 575, but I have mindi-busybox at 1.18 (latest)).
  5. So, I am stuck right now. Can you check and let me know what is happening?

Again thank you very much for providing the support.

Change History (9)

comment:1 by Bruno Cornec, 12 years ago

The only way to be support is to follow recommendations on the support page of our web site, and provide log files, and context (here the panic info)

comment:2 by bgunda, 12 years ago

I tried everything you have given on the Support page. But I am not able to resolve the issue. Regarding providing logs, the problem I am getting is during NUKE of new machine from the image. It is not going any further and crashing with Kernel panic. So, there are no log files generated.

comment:3 by Bruno Cornec, 12 years ago

The kernel panic could be due to the load of a kernel module not appropriate at restore time. Can you at least take a picture of what is displayed on the screen, so I can guess which driver could be involved ?

You can then use denymods to disable it at boot prompt at restore time. Maybe fdomain ?

comment:4 by Bruno Cornec, 12 years ago

Owner: changed from Bhaskar to Bruno Cornec
Status: newassigned

comment:5 by Bruno Cornec, 12 years ago

Any feedback on this ?

in reply to:  5 comment:6 by bgunda, 12 years ago

Replying to bruno:

Any feedback on this ?

Hello Mr.Bruno,

Thanks for the follow up. The systems I was working on were built completely taking image in a different way (using Hardware Mirroring of OS disks), which is not our preferable method anyway. I am trying to find some resources in our Lab to test this and send you the required output. As soon as I get our lab systems, I will simulate the problem and send an update.

-- Bhaskar

comment:7 by Bruno Cornec, 12 years ago


comment:8 by bgunda, 12 years ago

Hello Bruno,

Thanks for the new release of 3.0.2. I was testing the Beta release of 3.0.2 for sometime and every combination test I have done was successful. I have also downloaded GA release of 3.0.2 and tested thoroughly and everything works great now.

Thank you so much for your continued effort and helping the community. Truly, it was great effort and we really appreciate it.

-- Bhaskar

comment:9 by bgunda, 12 years ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.