You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by Manfred at: SF#3473424 on 2012-01-13 05:38:16 PST
Original report
Successful created ISO File with TSM-Support with rear mkbackup
boot from ISO and execute "rear recover" successfully without errors
booting restored system hangs after mounting the last mountpoint. boot does not freeze, or give some error messages. System Request keys shows the boot prozess stops by executing kjournald on last the mountpoint during mountall prozess.
There no errors from creating ISO FIle till succesfull restore.
After rebooting sometimes, the boot process does suddenly work, and the boot failure does not come any more.Very strange.
Environment:
Problem occured on Physikal Hardware and Virtual Machines (Vbox, VMware ESX)
OS: Ubuntu 10.04.03 LTS
TSM BA Client 6.2.2.5
Rear Version 1.11.0 / 2011-05-24 10:39:25 +0200
The error occurs with GRUB2 and GRUB Legacy, with using UUID and also with using PATH Devices.
I have tested so many things and have no more Ideas to solve this Problem.
Hope anyone else has some Ideas or Expirience with Rear and Ubuntu.
Cheers
Additional note by Manfred on 2012-01-13 06:03:50 PST
Please take a look at the dmesg output i added before.
Additional note by Gratien D'haese on 2012-01-31 11:37:50 PST
what kind of data does sda7 contain (ext3 type)? I find pt 5 quite strange
looks like the file system is dirty and needs a fsck, but it is journaled
file system, but still the question is why?
Additional note by Gratien D'haese on 2012-02-22 23:35:45 PST
is it possible to mail the recovery logs?
The text was updated successfully, but these errors were encountered:
Reported by Manfred at: SF#3473424 on 2012-01-13 05:38:16 PST
Original report
rear mkbackup
Environment:
Problem occured on Physikal Hardware and Virtual Machines (Vbox, VMware ESX)
OS: Ubuntu 10.04.03 LTS
TSM BA Client 6.2.2.5
Rear Version 1.11.0 / 2011-05-24 10:39:25 +0200
The error occurs with GRUB2 and GRUB Legacy, with using UUID and also with using PATH Devices.
I have tested so many things and have no more Ideas to solve this Problem.
Hope anyone else has some Ideas or Expirience with Rear and Ubuntu.
Cheers
Additional note by Manfred on 2012-01-13 06:03:50 PST
Please take a look at the dmesg output i added before.
Additional note by Gratien D'haese on 2012-01-31 11:37:50 PST
what kind of data does sda7 contain (ext3 type)? I find pt 5 quite strange
file system, but still the question is why?
Additional note by Gratien D'haese on 2012-02-22 23:35:45 PST
is it possible to mail the recovery logs?
The text was updated successfully, but these errors were encountered: