Opened 12 years ago
Closed 12 years ago
#618 closed defect (fixed)
restored machine with RHEL 5.6 doesn't reboot after restore
| Reported by: | Bruno Cornec | Owned by: | Bruno Cornec |
|---|---|---|---|
| Priority: | highest | Milestone: | 3.0.2 |
| Component: | mondo | Version: | 3.0.1 |
| Severity: | critical | Keywords: | |
| Cc: |
Description
After reboot of the restored system, the grub boot loader is unable to load the / FS
Change History (3)
comment:1 by , 12 years ago
| Status: | new → assigned |
|---|
comment:2 by , 12 years ago
tested workaround:
After the restore, use the following to relabel your FS:
# mount-me # chroot /mnt/RESTORING # e4label /dev/cciss/c0d0p3 /
Adapt the device name to your needs as well as the label.
comment:3 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Should be fixed with rev [3008].
Cf: https://ext4.wiki.kernel.org/index.php/Ext4_Howto#For_people_who_are_running_RHEL which gives an explanation why there are different tools there.
Note:
See TracTickets
for help on using tickets.
it appears that e2label is not able anymore to label an ext4 FS with this RHEL version at least. A e4label binary exists which should probably be used instead. In that case the / FS was a ext4 FS, whereas /boot was ext3 and was no problem