R: Re: problem with my host system

massrado at tin.it massrado at tin.it
Wed Oct 3 02:49:08 PDT 2007


Acc! My Fedora system is really crashed. The rescue CD don't find my 
sistem. I'll install a new distribution.
What do you suggest? I think 
to create two partitions (physical hard disk partitions!) and install 
my distribution on a partition and a LFS system on the other.
Didn't 
you?

Thanks 

Massimo

----Messaggio originale----
Da: 
alanslists at gmail.com
Data: 2-ott-2007 10.33 AM
A: <lfs-
support at linuxfromscratch.org>
Ogg: Re: problem with my host system

massrado at tin.it wrote:
> Hi, my name is Massimo, I'm going to install a 
LFS system next my host 
> system, a Fedora core 4 distribution.
> I 
followed the instructions by 
> LFS-book and the 
'lfs_next_to_existing_system.txt', creating a 
> directory in 
/home/LINUX_FROM_SCRATCH, mount --bind etc.
> I compiled and 
> 
installed succesfully binutils, then i unpackaged gcc and when it 
> 
finished to extract all files, exactly when it finished, a message of 
> system sayd Nautilus closed and all Desktop became empty. The system 
> was locked and I could close it only with the case's button. When I 
> restarted the PC, the boot message is:
> 
> Filesystem type is 
ext2fs, 
> partition type 0x83
> Kernel /vmlinuz-2.6.11-1.1369_FC4 ro 
> root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, 
setup=0x1e00, 
> size=0x18e473]
> Initrd /initrd-2.6.11-1.1369_FC4.img 
[Linux-initrd @ 
> 0x13e3f000, 0x1a0f24 bytes]
> Uncompressing Linux... 
Ok, booting the 
> kernel.
> ACPI:BIOS age (1999) fails cutoff (2001), 
acpi=force is 
> required to enable ACPI
> Reading all physical 
volumes. This may take a 
> while...
> Incorrect metadata area header 
checksum
> Incorrect metadata 
> area header checksum
> Incorrect 
metadata area header checksum
> Unable to 
> find volume group 
"VolGroup00"
> ERROR: /bin/lvm exited abnormally with 
> value 5 ! (pid 
335)
> Mount: error 6 mounting ext3
> ERROR opening 
> 
/dev/console!!!!: 2
> Error dup2`ing fd of 0 to 0
> Error dup2`ing fd 
of 0 
> to 1
> Error dup2`ing fd of 0 to 2
> Switchroot: mount failed: 
22
> Kernel 
> panic - not syncing: Attempted to kill init!
> 
> and 
it's locked.
> What's 
> happened?
> 
> Thank you!
> 
> Massimo

Ooooops - from the messages, I'd guess that the fedora host was using 
LVM rather than direct hard disk partitions. You *might* have just 
crashed your whole fedora system... If I were you, I'd get a rescue CD 
from somewhere (maybe the fedora one?) that supports LVM, boot from 
that 
and see what the damage is... (The LFS LiveCD is a great host 
for 
building LFS and makes a good rescue CD but I don't know if it 
supports 
LVM directly).

Your problem *could* be pretty messy to fix. 
This is one reason why I 
have never used LVM - if something goes wrong 
"underneath" the LVM layer 
(and without it's knowledge), your entire 
disk system can be toasted!

If you don't know what LVM is or what I am 
talking about, google is your 
friend.

LVM allows Linux systems to 
manage disk partitions purely in a software 
sense. You can create, 
move, resize, merge, delete partitions without 
having to touch the 
physical hard disk partition table at all. In theory 
it is a nice idea 
and lots of people use it - especially in servers 
where disk space 
needs to be managed more efficiently. But, there are 
downsides to LVM 
too:

Performance - I don't think this has ever really been proven but 
it 
seems to me if there is a software layer abstracting the hardware, 
it 
*must* use some cpu cycles over and above direct hardware access.

Reliability - if you have a failure on your hardware (disks) and your 
LVM partitions span multiple disks, just one disk failure can bring 
the 
whole thing tumbling down.

Good Luck.

Alan
-- 
The way out is 
open!
http://www.theopensourcerer.com

-- 
http://linuxfromscratch.
org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.
org/lfs/faq.html
Unsubscribe: See the above information page






More information about the lfs-support mailing list