| Fedora This forum is for the discussion of the Fedora Project. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
02-20-2007, 03:57 PM
|
#1
|
|
LQ Newbie
Registered: Sep 2006
Posts: 13
Rep:
|
Grub/LVM boot problem
Hi,
I have a problem with the grub bootloader, as follows. I have a
laptop, with an 80G disk, with Windows XP on the first half of
the disk (NTFS), and Fedora core 4 (LVM) on the rest. Dual boot
is managed by grub, installed with the Fedora install.
I wish to clone this disk, so I don't lose hours of setup/installs
on both OS's, and my work, in case of a crash. I did the following:
1) Installed Acronis 10 under Windows, and cloned the entire disk
to a 120G USB disk.
2) Restored from that clone onto a new 80G disk of the same geometry,
and replaced the existing disk with the newly cloned one.
3) On start-up, got a grub hang, so did the following: a) Boot from Fedora core 4 rescue CD
b) chroot /mnt/sysimage
c) grub-install /dev/hda
d) Enter grub
e) grub> find /grub/stage1 -> gave me (hd0,3)
f) grub> root (hd0,3)
g) grub> kernel /vmlinuz-2.6.17-1.2142_FC4 ro root=/dev/hda4
h) grub> initrd /initrd-2.6.17-1.2142_FC4.img -> gave me
"Error 16: Inconsistent filesystem structure"
i) Exit grub, repeat to step b) above, and rebuild initrd:
"mkinitrd -v -f initrd-2.6.17-1.2142_FC4.img 2.6.17-1.2142_FC4
j) Repeat from d) again, and get the same Error 16 as above. 4) Note that after step 3-c) above, I got past the grub hang, and was able
to boot Windows. But selecting the Linux installation gave me "Error 17:
Cannot mount selected partition". That's when I did the remaining steps
above.
Sorry about the long-winded explanation, but this is frustrating, and I
wanted to provide all the details, in the hope that some-one could throw
some light on the dark innards of grub vis-a-vis LVM, to resolve this.
Thanks in advance.
regards,
John
|
|
|
|
02-21-2007, 03:20 PM
|
#2
|
|
Member
Registered: Sep 2006
Distribution: Ubuntu 8.04 Hardy Heron LST
Posts: 346
Rep:
|
Boot from Fedora core 4 rescue CD
chroot /mnt/sysimage
grub
grub> find /grub/stage1
grub> root (hd0,3)
grub> setup (hd0)
grub> quit
|
|
|
|
02-21-2007, 11:44 PM
|
#3
|
|
LQ Newbie
Registered: Jan 2006
Posts: 11
Rep:
|
hi
{QUOTE=jkoshi]Hi,
a) Boot from Fedora core 4 rescue CD
b) chroot /mnt/sysimage
c) grub-install /dev/hda
d) Enter grub
e) grub> find /grub/stage1 -> gave me (hd0,3)
f) grub> root (hd0,3)
g) grub> kernel /vmlinuz-2.6.17-1.2142_FC4 ro root=/dev/hda4
h) grub> initrd /initrd-2.6.17-1.2142_FC4.img -> gave me
"Error 16: Inconsistent filesystem structure"
[/QUOTE]
As You have already mentioned your ROOT fs is LVM, the root=/dev/hda4 is the problem. Generally it is going to be something like this
root=/dev/VolGroup001/LogVol001
Where VolGroup001 is the Volume Group name & LogVol001 is the Logical Volume name. To get the correct values for your system get into rescue mode and choose automatically mount FS option. Then use the mount command to find out what you named your LVM as. The root fs would be mount on /mnt/sysimage.
The inconsistent FS error comes because you are trying to access the partition rather than the LVM.

|
|
|
|
02-27-2007, 12:55 PM
|
#4
|
|
LQ Newbie
Registered: Sep 2006
Posts: 13
Original Poster
Rep:
|
Quote:
|
Originally Posted by Duck2006
Boot from Fedora core 4 rescue CD
chroot /mnt/sysimage
grub
grub> find /grub/stage1
grub> root (hd0,3)
grub> setup (hd0)
grub> quit
|
Hi Duck2006,
Thanks for your feedback.
Tried this, too, with the same result.
John
|
|
|
|
02-27-2007, 01:05 PM
|
#5
|
|
LQ Newbie
Registered: Sep 2006
Posts: 13
Original Poster
Rep:
|
Quote:
|
Originally Posted by sai_kiran
As You have already mentioned your ROOT fs is LVM, the root=/dev/hda4 is the problem. Generally it is going to be something like this
root=/dev/VolGroup001/LogVol001
Where VolGroup001 is the Volume Group name & LogVol001 is the Logical Volume name. To get the correct values for your .....
|
sai_kiran,
Thanks for your reply.
I did try "root=/dev/VolGroup00/LogVol00", and "root=/LABEL=/",
in place of "root=/dev/hda4" on the "kernel" line, but got the
same result.
However, you mentione Group and Volume 001, rather than 00.
What is the reason for this?
John
|
|
|
|
02-27-2007, 11:37 PM
|
#6
|
|
LQ Newbie
Registered: Jan 2006
Posts: 11
Rep:
|
Quote:
|
Originally Posted by jkoshi
However, you mentione Group and Volume 001, rather than 00.
What is the reason for this?
John
|
John,
What i gave is an approximate value. Generally in RHEL swap is also created as a the first Logical Volume, So the root vol comes to be the second. You have to find the correct values by going into the Rescue environment. During Installation the VG & LV names can be changed from default values. So check and use the correct values.
|
|
|
|
02-28-2007, 10:48 AM
|
#7
|
|
LQ Newbie
Registered: Sep 2006
Posts: 13
Original Poster
Rep:
|
Follow-up on grub dual-boot problem
Hi everyone, any ideas on a solution to the problem below?
Quote:
|
Originally Posted by jkoshi
Hi,
I have a problem with the grub bootloader, as follows. I have a
laptop, with an 80G disk, with Windows XP on the first half of
the disk (NTFS), and Fedora core 4 (LVM) on the rest. Dual boot
is managed by grub, installed with the Fedora install.
I wish to clone this disk, so I don't lose hours of setup/installs
on both OS's, and my work, in case of a crash. I did the following:
1) Installed Acronis 10 under Windows, and cloned the entire disk
to a 120G USB disk.
2) Restored from that clone onto a new 80G disk of the same geometry,
and replaced the existing disk with the newly cloned one.
3) On start-up, got a grub hang, so did the following: a) Boot from Fedora core 4 rescue CD
b) chroot /mnt/sysimage
c) grub-install /dev/hda
d) Enter grub
e) grub> find /grub/stage1 -> gave me (hd0,3)
f) grub> root (hd0,3)
g) grub> kernel /vmlinuz-2.6.17-1.2142_FC4 ro root=/dev/hda4
h) grub> initrd /initrd-2.6.17-1.2142_FC4.img -> gave me
"Error 16: Inconsistent filesystem structure"
i) Exit grub, repeat to step b) above, and rebuild initrd:
"mkinitrd -v -f initrd-2.6.17-1.2142_FC4.img 2.6.17-1.2142_FC4
j) Repeat from d) again, and get the same Error 16 as above. 4) Note that after step 3-c) above, I got past the grub hang, and was able
to boot Windows. But selecting the Linux installation gave me "Error 17:
Cannot mount selected partition". That's when I did the remaining steps
above.
Sorry about the long-winded explanation, but this is frustrating, and I
wanted to provide all the details, in the hope that some-one could throw
some light on the dark innards of grub vis-a-vis LVM, to resolve this.
Thanks in advance.
regards,
John
|
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 07:20 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|