If I move hd labels, what changes? fstab, grub.conf...
What happens to an RH9 installation when the disk labels hda, hdb etc change?
When I installed RH9 on my laptop, it was on the only drive, hda.
Now I want to move that drive into a modular bay and put Win98 in the permanent bay.
By fiddling with bios I'm able to boot linux by inserting the modular drive and turning the machine on. If the modular drive is absent, Win98 boots.
But in this arrangement, the drive labels are different than they were when I installed RH9 on the linux drive. Linux seems to boot OK, but (for example) I noticed that SWAP fails to mount.
The question is, what do I need to change to make this arrangement work? Off the top of my head I suppose: fstab and grub.conf (?) . Anything else?
(Linux is using grub to select kernels. But grub doesn't know about win98.)
"The question is, what do I need to change to make this arrangement work? Off the top of my head I suppose: fstab and grub.conf (?) . Anything else?"
You got it. Just change /etc/fstab and grub.conf.
Be prepared. Create a LifeBoat CD.
Thanks, I'll give that a whirl and report back.
Thanks for your help. I've had a confusing success.
In the target configuration, my linux hd that was hda becomes (surprisingly) hdc, not hdb. I see no hdb in the RH9 hardware browser. There were some scary non-booting moments when I made changes assuming the second drive was hdb, but I was saved by a fresh boot-disk.
I now have the following working setup:
change "hda" to "hdc" in fstab, and leave "hd0" as "hd0" in grub.conf.
Grub seems to work fine. But I would have thought grub required a change from "hd0" to "hd2", which I have not tried yet due to the gut-wrenching hdb experience :) . Any thoughts? Is it dangerous to leave it as is?
BTW a Gateway Solo with two hard disks sounds like a jet ready for takeoff! ha ha
Grub doesn't count hd's like Linux, it numbers by the number of hd's, not by the number of places to put them like Linux does.
I have two drives, so in grubspeak they are hd0 and hd1.
I have the bios set to boot from the modular drive first, if it is present. Perhaps that is why grub sees it as hd0, and not hd1, even though it is in the slave position (I think).
All's well that ends well! Thanks!
Pretty close to the same thing that happened to me here:
I couldn't make heads or tails of the re-assignment but it all works and I've adjusted accordingly.
|All times are GMT -5. The time now is 09:10 AM.|