Installed Fedora at home, brought drive to school, no boot...
 

I installed fedora 8 at home and spent many hours configuring it the way I like it to look and the software I installed. I then put the drive into a enclosure that my school uses for swapping our drives with their's while in class and I get the message while trying to boot:

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 or directory
switchroot: mount failed: no such file or directory

*freeze with no prompt*

I can run the rescue disc and see /dev/VolGroup00/LogVol01. It won't boot it though.

If I bring it back home, it boots fine. Just not at school, even if I remove the drive from the enclosure and directly connect it with the sata cable like I did at home.

Please let me know what more details you need and I will provide them.
I need to have this drive booted by Friday. I really don't want to spend tons of time running 'yum update' and all that stuff if I can help it.

What is the deal here?

Help!

The deal is that you did something wrong. You plug the drive in at home and it works fine? How many other drives are in the computer at home?

Using LVM is rarely a great idea unless it is really needed. But your real problem in this case could lie elsewhere. It is quite possible that your bootloader is confused because of the way it was installed. I wouldn't be surprised if attaching it directly to the cable makes the drive appear like an internal drive while using an enclosure probably makes it appear like an external one.

Yes, I'm quite well aware of that. Wasn't sure that was the purpose of forums, to find out you did something wrong, but rather, how to fix it.

No other drives in my pc at home when using the drive from school.

Yes, I agree. Except I installed Fedora on the drive at home while it was outside of the enslsosure directly connected to the SATA cable. I've tried it both ways at the school. leaving it in the enclosure, and also removing it, bypassing the enslosure inside the PC, and hooking it up directly, just like at home... same results.

It's weird to me that I can hook it up the same way and it boots fine on one pc, but not another.

Any other thoughts? Anyone?




BTW, It REALLY irritated me that my thread was moved as I really believed this to be an issue regarding GRUB, rather than Fedora. No offense to the people who read the Fedora section, but now it's in front of about 10% of the eyes I was expecting, and I need this booted by Friday. Lame.

OK So are these two computers identical hardware wise. Same SATA controller same everything. Cause if not I would not expect it to work at all. Dream Distro if I can move my boot hard drive to any computer and it works.....

The list of possible problems here are endless. Most likely it can't load b/c you have a totally different computer.

Good Luck!

No, the computers are quite different in fact.
That's kind of a bummer. I guess I'll just have to start from scratch at the school, which will take forever, 'cause their internet is also slower than mine.

There's no way to do like an lsmod (or whatever) to find out how the parition needs to be read and then just change grub.conf?

Or is all of this likely caused because I'm using an LVM?

Hi Erik765,

I just had a thought!, if both PCs have a usb port (ensure they are both using usb 2.0).
You can use a an external 2.5 removable drive and build the fedora OS to usb removable drive and move that from location to location.

I hope this is of help.

Jnike

Really good thought. I could do that. I used to have one of those infact. Rather than buy another one though, I'm actually on my way to the school right now to start over on my HDD.

Thanks for all your help guys.

E

avoid LVM in this case
 

I would avoid using LVM if it's only for a single disk - in that case it's meaningless anyway: it is meant to span multiple disks to appear as one. Obviously not what you need.

Avoiding LVM and using a traditional partition type will make moving the disk between PC's much easier (in the sense that it works).

Please note that if the disk was assigned in a 'master' (or 'slave') position within the hardware, then it must have the same role in the other PC - otherwise you should change the pin on the disk.

If you have multiple disks to deal with, then you also have to adjust /etc/fstab to mount everything properly.

Hope this helps,
Regards,
SIMP

Linux Archive