2 VG's in separated HD's
Sup folks!
I put another HD on my box to test with LVM, my primary HD is working all with LVM and a VG called vg_root. When I initialize and create a VG in the secondary HD, works well, I create a LV, perfectly...but when I reboot...donno what happens but the sistem doesnt initialize INIT, and send me a BusyBox (Debian).
And then I must mount the root LV, chroot to it and fdisk to erase the secondary HD, and reboot. Otherwise it doenst starts INIT.
Does anybody knows what's happening?
Tnx in advance!
Quoted 10 lines · Du
I put another HD on my box to test with LVM, my primary HD is working all with LVM and a VG called
vg_root. When I initialize and create a VG in the secondary HD, works well, I create a LV, perfectly...but when I reboot...donno what happens but the sistem doesnt initialize INIT, and send me a BusyBox (Debian).And then I must mount the root LV, chroot to it and fdisk to erase the secondary HD, and reboot. Otherwise it doenst starts INIT.
Does anybody knows what's happening?
what do you mean by "doenst starts INIT"? Is the kernel not found (a LILO or GRUB problem) or does "init" not find the root partition? Or was the LV-partition, you created, not found?
Are both disks connected to the same controller?
Are they IDE or SATA disks?
If you have several disk controllers on board, you may be surprised to find /dev/hda1 turning into /dev/hde1, as the sequence of your different controllers is not necessary stable, if you connect additional disks.
BTW: why do you want an new VG? Why not expanding your current VG by a new disk?
Dieter.
Quoted 11 lines · Dieter St�ken
Quoted 9 lines · Du
I put another HD on my box to test with LVM, my primary HD is working all with LVM and a VG called
vg_root. When I initialize and create a VG in the secondary HD, works well, I create a LV, perfectly...but when I reboot...donno what happens but the sistem doesnt initialize INIT, and send me a BusyBox (Debian).And then I must mount the root LV, chroot to it and fdisk to erase the secondary HD, and reboot. Otherwise it doenst starts INIT.
Quoted 7 lines
Quoted 2 lines
Does anybody knows what's happening?
what do you mean by "doenst starts INIT"? Is the kernel not found (a LILO or GRUB problem) or does "init" not find the root partition? Or was the LV-partition, you created, not found?
The 'init' in root partition wasnt found.
Quoted 2 lines
Are both disks connected to the same controller?
The 2 disks are in the same controller yes!! Is this the problem?
Quoted 2 lines
Are they IDE or SATA disks?
IDE disks
Quoted 8 lines
If you have several disk controllers on board, you may be surprised to find
/dev/hda1turning into/dev/hde1, as the sequence of your different controllers is not necessary stable, if you connect additional disks.BTW: why do you want an new VG? Why not expanding your current VG by a new disk?
Nothing but to learn, to make several tests on the second disk, that I can do errors at will :)
Quoted 18 lines
Dieter.
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/E-mail classificado pelo Identificador de Spam Inteligente Terra. Para alterar a categoria classificada, visite
http://mail.terra.com.br/protected_email/imail/imail.cgi?+_u=minicom024&_l=1,1151680591.250192.29668.arrino.hst.terra.com.br,4463,Des15,Des15Esta mensagem foi verificada pelo E-mail Protegido Terra.
Scan engine: McAfee VirusScan / Atualizado em 29/06/2006 / Vers�o: 4.4.00/4796 Proteja o seu e-mail Terra: http://mail.terra.com.br/