(First post on forum)
My goal is to install Fedora 8 on 2.5" HD for use in an embedded PC (no CD, non standard ethernet etc...) I acquired a 2.5" to 3.5" IDE adapter, connected it to a PC, and successfully installed Fedora 8 (via Fedora Installer) on this HD from DVD. Linux now ran fine on the PC so I removed the HD and plugged it into the 'target' system.

The Fedora startup menu came up fine showing the Linux version in its menu; when in "console" mode, the following messages were displayed:

root (hd0,0)
Filesystem type is ext2fs, partition type is 0x83
kernel /vmlinuz-2.6.23-42.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[Linux-bzImage, setup=0x2c00, size=0x1e0320]
initrd /initrd-2.6.23.1-42.fc8.img
[Linux-initrd @ 0xd44d000, 0x37e037 bytes]

Uncompressing Linux .. Ok, booting the kernel
Red Hat nash version 6.0.19 starting

...
...

Reading all physical volumes. This may take a while ..
No volume groups found
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
setuproot:moving /dev failed: No such file or directory
setuproot:error mounting /proc: No such file or directory
setuproot:error mounting /sys: No such file for directory
switchroot:mount failed: No such file or directory


For some reason, the "target" cannot read the partition containing Linux ... BUT the original HD installed on the target had a functioning dual boot XP/Linux (Fedora 6) that ran fine; so I know the hardware is OK.


Am I safe with installing Linux on machine "A" and running on machine "B" by moving the HD or are there hardware dependencies (in the boot?) that would prohibit this? Possibly a (ram) loading address conflict? The target has a PC "BIOS" .. I didn't see any configuration conflicts there; I also assumed the installer's choice of partitions would be compatible.

thanks for the help ....

Okay so i think i understand what you are trying to do and i can definitly help you with that, but i need a bit more information:


1. Did you run the Fedora 8 installation on the same Hardware?

2. Did you configure Grub/lilo to compensate for the drive being a different address, meaning if you installed it as /dev/hda when you put it in the computer it is probably being detected as /dev/hdb if it is the Second IDE device?

3. Is your goal a Dual boot Environment with XP on one drive and FC8 on the other?

With this information i might able to further assist you.


-weisso

Hi weisso5, thanks for the reply. Here's the requested info ...

1. No. I didn't know how to perform Fedora 8 installation since the target has no CD/DVD drive nor supported ethernet chip (driver not in 2.6)

2. No .. still a novice; I don't know much about the boot process/configuration (yet)

3. Goal is single Linux boot .. target only has one accessible IDE connector. (In the longer term, other Linux PC's will "SSH" into this system (after ethernet driver patch done))

Great thanks for the info. BTW welcome to Linux!


1. The Fedora 8 installation process detects your hardware and install modules for those, and also installs a bootloader, so when you switch machines on it, it doesn't "know" that you have changed machines unless you "tell" it to.

2. My best suggestion then would be to follow the link below about how to install FC via Live-Cd off a USB Flash drive. This way you won't have to worry about editing things that you aren't comfortable with.

This might seem like a super difficult task, but once you read the instructions it is not that bad. Basically what you are going to do is boot off the Live CD to any machine and then use that environment to create a USB bootable live cd.

Here is a link to a good guide.
http://www.redhatmagazine.com/2007/1...nd-so-can-you/

Please let me know if you need anymore help, i will gladly assist you to the best of my knowledge

-weisso

Hi weisso5 - I'll try the USB bootable path.

I took another look at the "target" BIOS & found that its HD resides on IDE2 (vs IDE0 on PC). This may explain why the target can't see the partition. I initially hoped that a quick menu addition to grub.conf would add this new "slot" (for the target); but there appears to be more to it due to Logical/Physical drive mapping.

Anyway, thanks for your help ..