-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OS doesn't boot after recover #757
Comments
Hi, Try to boot system using Standard SLES11 ISO to Rescue mode, and trigger:
|
Ok, but why Rear improperly setup bootloader? |
Not sure if this is fault of ReaR ... |
The grub tries to setup a multipath device:
Is this correct? |
yes it's correct |
I think grub does not understand /dev/mapper/mpatha - perhaps it should be /dev/disk/by-id/scsi-... |
It's also worth testing with the recent snapshot version, as there were some improvements since the August version. |
it's seems to be true about grub. So we must to boot using Standard SLES11 ISO and reinstall bootloader after OS recover? there are no other options in rear to solve this issue? |
@yunsr SAN boot disks are not yet 100% fully integrated into rear. I cannot do it blindly without doing hands-on. If no-one do it for us then the community (customers) can buy time do implement this for them (remotely or on-site). |
@yunsr PS I have changed the title accordingly, if that was ok for you? |
It's not true. We havn't Boot from SAN in our case. Boot partition reside on local disk but it was named as mpath device. |
@yunsr Check your |
Could you tell pls why after recovery OS ReaR:
As solution was written script which was added to rear config with POST_RECOVERY_SCRIPT option. |
The target disk device must be a different one then the original one. That is the reason why disk migration happens and therefore a different UUID is in use. Did you executed a |
I agree with you (or when restoring to a new disk will be new UUID). |
@ypid Are your questions being answered? If yes, please close this issue. If not, tell us what is not yet clear. |
@gdha I did not open the issue 😉 |
@yunsr Are your questions being answered? If yes, please close this issue. |
I could successfully created backup (mkbackup) of OS (SUSE 11 SP3 with rear-1.17.2-1) and sent to NFS share.
My site.conf:
I'm try to recover my system and recover ended successfully.
And in next step OS didn't boot from recovered system disk! (server boots in 'Red Screen' with illegal opcode)
If you can guide me the right direction, it would be much appreciated.
Thanks
The text was updated successfully, but these errors were encountered: